Discovered - currently not indexed: next steps
Read the conclusion first
‘Discovered, currently not indexed’ means Google knows the URL but has not yet crawled it. Check useful discovery paths, host health and unnecessary URL growth. The label alone does not prove a crawl-budget shortage or that Googlebot tried to fetch this specific page.
Applicable conditions
Applicable to important new pages and sites with a sudden increase in URL count, requiring host, link, and log data.
Before you open the report
The URL, sitemap location, reachable internal links and server availability around attempted crawls.
Use one concrete URL or report first. Keep account credentials and private visitor data out of shared notes.
Steps and verification
Trace the URL to a real navigation path
Start from the homepage or an established category and follow ordinary links to the intended page. Confirm the links are crawlable and point to its final canonical address. Check the submitted sitemap for the same address and remove accidental error, redirect and parameter URLs.
An isolated URL in a spreadsheet is not a functioning site entry point. If a new publishing system has generated many near-identical combinations, quantify those groups and distinguish useful pages from noise before adding every generated address to a sitemap.
Check host health with actual observations
Test important URLs and their required resources without login. Review robots permissions, server error rates and native crawl/host reports. Where logs are available, verify crawler identity and record whether the specific URL was fetched; an empty last-crawl value is not evidence of an attempted fetch.
Correct confirmed timeouts, access blocks or overloaded publishing routes first. Do not infer overload from this report label alone. A small healthy site with recently published useful content may need observation rather than a complex crawl-budget project.
Reduce waste while keeping useful pages discoverable
Fix infinite faceted links and duplicate generated paths at their source. Keep stable category links to important pages and avoid blanket robots blocks that also prevent intended content from being crawled. Plan redirects or exclusions according to the real page purpose.
Save the discovery-path repair, host checks and affected URL groups. Subsequent crawl evidence is one milestone; indexing is another. Repeated requests or paid ‘indexing guarantees’ cannot establish either. If the page is later crawled but still not indexed, switch to the corresponding content and canonical review.
Common mistake: Block all uncrawled pages with robots
This may prevent important pages from being crawled and does not solve content and scale issues.
How to decide when you encounter different situations
Match your actual observation to a row before changing the page. If it does not match, collect the missing evidence first.
| What you see | Next step | How to confirm |
|---|---|---|
| The page only has a sitemap entry | Add real sections and semantic internal links | Users can click through to that page |
| Persistent server errors | Fix response and capacity issues first | Check the actual logs |
| Parameter URLs expand rapidly | Control low-value discovery paths | Do not block important pages across the board |
A sitemap entry without a useful internal route
Teaching scenario. Names, URLs and numbers illustrate the method; they are not customer or measured site results.
- What you observe
- Example: a new guide appears in sitemap.xml but no category or related article links to it. GSC says discovered, not indexed.
- What it establishes
- Discovery alone does not establish a crawl or useful placement. A sitemap is not a substitute for a reader-facing path.
- What to do next
- Add a relevant link from the actual category or a useful related article. Check the final 200 response and whether growing parameter URLs are competing for unnecessary discovery.
What counts as a checked result
Click from the linking page to the guide and preserve the final URL. Use verified Googlebot logs if available to establish crawling; a generic bot visit is not proof.
If a required check fails, keep the error and return to the matching decision branch. A blank record means unverified, not passed.
Leave with a checked result, not another vague instruction
- Your deliverable
- A verified discovery route, current host evidence and a bounded URL-generation review.
- Stop and resolve this first
- Do not infer crawl-budget exhaustion from this label alone.
Record missing evidence in the worksheet below. An unresolved test is useful information; a blank field is not a pass.
Checklist for this page
Fill in your own check results, then decide the next step. Blank means not yet verified, not normal. Content is saved only in the current local session and is not submitted to the server or AI.
Frequently asked questions
Should I immediately buy so-called indexing services?
No. Troubleshoot verifiable issues first; no service can guarantee that Google chooses to index.
Will submitting the sitemap force a crawl?
No. It provides discovery information. Availability, useful paths and Google’s scheduling still matter.
Official materials and usage boundaries
This page provides operational judgment and checking methods, and does not show customer success cases. Calculation examples and request samples are teaching materials, not actual website metrics. Google's reports, conditions, and interfaces may change; please refer to the current official documentation.
Read the corresponding Google official documentationContinue with the relevant tool
Keep the discovery links and response checks in an AISEO Site task, then record Google's first observed crawl separately.
See how it works →