Skip to content
Kuraib Ali

Indexed but not ranking: what Google Search Console is telling you

A page can be indexed and still invisible in results. What that Search Console status means.

By Kuraib AliPublished Updated 10 min read

Graphs of performance analytics displayed on a laptop screen, representing the Search Console data used to diagnose a ranking problem
Photo: Unsplash

Indexing and ranking are two separate systems, and Search Console's language makes that easy to miss. A page can be fully indexed and still rank nowhere. That's a quality and relevance problem, not an indexing problem. A page can also show as "not indexed" for reasons that have nothing to do with quality at all. Confusing the two leads to the wrong fix almost every time, and Search Console's own status labels don't spell that distinction out plainly enough on their own.

What's the difference between indexing and ranking?

Indexing is Google deciding whether a page goes into its index at all: a yes/no gate. Ranking is a completely separate process that only runs on pages that already cleared that gate, deciding where a page places for a given query. A page stuck at "not indexed" was never in the ranking race to begin with. A page that's indexed but ranks poorly cleared the gate and lost the race. Those need different diagnoses and different fixes, and running the wrong one wastes time without moving the problem.

What do "Discovered, currently not indexed" and "Crawled, currently not indexed" mean?

StatusWhat it meansTypical cause
Discovered, currently not indexedGoogle found the URL but has not crawled it yetGoogle says it typically wanted to crawl the URL but expected that to overload the site, so it rescheduled; the last crawl date is empty
Crawled, currently not indexedGoogle crawled the page but has not indexed itGoogle says this is common, because it does not index every page, and does not necessarily indicate a problem

The distinction matters because the fix is different for each. "Discovered" is a scheduling and crawl-access question. Check for server issues, thin sitemaps, or a lack of internal links pointing to the page. "Crawled, currently not indexed" is a different question. Google says the status is common and does not necessarily mean something is wrong. For a page that matters, diagnose it with the URL Inspection tool: check that the page is not blocked, that it is not a duplicate of a canonical URL elsewhere, and that it gives a reader something the pages already indexed do not.

Does requesting indexing help?

Sometimes, but probably not for the reason a lot of SEO advice assumes. Google's own documentation on the "Request indexing" feature is narrow about what it does: the URL goes into a priority crawl queue, subject to a daily quota, and Google is explicit that requesting a recrawl multiple times for the same URL "won't get it crawled any faster." Nothing in that documentation, or in any other current Google Search Central material, describes the request as granting a URL a temporary ranking, priority, or "freshness" boost in the sense a lot of SEO blog posts describe it.

SEO practitioners have reported a consistent pattern across case studies and forum threads. Some previously stuck URLs get indexed shortly after a manual request, then occasionally drop back out weeks later. That fits a mundane effect: a queue jump gets the page crawled sooner, and Google's ordinary re-evaluation of every indexed page then plays out on its own timeline. It is not an official, documented boost. It is community-observed behaviour, not a confirmed Google lever. Treat it as useful to know, not as something to rely on or re-trigger repeatedly on a page that doesn't meet the bar.

That distinction has a practical consequence: if requesting indexing were a real ranking lever, repeatedly re-requesting a weak page would be a reasonable workaround. It isn't one, because the request only affects when Google gets around to crawling a URL, not its underlying judgement of whether that URL belongs in the index at all.

Why is my page indexed but still not ranking?

This is the other half of the confusion, and it runs the opposite direction. If Search Console shows a page as indexed, it has already cleared Google's inclusion bar. Whatever's holding rankings back from there is a relevance, competition, or content-quality question, not an indexing one. Re-requesting indexing, resubmitting sitemaps, or checking crawl stats won't move a ranking problem, because none of those tools touch the part of the system responsible for ranking. That's a different diagnosis entirely: search intent match, content depth relative to what's already ranking, and the usual on-page and authority signals.

A chart showing a declining trend line, representing a page that's indexed but losing visibility

Is it a canonicalisation problem or a real quality problem?

This is the diagnostic step most people skip, and skipping it is why "improve the content" so often fails to move a page that was never being suppressed for quality reasons in the first place. Before touching a word of the content, walk through this in order:

  1. Check the Page indexing report's exact status for the URL, not just whether it says "indexed" or "not indexed." Google's own report distinguishes several sub-statuses that read like quality problems but are canonicalisation outcomes: "Duplicate, Google chose different canonical than user," "Duplicate without user-selected canonical," and "Alternate page with proper canonical tag." Any of those means the page is fine, it's just not the URL Google decided to show, because Google clustered it with one or more near-identical pages and picked a different one as canonical.
  2. Search for a distinctive sentence from the page in quotes, site-restricted to the domain. If another URL on the same site returns instead of the one you expected, or alongside it, that's a strong sign of an unintended duplicate: a parameterised version, an HTTP/HTTPS split, a staging URL that never got removed, or a near-identical page targeting the same query from a different section of the site.
  3. Only once both of those come back clean (a unique status, no competing duplicate URL) does it make sense to treat this as a real content-quality gap and move to the content-depth and authority questions below.

