How to get indexed by Google: why pages don't get in, and how to fix it

There was a time when publishing a page and waiting a day or two was all it took to get it into Google. That era is over. Google now crawls far more pages than it chooses to index, and "crawled – currently not indexed" has become one of the most common and frustrating statuses in Search Console. A page can be perfectly crawlable and still not make it into the index, because indexing is a decision, not an automatic consequence of crawling. This guide separates the two reasons a page fails to get indexed — technical problems that block it, and quality judgements that exclude it — and walks through the fixes in the order worth trying them. If your content is published but invisible, the cause is almost always on this list.

Crawling and indexing are not the same

The first thing to internalise is that crawling and indexing are separate steps. Crawling is Google fetching your page; indexing is Google deciding to store it and make it eligible to appear in results. A page can be crawled and not indexed, which trips up a lot of people who assume that if Googlebot visited, the page is "in." It isn't necessarily. When you diagnose an indexing problem, your first question is which step is failing: was the page never discovered or crawled at all, or was it crawled and then left out? Search Console's page indexing report tells you this, and the two situations call for completely different fixes.

Reason 1: Google never found the page

A page can't be indexed if Google never discovers it. This happens when a page has no internal links pointing to it (an orphan), isn't in your sitemap, or is buried so deep in your site that the crawler rarely reaches it. New sites and new pages are especially prone to slow discovery. The fixes are straightforward: link to the page from other relevant pages on your site, include it in your XML sitemap, and make sure it's reachable within a few clicks of a well-crawled page like your home page or a hub, as we cover in our XML sitemaps guide. If a page genuinely isn't being discovered, no amount of on-page work will help until there's a path to it.

Reason 2: something is telling Google to skip it

If a page is crawled but not indexed, the next suspects are signals that explicitly tell Google not to index it — and these are often accidental. A stray noindex meta tag (very common on pages copied from templates or left over from staging), a canonical tag pointing to a different URL, a robots rule, or an HTTP error can each keep a page out, as our robots.txt guide explains. These are the first things to check because they're common, easy to miss, and completely override your intent: a page can be excellent and still be invisible because a single tag is quietly telling Google to ignore it. Inspect the live URL in Search Console, which reports exactly which signal, if any, is blocking indexing.

Reason 3: Google can't see the content

A page can be crawled, carry no blocking signals, and still fail to index because Google received an empty or near-empty page. This is the rendering problem: if your content is built by JavaScript in the browser and the initial HTML is a shell, Google may index little or nothing, as we discuss in our guide to JavaScript SEO. From Google's side, there's nothing worth indexing because it didn't receive any real content. The fix is to make your important content present in the HTML the server sends, through server-side rendering or static generation. Always check what Google actually received — the rendered HTML in the URL inspection tool — rather than trusting what your browser shows.

Reason 4: the page isn't worth indexing (yet)

Here's the uncomfortable one. Often there's no technical problem at all: Google crawled the page, understood it fine, and decided it wasn't worth keeping. This happens to thin pages, near-duplicates of content already indexed, auto-generated or templated pages with little unique value, and pages that don't add anything the index doesn't already have. "Crawled – currently not indexed" is frequently Google's polite way of saying the page doesn't earn its place. The fix here isn't technical; it's to make the page genuinely substantial and distinct, or to accept that near-duplicate and thin pages may simply not get in. No submission trick overrides a quality judgement.

Why thin and duplicate pages get left out

Google has strong incentives not to bloat its index with low-value or redundant pages, and it has become much more willing to simply leave such pages out. If you've published a large number of thin, similar pages — the kind of templated, keyword-swapped content that scales easily — a chunk of them not getting indexed is the predictable result, not a bug. The lesson is that indexing increasingly rewards quality and distinctiveness: a smaller number of genuinely substantial, unique pages indexes far more reliably than a large number of thin ones. If you're struggling to get many similar pages indexed, the honest answer is usually to consolidate them into fewer, better ones.

How to actually request indexing

For an individual important page, you can prompt indexing: inspect the URL in Search Console and request indexing, which puts it in the queue for crawling and reconsideration. For larger sets, a current XML sitemap is the right mechanism, and protocols like IndexNow can notify engines of new and updated URLs faster, as we touch on in our crawl budget guide. But understand what requesting indexing does and doesn't do: it asks Google to crawl and reconsider the page sooner; it does not force Google to index a page it has judged unworthy. If a page keeps failing to index after a request, the problem isn't the request mechanism — it's one of the reasons above.

