When a page doesn't show up in Google, the first thing to find out is how far it got. A page Google has never heard of and a page Google has stored but never shows are different problems with different fixes. This post walks through the four questions I ask to find where a page stopped, using Google Search Console, then works through one real report from my own site.
Two terms first. Crawling is when Google's bot visits a page and reads it. Indexing is when Google stores the page so it can appear in results. A page has to be indexed before it can show up, but being indexed doesn't mean it will.
Where can a page stop?
Ask these in order. The first answer that's "no" is where the page stopped.
- Does Google know the page exists? Google finds pages through links from pages it already knows, or through a sitemap, a file that lists the pages you want found. To check one page, paste its URL into the URL Inspection tool. If it says "URL is unknown to Google," this is where the page stopped.
- Has Google crawled it? In the Page indexing report, a page Google knows about but hasn't visited yet is listed as "Discovered - currently not indexed." Google describes it as: "The page was found by Google, but not crawled yet."
- Did Google index it? A page Google crawled and chose not to store is listed as "Crawled - currently not indexed." Google's note says it "may or may not be indexed in the future; no need to resubmit this URL for crawling."
- Does Google show it for any search? Open the Performance report (Search results), filter it to the page, and look at impressions, the number of times the page appeared in results. An indexed page with almost no impressions stopped here.
The Page indexing report also lists pages that were left out on purpose: redirects, URLs that return a 404 error, and pages with a noindex tag, a line in the page's code asking Google not to index it. Those are often fine. The only question for each is whether you meant it. Google's help page for the report lists every status.
What does that look like in a real report?
I rebuilt this site and relaunched it on October 12, 2026. Five days later I downloaded its Page indexing report. Google knew 100 URLs on the site: 39 indexed and 61 not.
| What Search Console says | URLs |
|---|---|
| Indexed | 39 |
| Crawled - currently not indexed | 30 |
| Not found (404) | 14 |
| Page with redirect | 12 |
| Excluded by noindex tag | 5 |
The 61 that weren't indexed fell into two groups. 31 were the 404s, redirects and noindex pages (14 + 12 + 5), which are usually left out on purpose, though each is worth a quick check. The other 30 were crawled and not indexed.
I checked the 31 first, because each one only needs a yes or no: did I mean this? Four needed a second look. Three were old URLs that should have pointed to new pages but returned a 404, because I hadn't recorded where they should go during the rebuild. I gave each one a redirect on October 17. The fourth was a file from 2018 with no replacement, so it stays a 404 on purpose. To catch this sooner next time, I now compare the URLs Google knows against my list of redirects and removed pages before every update.
Then the 30. 19 were brand-new pages that Google had crawled the day after launch. Google says it "can take a week or so" to crawl and index a new page, so those needed time, not changes. 3 were leftovers from the old site, such as its feed. The last 8 were old blog posts that Google had crawled and left out for months, one since May. The report doesn't say why, so I don't guess. They moved to new URLs in the rebuild, so there was nothing to change yet: the next report will show whether Google indexes them at their new URLs.
What do I change at each step?
Find the row that matches what the reports say.
| Where it stopped | What Search Console says | What to change |
|---|---|---|
| Google doesn't know the page | URL Inspection says "URL is unknown to Google" | Link to it from a page Google already knows, and list it in your sitemap |
| Known, never crawled | Discovered - currently not indexed | New pages can take time. For important pages still waiting, inspect internal links, sitemap inclusion and crawl access before changing the content or publishing schedule |
| Crawled, not indexed | Crawled - currently not indexed | Inspect the live page, preferred URL and answer it provides. Correct an identified technical issue; rewrite or combine pages only when inspection shows a missing answer or duplicated purpose |
| A 404 or redirect you didn't intend | Not found (404) or Page with redirect, on a URL you meant to keep | Decide where it should go, and redirect it if a page replaced it |
| Indexed, rarely shown | Few or no impressions in the Performance report | Check the page’s queries, the reader’s question and current results. Improve an unclear title or opening when you find a mismatch; combine pages only if they serve the same purpose |
A few new pages may simply need time. A large backlog is a reason to inspect important URLs, not proof of a particular cause. Google's crawl guide explains how crawl demand and server capacity affect crawling on large sites; that does not establish the cause on a small site. Check access, internal links and the purpose of the pages before deciding whether the publishing plan needs to change. An indexed page that rarely shows up needs a different investigation. Once it appears, getting it clicked is covered in why a page that ranks still doesn't get picked.
When should you cut a page instead?
When inspection shows it has no distinct purpose for the people who use the site, or another page serves that purpose better. Check visits from other routes and useful support or reference roles before deciding that low search demand makes a page unnecessary. Every URL should justify being there. Merge it into the better page with a redirect, or let it go. Deciding where each old URL should go is its 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?
They can't tell you why Google left a page out: "Crawled - currently not indexed" is a status, not a reason. They are snapshots, so two downloads say nothing about the days in between, and the indexing report can lag behind the Performance report. They also cover only Google. Bing keeps its own index, so a page missing from Google can still be found elsewhere.
For a broader tour of Search Console, Search Console as a visibility dashboard covers the whole report.
Where these numbers come from: Google Search Console's Page indexing report for haydenschuster.com, downloaded October 17, 2026.
To practice choosing what to investigate from a whole-site summary, work through the indexing lesson. It compares redirect exclusions with pages Google knows about but has not indexed, then asks which specific check would justify a change.
First published November 1, 2026.