The pages Google never shows anyone
Publishing a page and Google showing it to someone are two separate events, and nothing on your website tells you whether the second one happened. The answer lives in the gap between the pages you listed and the pages that actually appeared in a search result.
Last updated 2026-09-04 · The Clode team · Guides
The short version
Compare your sitemap against the URLs with impressions in Search Console. Three groups matter: listed but never shown (usually thin or duplicated content), shown but not listed (orphans your sitemap forgot), and used to be shown and stopped (almost always a technical change you can fix).
The three lists worth having
In your sitemap, zero impressions.
Google either does not have it, or has it and never considers it a good enough answer to show. Both are worth knowing about, and on most sites this list is longer than the owner expects.
Getting impressions, not in your sitemap.
These are orphans: old URLs, campaign landing pages, things your CMS left out. They are working despite you, and they are usually the easiest wins on a site because they are already proven.
Had impressions, now zero.
The urgent one. A page that used to appear and stopped is almost always a technical change: an accidental
noindex, a robots rule, a redirect, a template change that removed the content. It is also the first dull explanation to rule out when traffic drops.
Why "zero impressions" is not "not indexed"
These get conflated constantly and they are different facts. A page can be perfectly indexed and still get zero impressions, because being in the index only means Google could show it, not that it was ever the best available answer for anyone's search.
The distinction matters because it changes what you do. Not indexed is a technical problem: crawling, directives, duplication. Indexed but never shown is a content and competition problem: the page exists, and nothing about it earns a place on the page. Only Search Console's URL Inspection tool can tell you which one you have, and it is worth checking before you act.
Doing it by hand
Export your sitemap URLs, export the pages with impressions from Search Console, and compare the two lists in a spreadsheet. It is a genuine half hour, and it is genuinely worth doing once.
Two things make it harder than it sounds. Sitemaps are often nested (an index file pointing at other sitemaps), so you have to follow them all. And the export is capped, so on a site of any size you are comparing against a top slice rather than the full list, which biases the result towards saying everything is fine.
How this works in Clode
Clode's Page coverage runs this comparison at every sync. It follows sitemap index files down into the sitemaps they list, and checks every URL against the full list of pages Search Console served, up to 250,000, rather than an export's top slice.
The trailing-slash trap
When you compare two URL lists, resist the urge to tidy them up. /services and /services/ can be two genuinely different pages, and merging them because they look alike invents a result that matches neither.
The right behaviour is to compare URLs exactly as they appear and, if both forms show up with traffic, treat that as a finding. It usually means your site is serving the same content at two addresses, which is a real problem worth fixing rather than a data-cleaning step.
How we do it
Clode reads your sitemap the way a crawler does, following index files and nested sitemaps, and compares it against every URL Google recorded an impression for, pulled exhaustively rather than from a capped export. You get the three lists above, kept up to date daily, with the "stopped being shown" list flagged because it is the one with a deadline on it.
URLs are matched exactly as written. Where the same content appears at two addresses we show both and say so, rather than silently merging them into one row that is not true of either.