Information checked: 21 July 2026.
Search Console labels are diagnostic clues, not a list of penalties. Many excluded URLs are intentionally redirected, canonicalised or marked noindex. Troubleshooting begins by deciding what the URL should do.
In brief: Decide the intended URL state, then align status, indexing controls, canonical and links.
Classify the URL first
| URL purpose | Correct outcome | Example |
|---|---|---|
| Public canonical page | 200 and indexable | Main service or guide |
| Duplicate version | Canonical or redirect to preferred URL | Tracking or alternate path |
| Removed without replacement | 404 or 410 | Expired content with no equivalent |
| Private page | Authentication and usually noindex | Account or staging area |
| Moved page | 301 to the closest replacement | Changed permanent URL |
Diagnostic sequence
- Open the exact URL outside the admin session.
- Check HTTP status and redirect chain.
- Inspect robots and noindex controls.
- Check canonical in the rendered page.
- Use URL Inspection for the indexed and live views.
- Confirm internal links and sitemap treatment.
- Fix the underlying template or process if many URLs share the issue.
Common report messages
“Crawled – currently not indexed” does not provide a single fix. Review duplication, usefulness, internal context and whether the page deserves a separate URL. “Discovered – currently not indexed” can reflect discovery, crawl demand or site quality; submitting the same sitemap repeatedly is unlikely to solve it.
Validate only after fixing
Use validation or reinspection after the relevant site change is live. Keep screenshots or exports of the original evidence and avoid changing several unrelated settings simultaneously.
Escalation threshold
Seek specialist help when a large section disappears, live tests cannot render essential content, redirects loop, security issues appear or a migration produces sustained loss.
Common failure pattern
Teams may validate an issue before the underlying template is fixed, or request indexing repeatedly for a page that remains duplicate or thin. Diagnosis should identify the common source before individual URLs are resubmitted.
Incident evidence
- Example URLs from each affected pattern.
- HTTP, rendered HTML and canonical evidence.
- Date the fix reached production.
- Validation result and subsequent monitoring.
Next practical step
Pick several URLs from the same report pattern and determine their intended state. Fix the common source in the template or publishing process rather than applying unrelated page-by-page workarounds.
Sources and date checked
Search, product and regulatory information was checked against the following primary sources. Interfaces and policies can change, so recheck operational details before acting. Date checked: 21 July 2026.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.