5

Some of the network sites have names like Seasoned Advice which don't inherently represent their content. I was trying to remember the name for the 'Cooking Stack Exchange' and couldn't find it by searching for cooking, kitchen or food.

I think this quickly becomes frustrating on mobile.

My suggestion is to add some keywords that aren't displayed but are indexed in addition to the name and description of each network site.

Some more examples:

  • linux doesn't list the Ubuntu site
  • arcade doesn't return the Arqade site
  • bike doesn't return the Bicycles site
  • It must do this a little already. Searching 'Cooking' returns Seasoned Advice for me, and 'Gaming' returns Arqade, 'Cycling' for Bicycles etc.. but maybe it's restricted to 1 key word describing the action – OGHaza Feb 13 '14 at 13:03
  • 1
    They already added the search to include the subdomains, but it could be better indeed. – 3ventic Feb 13 '14 at 13:05
  • The tagline in the tour is "Seasoned Advice is a site for professional and amateur cooks and chefs" @OGHaza... I suspect that's why cooking gets it. Though, strangely "cooks" doesn't. – ben is uǝq backwards Feb 13 '14 at 13:05
  • The tagline in Seasoned Advice for me is "professional and amateur chefs", so it doesn't appear for search terms cooks or cooking on my iPhone. – David Snabel-Caunt Feb 13 '14 at 13:06
  • The tagline in the search box doesn't show the "cooks and chefs", but searching for cooking does work on desktop (no idea why cooks wouldn't) - based on the searches that return 'Bicylces' (cycling, commute, repairs) it does indeed seem to be matching against the tag line like @ben says. – OGHaza Feb 13 '14 at 13:11
  • @OGHaza I'm pretty sure it only searches the name and audience fields of the data returned by the API. Again, searching for cooking DOES NOT return any results on the iOS app. – David Snabel-Caunt Feb 13 '14 at 13:16
4

Yep, the bigger blacker bar is checking the site URL and we weren't. Fixed in the next build. That fixes Seasoned Advice. The other stuff is a more general issue with the data available. We're realistically not going to do more than the bar can do.

Fixed in the next build.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .