Lorixen.
EN

Should your site's search results pages be indexed?

Short answer: In almost every case, your website's internal search results pages (URLs like /search?q=boots or /?s=plumbing) shouldn't be indexed. They're endless, thin and duplicate your real pages; the cleanest approach for a site that's not yet affected is to block them from crawling in robots.txt. If some are already indexed, use noindex first and let Google see it before blocking. If a particular search is valuable, build a proper category or landing page for it instead of letting a search URL rank.

Site search is useful for visitors. The pages it produces are a different matter: any word anyone types creates a new URL, and if those URLs get crawled, Google can spend time on thousands of near-empty or repetitive pages. Some sites find odd search pages showing up in Google, sometimes with spammy queries in the URL. The decision path below sorts out what to do.

Check two things:

  • Does your site link to search result URLs? For example, "popular searches" links, tag clouds that point to search, or pagination inside results.
  • Are any indexed? Search Google for site:yourdomain.com.au inurl:search or inurl:?s= (WordPress uses ?s=).

No links, nothing indexed → go to Question 2.

Already indexed → go to Question 3.

Question 2: Not indexed yet: block crawling with robots.txt

If no search URLs are indexed, blocking them from crawling is the simplest, most efficient option.

Google's crawl budget documentation gives the reasoning. It recommends blocking pages that are useful to users but that you don't want on Google, giving examples such as differently sorted versions of the same page, using robots.txt. It explains that blocking with robots.txt prevents crawling and significantly reduces the chance the URLs get processed by other Google systems, including indexing. It also advises against using noindex for this purpose, because Google still requests the page before dropping it, which wastes crawling time.

A typical rule, adjusted to your site's actual search path:

User-agent: * Disallow: /search Disallow: /*?s=

Check the path your site uses first. Blocking too broadly, such as a pattern that also matches product or blog URLs, is a common mistake. Test a few real URLs against the rules before saving.

Google's faceted navigation guidance takes a similar line for filter URLs: there's often no good reason to allow crawling of filtered results, and crawling just the individual item pages plus a listing page without filters is usually enough. Site search results are an even more extreme version of the same problem.

Question 3: Already indexed: noindex first, then block

If search URLs are already in Google's index, blocking them in robots.txt immediately can backfire. Google's documentation on noindex is explicit: for noindex to work, the page must not be blocked by robots.txt and must be accessible to the crawler; if robots.txt blocks it, the crawler never sees the noindex rule, and the page can still appear in results if other pages link to it.

So the order is:

  1. Add noindex to search results pages. Many CMSs and SEO plugins have a setting for this; otherwise a developer can add a noindex robots meta tag or an X-Robots-Tag header to the search template.
  2. Wait for Google to recrawl and drop the pages. Check progress with site: searches and the Page indexing report.
  3. Then add the robots.txt block, if you want to stop the crawling entirely.

If the indexed search URLs are spammy (strange queries in the URL), also check why they exist: other sites may be linking to them. Making sure your search pages don't display the query text prominently, or return a sensible "no results" page, reduces their usefulness to spammers.

Question 4: Does any search represent real, lasting demand?

Look at your internal search data: in your analytics or the site search tool's reports, which terms come up again and again?

Yes, some searches are frequent and meaningful (e.g. "gluten free", "school shoes", "emergency plumber") → go to Question 5.

No → stick with Questions 2 or 3. You're done.

Question 5: Build a real page for valuable searches

Instead of letting /search?q=school+shoes rank, create a proper page:

  • a category or collection page ("School shoes") with a stable URL, a clear heading, a short introduction and curated products;
  • or a landing page for a service ("Emergency plumbing in the inner west") with real information, not just a list.

Link to it from your navigation or related pages, and include it in your sitemap. These pages can rank on their own merits, and they're far better for visitors arriving from Google than a raw search result list.

A worked example (hypothetical)

A Melbourne homewares shop notices URLs like /search?q=linen+throw and a few with nonsense queries appearing in Google. Its search template has no robots meta tag, and robots.txt allows everything. Following the path above, it adds noindex to the search template, waits several weeks while the indexed search URLs drop out, and then adds a Disallow rule for the search path. Its site search reports show "linen throws" is a frequent query, so it also creates a proper "Linen throws" collection page and links it from the bedroom category. Visitors from Google now land on a curated page rather than a raw list.

Things to avoid

  • Linking to search results from site-wide navigation. It invites crawlers into an endless space.
  • Blocking with robots.txt and expecting already-indexed pages to vanish. Without a visible noindex, they may linger.
  • Noindexing everything with a query string. Some legitimate pages may use parameters; target the search path specifically.
  • Search URLs in your XML sitemap. Some plugins add them by accident; check.

FAQ

Does WordPress noindex search pages by default?

Behaviour depends on your theme and SEO plugin. Check the source of a search results page for a robots meta tag, and your robots.txt, rather than assuming.

Will blocking search pages hurt my site?

No. Visitors can still use search normally; you're only telling crawlers not to fetch those pages.

Should I block search pages if my site is small?

It's still sensible. A small site gains nothing from search URLs being crawled, and blocking prevents future problems.

What about filtered category pages?

They're a related but separate decision. Google's faceted navigation guidance covers them; often you'll allow a few useful filtered pages and block the rest.

If you've found your site's search URLs turning up in Google, send us a couple of examples and we'll suggest the right mix of noindex, robots.txt and proper landing pages.

Sources

WhatsAppLet’s talk