Indexing issues occur when search engines do not add an important page to their search index, or when they select a different URL to represent similar content. A page may be technically live and accessible to visitors but still not appear in Google Search.
The first step is to identify what is actually happening. Is Google unable to discover the URL? Has it crawled the page but not indexed it? Is the page blocked by a noindex directive? Has Google selected another canonical URL? Each situation needs a different solution.
This guide explains how to diagnose common Google indexing problems using Search Console, how to fix them safely and how to monitor changes without assuming that a request for indexing guarantees inclusion.
What Is Indexing in SEO?
Indexing is the process in which a search engine analyses a page and may store information about it in its index. The index is the collection of content that the search engine can consider when responding to searches.
Being indexed makes a page eligible to appear in search results, but it does not guarantee rankings, impressions or traffic. Google decides which pages to index and how to present them.
Crawling vs. Indexing vs. Ranking
- Crawling: a search engine discovers a URL and fetches its content.
- Indexing: it analyses the fetched page and may store it in the index.
- Ranking: it selects and orders eligible results for a user’s search.
A page can be crawled but not indexed. A page can also be indexed but receive few impressions because it is not relevant or competitive for the searches people make. Read Website Crawling Explained and Technical SEO Explained.
How to Check Indexing Status in Google Search Console
1. Open the Page Indexing report
Choose the correct website property in Google Search Console and open the Indexing → Pages report. Review indexed and not-indexed URL groups. Look at trends and examples rather than treating every excluded URL as an error. Some exclusions are expected, such as redirects, alternate canonical URLs and pages intentionally marked noindex.
2. Inspect an individual URL
Paste the exact URL into the URL Inspection tool. Review whether the URL is known to Google, its reported indexing status, the user-declared canonical and Google-selected canonical when available, and the last crawl information.
3. Run a live URL test
Use Test Live URL to check whether Google can access the current page and inspect its current response. A live test is not the same as the stored index status. A successful test does not guarantee that Google will index the page.
4. Check the sitemap report
Open Indexing → Sitemaps to review submitted sitemap files and processing status. A sitemap can help discovery, but submission does not force Google to crawl or index every listed URL.
Common Google Indexing Statuses and What They Mean
Search Console uses status labels to describe why URLs are or are not indexed. The wording and examples shown can vary as Google’s reports evolve. Always inspect representative URLs before taking action.
| Status or situation | What it usually means | What to do |
|---|---|---|
| Crawled – currently not indexed | Google fetched the page but has not indexed it at this time | Review content value, duplication, canonical signals, internal links and overall site quality |
| Discovered – currently not indexed | Google knows the URL but has not crawled it yet | Check crawl demand, site health, URL duplication, internal links and server capacity |
| Excluded by noindex | A robots meta tag or X-Robots-Tag instructs search engines not to index the page | Keep it if intentional; remove the directive only if the page should be indexed |
| Blocked by robots.txt | The crawler is prevented from fetching the URL | Review the rule; allow access if Google needs to crawl the page |
| Duplicate, Google chose different canonical | Google selected another URL as the representative version | Check whether the selected canonical is appropriate and align signals if needed |
| Alternate page with proper canonical | The URL is an alternate version and points to a preferred canonical | Usually no action is needed if the canonical setup is intentional |
| Page with redirect | The URL redirects to another destination | Usually expected; ensure the target is relevant and internal links use the final URL |
| Not found (404) | The server reports that the URL does not exist | Restore it or redirect to a close replacement if one genuinely exists |
| Server error (5xx) | Google could not fetch the page because the server failed | Investigate hosting, application errors, timeouts and server capacity |
| Soft 404 | The page appears to contain no real content or an error despite returning a success response | Provide useful content or return the correct not-found status |
How to Fix the Most Common Indexing Issues
1. Crawled – currently not indexed
This status means Google crawled the URL but did not add it to the index at that time. It does not automatically mean there is a technical error or a penalty.
Review the page carefully:
- Does it provide original, useful information that satisfies a clear search need?
- Is it substantially similar to another page on your website or elsewhere?
- Does it have a clear purpose, enough useful detail and a good user experience?
- Does the canonical tag point to the intended URL?
- Can users and crawlers reach it through relevant internal links?
- Does the page return a successful response and avoid accidental noindex directives?
Improve the page where there is a real content gap. Merge or redirect pages only when they genuinely overlap and a relevant destination exists. Do not add words merely to reach an arbitrary word count.
2. Discovered – currently not indexed
Google knows the URL but has not crawled it yet. Possible reasons include low crawl demand, a large or confusing URL inventory, weak discovery paths or site availability issues.
- Add useful internal links from relevant, already accessible pages.
- Include the preferred URL in an accurate XML sitemap.
- Remove unnecessary URL variations and avoid generating endless filter combinations.
- Check server response stability and Search Console Crawl Stats.
- Confirm that the page is not blocked by access controls or incorrect rules.
Do not repeatedly submit the same URL. Improve discovery and site health, then allow Google to revisit it.
3. Incorrect noindex directive
A page may contain a robots meta tag such as <meta name="robots" content="noindex">, or the server may send an X-Robots-Tag header. This tells compliant search engines not to index the page.
If the page should be indexed:
- Check the page source and response headers.
- Review SEO plugin settings, CMS visibility options and template rules.
- Remove the unintended noindex directive.
- Confirm the page is accessible to the crawler.
- Run a live URL test and monitor the index status over time.
Do not remove noindex from private, thank-you, internal search or other pages that should stay out of search.
4. Blocked by robots.txt
Robots.txt controls crawler access; it does not reliably remove a URL from the index. If Google needs to see a page-level noindex directive, the page must be crawlable so the directive can be fetched.
Review the live robots.txt file and check whether a broad Disallow rule is blocking important content. Change only the rule that is wrong. See Robots.txt Explained and Google’s robots.txt documentation.
5. Duplicate page and canonical conflicts
Similar URLs can arise from tracking parameters, filters, product variants, HTTP/HTTPS, www/non-www versions and trailing-slash differences. Use redirects and canonical annotations consistently to indicate the preferred version.
Check that:
- The canonical URL is the version you actually want indexed.
- Internal links point to the preferred URL.
- The sitemap lists canonical URLs rather than duplicates.
- Redirects lead directly to the correct destination.
- Canonical tags are not pointing to unrelated pages.
Google treats canonical tags as signals and can choose a different canonical. Learn more in Canonical Tags Explained.
6. Page returns 404 or soft 404
If a page has been removed permanently and no relevant replacement exists, a genuine 404 or 410 response is appropriate. If the content has moved, use a relevant permanent redirect. If the page should exist, restore it and return a successful response.
A soft 404 can occur when a page returns HTTP 200 but communicates that content is missing or provides almost no useful content. Make the page useful or return the correct status code. Avoid redirecting unrelated missing URLs to the homepage.
7. Server errors and access problems
Repeated 5xx responses, timeouts, DNS failures and access restrictions can prevent Google from fetching pages. Check hosting logs, application errors, firewall rules, CDN settings and uptime monitoring. Make sure legitimate crawlers are not accidentally blocked or rate-limited.
8. JavaScript or rendering problems
If important text or links appear only after scripts run, check the rendered page and browser console for errors. Ensure essential content is available to search engines and use crawlable links with real destinations. Test representative pages with URL Inspection and review Google’s JavaScript SEO guidance.
9. Thin, duplicate or low-value content
Pages with little original value, near-duplicate location pages, automatically generated combinations or copied descriptions may not be selected for indexing. Improve the page by adding information that genuinely helps the reader: first-hand examples, useful comparisons, accurate details, clear answers and relevant supporting resources.
If multiple pages serve the same intent and have no distinct purpose, consider consolidating them. Preserve useful URLs and plan relevant redirects before removing pages.
Why Submitting a URL for Indexing Does Not Guarantee Indexing
The Request Indexing feature in URL Inspection can be useful after publishing a new page or making a meaningful change. It asks Google to consider crawling the URL. It does not guarantee that the page will be crawled immediately, indexed or ranked.
For many URLs, maintain an accurate sitemap and a strong internal linking structure rather than submitting every page manually. Repeated requests do not make a low-value or blocked page eligible for indexing.
Indexing Checklist for WordPress Websites
- Confirm the post or page is publicly published, not draft, private or password-protected.
- Check that the SEO plugin has not added an unintended noindex directive.
- Review the canonical URL generated by the page template.
- Check robots.txt and ensure important content is crawlable.
- Confirm the URL returns the expected HTTP status.
- Ensure the preferred URL appears in the XML sitemap.
- Add relevant internal links from related posts, categories or service pages.
- Check for duplicate content, thin archives and unnecessary tag pages.
- Inspect the URL in Google Search Console and run a live test.
- After a meaningful fix, monitor the status instead of repeatedly requesting indexing.
How to Prioritise Indexing Fixes
Not every excluded URL deserves the same effort. Prioritise based on business value, search demand, page purpose and the scale of the issue.
| Priority | Examples | Suggested response |
|---|---|---|
| High | Important service page blocked, accidental noindex on key landing page, site-wide server errors | Investigate and fix promptly; verify key URLs |
| Medium | Valuable article crawled but not indexed, canonical mismatch on a key category | Review content and signals; improve and monitor |
| Low or expected | Redirect source URLs, intentional noindex pages, duplicate alternates with correct canonicals | Document and leave unchanged when behaviour is intentional |
How Long Does Indexing Take After a Fix?
There is no fixed timeline. Google may revisit a page at a different time depending on its systems, crawl demand and site conditions. Some changes can be processed relatively quickly, while others take longer or may not lead to indexing at all.
Track the date of the change, the affected URLs and the Search Console status. Do not promise a specific number of days for indexing or ranking recovery.
Frequently Asked Questions
Why is my website not indexed by Google?
Possible reasons include poor discovery, a noindex directive, robots.txt restrictions, server errors, canonical selection, duplicate content or limited page value. Use URL Inspection and the Page Indexing report to identify the specific reason.
What does crawled – currently not indexed mean?
It means Google fetched the URL but has not indexed it at the time of reporting. Review content value, duplication, canonical signals, internal links and technical accessibility. It is not automatically a penalty.
What does discovered – currently not indexed mean?
It means Google knows the URL but has not crawled it yet. Improve internal discovery, maintain an accurate sitemap, review URL duplication and check site availability.
Can I force Google to index a page?
No. You can make a page accessible, useful and easy to discover, then request indexing where appropriate. Google makes the final decision about crawling and indexing.
Does noindex affect crawling?
Noindex is an instruction about indexing, not a crawl block. The crawler needs to access the page to read the directive. If robots.txt blocks the page, the crawler may not see the noindex tag.
Should every URL in my sitemap be indexed?
No. A sitemap should list the important canonical URLs you want search engines to discover. Google does not promise to index every submitted URL.
Can duplicate content cause indexing problems?
Similar pages can lead Google to select one canonical version and leave alternate URLs out of the index. Use consistent canonical and redirect signals, and consolidate pages when they genuinely serve the same purpose.
Does requesting indexing improve rankings?
No. Requesting indexing is a crawl request, not a ranking boost. Rankings depend on many systems and signals, and indexing alone does not guarantee visibility.
Official Google Resources
- How Google Search works
- Search Console Page Indexing report
- URL Inspection tool
- Robots.txt documentation
- Consolidate duplicate URLs
Final Thoughts
Indexing problems are easier to solve when you diagnose the exact status instead of treating every excluded URL as an error. Start with Search Console, inspect the affected URL, check access and indexing directives, review canonical signals and evaluate whether the page offers distinct value.
Fix the cause, verify the live page and monitor the result. A clean sitemap, useful internal links, reliable hosting and helpful content create a stronger foundation—but Google always makes the final decision about indexing. For the wider technical picture, continue with the Technical SEO Checklist.