Crawl budget and large sites

On very large sites, crawl budget becomes a real factor: Google allocates a finite amount of crawling to each site, and if that budget is spent on low-value, duplicate, or parameter-generated URLs, your important pages may be crawled and indexed slowly or not at all. The fix is to stop wasting crawl budget: reduce duplicate and low-value URLs, use canonicals and robots sensibly, keep your sitemap clean, and make sure your internal linking prioritises the pages that matter. For most small and medium sites crawl budget isn't the bottleneck, but for large sites with lots of generated URLs, cleaning up what Google wastes its crawling on can meaningfully improve how reliably the important pages get indexed.

A diagnostic order that works

When a page won't index, work through it in this order. First, is it discovered? Check that it's linked internally and in your sitemap. Second, is it blocked? Inspect the URL for a noindex, a conflicting canonical, a robots block, or an error. Third, can Google see the content? Check the rendered HTML for your actual content. Fourth, is it worth indexing? Ask honestly whether the page is substantial and distinct, or thin and duplicative. Nine times out of ten, the answer is in one of those four, and they're worth checking in that order because the early ones are quick and common while the last requires honest judgement about the page itself.

How long indexing should take

Set realistic expectations. For an established, well-crawled site, a good new page often indexes within days of being discovered. For a new or rarely-crawled site, it can take longer, because Google crawls it less frequently and is more cautious about a site it doesn't yet trust. If a page isn't indexed after a couple of weeks despite being discoverable, unblocked, renderable, and genuinely good, that's when to request indexing and investigate. But don't panic at day two: some patience is normal, especially for newer sites, and constantly resubmitting a page doesn't speed things up. Build the site's overall trust and crawl frequency, and individual pages index faster as a result.

The bottom line

Getting indexed is no longer automatic: Google crawls more pages than it keeps, and indexing is a decision. When a page doesn't get in, the cause is almost always one of four things, worth checking in order: it was never discovered (fix internal links and sitemaps), something is blocking it (check for stray noindex tags, conflicting canonicals, robots rules, and errors), Google can't see the content (fix rendering so your content is in the server HTML), or the page isn't worth keeping (make it genuinely substantial and distinct, or consolidate thin pages). Requesting indexing helps a good page get reconsidered sooner but won't force in a page Google judged unworthy. Build a trustworthy, well-structured site full of genuinely valuable pages, and indexing stops being a fight.

Frequently asked questions

Why is my page crawled but not indexed?

Because crawling and indexing are separate steps: Google fetched your page but decided not to store it. The usual causes are a blocking signal you may not realise is there (a stray noindex tag, a canonical pointing elsewhere, a robots rule, or an error), a rendering problem where Google received an empty HTML shell, or — most often for 'crawled – currently not indexed' — a quality judgement that the page is too thin or duplicative to be worth keeping.

How do I get Google to index my page faster?

For an important individual page, inspect the URL in Search Console and request indexing, which queues it for crawling and reconsideration sooner. For larger sets, keep a current XML sitemap and consider protocols like IndexNow for faster notification. But requesting indexing only asks Google to reconsider sooner — it won't force in a page Google has judged thin or duplicative, so fix the underlying reason first.

Why won't my new pages get indexed at all?

First check they're discoverable — linked internally and in your sitemap, and not orphaned or buried deep in the site. Then check nothing is blocking them (noindex, canonical, robots, errors) and that Google receives real content, not an empty JavaScript shell. If all that's fine and they still won't index, they may be too thin or similar to existing pages — publishing many thin, templated pages predictably leads to a chunk of them never getting indexed.

Does requesting indexing in Search Console guarantee my page gets in?

No. It asks Google to crawl and reconsider the page sooner, but it doesn't override Google's judgement. If a page keeps failing to index after a request, the problem isn't the request mechanism — it's a discovery issue, a blocking signal, a rendering failure, or a quality judgement that the page doesn't earn a place in the index. Fix that underlying cause rather than resubmitting repeatedly.

How long should indexing take?

For an established, well-crawled site, a good new page often indexes within days of discovery. For a new or rarely-crawled site it can take longer, because Google crawls it less and is more cautious about a site it doesn't yet trust. If a discoverable, unblocked, renderable, genuinely good page isn't indexed after a couple of weeks, request indexing and investigate — but some patience is normal, and resubmitting repeatedly doesn't speed it up.