Skip to main content
URL indexing page with URL submission input, indexing status cards, and URL status table
Use this page to monitor index coverage and resolve blocked or failed URLs before visibility drops.

Questions this page should answer

  1. Are key pages being indexed correctly?
  2. Which URLs are failing indexing and why?
  3. Which indexing actions should happen first this week?

Before you analyze

  • Start with high-priority page groups (money pages and key content hubs).
  • Review status counts before checking individual URLs.
  • Separate Errored pages from pages that are simply not yet discovered.

What this page gives you

  • URL submission tools (Check Status, Request Indexing).
  • Indexing status cards:
    • All URLs
    • Indexed URLs
    • Discovered
    • Unknown to Google
    • Indexing requested
    • Errored
  • A URL-level status table with last-check information.

How to read the status cards

  • All URLs: tracked URLs in this project.
  • Indexed URLs: pages currently known and indexed.
  • Discovered: found but not yet fully indexed.
  • Unknown to Google: not recognized in index checks.
  • Indexing requested: URLs sent for indexing recently.
  • Errored: URLs whose status check failed; their actual indexing state is not established by that failed check.
The table uses Indexed, Discovered, Not discovered, Indexing requested, Error, and sometimes Not checked. Not discovered corresponds to the Unknown to Google card. Not checked means no inspection result is available. Click status cards to filter the table, and clear the selection with All URLs. An indexing request is a submission state, not confirmation of inclusion. Recheck afterward. Use Last checked to distinguish an old observation from a current result. How to interpret:
  • High Errored count means inspection failures need investigation before you can establish indexing coverage.
  • Large gap between All URLs and Indexed URLs means coverage opportunity.
  • Rising Unknown to Google often means discovery or sitemap issues.

How to use the URL table

Use the table to create an execution queue:
  • Sort and review failed URLs first.
  • Group issues by path/template to find shared root causes.
  • Check Last checked to avoid acting on stale assumptions.
Use bulk actions:
  • Load URLs from sitemap to refresh candidate URLs.
  • Index all URLs or targeted requests after fixes are live.

Quick weekly checklist

  1. Review status-card changes from last week.
  2. Triage Errored URLs first.
  3. Submit fixed priority URLs for re-indexing.
  4. Validate status movement after recheck.
  5. Escalate repeated failures to engineering.

What to fix first

Team routine

  1. Weekly: index-status review and top-priority URL triage.
  2. Bi-weekly: investigate recurring failure patterns.
  3. Monthly: report coverage growth and persistent indexing blockers.

Keep in mind

  • Indexing changes may take time after requests.
  • Requesting indexing without fixing root cause rarely works.
  • Priority should follow business impact, not URL count alone.

Where to go next