Here's the most ignored sentence in all of SEO: you cannot rank a page that isn't indexed. Doesn't matter how brilliant the copy is, how many keywords you nailed, how perfect the schema. If Googlebot has looked at it and walked away, all of it counts for zero.
And the truth is that for a lot of sites, a big chunk of pages never make it in. They sit in Search Console with a status that reads like an excuse: "Discovered currently not indexed." This guide is the diagnostic order we actually use with clients — the sequence that resolves more indexation problems than any single "fix," and the habits that keep the problem from recurring.
Understand what "not indexed" actually means
That status doesn't mean Google hasn't seen your page. It means Google has found the URL and decided, at least for now, that it isn't worth indexing. That's the important reframe: indexing is a judgment call, and usually a correct one. Your job is to give Google a reason to reverse it.
The related statuses tell you which stage the judgment failed at:
- "Crawled — currently not indexed" — Googlebot fetched the page, read it, and declined. This is usually a content-quality or duplicate-content call.
- "Discovered — currently not indexed" — Google knows the URL exists (from a sitemap or a link) but hasn't crawled it yet. This is a crawl-priority call, and it's where most "why won't my new pages index" complaints actually start.
- "Excluded by noindex" — there's a directive, deliberate or accidental, telling Google to stay away, and the noindex audit is its own diagnosis. Different problem entirely.
- "Blocked by robots.txt" — the crawler was told it can't even look. Also fixable, also different.
Each status is a diagnosis with its own medicine. Treating "not indexed" as one problem is how teams spend months "requesting indexing" on pages whose real problem is a crawl-priority judgment they never addressed.
The diagnostic order we use
This is the exact checklist our technical SEO engineering team runs when a client says "my page won't index."
When a page won't index, we work through these in order. Maybe that sounds obvious, but the order matters — most people jump to the glamorous fix and skip the boring one that's actually causing it.
1. Can Google reach it at all? Search the exact URL. If it shows as "Discovered" but never "Crawled," check for a blocked robots directive, a nofollow, or a page that only loads via a script Googlebot isn't executing — the JavaScript render problem in its native habitat. Fix the access before anything else. A page that requires a JavaScript click before content exists is an indexing problem wearing a rendering problem's suit.
2. Is it orphaned? This is the #1 fix. If nothing links to the page — no internal links, no sitemap entry that matters — Google finds it and treats it as an afterthought. Give it real internal links from a page that's already indexed — the kind that come from a deliberate site architecture, not a footer scrape. That single change unblocks more pages than anything else we do. The reason is mechanical: Googlebot crawls links, and a page with no links into it is a page no crawl path reaches. Nearly every "discovered" page we unstick becomes an indexable page the moment it gets meaningful links from the site's established pages.
3. Is it thin or duplicate? A page with 200 words of near-duplicate copy gets deprioritized on purpose. Make it distinct and genuinely useful, or merge it. Don't fight Google for the right to index a page nobody would want. "Crawled but not indexed" status is the strongest tell here — Googlebot bothered to read it and decided there wasn't enough there. The fix is substance, not a re-request.
4. Is it slow? A page that takes forever to load teaches Googlebot that crawling your site is expensive. Speed is an indexing factor, quietly. The crawler also runs into the same render bills your users do, and it prices the whole site accordingly. If your failing pages are also your slowest templates, fix the performance before you re-request.
5. Request it properly. Once the page is reachable, linked, distinct, and fast, use URL inspection and request indexing. Do it after you've fixed the reasons, not instead of fixing them. Requesting indexing on a page that's still orphaned or thin is asking Google to index a page it has already correctly declined.
The honest truth about "requesting indexing"
Request indexing is not a button that forces entry. It's a polite suggestion, and two limits apply: you can't game it in bulk (abusing it triggers throttling), and Google evaluates the page again on the merits. The traffic analogy is submitting a résumé to a hiring manager: it only works if the résumé cleared the actual bar. The pages that enter the index fastest are the ones that never need the request at all — they're linked, crawled, and evaluated as part of the site's normal flow. And when you do use it, batch requests only after the fixes land, not before. Teams that fix ten pages and request ten indexes in the same afternoon see a very different outcome than teams who request before fixing — and the difference shows up in the statuses a week later.
Indexing speed is a reputation thermometer
Without over-anthropomorphizing the crawler: indexing speed is a leeriness measurement. A page that arrives linked, distinct, and fast tends to get indexed within hours to a few days. A page that arrives orphaned, near-duplicate, and slow waits weeks. Google isn't punishing the slow page; it's allocating effort according to perceived value, and it prices the whole site on the pattern. A site whose new pages consistently index quickly has effectively demonstrated that its content is worth reading early — and that reputation compounds across every future publish.
The practical consequence is that indexing is rarely a single-page problem. The pages you invest in should inherit the site's existing reputation — published as part of a hub, linked from a related article, surfaced in a sitemap that only lists real pages. New content launched inside an existing flow indexes on its own; new content launched into a vacuum is where the "discovered, waiting" statuses breed. That's the difference between indexing as an afterthought and indexing as a byproduct of how you publish.
The compound fixes that work at scale
For a site with dozens of stuck pages, fixing them one at a time is a treadmill. The structural fixes change the whole population at once:
- Fix the orphan problem at the template level. Every new page should inherit links by design — a related-articles block, a breadcrumb chain, a hub-and-spoke structure. If new pages are typically orphaned-by-accident, the pattern, not the pages, is what needs fixing.
- Kill the parameter and filter URL bleed. Hundreds of auto-generated URL variants compete for crawl attention and split the index's opinion of what your site actually contains. Cap them and the real pages get the attention. This is also where a canonical strategy stops random URL noise from diluting your money pages.
- Prune the near-duplicates. "We have two pages saying the same thing with slightly different titles" is a product org problem, an internal-links problem, and an indexation problem all at once. Merge the weak variant into the strong one and consolidate the links — the strong page indexes faster and ranks better.
- Tighten the sitemap. A sitemap full of thin, blocked, or redirecting URLs teaches Google to ignore the sitemap. Keep it to pages you'd stake a reputation on.
The relationship between crawl and index
Indexing runs on crawling, and crawling runs on a request budget you can shape. Sites that wonder why new pages stall should look at how the crawler is spending its visits: if most requests go to old, low-value URLs or malformed archive pagination, the new pages wait. You don't need to obsess over crawl budget on a small site, but the logic holds everywhere: make the important pages the easy pages, and the index follows the crawl. This is exactly why our advice on crawl efficiency and on indexation is the same advice — spend the crawler's attention where you spend your money.
The habit that prevents the whole problem
Here's the strategic habit that means you rarely chase indexing at all: build your site so authority flows to a small number of important pages, and publish new pages from a position of existing links. New content that inherits internal links and reputation indexes on its own, because it enters the flow. Content that's published into a vacuum sits there — "discovered," waiting, ignored.
The same architecture that gives you databases of topical authority gives you indexation as a byproduct. A hub page linking to fresh spokes on publish isn't just good internal linking; it's a factory that hands new pages a crawl path on day one.
Indexing isn't a button you press. It's the reward for a site that makes Google's job easy and your pages obviously worth the effort. Ask yourself the same question Google asks of every URL: would a searcher be glad this page exists? If the answer is yes and the architecture supports it, the index follows — usually within days of the fix, and always without the re-request theater.
If you're looking at a Search Console full of unindexed pages and don't know which fixes apply, our teardown walks through this diagnostic with your actual data. book a free website teardown and we'll tell you which of the five steps is holding your content back.