The reason this order matters: a canonicalisation problem and a real quality problem produce the exact same symptom in Search Console (the page doesn't show up for its target query) but need opposite fixes. Rewriting a page that Google has simply folded into a duplicate cluster does nothing, because the rewritten version gets folded into the same cluster again. Consolidating two pages that are different in intent, on the other hand, throws away content that was never the problem. See canonical tags and canonicalisation explained for how Google weighs the signals (redirects, rel="canonical", sitemap inclusion) that decide which URL wins when it detects duplication.

How do I check whether a page is indexed?

Search Console's URL Inspection tool is the authoritative source, more reliable than the broader Page indexing report, which can lag behind the current real state. A live test through URL Inspection shows the current crawl and indexing status directly, rather than a cached report snapshot. Google's own guidance is specific here too: even a live test result of "URL can be indexed" is a real-time eligibility check, not a guarantee the page is indexed right now. Confirm it against the indexing status shown in the same report.

A magnifying glass resting on an open book, representing the closer read needed once the obvious causes are ruled out

What does a live URL Inspection test show, step by step?

Running "Test Live URL" inside URL Inspection does more than confirm a yes/no status, and most of what it surfaces goes unused. After the test finishes, clicking "View Tested Page" opens three things worth checking in order:

  • The rendered HTML and a screenshot of what Googlebot saw. If the screenshot looks materially different from what a visitor sees, a rendering or blocking problem is a more likely cause than a content-quality one. This is the same underlying rendering pipeline covered in JavaScript SEO: if content only appears after client-side JavaScript runs and something in that process fails, the screenshot shows an incomplete page even though the source code looks fine to a human reading it.
  • JavaScript console messages, which appear both here and under "View crawled page" for the indexed version; only the screenshot is limited to the live test. Errors or warnings logged here during rendering can point at a script failure that's quietly removing content from what Google indexes, something that never shows up just from viewing page source.
  • HTTP response headers, including status code, X-Robots-Tag, and caching behaviour. A stray noindex in a response header (as opposed to the page's HTML) is easy to miss by eye and shows up clearly here.

None of this replaces the indexing status in the same report. It's a diagnostic layer underneath it: the status tells you what happened, this tells you why.

A stethoscope resting on a plain background, representing the diagnostic process of separating a canonicalisation problem from a content-quality one

What to fix when the content looks fine

This is the harder case: a page reads well, covers the topic, has cleared the canonicalisation check above, and is still stuck ranking nowhere. Before assuming the content itself is the problem, rule out the two causes that get mistaken for a content problem most often:

  • Internal cannibalisation. A second page on the same site, targeting the same or a very similar query, can quietly split ranking signal between them, so neither ranks as well as one consolidated page would. Search Console's Performance report, filtered to the target query, shows whether more than one URL from the same site is competing for the same search terms.
  • Thin authority relative to the query's competition. A well-written page can still lose to a page with substantially stronger topical authority or backlink profile answering the same query. This isn't fixed by rewriting the page again; it's fixed by strengthening internal linking into it from other relevant pages on the site, and, where relevant, earning links from outside the site.

If neither of those explains it, the remaining diagnosis is about depth and differentiation: does the page cover something the currently-ranking pages don't, or does it just restate what's already available elsewhere in slightly different words. A useful gut check, independent of any tool: would the page still be worth publishing if search engines didn't exist?

Do these patterns look different across site types?

The mechanics above are the same everywhere, but which cause shows up most often shifts a lot depending on what kind of site it is:

Site typeMost common cause of "stuck, not ranking"Where to look first
Large e-commerceFaceted or parameterised URLs (filters, sort orders, tracking parameters) generating near-duplicate pages that compete with the canonical product or category pagePage indexing report's duplicate sub-statuses, and whether faceted URLs are being crawled at all
Content and blog sitesInternal cannibalisation between an older post and a newer one covering the same query, or thin coverage compared to what's currently rankingPerformance report filtered by query, to see if two of the site's own URLs are splitting impressions
Local business and service sitesDuplicate or near-duplicate location pages built from the same template with minimal unique content per locationWhether Google is quietly canonicalising multiple location pages into one, rather than indexing each separately

None of that changes the two-step diagnosis: rule out indexing and canonicalisation first, then treat what's left as a real relevance or authority gap. What changes by site type is which cause is more likely to be the answer. Check that one first rather than working through every possibility in a fixed order.

Related: crawling vs indexing, canonical tags and canonicalisation, JavaScript SEO.

Frequently asked questions

Can a page be indexed on mobile but not desktop, or vice versa?

Google runs a single, mobile-first index now, so there's no separate desktop index a page could be missing from. If URL Inspection shows a page as indexed, that's one status covering both, not two independent checks.

Does resubmitting a sitemap help a page that's stuck at "Crawled, currently not indexed"?

Rarely. A sitemap is a weak signal that mainly helps Google discover URLs faster. If Google has already crawled and evaluated the page and chosen not to index it, resubmitting the same URL in a sitemap doesn't change that judgement.

How long should I wait before assuming a page will never get indexed?

There's no fixed deadline in Google's own guidance, but weeks rather than days is normal for a new page on an established site, and it can run longer on a new or low-authority site. If a page is still unindexed after a thorough content and authority review, the more useful question becomes whether it deserves a separate URL at all.