The verdict
A page that gets no search traffic has failed at one of four stages: Google never crawled it, could not render it, chose not to index it, or indexed it and ranks it nowhere useful. Each stage leaves a different mark in Search Console. Find the stage before fixing anything, because the fixes do not overlap.
Most “why isn’t this page ranking” questions are really a different question: where did the page drop out? A page that was never crawled needs links. A page that was crawled and not indexed needs a reason to exist. A page that is indexed and sits on page six needs a better answer than the pages above it. Those are three different jobs, and doing the wrong one wastes months.
This is the order I work through on every page that should be getting traffic and isn’t.
Google says three stages. I check four
Google’s own guide to how Search works describes three stages, crawling, indexing and serving, and adds that “not all pages make it through each stage.” It also says plainly that Google “doesn’t guarantee that it will crawl, index, or serve your page,” even when the page follows every rule.
I split rendering out as its own stage because that is where JavaScript sites fail without anyone noticing. Google’s guide folds rendering into the crawl: “Google renders the page and runs any JavaScript it finds using a recent version of Chrome.” When that goes wrong, the page is crawled, sometimes even indexed, and the content that should rank is simply not there.
Stage one: was the page ever crawled?
Google finds URLs in three ways: links from pages it already knows, sitemaps, and URLs it has seen before. A page with no internal links pointing at it, missing from the sitemap, depends on luck.
The sign in Search Console is the URL Inspection tool saying the URL is not on Google, or the Page indexing report listing it as “Discovered, currently not indexed”, which means Google knows the address and has not fetched it yet. The fix is almost always internal links. I once audited a site where ninety per cent of pages were unreachable from the navigation, and no amount of content work would have helped until that changed.
Crawl capacity is rarely the real constraint below a few hundred thousand URLs. I have written about why almost nobody has a crawl budget problem, and it is still the first wrong diagnosis I see in other people’s audits.
Stage two: did Google see the content?
Rendering problems hide well. The page loads fine in your browser, and the HTML Google receives is a shell that fills itself in with JavaScript. If a script fails, times out, or waits for a click, the text that should rank never reaches Google.
The test takes two minutes. Run the URL through URL Inspection, open the tested page, and look at the rendered HTML and the screenshot. If the main copy, the product grid or the internal links are missing there, the page has a rendering problem, whatever else is wrong with it. I go through what this looks like on real builds in what Googlebot actually sees on a JavaScript site.
Stage three: did Google decide to index it?
Crawled is not indexed. Google’s guide describes how, during indexing, it groups similar pages and picks “the one that’s most representative of the group.” Every page that loses that vote is a duplicate in Google’s eyes, whatever you think of it.
Status codes matter here too. Google’s documentation on how status codes affect its crawlers is blunt: “an HTTP 2xx (success) status code doesn’t guarantee indexing.” A 200 response gets the page considered. It does not get the page in.
The Page indexing report shows the reason for each excluded URL. The two that matter most:
- Crawled, currently not indexed. Google fetched the page and decided it was not worth a place. This is usually about the page, not the site’s technology, and I cover it in detail in what crawled, currently not indexed actually means.
- Duplicate, Google chose a different canonical. Google grouped the page with another URL and picked the other one. Sometimes Google is right. Sometimes your own internal links and canonicals are telling it to.
- Excluded by noindex. Less common than people fear. HTTP Archive’s 2025 crawl found a noindex directive on only 2.4% of mobile pages, but when it is on a page that should rank, it is usually a plugin or a staging setting nobody switched off.
Stage four: indexed, so why no traffic?
If URL Inspection says the page is on Google, the technical part is done. What is left is ranking, and ranking is about relevance and competition.
Open the Performance report filtered to that one page. Three patterns cover most of what I see:
- No impressions at all. The page is indexed but matches nothing people search for, or matches it so weakly it never appears. Look at what the page is actually about against the words people use.
- Impressions at position 30 and beyond. Google considers the page relevant and not good enough. Compare it honestly with the pages in the top five.
- Impressions in the top ten, almost no clicks. The page ranks and the result does not get chosen. I wrote up a case with 27,903 impressions and 106 clicks where this was the whole problem.
The order matters more than the checks
Every one of these checks is simple. The mistake is doing them out of order. Rewriting copy on a page Google has never crawled changes nothing. Building links to a page that renders empty sends authority to a blank. Fixing canonicals on a page that ranks fine and gets no clicks solves a problem the page does not have.
So I start at stage one and stop at the first stage that fails. Whatever is wrong further down can wait, because Google cannot see it yet.
The short version
- Four stages: crawl, render, index, rank. Google describes three. Rendering deserves its own check.
- Not crawled means not linked. Internal links fix this far more often than sitemaps do.
- Check the rendered HTML. If the content is missing there, nothing else matters yet.
- A 200 status does not mean indexed. Google still decides whether the page earns a place.
- Indexed with no traffic is a ranking problem. Read the page’s own Performance data.
- Stop at the first stage that fails. Fixes further down are wasted until it is solved.
If a site should be ranking and it isn’t, that’s the work I do. Technical SEO starts by finding which of these four stages your pages are failing at.










