Start a project

Tool 19 of 194 · Indexing

Search Console Indexing Report Analyser

Turn Search Console's "Why pages aren't indexed" exports into a ranked list of fixes, grouped by reason and by the folder they're in.

Search Console Indexing Report Analyser

Your Search Console export

In Search Console open Indexing, Pages, pick a reason under "Why pages aren't indexed" and Export. Paste each table under its reason. Dates of 1970-01-01 mean Google has never crawled the URL. Nothing is uploaded.

Ranked fix list

#ReasonFolderPagesWhat to do
Fix list (CSV)

By reason

ReasonPagesPriorityStale

By folder

Want the AI crawler view of your whole site? Run PingAI, which scores how well ChatGPT, Claude, Perplexity, Gemini and Copilot can reach and read it.

01

What it does

Groups Search Console's not-indexed pages by reason and folder, weighs each reason by how much it matters and ranks the fixes, with a CSV to work through.

  • Reads the Page indexing drill-down exports, several at once, or any CSV with URL and Reason columns
  • All 17 of Google's reasons recognised, each weighted from Expected to Urgent
  • Grouped by folder, so one template problem shows as one fix
  • Never-crawled (1970) and stale crawl dates flagged

02

Private by design

Everything happens in your browser. Nothing you type, paste or upload is sent anywhere, and it keeps working offline once the page has loaded.

03

What you get

A ranked fix list, per-reason and per-folder counts and a CSV, with a Copy and a Download button on every result.

  • Search Console
  • Indexing
  • Google
  • SEO

Why it matters

Search Console's Page indexing report lists every reason Google left pages out, but it shows them one reason at a time and treats a thousand expected redirects the same as ten server errors. The exports are flat lists of URLs, so the pattern behind them (one template, one folder, one filter) is hard to see.

This analyser reads the exports you download from the report and puts them back together. Each reason is weighted by how much it usually matters: server and redirect errors first, then soft 404s and canonicals Google overruled, then pages it crawled or found and chose not to index. Alternates with a proper canonical are expected and drop off the list. URLs are grouped by their first folder, so the fix list reads "/tags/: crawled, not indexed, 3 pages" rather than three separate rows, and crawl dates show which ones Google hasn't been back to.

How to use it

  1. In Search Console open Indexing, then Pages, and export each reason you want to fix.
  2. Drop the CSV files here, or paste each table under a # line naming its reason.
  3. Read the fix list from the top: it's ranked by pages times priority.
  4. Download the CSV and work through it; check a sample URL in URL Inspection after each fix.

FAQ

What's the difference between 'Crawled' and 'Discovered - currently not indexed'?

Crawled means Google fetched the page and decided not to index it, usually because it judged the content thin or duplicated. Discovered means Google knows the URL but hasn't fetched it yet, often because of crawl capacity or weak internal linking.

Should I worry about 'Page with redirect' and 'Alternate page with proper canonical tag'?

Usually not. They mean Google followed your redirect or canonical, which is what you asked for. The analyser marks them Low or Expected. Just keep old URLs out of your sitemap and internal links.

Why do some URLs show 1970-01-01 as the last crawl?

That's Search Console's placeholder for a URL Google has never crawled. The analyser counts them as stale.

Is my export uploaded?

No. The files are read in your browser and nothing is sent anywhere.

Work with me

Want a site that gets these right?

I build fast, accessible websites and web apps that pass these checks from day one. Tell me about your project and I'll reply personally with honest next steps.

All developer tools · Back to leej.uk