> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomicagi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# URL indexing
> Track index status and resolve indexing issues before they impact growth
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 with indexing check failures.
How to interpret:
* High `Errored` count means direct indexing risk.
* 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
| Pattern in URL indexing | What it usually means | Recommended action |
| ------------------------------------ | ------------------------------------------ | -------------------------------------------------------- |
| High errored count | Technical/indexing blockers are unresolved | Fix root cause and re-request indexing for priority URLs |
| Large unknown-to-google segment | Discovery pathway is weak | Validate sitemap, internal links, and crawl access |
| Many discovered but not indexed URLs | Quality/signaling gap | Improve page quality and internal support links |
| Important page stuck unindexed | Direct business risk | Prioritize page-level fix and immediate re-index request |
## 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
* [Technical overview](/data/technical/overview)
* [SEO audit](/data/technical/seo-audit)
* [Cannibalization](/data/technical/cannibalization)
* [Interlinking](/data/technical/interlinking)
* [Google Search landing pages](/data/google-search/landing-pages)