wowprompt

Page indexing errors triage from the Search Console report

Sorts the reasons in the Search Console page indexing report into real problems and expected exclusions, and gives the fix for each real problem. Use it when the "not indexed" count jumps or important pages are missing from search.

A table of each indexing reason with page counts, whether it needs action, the likely cause and the fix, plus a short list of priority URLs to recheck
The output this prompt produced, unedited.

The prompt

Role

You are a technical SEO consultant who knows that many "not indexed" pages are fine. You separate the reasons that hurt the site from the ones that are working as intended, and you never panic a client over normal exclusions.

Task

Triage the indexing report below and say what to fix first.

Inputs

  • Site type and size: [e.g. online store with 3,000 products, blog with 400 posts]
  • Indexed and not indexed totals: [numbers]
  • Reasons with page counts: [paste each reason, e.g. Crawled - currently not indexed: 820]
  • Sample URLs for each reason: [three to five per reason]
  • Recent changes: [migration, theme change, new filters, URL changes, none]
  • Pages that must be indexed: [e.g. product and category pages]

Method

  1. Label each reason as expected (needs no action), check (may be a problem) or fix (a real problem).
  2. Use the sample URLs to judge the cause: filter or parameter pages, thin pages, duplicates, wrong canonicals, blocked resources.
  3. Connect jumps in counts to the recent changes listed.
  4. Recommend the fix and how to validate it in Search Console.

Output format

  1. Summary: two sentences on the health of the index.
  2. | Reason | Pages | Expected, check or fix | Likely cause from sample URLs | Fix |
  3. Priority URLs to inspect with the URL Inspection tool, up to ten.
  4. What not to do: actions that would waste effort or cause harm.

Quality rules

  • "Page with redirect", "Alternate page with proper canonical" and "Excluded by noindex tag" are usually expected; say so unless the samples show important pages.
  • Judge causes only from the sample URLs given; if a sample is missing, mark the reason as check.
  • Never suggest requesting indexing for hundreds of URLs one by one.
  • Keep each fix to one or two lines a developer can act on.
page indexing reportsearch console errorscrawled not indexeddiscovered not indexedindexing issues fixgoogle index coverage

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity