Crawling and Indexation Control
Indexation Problems the GSC Pages Report Decoded
Read the Search Console Pages report line by line and turn each exclusion reason into a fix.
Reading time · unlocks the next lesson
0:00 / 5:00 · pausedIndexed versus not indexed
The Pages report splits URLs into Indexed and Not indexed, then subdivides the latter into specific reasons. Treat this report as diagnostic, not just a scoreboard: a healthy site still has excluded URLs for legitimate reasons like pagination or redirects, so the goal is matching each reason to intent, not driving the excluded count to zero.
Reading the common exclusion reasons
'Crawled - currently not indexed' means Google fetched the page but chose not to index it, usually due to thin or duplicate content, and is the reason worth the most attention. 'Discovered - currently not indexed' means Google knows the URL exists but has not crawled it yet, often a crawl budget or internal linking signal. 'Alternate page with proper canonical tag' and 'Duplicate without user-selected canonical' both point to duplication, but the second means Google overrode your signals entirely.
- Crawled - currently not indexed: quality issue, improve or merge content
- Discovered - currently not indexed: strengthen internal links, check crawl budget
- Duplicate without user-selected canonical: add explicit rel=canonical
- Soft 404: page returns 200 but reads as empty or error-like to Google
- Blocked by robots.txt: intentional or accidental exclusion
Prioritising fixes
Sort excluded URLs by estimated traffic potential, using internal search volume data or historical rankings before the exclusion appeared, and fix the highest-value pages first. For 'crawled - currently not indexed' at scale, look for a shared template weakness, such as thin product descriptions, rather than fixing one URL at a time.
Requesting indexing responsibly
URL Inspection's 'Request indexing' is useful for a handful of high-priority pages after a genuine fix, but it has a low daily quota and does not override an underlying quality problem. Resubmitting the same thin page repeatedly wastes quota and rarely changes the outcome.
Tracking exclusions over time in RankAudit
RankAudit's indexation tracker snapshots your Pages report categories weekly and highlights URLs that moved from Indexed to an exclusion reason, so regressions are caught within days rather than discovered months later in a traffic drop.
Key takeaways
- ✓Match each exclusion reason to a specific root cause, not a generic fix
- ✓Prioritise 'crawled - not indexed' pages by traffic potential
- ✓Look for shared template issues behind repeated exclusions
- ✓Only request indexing after making a real content change
Why this lesson matters
This lesson belongs to Crawling and Indexation Control, the part of Technical SEO Excellence where the goal is: give googlebot precise instructions and confirm every page you care about is actually indexed.
Read it once, then do it straight away on a real site inside RankAudit. Nothing here is theory for its own sake — every step produces something you can show a client.
Do it now
- 1Open RankAudit with sample data already loaded, so you are not stuck on setup.
- 2Crawl a site and triage the issue list.
- 3Run a crawl in RankAudit and cross-check the robots.txt, sitemap and index coverage reports it produces.
