Why Is My Page Not Indexed? A Diagnostic Order

Why is my page not indexed?

A page that is not indexed has been told not to be, has never been reached, or was judged not worth keeping. Those are three different problems. Work through them in this order and stop when you find the cause.

Reads robots.txt, meta robots, the X-Robots-Tag header, the canonical and the sitemap for your site, from outside your network. Nothing is stored.

Before anything else, search for the exact URL rather than a phrase from the page. If the URL matches a different page you own, you have a duplicate or canonical problem, not an indexing problem. If nothing matches, keep going.

1. Is it blocked from being crawled?

robots.txt controls crawling, not indexing, but it comes first because a blocked page cannot deliver any of the other signals. A Disallow rule that matches the path, whether you intended it or not, stops the crawler before it sees the page at all.

2. Is it marked noindex?

There are two places noindex hides: a meta robots tag in the HTML and an X-Robots-Tag response header. The header is the one people miss, because it is not in the page source and is often set at a CDN or proxy that was configured for staging. A noindex only works if the page can still be crawled, which is why steps one and two are separate.

3. Does the canonical point somewhere else?

If the canonical on the page names a different URL, you have told search engines which version to index, and it is not this one. That is correct for a genuine duplicate and wrong when a plugin or tag is adding a canonical you did not intend.

4. What status does the URL actually return?

A 404 or 410 cannot be indexed. A redirect means you should be looking at the destination. A 200 that renders an empty or error message is a soft 404 and is treated as thin content even though the status says success.

5. Can anything reach it?

A page with no internal links is an orphan. Crawlers find it far less often, and it collects no internal authority, so even a good page underperforms. A page in the sitemap but linked from nowhere is a common form of this.

6. Is it in the sitemap, and is the sitemap healthy?

The sitemap is a hint, not a command, but it is the clearest signal you can send that a URL is worth fetching. A sitemap that 404s or lists dead URLs sends the opposite message.

Every Search Console “why pages aren’t indexed” status, with its fix

The Pages report in Search Console names the reason for each excluded URL. Each status below has its own guide: what it means, whether it needs fixing at all, and the steps on Shopify, WooCommerce and other platforms.

The tool that checks all six at once

The indexing check reads robots.txt, the meta robots tag, the X-Robots-Tag header, the canonical, the response status and the sitemap for one URL, from outside your network, and reports which of the six is the reason.

Related explainers

Questions

Does a robots.txt block remove a page from search?

It stops crawling, not indexing directly. A blocked URL can still be indexed from links alone, without a snippet. If you want it out of search, allow crawling and use noindex.

How long does indexing take after a fix?

Days to weeks. A fixed page still shows the old status in Search Console until it is recrawled, so use the URL inspection request or resubmit the sitemap.

Can a page be indexed without being in the sitemap?

Yes. The sitemap is a hint and not required. Links and Search Console submissions also lead crawlers to pages.

What is a soft 404?

A URL that returns 200 but has no useful content, often a removed product shown as a blank template or an empty category. Search engines treat it as thin.