Tripline

Excluded by ‘noindex’ tag

Google says your page is excluded by a noindex tag.

A noindex tells search engines to leave a page out of results. Often nobody added it on purpose: it came from a setting, a plugin or a header you can't see in the page. Find out where yours is.

Free, with no sign-up. Takes a few seconds.

What it means

Google read the page and found an instruction not to index it, so it was dropped from search results. The page still loads for visitors, which is why this can go unnoticed for weeks.

The instruction can sit in two places: a <meta name="robots" content="noindex"> tag (or name="googlebot") in the page's head, or an X-Robots-Tag: noindex header in the server's response. The header never appears in the page source, so viewing source can show nothing wrong.

Why it happens

Settings › Reading☑ Discourage search engines
from indexing this site

A site-wide CMS setting

WordPress and other CMSs have a single switch that adds noindex to every page. It is often ticked during a build and never unticked.

Response headerx-robots-tag: noindex

A header from the server

Added by server config, a CDN rule or a hosting platform's preview setting. Invisible in the page source.

SEO plugin, this pageShow in search results? No

One page's toggle

Per-page switches in SEO plugins are easy to flip on the wrong page or carry over when a page is duplicated.

Template<meta name="robots" content="noindex">

A staging template that went live

A layout written for staging, or a build that reads the wrong environment, ships noindex on every page that uses it.

How to fix it

  1. Find which kind it is.

    Run the check above: it reads both the page's meta tags and the X-Robots-Tag header and says which one it found. From a terminal, curl -sI https://yoursite.com/page shows the headers.

  2. Remove it where it starts.

    Untick the CMS setting, change the SEO plugin's per-page switch, fix the template, or remove the header rule in your server, CDN or hosting settings. Editing the page alone won't help if the header comes from elsewhere.

  3. Clear caches.

    A CDN or page cache can keep serving the old page with the tag for hours. Purge it, then check again.

  4. Make sure Google can read the page.

    If robots.txt also blocks the page, Google can't fetch it to see the noindex has gone. Remove the block too.

  5. Ask Google to look again.

    In Search Console, use URL Inspection and Request indexing, or press Validate fix on the report. Pages usually return within days to a few weeks.

Common questions

I can't see a noindex tag in the page source. Where is it?

Most likely in the X-Robots-Tag response header, which the source never shows. It can also be added by JavaScript after the page loads. This check reads the header and the delivered HTML.

Is noindex ever right?

Yes, for pages you don't want in search: thank-you pages, internal search results, account pages. Only remove it from pages that should rank.

Should I block the page in robots.txt as well?

No. If Google can't fetch the page, it can't see the noindex, and the address may still be listed. Use one or the other: noindex to keep a page out of results.

How long until the page is back in Google?

It depends on how often Google crawls your site, from a few days to several weeks. Requesting indexing in Search Console can speed it up.

Other fixes