Home → Pages Not Indexing
Find the exact Search Console status first
Pages Not Indexing: What Your Search Console Report Means
An unindexed URL is not automatically a fault. The useful question is which important pages are missing—and what reason Google reports for each one.
Not every URL should be indexed
Google’s Page indexing documentation makes the distinction clear: duplicate, alternate, removed and deliberately excluded URLs can all be absent from the index for valid reasons.
So the target is not a 100% indexed score. It is to have each important canonical page available for indexing and every intentional exclusion behaving as intended.
Find the status you are looking at
Open Search Console → Pages, then select the reason shown under Why pages aren’t indexed. For a single URL, Google recommends using URL Inspection.
| Status | What it means | What to check |
|---|---|---|
| Crawled – currently not indexed | Google crawled the page but has not indexed it. It may be indexed later; Google says there is no need to resubmit it for crawling. | Stop repeatedly requesting indexing. Check whether the page is important, substantially useful, duplicated elsewhere, internally linked and intended as the canonical version. |
| Discovered – currently not indexed | Google knows the URL exists but has not crawled it yet. Google may defer crawling when it predicts that doing so could overload the site. | New URLs may simply need time. If the status persists across many important pages, inspect server availability, crawl patterns, internal links and sitemap inclusion. |
| Excluded by ‘noindex’ tag | Google found a directive telling it not to index the page. | Decide whether the exclusion is intentional. On a new or rebuilt site, check WordPress, the SEO plugin and any page-level settings. |
| Alternate page with proper canonical tag | The URL is an alternate version of another page that Google treats as canonical. | Usually nothing, provided the selected canonical is the version you intended. |
| Duplicate, Google chose different canonical than user | You declared one canonical, but Google selected a different URL as the representative version. | Inspect the Google-selected canonical, then align canonical tags, internal links, redirects, sitemap URLs and content signals where they conflict. |
| Blocked by robots.txt | A robots.txt rule prevents Googlebot from crawling the URL. | Check whether the block is intentional. Remember that robots.txt controls crawling; it is not the recommended way to prevent a URL appearing in search. |
| Not found (404) | The URL returned a not-found response. | Fine if it was removed deliberately and has no replacement. If the content moved, redirect to the closest genuine replacement and update internal links. |
| Page with redirect | The URL redirects, so that URL itself is not indexed. | Normal after a site change when the redirect leads directly to the correct destination and is not part of a chain or loop. |
Indexed result or live test: what is the difference?
| Check | What it tells you | What it does not confirm |
|---|---|---|
| Indexed result | Google’s stored information from its last processing of the URL. | Whether the page has changed since Google last crawled it. |
| Live URL test | Whether Google can access and assess the page now. | That Google has indexed it or selected it as canonical. |
Which issue should you check first?
| Situation | Starting point |
|---|---|
| A key page has an unintended noindex | Check the page and site settings, correct the directive and inspect the live output. |
| Google selected a different canonical | Compare both pages and their canonical tags, redirects, sitemap entries and internal links. |
| A page was crawled but not indexed | Check whether it has a distinct purpose, useful content and links from relevant pages. |
How to check one page with URL Inspection
- Paste the full URL into the inspection bar at the top of Search Console and read the indexed result and reported reason.
- Open Page indexing and compare the user-declared canonical with the Google-selected canonical. If they differ, investigate the signals pointing to each version.
- Check the last crawl, whether crawling and indexing were allowed, and any reported fetch issues.
- Select Test live URL to check the current page. A successful live test does not mean Google has indexed it or selected it as canonical; it cannot predict Google’s selected canonical.
- After correcting an issue, you can request indexing once. A request does not guarantee indexing or immediate crawling.
For a fix affecting multiple URLs, use Validate fix on the relevant Pages report issue where available. Validation can take time and does not guarantee indexing.
The status that catches newly launched sites
Excluded by ‘noindex’ tag
If most pages on a recently built or rebuilt WordPress site show this reason, the cause is often a site-wide setting.
WordPress has a “Discourage search engines from indexing this site” option under Settings → Reading, and SEO plugins can add their own site-wide or page-level controls. These are useful during development and easy to leave enabled at launch.
Check the live page’s robots meta tag and HTTP response before changing anything. Removing noindex makes the page eligible for indexing; it does not guarantee that Google will index it.
Our WordPress SEO checklist shows where to find the relevant settings and check the live page.
“Crawled – currently not indexed” needs diagnosis, not repeated submission
This status confirms that Google reached the URL. It does not confirm that the page is otherwise technically sound, unique, useful or the version Google wants to index.
On small service sites, three patterns are worth checking first:
The right outcome may be to improve the page, consolidate it into a stronger page, correct conflicting signals or accept that the URL does not need to be indexed. Repeated submission is not a substitute for deciding what job the page performs.
When it is worth investigating properly
A handful of deliberately unindexed or duplicate URLs is normal. Investigate when:
- important service or location pages are missing
- the number of indexed pages fell suddenly
- a whole template or section is excluded
- the reported reason does not match what you intended
- the same important URLs remain affected after the underlying problem was corrected
Which fixes can you investigate yourself?
Check the reason and preserve the current settings before changing anything. Get help if the change affects many pages or you cannot identify what a rule protects.
| Situation | First check | When to seek help |
|---|---|---|
| Site-wide noindex after launch | Check WordPress Settings → Reading and your SEO plugin, then verify the live directive. | The directive remains after the intended setting is corrected. |
| One page has unintended noindex | Check its SEO settings and live robots directives. | The setting returns or a template or plugin may be involved. |
| Content moved | Use a permanent redirect to the closest genuine replacement and update links. | Many URLs changed or a migration needs a redirect plan. |
| Google chose another canonical | Compare both pages, canonicals, internal links and sitemap entries. | Several similar pages require a decision about which version to keep. |
| Crawled but not indexed | Review the page’s purpose, usefulness, links and duplication; indexing is not guaranteed. | Important pages or a whole section remain affected. |
| Blocked by robots.txt | Check whether the rule is intended; robots.txt controls crawling rather than reliably preventing indexing. | You cannot tell what the rule protects. |
Our guide to location pages competing explains how to investigate overlap before merging pages.
Common questions about indexing
How long does Google take to index a new page?
There is no fixed time. Google may take days or longer and does not index every page. Links from relevant existing pages can help discovery.
Does submitting a sitemap force indexing?
No. A sitemap helps Google discover URLs but does not guarantee crawling or indexing.
Should I keep requesting indexing?
No. After correcting a problem, a request can prompt recrawling, but repeated requests do not speed it up or guarantee indexing.
Is “Page with redirect” a problem?
Usually not when the redirect is intentional and leads directly to the right destination. Check the destination itself; a redirect does not guarantee it will be indexed.
Check the reason before choosing the fix
That is the diagnostic side of Technical SEO: crawling, indexing and rendering, with findings checked against the live page and what Google actually reports. Our SEO audit with implementation costs £695 for eligible sites and includes agreed priority fixes within its confirmed scope. If the issue followed a rebuild, see traffic lost after a redesign. For broader visibility changes, see what to check when rankings drop.
Ask us to check your indexing
0115 646 9772 · Email us
Last reviewed: 21 September 2026 by David, founder.