The Page Indexing report groups URLs Google knows about by their latest reported indexing state and reason. A Not indexed label is not automatically an error: redirected URLs, duplicate variants, intentional noindex pages, and genuinely removed URLs normally should not be indexed.
Use this dictionary to decide three things:
- Whether the affected URLs are intended to appear in Google Search.
- Whether the reported outcome matches that intent.
- Which evidence or tool should be checked next.
This reference uses the current English labels in Google's documentation as verified on July 18, 2026. Google can change report labels and groupings, so follow the report's Learn more link if your property shows a different reason.
Read the report correctly before using the dictionary
The report is a site-level diagnostic, not a complete URL inventory or a live test.
- It contains URLs Google knows about. A URL Google has not discovered can be absent from both Indexed and Not indexed totals.
- Indexed and Not indexed totals are complete from Google's perspective, but the example table for any reason is limited to 1,000 URLs and is not guaranteed to contain every affected URL.
- The chart shows the number of URLs in each state on each date, not the number crawled that day.
- The report can lag behind a recent deployment, recrawl, or indexing decision.
- Use URL Inspection for the latest indexed evidence about one URL. Use Test live URL to test the current fetchable version.
- A live test does not reproduce every indexing decision. In particular, it does not test duplicate or canonical selection the same way Google's indexing systems do.
The report's Source column distinguishes an issue attributed to the Website from one attributed to Google. Google says you can generally fix only reasons whose source is Website. Even then, first decide whether the outcome is intentional.
Quick decision table
| Status family | Typical interpretation | Normal first action |
|---|---|---|
| Technical fetch or response failure | Google could not obtain a usable indexable response | Reproduce the response and fix the platform, server, CDN, firewall, DNS, or redirect rule |
| Explicit exclusion | The site told Google not to crawl or index the URL | Confirm the directive is intentional; remove it only from URLs meant to be indexed |
| Discovery or indexing deferral | Google knows or crawled the URL but has not indexed it | Assess importance, crawlability, duplication, rendering, content usefulness, and site-wide patterns |
| Duplicate, alternate, or redirect | Google consolidated the URL with another version | Usually no action if the selected destination is correct |
| Expected missing URL | A removed or nonexistent URL returns 404/410 | Leave it alone unless it moved or an internal source still submits or links to it |
| Indexed warning | The URL is indexed but Google could not crawl or read it normally | Fix access or content delivery if the result is unintended |
Not indexed: technical response and fetch reasons
Server error (5xx)
Meaning: Google's request received a 500-level response, timed out, or encountered a related server connectivity failure.
Is action required? Yes for important URLs, repeated incidents, or a broad pattern. A one-time transient response can disappear after a successful recrawl, but recurring 5xx errors can reduce crawl rate and eventually cause indexed URLs to be dropped.
Check next:
- URL Inspection's last crawl result and live test.
- Crawl Stats → Host status and By response.
- Origin, CDN, load balancer, application, and firewall logs at the reported time.
- Whether
429 Too Many Requestsis being generated; Google treats 429 like a server error.
Redirect error
Meaning: Google encountered a redirect chain that was too long, a loop, an eventual URL that exceeded the maximum length, or a bad or empty URL in the chain.
Is action required? Yes when the URL or its intended destination matters.
Check next: Trace the complete server-side redirect chain with an HTTP client or browser network tool. Make each old URL resolve through as few hops as practical to one valid, public destination. Do not confuse this with Page with redirect, which is normally expected.
Blocked due to unauthorized request (401)
Meaning: The server required authentication when Googlebot requested the page.
Is action required? Only if the page is intended to be public and indexed. Authentication is the correct protection for private content.
Check next: Open the URL in a signed-out or private browser session. If it should be public, remove the authentication requirement from that route. Do not expose confidential content merely to satisfy the report.
Blocked due to access forbidden (403)
Meaning: The server denied Google's request with HTTP 403.
Is action required? Yes when the page should be public. Common causes include web application firewall rules, CDN bot controls, geographic blocks, rate limits, and application authorization.
Check next: Reproduce with a live inspection, review security logs, and verify that any request claiming to be Googlebot really originates from Google before allowlisting it.
URL blocked due to other 4xx issue
Meaning: Google received a client-error response other than the separately reported 401, 403, or 404 cases. This can include malformed-request handling and other access failures. Google treats 429 differently—as a server-overload signal.
Is action required? Yes if the URL should be indexed; otherwise confirm the response matches the intended lifecycle.
Check next: Record the exact status, response headers, response body, affected template, and Googlebot access path. Fix the cause rather than replacing every 4xx with 200.
Soft 404
Meaning: The URL returned a success-like response, often 200 OK, but Google judged the content to be an error, empty, or equivalent to “not found.”
Is action required? Usually. Choose the correct outcome:
- If the resource is truly gone with no replacement, return HTTP 404 or 410.
- If it moved, permanently redirect to a close replacement.
- If the page should exist, serve substantial, usable content with a successful response.
Check next: Run a live inspection and view the tested page's rendered HTML and screenshot. Do not redirect all missing URLs to the homepage; irrelevant redirects can themselves be treated like soft 404s.
Not indexed: explicit website directives
URL blocked by robots.txt
Meaning: A rule in the site's robots.txt prevented Googlebot from crawling the URL.
Is action required? It depends on intent. Blocking unimportant crawl paths can be correct. If the page should be indexed with full content and a useful snippet, remove the blocking rule.
Important distinction: robots.txt controls crawling, not guaranteed indexing. Google may index a blocked URL from links or other evidence without fetching its content. If the goal is to prevent a public page from appearing in Search, allow crawling and use noindex; if the content is private, require authentication.
Check next: The robots.txt report/tester, URL Inspection's Crawl allowed? result, and the exact user-agent group and matching rule.
URL marked ‘noindex’
Meaning: Google crawled the page and found a noindex robots meta tag or X-Robots-Tag HTTP header.
Is action required? No when exclusion is deliberate. If the page should be indexed, remove every applicable noindex directive and ensure robots.txt allows Google to recrawl the page and see the change.
Check next: Inspect both rendered HTML and HTTP headers. Test the live URL after deploying the fix. Repeated indexing requests cannot override a live noindex directive.
Not indexed: discovery and indexing decisions
Discovered – currently not indexed
Meaning: Google knows the URL but has not crawled it yet. The last crawl date is empty. Google's report documentation says this commonly occurs when crawling was rescheduled because fetching the URL was expected to overload the site.
Is action required? Investigate when important URLs persist in this state or the affected group grows unexpectedly. On a new page or small sample, waiting can be reasonable.
Check next: Sitemap inclusion, crawlable internal links, server capacity and latency, Crawl Stats host status, duplicate or low-value URL inventory, faceted navigation, and whether Google is spending requests on unwanted URL variants.
Crawled – currently not indexed
Meaning: Google fetched the URL but did not add it to the index. It may be indexed later. Google's documentation explicitly says there is no need to resubmit the URL for crawling.
Is action required? Only when the URL is an important canonical page and the status persists across a meaningful group or period. The label does not by itself identify a technical failure.
Check next: Google-selected canonical, duplication, soft-404-like output, rendered main content, indexable file type, content purpose and originality, internal linking, sitemap accuracy, and whether the URL is actually a page intended for web search.
Not indexed: duplicates, alternates, and redirects
Alternate page with proper canonical tag
Meaning: The URL is a supported alternate of another page and correctly points to an indexed canonical. Google's examples include an AMP or separate mobile variant.
Is action required? Usually no. This status normally means consolidation is working.
Check next: Inspect the canonical URL and confirm that it is indexed, correct for users, and referenced consistently. Google notes that alternate-language pages are not detected by this Search Console status; use correct hreflang annotations for localized equivalents.
Duplicate without user-selected canonical
Meaning: Google considers the page a duplicate, no preferred canonical was declared, and Google selected another URL to serve.
Is action required? No if Google's choice is correct. If the wrong variant is selected, decide on a canonical and make redirects, rel="canonical", sitemap inclusion, and internal links consistently support it.
Check next: URL Inspection's Google-selected canonical, then compare the duplicate and selected page.
Duplicate, Google chose different canonical than user
Meaning: The site declared one canonical, but Google selected a different URL for the duplicate cluster.
Is action required? Only if Google's selected URL is genuinely worse for users or business requirements. A canonical declaration is a strong signal, not an absolute rule.
Check next: Compare the inspected URL, user-declared canonical, and Google-selected canonical. Look for conflicting redirects, sitemap URLs, internal links, hreflang, protocol/host variants, rendered canonicals, substantially different content, server misconfiguration, or an inaccessible preferred URL.
Page with redirect
Meaning: The inspected URL redirects, so it is not normally indexed as a separate page. The final destination may or may not be indexed.
Is action required? Usually no when the redirect is intentional and its destination is correct. Remove redirecting URLs from canonical sitemaps and update internal links to the final URL.
Check next: Inspect the final target separately. If the chain fails, use the Redirect error diagnosis instead.
Not found (404)
Meaning: Google requested a URL that returned 404. It may have been discovered from an internal link, external link, sitemap, old page, or malformed URL.
Is action required? Not automatically. A correct 404 for removed content without a replacement is healthy and does not need a redirect.
Check next:
- If the content moved, use a permanent redirect to the closest relevant replacement.
- If the URL should exist, restore it with a successful response.
- If it is submitted, remove it from the sitemap or fix the source.
- If it never existed and has no important links, leave the 404 in place.
Google currently treats 404 and 410 the same for Search processing.
Indexed warnings
Indexed, though blocked by robots.txt
Meaning: Google indexed the URL using information from links or other sources even though robots.txt prevents fetching its content. The result can have a limited snippet.
Is action required? Yes if either the indexing or the crawl block is unintended.
- To keep the page out of Search, remove the robots block, allow crawling, and provide
noindex; use authentication for private material. - To show the page normally, remove the robots block and let Google recrawl it.
Page indexed without content
Meaning: The URL is in the index, but Google could not read its content. Google lists cloaking or a non-indexable format as possible causes and distinguishes this from a robots.txt block.
Is action required? Yes for an important page.
Check next: Inspect the indexed evidence and live rendered page. Confirm the response has a supported content type, the main content is visible to Googlebot, essential resources load, and users and Google receive equivalent content.
Indexed
Page is indexed
Meaning: Google successfully indexed the page.
Is action required? No indexing fix is required. The URL can still have structured-data, page-experience, security, manual-action, ranking, or serving issues. “Indexed” also does not guarantee that the URL will appear for every search.
How to prioritize a mixed report
Prioritize by business and technical impact:
- Important canonical URLs newly affected by server, DNS, redirect, authorization, robots, or
noindexfailures. - Template-level changes that caused a corresponding fall in indexed pages.
- Important submitted URLs persistently deferred after discovery or crawling.
- Wrong canonical selection that sends users or performance attribution to an unsuitable URL.
- Broken internal links and stale sitemap entries producing avoidable 404s or redirects.
- Expected duplicates, redirects, removals, and intentional exclusions, which usually require monitoring rather than fixes.
Compare the trend with release dates, migrations, CDN or firewall changes, sitemap deployments, and server incidents. A large count is less useful than knowing which URL class changed and whether those URLs matter.
When to validate a fix
Use Validate fix after correcting all affected instances of a website-controlled reason. Validation is issue-wide, not a button that makes URLs indexable.
Google says validation typically takes up to about two weeks and can take longer. It first checks a sample, then recrawls known affected URLs. A remaining instance can fail the attempt. Google can also detect fixes during normal crawling even if you never start validation.
Do not validate intentional robots blocks, noindex pages, redirects, duplicates, or correct 404s merely to make a report row disappear.