Where you control the site, inspect the exact URL in Search Console. Compare its indexed record with a live test, server response, directives and selected canonical. Without property access, external checks provide weaker evidence.
Follow this diagnostic path: inspect the exact URL and preferred canonical → find Google's reported state → verify the relevant evidence → fix the actual cause → live-test the change → recheck Google's indexed record. Each branch requires a distinct action.
Use this first-pass decision table prior to changing anything.
| What you find | First interpretation | Next action |
|---|---|---|
| No Google-side record for the exact URL | URL Inspection doesn't establish a known indexed or crawled state for that address | Confirm the correct property and URL, check crawlable internal links and sitemap inclusion, then recheck Google's available evidence |
| The preferred URL is already indexed | There may be no indexing problem | Check whether the complaint is about ranking or a distinct URL |
| Discovered — currently not indexed | Google knows the URL, but has not crawled it according to the reported state | Check internal discovery paths, sitemap signals and whether the URL is worth crawling |
| Crawled — currently not indexed | Google has fetched the URL but has not included it in the index | Check canonical signals, the page Google received and its distinct usefulness |
Blocked by robots.txt or excluded by noindex |
An access rule or indexing directive may explain the exclusion | Determine whether the restriction is intentional prior to removing it |
| Page with redirect | The inspected URL points elsewhere | Inspect the final destination, not just the old URL |
| Alternate page with proper canonical tag or another Google-selected canonical | Google may be consolidating similar URLs | Confirm whether the selected URL is the one you want indexed |
| Server error, access denial or soft 404 | Google may not receive a usable page | Repair the response or the content being served, then retest |
For the meanings and limitations of these reporting categories, see Google's Page Indexing report help.
Check Whether the URL Should Be Indexed
Start with a single, exact address. https://example.com/guide/, https://example.com/guide, and a URL containing a tracking parameter may lead to distinct redirects or canonical signals. Write down the URL visitors should land on and the URL Google reports.
Then decide whether the page is meant to appear independently in Google Search. A public, helpful guide or product page may be a candidate. A login screen, internal search results page, obsolete URL, or alternate copy might be intentionally excluded. The absence of a noncanonical URL isn't automatically an SEO defect.
For a verified property, inspect the individual URL in Google Search Console. Its indexed record is the most relevant starting point for Google's known indexing state. The Test Live URL function helps check current accessibility and indexability, but a successful live test doesn't confirm that Google has indexed the URL. Also check whether the inspection is referring to your requested URL or a distinct Google-selected canonical.
Where many URLs are affected, group them by template or reported reason and use the Page Indexing report to find patterns.
Without Search Console access: an external checker may help you to screen an address, but don't treat a missing site: result as conclusive proof that Google has excluded it. Google's documentation on the site: operator explains that results are not exhaustive. Ask the site owner for URL Inspection evidence if you need an authoritative property-level diagnosis.
Identify Which Indexing Stage Failed
Discovery, crawling and indexing produce distinct evidence. Neither a sitemap entry nor a Googlebot visit proves inclusion.
No Google-side record: don't assume Google has never encountered the URL. Check that you're inspecting the correct address in the correct Search Console property. Verify that the page is accessible, linked from relevant crawlable pages and represented by its preferred URL in the sitemap, if applicable. Only then evaluate later crawl or indexing signals.
| Reported or observed state | What the evidence supports | What it doesn't establish | Most useful next question |
|---|---|---|---|
| URL appears in a sitemap or an internal link | The site offers a discovery path | That Google has discovered or crawled the URL | May Google reach the URL from significant, crawlable pages? |
| Discovered — currently not indexed | Google's reported state indicates discovery without a completed crawl reflected there | That the page is low quality or permanently rejected | Is this an isolated URL or a repeatable discovery/crawl pattern? |
| Crawled — currently not indexed | Google reports having crawled the URL | That a particular content-quality issue was the cause | What did Google fetch, and does it prefer another URL? |
| Recent Googlebot visit in verified logs | A crawler requested the URL at a recorded time | That Google indexed or ranked it | What response and content did the bot receive? |
| Page is indexed, with a selected canonical | Google's indexed information supports inclusion of the chosen canonical | That the exact alternate URL is indexed separately or will rank | Is the indexed canonical the intended page? |
Discovered but Not Crawled
A URL may be discovered via a sitemap or another page without being fetched immediately. Check whether it's linked from a relevant, accessible section of your site. A URL listed only in a sitemap, with no meaningful internal route to it, deserves closer inspection.
Look for broken navigation, server problems, migrations or excessive URL variants. These are leads, not Google's disclosed quality verdict.
A clear internal link to the preferred URL and a consistent sitemap discovery setup may improve how your site presents that URL to crawlers. Neither forces a crawl or index decision.
Crawled but Not Indexed
This status changes the task. making Google aware of the URL again is unlikely to answer why it was excluded. First inspect the latest known crawl information, the Google-selected canonical and the content that Google may process. Compare those observations with the current live page.
Search Console records may lag behind changes; a live test displays a distinct moment. To establish visit evidence, verify Googlebot crawl activity instead of trusting a user-agent string.
Indexed, but Not Showing for Your Search
An indexed preferred canonical may not rank for the query you tried. That is a search visibility issue, not proof of excluded indexing.
Rule Out Access and Indexing Blocks
Check what the server delivers prior to requesting another crawl or rewriting content.
| Signal to check | What it may mean | What to do if the exclusion is unintended |
|---|---|---|
HTTP 404 or 410 |
The requested page is missing or gone | Restore the page at its intended address if it should exist; otherwise treat removal as expected |
HTTP 5xx, repeated timeouts or DNS failures |
The server may be preventing reliable fetching | Resolve hosting, application, firewall or upstream failures and confirm a stable response |
HTTP 401 or 403 |
Login or access controls may block the crawler | Make the intended public content accessible without authentication |
HTTP 301, 302, 307 or 308 redirect |
The requested URL forwards to another address | Follow the full redirect path, inspect the final destination and confirm it matches the intended canonical |
| Redirect error, excessive chain or loop | Google may be unable to reach the intended final content | Check for loops, long chains, invalid targets and broken redirect rules; repair the path and retest |
robots.txt disallow |
Googlebot may be prevented from crawling the page | Allow crawling if Google needs to access and index the content |
HTML robots noindex or X-Robots-Tag: noindex |
An accessible page may explicitly request exclusion | Remove the instruction if the page is intended for search |
HTTP 200 with a missing-page message |
Google may classify the response as a soft 404 | Serve genuine content or a suitable error status instead of a false success page |
| Critical content absent after rendering | Google may not receive the content you expect it to process | Inspect rendered HTML, resource access and JavaScript failures |
Check the response of the exact URL, such as redirects. A successful homepage fetch says nothing about a failing subpage. For HTTP behavior, Google's status-code documentation distinguishes successful responses, redirects and errors. An HTTP 200 means the server responded successfully; it doesn't certify that the page qualifies for indexing.
Robots.txt Is Not the Same as Noindex
This difference matters when a page unexpectedly disappears from Google. robots.txt controls crawler access. A noindex robots meta tag or HTTP X-Robots-Tag instructs Google not to include an accessible resource in results. Google must be allowed to crawl a page to discover and apply its page-level noindex instruction.
Google may sometimes list a known URL as Indexed, though blocked by robots.txt based on discovery signals without fetching its content. A crawl block therefore doesn't promise exclusion from search, and adding noindex to blocked HTML may fail since Google may't read it. For intentional exclusion, use a crawl-accessible noindex; for private content, enforce authentication. Check Google's robots meta and X-Robots-Tag rules before changing directives.
Check HTML and HTTP headers: a CDN, CMS or server rule may add X-Robots-Tag: noindex without an HTML meta tag.
A Live Page Can Still Be a Soft 404
A URL that displays "product unavailable," an empty template or a missing-item notice with HTTP 200 may be treated as a soft 404. Restore genuine content where appropriate, or return a suitable missing-page status.
For JavaScript pages, inspect rendered output instead of your signed-in browser alone. See Google's JavaScript SEO guidance.
Check Canonicals and Duplicate URLs
A redirect, canonical hint or Google's duplicate selection may associate content with another URL. The alternate may be excluded even when the selected canonical is indexed.
Compare these fields for the exact URL you inspected:
| Evidence | What to record | Decision it supports |
|---|---|---|
| Requested URL | Address you want to appear in search | Is this the actual preferred public page? |
| Redirect destination | Final URL and response path | Did the old address intentionally move? |
| User-declared canonical | rel="canonical" target, if provided |
Which version is the site recommending? |
| Google-selected canonical | Canonical reported by URL Inspection, when available | Did Google select a distinct version? |
| Internal links and sitemap URLs | Which variants the site consistently exposes | Are site signals supporting the preferred version? |
| Indexed-state evidence for the destination | Standalone inspection of the preferred URL | Is the canonical itself present in Google's index? |
For /guide/ and /guide/?source=email, indexing only the clean canonical may be correct. Where Google instead chooses an unrelated or outdated page, investigate content, links, redirects and canonical signals.
A rel="canonical" declaration is a strong hint, not a command. Redirects also signal consolidation, while sitemap inclusion is weaker. Google may select differently, as its canonicalization documentation explains.
Where the Page Indexing report says Page with redirect, confirm the destination and inspect that destination's index status. The redirecting source normally should not appear as a standalone indexed page. An unexpected redirect to an irrelevant destination is a technical issue. An intended move is not.
For a distinct Google-selected canonical, align your signals with the preferred page without assuming a tag change compels Google to select it.
Investigate Crawled but Not Indexed
Once the URL is accessible, crawlable and not intentionally consolidated elsewhere, the investigation becomes less mechanical. Crawled — currently not indexed is a reported outcome, not Google's disclosure of one precise cause. Avoid generic claims that every such page is "thin," "low quality" or affected by crawl budget.
Instead, use observations to test particular hypotheses.
| What you can observe | Plausible explanation to investigate | A useful test or change |
|---|---|---|
| The body is absent or incomplete in rendered HTML | Essential content may not be available to Google | Inspect rendering and fix blocked or failing assets, scripts or API responses |
| Many URLs use almost identical copy and serve the same purpose | Google may be consolidating similar material or finding little distinct value | Compare the pages and make the helpful differences real; consolidate needless variants |
| The page is isolated from relevant navigation | Users and crawlers have weak paths to it | Link from an appropriate, related page using a crawlable HTML link |
| The page displays placeholders, an empty listing or stale information | The fetched result may not meet the page's intended user task | Publish complete, current content or retire the URL if it serves no purpose |
| A migration changed addresses or canonical signals | Google may be processing conflicting old and new versions | Align redirects, canonicals, internal links and sitemap entries |
| Multiple URLs from one template have the same status | A template-wide defect is possible | Sample representative pages and compare headers, directives, rendering and body content |
| One page is missing while peers are indexed | The cause may be particular to that URL | Compare its response, content, links and selected canonical with genuinely similar indexed pages |
Even a technically accessible page with no obvious indexing restrictions may remain unindexed. Passing basic checks makes inclusion possible, not certain.
Make the Content Diagnosis Specific
Read the page as someone who followed its internal link expecting an answer. Does it address a distinct need? Does it present helpful information that isn't already provided more clearly by the site's canonical alternative? Does the main content load for a visitor who isn't signed in? Are significant sections present in the rendered output?
Don't pad an empty listing with boilerplate. Add genuinely helpful information or consolidate duplicates where appropriate.
When Many Pages Are Missing
When Google indexing issues affect many pages, standalone the number of excluded URLs from the number of significant URLs that should be indexed. Parameter variants, redirects, noindexed pages and duplicates may produce substantial exclusion totals without requiring repair.
Group unexpected exclusions by template and cause. Fix widespread access or canonical defects prior to rewriting isolated articles.
Fix the Cause and Verify the Result
Record the original state, fix the cause, verify the live page and monitor the Google-side result.
Use the following worksheet for one significant page or one representative URL from an affected group:
| Record | Before repair | After repair or next review |
|---|---|---|
| Exact URL and preferred canonical | Requested address and intended canonical | Same target, or documented migration destination |
| Google-reported indexed state | Report reason and last known crawl, if shown | New indexed state or unchanged reason |
| HTTP response and final destination | Status, access result, redirect target | Working response and expected destination |
| Robots and index directives | robots.txt, robots meta and response header findings |
No unintended restriction remains |
| User-declared and Google-selected canonical | Record both instead of assuming agreement | Check whether Google now selects the preferred URL |
| Discovery and rendered content | Relevant internal link, sitemap presence and meaningful content | Confirm improvements are visible on the live page |
| Change and verification date | Date, action taken and evidence used | Retest outcome and next review date |
Match the Follow-Up to the Fix
- After fixing access or
noindex: confirm the new response and directives in a live test. Then monitor the indexed record for the particular URL. A live pass alone isn't index inclusion. - After changing redirects or canonicals: inspect both the source and selected destination. The intended outcome may be indexation of the destination, not the old URL.
- After improving a discovered but uncrawled page: check its internal discovery path, sitemap consistency and later crawl evidence. Don't treat repeated submission as a substitute for those changes.
- After revising a crawled but unindexed page: compare the new rendered content, canonical selection and eventual index state. Give Google's systems time to revisit and process it.
- After repairing a template-wide defect: validate representative URLs prior to assuming that every affected page is resolved.
Where a changed URL belongs to a property you manage, Search Console may offer an individual Request Indexing workflow. Where the request is rejected, record the particular message. Check property permissions, live-test indexability and any stated request restrictions prior to retrying. A failed submission isn't the same as Google's later decision not to index a page. Repeated requests don't guarantee an earlier crawl. For many URLs, rely on normal discovery paths and a sitemap instead of requesting each page.
When tracking the result, select the evidence that answers your question. For your own verified property, Search Console's indexed record and canonical information are stronger diagnostic evidence than a general search operator. Nuclear Link Indexer's standalone Google Index Checker provides a paid, independent site:-based status signal for URLs you want to screen, such as URLs you don't own. Its result isn't Google's verified Search Console record, and an absent result can't definitively establish deindexing.
Nuclear Link Indexer also offers an independent URL indexing delivery workflow for selected URL lists. Delivery, any subsequently observed Googlebot activity and Google index inclusion are standalone outcomes. Delivery cannot override a noindex directive, an incorrect canonical or Google's decision not to index a page. Diagnose the URL first; use delivery only where it serves a standalone, legitimate discovery or crawl workflow.
There's no guaranteed deadline. Record the repair date and recheck.
When Indexing Is Intentionally Prevented
Not every exclusion needs repair. First compare it with your publication decision.
| Intended outcome | Appropriate interpretation |
|---|---|
| A public page should be independently indexed | Investigate unintended blocking, failed crawling or canonical selection |
| An alternate or duplicate should consolidate into another URL | A Google-selected canonical may be the desired outcome |
| An old URL should redirect to its replacement | Inspect the replacement; exclusion of the redirecting source is expected |
| A public but non-search page should remain out of search | Use an appropriate accessible noindex directive and confirm Google may read it |
| A genuinely removed page should stay removed | Return the appropriate missing-page status or use a suitable redirect if there's a real replacement |
| Private or sensitive content must not be exposed | Enforce authentication or other real access controls; indexing directives are not a security mechanism |
WordPress visibility settings and SEO plugins may add noindex; verify the live output and headers. robots.txt alone isn't a reliable removal instruction for a known URL.
The diagnosis is complete when you may state three things: what Google or your server reported, whether that outcome is intentional, and which particular change or verification should follow. An index check, an indexing request and a recorded Googlebot visit answer distinct questions. None may substitute for a correct page, a consistent canonical and Google's eventual indexing decision.