By Rahul Saini, Author at Search Counsel Co. Last updated [JULY] 2026.

1) The two kinds of indexing problem

Every indexing problem is one of two things, and telling them apart saves you hours. Either Google can’t find your page, or Google found it and decided not to index it. The fix is completely different for each.

• Discoverability problems. Google never gets to the page because nothing points it there: no internal links, no sitemap entry, no external links. Orphan pages are the classic example.
• Indexing-decision problems. Google reaches the page fine but chooses to leave it out, usually over quality or duplication, or because a noindex tag tells it to.

One important boundary: this guide is about pages Google can reach but won’t index. If a page is throwing a 404, a server error, or is blocked in robots.txt, that’s a fetch failure, and it belongs in our guide to finding and fixing crawl errors. Here we’re dealing with pages that load fine and still don’t make it in. For how crawling, rendering, and indexing fit together, see the technical SEO pillar.

One more thing worth saying: not every page needs to be indexed. Thank-you pages, internal search results, filtered category views, and thin tag archives are often better left out. Some “not indexed” is healthy. The goal is to make sure the pages you care about get in, not to force every URL into the index.

2) “Discovered” vs “Crawled, currently not indexed”

These two statuses in the Pages report cause more confusion than anything else in Search Console, because they look alike and mean different things. The difference comes down to one question: has Google actually crawled the page yet?

“Discovered, currently not indexed” is often about crawl timing rather than the page itself. Google knows the URL but hasn’t fetched it, sometimes because it rescheduled the crawl to avoid overloading a slow server, sometimes because the page or the whole site is low crawl priority. Because Google hasn’t read the page, it guesses at quality based on similar URLs and your site’s overall reputation. On a handful of low-value URLs this is normal, and Google may come back on its own. When it hits important pages, the levers are internal links, sitemap quality, server speed, and reducing duplicate URLs, which overlaps with crawl budget on larger sites.

“Crawled, currently not indexed” is a stronger signal, because Google did read the page and still passed. It’s not a penalty. It means Google didn’t see enough value to justify a spot in the index. The usual causes are thin content, near-duplicate content, weak internal linking (a page Google can only reach through the sitemap reads as less important), or a stronger competing page. Fix the underlying value: make the page more useful, link to it from related indexed pages, and consolidate anything duplicative. Then, and only then, request indexing. Requesting it without real changes rarely helps and can delay Google’s reassessment.

3) Rogue noindex tags

A rogue noindex is the most annoying indexing problem, because the page is fine, the content is good, and one line of code is quietly telling Google to stay away. In the Pages report this shows up as “Excluded by noindex tag.” The page still gets crawled, so Google can see the directive, and then it’s dropped from the index.

Two places to check, because the directive can live in either:

• The meta robots tag in the page’s HTML head: <meta name=”robots” content=”noindex”>.
• The X-Robots-Tag in the HTTP response header, which you won’t see in the page source at all.

The usual culprits are predictable. A staging or development setting copied to production. A CMS toggle left on, like WordPress’s “Discourage search engines from indexing this site” checkbox, or a noindex switch in an SEO plugin. A page template that applies noindex site-wide by mistake. To find every instance fast, crawl the site with a tool like Screaming Frog and check its Noindex filter, which catches both the meta tag and the header. You can also confirm any single URL with the URL Inspection tool, which tells you plainly whether indexing is allowed. The fix is simple once you find it: remove the noindex from any page that should be indexed, and check both the HTML and the HTTP header so you don’t miss one.

4) Orphan pages

An orphan page is a page with no internal links pointing to it. Since crawlers discover content mainly by following links, an orphan is hard for Google to find and easy to treat as unimportant even when it does. Orphans usually appear after a redesign or migration, when pages get moved or renamed without updating the links, or from out-of-stock products and old campaign pages that were never unlinked.

Here’s the catch that trips people up: Search Console has no orphan-pages report. It only reports on URLs Google already knows about, so a page with no links and no sitemap entry never shows up anywhere in it. To find orphans, you crawl your own site and compare what the crawl reaches against other sources that list your URLs.

The reliable method uses a crawler like Screaming Frog or Sitebulb (which calls them “isolated URLs”):

• 1. Crawl the site from the homepage, which maps every page reachable through internal links.
• 2. Feed in extra URL sources: your XML sitemap, and Google Search Console and Analytics data through their APIs.
• 3. Run the crawl analysis and open the orphan URLs filter. Any URL that a source knows about but the internal-link crawl never reached is an orphan.
• 4. Check each one’s status code and value before acting, since some “orphans” turn out to be already-redirected or dead URLs.

