Open the Pages report in Google Search Console (under Index in the left sidebar) to see which pages made it into Google's index and which didn't, along with the exact reason for each one left out. Then use the URL Inspection tool to see what's blocking one specific page — each blocker has a matching one-step fix.
Not every unindexed page is a problem. Google sometimes crawls a URL without adding it to the index, and some statuses, like a duplicate Google already indexed somewhere else, are normal rather than errors worth chasing. Google also flagged longer delays in this report as of December 2025, so if a chart looks stale, check before you panic.
Where to find the Pages report in Google Search Console
Sign in to Google Search Console and pick your property. In the left sidebar, under Index — about a third of the way down — click Pages. That opens the Page indexing report, where Google shows which URLs made the index and which didn't.
The report has two parts. A chart up top tracks indexed pages over time. Below it sits a table, "Why pages aren't indexed," listing each exclusion reason with a page count beside it. Click any reason to see the URLs behind it.
A few things to know before you dig in:
- Use a domain property if you can. It rolls up http, https, www, and subdomains into one report instead of four.
- Counts update on a rolling basis, not instantly. A page you fixed yesterday may still show yesterday's status.
- Export the table if you're checking more than 20-30 URLs — it's easier to work through in a spreadsheet.
Google confirmed this report ran with longer delays than usual starting in late 2025. The lag hits reporting only, not actual crawling or ranking. If the numbers look frozen, don't assume indexing stopped — check a sample URL directly with URL Inspection instead.
What each indexing status means and which ones are problems
Google sorts every URL into one of two buckets: indexed or excluded. Not every excluded status is a problem — some show Google working exactly as designed.
| Status | What it means | Action needed? |
|---|---|---|
| Submitted and indexed | Indexed, and it was in your sitemap | No |
| Indexed, not submitted in sitemap | Indexed, but missing from your sitemap | Add it to the sitemap |
| Crawled - currently not indexed | Google visited but chose not to index it | Check content quality and internal links |
| Discovered - currently not indexed | Google knows the URL but hasn't crawled it yet | Usually clears up on its own |
| Duplicate without user-selected canonical | Google found near-identical content and picked a different URL | Add a canonical tag |
| Alternate page with proper canonical tag | Working as intended | No |
| Blocked by robots.txt | robots.txt blocks crawling | Fix if unintentional |
| Excluded by noindex tag | A tag or header tells Google to skip it | Fix if unintentional |
| Not found (404) | The page doesn't exist | Remove links to it or restore it |
| Soft 404 | Loads, but looks empty to Google | Add content or return a true 404 |
Fix these first: blocked by robots.txt, excluded by noindex, soft 404, and duplicate without a canonical. They usually mean a page you want live isn't there by mistake. Crawled or discovered but not indexed deserve a look too, though they're often a content or internal-linking problem, not a technical bug. Google indexes a URL by default unless it carries a noindex tag or gets blocked — so any exclusion on a page you want ranking means something is actively stopping it.
How to use URL Inspection to diagnose a specific blocked page
URL Inspection gives you a live, single-page check — more current than the Pages report, which can lag. Use it when you need a real-time answer for one URL.
- Paste the full URL into the search bar at the top of Search Console (the one with the magnifying glass, not the sidebar).
- Read the headline: "URL is on Google" or "URL is not on Google."
- Check Coverage for the specific reason, matching the statuses above.
- Compare Google-selected canonical to your declared canonical. A mismatch means Google picked a different page and folded yours in as a duplicate.
- Check Crawl details: last crawl date, and whether crawling and indexing were allowed.
- Once you fix the issue, click Test Live URL, then Request Indexing after the live test passes.
Requesting indexing doesn't guarantee a fast re-crawl, and Google caps how many you can submit per day — save it for pages you've actually fixed.
Build one habit: inspect a page 24-48 hours after you publish it, and again after any big edit. It catches a stray noindex tag or bad canonical before it costs you weeks of traffic.
Common indexing blockers and their one-step fixes
Most indexing problems trace back to a few causes. Here's what each looks like, and how to fix indexing errors for good.
Leftover noindex tag from staging. A dev site often carries a noindex meta tag, and it survives the move to production. Check Indexing allowed? in URL Inspection. Fix: remove the tag from the live template and request indexing.
Robots.txt disallow rule. Someone blocked a folder to keep crawlers off test pages, then forgot to unblock it. Fix: remove the Disallow line for that path.
Wrong canonical. A template default points every product variant at one "main" URL. Check the Google-selected canonical in URL Inspection. Fix: set a unique, self-referencing canonical on each page that should rank on its own.
Orphan pages. A page with no internal links can still get indexed if Google finds it another way, but it's slower and less likely to stick. Run a free Screaming Frog crawl to spot pages with zero incoming internal links. Fix: add a contextual link from a related, already-indexed page.
Soft 404s. An empty category or filter page returns a 200 status but shows nothing real to Google. Fix: add content, redirect it, or return a genuine 404.
Thin or duplicate content. Near-copies — printer-friendly versions, tag archives — get folded into "crawled, not indexed." Fix: merge with a 301 redirect or a canonical tag, and keep the version worth ranking.
Checklist: audit your indexing health in 20 minutes
You don't need a full technical audit to catch pages costing you traffic. Run through this in about 20 minutes:
- Open Index > Pages and note the indexed vs. not-indexed totals. (2 min)
- Scroll to "Why pages aren't indexed" and sort by count, highest first. (1 min)
- Open "Excluded by noindex tag" and "Blocked by robots.txt" first — these are usually mistakes, not choices. (5 min)
- Run your 3-5 highest-value pages through URL Inspection to confirm their live status. (5 min)
- For anything flagged "Crawled - currently not indexed," check it has at least one internal link from an indexed page; add one if it doesn't. (5 min)
- Fix what you can right now — remove a noindex tag, edit robots.txt, add a canonical — then request indexing for each corrected URL. (2 min)
Put this on a recurring reminder. Once a month is enough for most small sites; once a week if you publish daily. A 20-minute check now beats finding out three months later that your best article never made the index.
Frequently asked questions
How do I check what's being indexed versus what's blocked?
Open the Pages report under Index in Search Console — it splits URLs into indexed and excluded, with a reason listed for each excluded one. For a single page, URL Inspection gives a faster, live answer than waiting on the report to refresh.
What's the difference between crawled and indexed?
Crawled means Googlebot visited the page. Indexed means Google added it to the database it serves search results from. A page can be crawled and still excluded — 'Crawled - currently not indexed' is a common status, usually pointing to a content or internal linking issue rather than a technical block.
How often should I audit for indexing issues?
Check the Pages report monthly for most small sites, weekly if you publish often. Always run URL Inspection on a new page a day or two after it goes live, since the aggregate report lags behind reality.
Why does the Pages report look stale or wrong?
Google reported longer than usual delays in this report starting in late 2025. The lag is a reporting issue, not a sign that crawling, indexing, or rankings stopped — confirm the real status of any URL with URL Inspection rather than trusting the report alone.
Fix the pages that matter first
Start with the Pages report, not a full crawl of your whole site. Sort excluded pages by count, fix the statuses that are real mistakes — noindex tags, robots.txt blocks, soft 404s — and leave the ones Google is handling correctly alone. Recheck with URL Inspection before you request indexing, and put a 20-minute audit on your calendar so this doesn't turn into a one-time fix that quietly breaks again in six months.
Sources
- Page indexing report - Search Console Help — Index status definitions and the rule that Google indexes a URL unless it carries a noindex directive or is temporarily blocked.
- Page Indexing Report in Google Search Console - Matthew Edgar — Where the Pages report sits in the Search Console sidebar and the 2025-2026 reporting delay note.
- Google Search Essentials (formerly Webmaster Guidelines) | Google Search Central | Documentation — Baseline technical requirements a page must meet before Google can index it.