When a page of mine isn't getting found, the first thing I want to know is how far it got. A page Google has never heard of and a page Google stores but never shows are different problems, with different fixes. This post is about telling them apart, the first outcome in my system: get found. Search Console as a visibility dashboard covers the indexing report in general. This is how I use it when a page isn't showing up, with my own sites as the examples.
Crawlability, indexation, rendering. The technical foundation everything else stands on. A page that never gets through that foundation can answer the question well, and nobody sees it.
What has to happen before a page shows up?
Four questions, and Search Console has a status for most of them. They're how I diagnose, not a ladder every page climbs: Google can even index an address it knows only from links, without fetching it.
- Google finds the address, through a link from a page it already knows or a sitemap. The report lists examples, not every address, so a page missing from it isn't proof Google lacks it; URL Inspection answers that for one page.
- Google crawls it. A page Google knows but hasn't fetched is listed as "Discovered - currently not indexed". Google's own description: "The page was found by Google, but not crawled yet."
- Google keeps it. A page it crawled and left out is "Crawled - currently not indexed". In Google's words, it "may or may not be indexed in the future; no need to resubmit this URL for crawling."
- Google shows it for a search. Being indexed makes a page eligible. Whether it actually shows up is in the search results report, filtered to that page.
A fifth group holds the pages left out on purpose: redirects, pages with a noindex tag, and addresses that return a 404. Google says a page can be left out for the right reasons, and a 404 for a page you removed with no replacement is one of them. Those need one check each: was it a decision? Google's help page for the report lists every reason.
How do I read the report for one site?
This site is my example, because its own report caught me twice. Search Console's Page indexing export of October 17, 2026 counted 100 addresses on haydenschuster.com: 39 indexed and 61 not.
| What Search Console says | Addresses |
|---|---|
| Indexed | 39 |
| Crawled - currently not indexed | 30 |
| Not found (404) | 14 |
| Page with redirect | 12 |
| Excluded by noindex tag | 5 |
(Google Search Console, Page indexing, chart through October 11, pages crawled through October 13, 2026.)
I clear the pages left out on purpose first, because they're quick. 31 of the 61 were redirects, noindex pages or 404s, and I checked each one against the new site. Four needed a second look. Two were old /home addresses and one an old tag page Google had saved with a space in its name; on the new site they returned a 404 because nobody had recorded where they should go, so on October 17 I gave each a redirect. The fourth, a file from 2018, has no replacement and stays a 404 on purpose. The site's checks now fail when an address Google knows has no recorded decision.
The 30 Google crawled and left out
The other 30 were crawled and not kept. 19 were new pages, crawled on October 13, the day after the new site launched, and 3 were leftovers: the old feed, a WordPress script file and an address from before WordPress. Google says it "can take a week or so" to crawl and index a new page, so one export tells me nothing about those 19 yet. The search results report was already ahead of it. The new address of the Search Console dashboard post showed up 113 times in the June 22 to October 19 window, so Google had shown it at some point, whatever the last export said; the total can't say when it first appeared or whether it's indexed today, which is what URL Inspection is for. (Google Search Console, pages, June 22 to October 19, 2026.)
What about pages Google crawled and didn't keep?
On this site, the 8 that bothered me were old posts. Google knew 17 of my dated WordPress posts and kept 9. It had crawled the other 8, one as far back as May 15, and left them out, including my post about technical SEO clarity, crawled on October 2. Six of the eight never showed up in Google from June 22 to October 19. The report doesn't say why, so I won't guess. All eight moved to new addresses in the October rebuild, and the next export will say whether Google keeps them there.
Being indexed didn't promise much either. Four of the nine indexed posts showed up 6 times or fewer in those same four months. That's the last step, and it needs a different kind of fix.
What does "discovered, not indexed" warn you about?
It's the step before "crawled, not kept": Google knows the address and hasn't fetched it. Google doesn't call that a quality verdict. When the count kept growing on my water-quality site, I took it as my cue to stop adding pages, a judgment call; the CheckMyTap case study has that story. Every URL should justify being there.
What if a page is indexed and still doesn't show up?
Then crawling probably isn't the problem, but I check one of the pages with URL Inspection before ruling it out. WireRef, my electrical code reference, is the clearest case I have: in Google's last index export I have for it, 173 of the 225 addresses it knew were indexed, and its Google showings stayed tiny anyway. (Google Search Console, Page indexing export through September 20, 2026; an older export, so the share may have moved.) The pages were stored and eligible, and Google rarely chose them. So I stopped treating it as a crawl problem and put the effort where WireRef's readers already were. The WireRef case study has where that was and what followed.
At this step the questions are about the search: does anyone ask this, does a better answer already hold the spot, and is this the engine where the readers are? A page that shows up and still doesn't get clicked has moved on to a different outcome, get chosen, and why impressions rise while clicks stay flat covers how to read that.
What do I change at each step?
Find the row that matches what the reports say.
| Where it stops | What Search Console says | What I change | Where I did it |
|---|---|---|---|
| Google doesn't know the page | URL Inspection says it's unknown | Link to it from a page Google already crawls, and list it in the sitemap | Every post here is linked from each of its topic pages, and a check holds that |
| Known, never crawled | Discovered - currently not indexed | Stop adding pages, and make the ones that exist worth crawling | CheckMyTap, too late |
| Crawled, not kept | Crawled - currently not indexed | Give it one question it answers well, fold it into the page that does, or let it go | My eight old posts, now at new addresses |
| Left out, by accident | A 404 or redirect nobody chose | Give the address a decision | This site's four addresses, now held by a check |
| New | Crawled - currently not indexed, days after launch | Wait for a complete read before changing anything | This site's 19 new pages |
| Indexed, rarely shown | A handful of showings in the search results report | Change the question or the engine, not the crawl | WireRef |
When do I stop and cut a page?
When Google has crawled it and left it out, and another page of mine answers its question better, or nobody is asking it. Then I fold it into the better page with a redirect, or let it go.
Both happened in this site's rebuild, and the decisions about where each old address went are their own job: how I structured my old site for search covers which pages I let go and why.
What can't these reports tell you?
- Why Google left a page out. "Crawled - currently not indexed" is a status, not a reason. My eight old posts sit there with no cause I can name.
- What happened between two exports. Index counts are snapshots, and a count on two dates says nothing about the days between.
- Every address. Google limits each example list in the report to a thousand rows and says the list may leave out some pages with a status, even a short one.
- What's true today. The export trails the search results report, as the dashboard post's new address showed.
- What other engines did. Bing keeps its own index, and on my sites its count and Google's have moved in opposite directions. A Google-only read never settles where a page is found.
Every site I build teaches the next one. This site taught me to read the indexing report in the first week after a launch, not the first month.
Written for this site and first published October 30, 2026. Every number in it comes from my own exports and is dated where it appears.