Fixing an orphan depends on what it is. If it’s valuable and you want it found, add internal links to it from related pages (and make sure it’s in your sitemap). If it’s been replaced, 301-redirect it to the new version. If it’s intentional, like a PPC landing page or a thank-you page you don’t want in search, add a noindex tag so it stays out of results. And if it has no value at all, delete it, return a 404 or 410, and remove it from the sitemap. Strong internal linking is the real prevention here, which is why we cover it in depth in our guide to site architecture and internal linking.

5) Other “not indexed” statuses worth knowing

A few more statuses in the Pages report relate to indexing, and most of them are not problems at all:

• Duplicate without user-selected canonical. Google found near-identical pages and picked a canonical for you because you didn’t specify one. Fix it by setting a clear canonical tag on the version you prefer.
• Duplicate, Google chose different canonical than user. You set a canonical, but Google overrode it because it judged a different URL to be the better version. Make your preferred page clearly the strongest, and check your canonical and internal links point to it consistently. Both of these live alongside our full guide to canonical tags and duplicate content.
• Alternate page with proper canonical tag, and Page with redirect. These are usually fine. Google is correctly following your canonical or redirect to the right page, and no action is needed.

6) How to diagnose any indexing problem

When a specific page won’t index, work it in this order:

• 1. Inspect the URL. Paste it into the URL Inspection tool at the top of Search Console. It tells you whether the page is on Google, why not, whether indexing is allowed, and which canonical Google chose. This one step answers most questions.
• 2. Do a quick site check. Search site:yourdomain.com/the-page-url in Google. If nothing comes back, the page isn’t indexed.
• 3. Read the status. Match what the Pages report or URL Inspection says to the sections above, so you know whether you’re looking at a discoverability problem, a quality decision, or a noindex.
• 4. Crawl for the invisible ones. For orphans and site-wide noindex issues, crawl the site with Screaming Frog or Sitebulb, because those problems don’t surface in Search Console on their own.

7) How to get a page indexed

Once you know the cause, getting a page indexed is mostly about making it worth indexing and easy to find. In practice:

• Make sure it’s indexable. No noindex tag, not blocked in robots.txt, canonical pointing to itself (or intentionally elsewhere), returning a 200 status.
• Link to it. Add internal links from relevant, already-indexed pages. This is the highest-impact fix for both discoverability and perceived value.
• Make it truly useful. Depth, originality, and clear intent match are what move a page over Google’s indexing threshold. Thin pages get skipped.
• Put it in a clean sitemap. Include it, along with only other canonical, indexable, 200-status URLs.
• Request indexing, once. Use URL Inspection to request indexing after you’ve made real changes. Don’t spam the button; repeated requests without improvements won’t speed things up and can slow reassessment.

Then be patient. Indexing can take anywhere from hours to weeks, and it’s normal for a healthy page to sit for a while before Google picks it up.

8) Why indexing problems also block AI answers

Getting indexed isn’t only about Google’s blue links anymore. It’s the entry ticket to AI answers too. A page that isn’t in Google’s index can’t appear in Google’s AI Overviews, and the same logic extends to other AI engines: a noindex tag blocks the crawlers behind ChatGPT and Perplexity, not just Googlebot, so a non-indexable page is ineligible for citation across the board.

Discoverability matters just as much on the AI side. AI retrieval bots build their own indexes and, like Google, they discover pages by following links and reading sitemaps. An orphan page that Google struggles to find is a page AI engines struggle to find too. So the work in this guide, clean internal linking, no rogue noindex tags, useful pages, pays off on both surfaces at once. Our AI search optimization guide and the AI-readiness section of the technical SEO pillar go deeper on the AI side.

9) Sources used for this guide

This guide draws on Google’s own indexing documentation and the established behavior of standard crawler tools, rather than secondhand claims.

FAQ: indexing problems

Conclusion: get the right pages in, on both surfaces

Indexing problems feel mysterious until you split them in two. Either Google can’t find the page, which is a linking and sitemap job, or it found the page and won’t index it, which is a quality and duplication job. Add a rogue noindex tag as the third suspect, and you can diagnose almost any “why isn’t this indexed” case from the URL Inspection tool. Fix the pages that matter, leave the ones that don’t, and you clear the path to both Google’s results and AI answers at once.

That completes the crawling and indexing side of technical SEO. The next questions are whether Google can actually see your content once it arrives, and whether your site is built to be crawled efficiently in the first place. Those are covered under the technical SEO pillar, alongside our guides to crawl errors and crawl budget.