Discovered — Currently Not Indexed: What to Check
First distinguish discovered from crawled in Search Console. For a priority URL, record its reported state, live response such as HTTP 200, canonical and indexability as separate observations. Check Google’s indexing report definitions.
Updated

What the status tells you
“Discovered — currently not indexed” means Google knows about the URL and has yet to crawl it. “Crawled — currently not indexed” means a crawl has occurred. Record the exact status first, then choose the corresponding investigation path. Google’s Page indexing report.
Start with the pages your customers need: product, service, article, or useful category pages. Group duplicate and utility URLs by their intended canonical or exclusion rule. This guide combines Meridian’s diagnostic workflow with the linked Google documentation, reviewed on October 12, 2026.
If a page is crawled but still not indexed
Save the URL Inspection result, inspection date, last crawl, declared canonical, and Google-selected canonical where available. Select an affected URL and an indexed peer using the same template. Work through three checks:
1. Canonical and duplicate versions
Compare the inspected URL with its preferred search entry. Check redirects, canonical declarations, parameter variants, internal-link targets, and sitemap entries. For equivalent pages, choose one primary URL and align these signals with it. Record Google’s selected version alongside your declared version. Canonical guidance.
2. Response, directives, and rendered content
Capture the HTTP response and indexing directives. Compare the initial HTML with the rendered page: product description, key headings, navigation, and contextual links should be available in the intended output. Reproduce missing content, blocked resources, or render errors with the developer, then attach before-and-after evidence to the task. JavaScript SEO guidance.
3. Page purpose and internal links
Compare the affected page with its indexed peer. What distinct question does each answer? Does the page contain the product details, examples, or useful data that support that answer? Find its entry from the catalog, navigation, or a relevant article. Assign content improvements to the editor and shared template or link changes to the developer.
Finish with a task: affected URL → observed finding → proposed change → owner → retest date. Recheck the implementation, then record the next URL Inspection status. For a large generated site, also examine URL inventory, serving capacity, server logs, and crawl records to prioritize whole page groups.
Confirm the URL and the current evidence
Use Search Console’s URL Inspection tool to record the exact URL, property, inspection date, reported state, and available crawl information. Save the stored index result and the live test as two dated records. The stored result describes Google’s index; the live test examines the page’s current accessibility. URL Inspection guidance.
Start one record with:
- The requested URL, redirect destination, and preferred search URL.
- Page purpose, template, publication date, and latest substantive change.
- Search Console status, observation date, and screenshot or evidence link.
- Checks completed, findings, and the people responsible for follow-up.
Group affected pages before choosing a fix
Sample affected URLs across templates and publication periods, with an indexed comparison page for each relevant type.
| Page group | Useful comparison | Decision |
|---|---|---|
| New commercial pages | Older pages using the same template | Check the publishing and linking path |
| A language section | Its other-language counterpart | Compare links, URL rules, and language signals |
| Generated or parameter URLs | The preferred canonical page | Choose independent entries or consolidated versions |
| An isolated article | Similar indexed articles | Identify page-specific or template-wide work |
Prioritize useful commercial pages and shared issues that affect a larger group.
Check access and discovery for discovered URLs
Inspect the response and redirect chain. For errors, timeouts, or intermittent access, compare the observation time with server logs and Search Console crawl information. Review robots rules and indexing directives: robots.txt controls crawling; noindex specifies exclusion after Google can fetch the directive. Retain the intended restrictions for private and utility pages. Crawling troubleshooting, noindex documentation.
Check that the final URL, canonical, internal links, and sitemap point to the chosen version. Add a relevant, crawlable entry from navigation, a topic page, or related content. Use the sitemap to expose the intended URL inventory. Sitemap guidance.
Turn the investigation into a task
Planning example: a new service page is in the sitemap, while its navigation entry still points to an old redirecting URL. The resulting task is an internal-link correction:
| Field | Example record |
|---|---|
| Observation | Service navigation points to an outdated URL |
| Evidence | Requested URL, redirect destination, and actual link href |
| Change | Link directly to the preferred service URL |
| Owner | Website developer or CMS editor |
| Retest | Check link destination, response, canonical, and sitemap |
| Search follow-up | Record the next crawl and index status with a date |
Use the indexing investigation worksheet for your page. For a completed URL-rule task, inspect Meridian’s language URL finding and retest: old language parameter → 308 redirect → dedicated Chinese URL, with canonical and language-alternate checks.
Verify the change and follow up
Repeat the checks that established the finding. Keep the original evidence, implementation date, owner, and retest result together. Set a separate Search Console follow-up date to record whether the URL is discovered, crawled, or indexed.
Request a recrawl for an important changed URL, or submit an updated sitemap for a broader set. Google’s recrawl guidance describes the request process and a typical waiting period of days to weeks. Recrawl guidance.
Bring the right problem to the right service
For indexing patterns across templates, bring a URL sample, recent changes, and available Search Console or log access to a technical SEO audit. The output is a prioritized finding register and tasks for your team.
For a known fix that needs development coordination and release checks, see ongoing technical SEO support.







