Google Indexing Troubleshooting in 2026: Fix Crawled, Discovered, Canonical, and Sitemap Issues

A page can be live, linked, and included in a sitemap without appearing in Google. That does not always mean something is broken. Search engines discover URLs, decide whether and when to crawl them, interpret canonicals, evaluate duplicates, and choose which pages are useful enough to index.

The fastest way to solve indexing problems is to stop treating every status as the same problem. “Discovered – currently not indexed” is different from “Crawled – currently not indexed.” A canonical conflict is different from a noindex tag. A blocked resource is different from a thin duplicate page.

This guide gives you a practical troubleshooting order. The goal is not to force every URL into the index. The goal is to make sure important, useful, canonical pages are easy to discover, technically eligible, and worth indexing.

Start With the URL Inspection Tool

Open Google Search Console and inspect the exact URL. The URL Inspection tool can show whether the page is indexed, what canonical Google selected, whether crawling is allowed, when the page was last crawled, and whether Google encountered a specific problem.

Ask these questions first

Is indexing allowed?
Does the page return a normal 200 response?
What canonical does the page declare?
What canonical did Google choose?
Is the URL in a submitted sitemap?
Can Google reach it through internal links?
Is the content meaningfully different from other pages?

Answering these questions usually narrows the problem quickly.

Understand “Discovered – Currently Not Indexed”

This status generally means Google knows the URL exists but has not crawled it yet. That can happen on large sites, new sites, low-priority sections, or sites that create URLs faster than useful content can be reviewed.

Check internal discovery

A page that exists only in an XML sitemap has weaker context than a page linked naturally from a category, hub, navigation path, or related article. Add internal links from relevant pages if the URL matters.

Check for low-value URL growth

Faceted navigation, search pages, tag archives, calendar archives, tracking parameters, and automatically generated pages can create thousands of URLs. If most of them have little unique value, search engines may spend less attention on individual new pages.

Do not request indexing for hundreds of weak URLs

The indexing request feature is useful for important pages and testing, not as a replacement for good site architecture. Fix discovery and quality at the template level.

Understand “Crawled – Currently Not Indexed”

This status means Google fetched the page but did not add it to the index at that time. The reason may involve duplication, weak usefulness, soft error signals, canonical interpretation, or the broader quality of the page.

Compare the page against similar URLs

Search your site for near-duplicates. If five articles answer the same question with small wording changes, Google may choose only one or none of the weaker versions.

Check whether the page really solves a distinct problem

A 2,000-word article can still be thin if it repeats generic advice without examples, evidence, or a clear purpose. Length is not uniqueness.

Review the rendered page

Make sure the important content is present when the page renders. If a JavaScript error prevents the main content from appearing, a crawler may receive a very different page from the one you expect.

Check for Accidental Noindex Directives

One of the simplest causes is an explicit instruction not to index the page.

Places to check

A meta robots tag with noindex.
An HTTP X-Robots-Tag header.
SEO plugin settings on the individual post.
Taxonomy or post-type settings in an SEO plugin.
Staging-site settings copied to production.

In WordPress, review the page’s SEO settings and the site’s “Discourage search engines” option. Do not assume a sitemap entry overrides noindex. It does not.

Do Not Confuse Robots.txt Blocking With Noindex

A robots.txt rule controls crawling, not indexing in the same way a noindex directive does. If Google cannot crawl a URL, it may not see page-level directives or content.

Use the current guidance in Google Search Central’s robots.txt documentation when changing rules.

A common mistake

A site owner wants to remove a page from search, so they block it in robots.txt and add noindex. Because the crawler cannot fetch the page, it may not process the noindex instruction. If your goal is removal, make sure Google can access the directive long enough to process it, unless another removal method is more appropriate.

Inspect Canonical Tags Carefully

A canonical tag tells search engines which URL you prefer when similar pages exist. It is a strong hint, not a command.

Self-canonical important pages

Most standalone content pages should point their canonical to the clean preferred version of themselves. Check for templates that accidentally canonicalize every page to the homepage, category, or another article.

Watch for parameter variations

Tracking parameters, sorting options, and campaign URLs can create duplicates. Canonicals can help consolidate clean versions, but the site should also avoid generating unnecessary crawl paths to endless parameter combinations.

When Google chooses a different canonical

If Search Console shows “Google-selected canonical” different from your declared canonical, compare the pages. Are they nearly identical? Do internal links point mostly to the other URL? Does the sitemap list both? Is one version faster, cleaner, or more complete?

Make all signals consistent around the URL you actually want indexed.

Use XML Sitemaps as a Clean List of Preferred URLs

An XML sitemap should mainly contain canonical, indexable URLs you want search engines to discover.

Remove noisy entries

Do not include redirected URLs, obvious duplicates, noindex pages, or broken URLs. A clean sitemap does not guarantee indexing, but it gives clearer discovery signals.

Split large sitemaps logically

Many SEO plugins create separate sitemaps for posts, pages, categories, and other types. This can make monitoring easier because you can see which section has problems.

Submit the sitemap through Search Console and review the indexing reports for patterns rather than focusing on one URL at a time.

Check HTTP Status Codes and Soft 404 Signals

An indexable page should normally return a proper 200 status. Redirect chains, server errors, and soft 404s can interfere with indexing.

What is a soft 404?

A page may return 200 but look like an error or empty page. Examples include “product not found,” empty search result pages, or pages with almost no main content. Search engines can treat them as missing even without a 404 status.

Use the correct response

If the content is genuinely gone and has no replacement, a 404 or 410 can be appropriate. If it moved, use a relevant redirect. If it exists, make sure the page contains the expected content and returns 200.

Review Internal Links to the Page

Important pages should not depend only on sitemaps. Internal links explain how the page belongs to the site.

Link from relevant, useful pages

Add links from a topic hub, category page, navigation element, or related article where a reader would benefit. Avoid sitewide links to hundreds of unimportant pages.

Use the preferred URL consistently

If internal links alternate between HTTP and HTTPS, www and non-www, trailing-slash and non-trailing-slash versions, or parameterized URLs, clean them up. Consistent internal URLs reduce ambiguity.

Check Duplicate and Near-Duplicate Content

Duplicate content is not only exact copying. Programmatic pages can differ by a few words while serving the same purpose.

Common sources of duplication

Location pages with only the city name changed.
Tag and category pages that repeat the same article list.
Printer-friendly or AMP-like alternate versions left after a migration.
Product variants with no distinct information.
Search and filter pages indexed by mistake.
AI-generated pages built from one template with minimal original value.

Consolidate where possible. Give distinct pages a distinct job, evidence, and content.

Make New Pages Worth Discovering

When many new pages remain unindexed, the solution may be editorial rather than technical.

Improve the page’s unique value

Add first-hand examples, screenshots, clear procedures, comparison criteria, original data, expert input, calculators, templates, or local information where appropriate. A page should contribute something beyond a generic summary.

Strengthen the surrounding cluster

A new article is easier to understand when it sits inside a clear topic structure. Link it from a hub and related articles. Make sure the parent category has a purpose and is not just an endless archive.

JavaScript Indexing Issues: Check the Rendered Result

Modern search engines can render JavaScript, but heavy client-side sites can still create complications.

Important content should be reliable

If the title, main article, product details, or navigation fail without a client-side request, test how the page renders for crawlers. Server-side rendering or pre-rendered HTML can make critical content more robust, depending on the application.

Do not hide links behind interactions only

If related pages become available only after a user clicks a complex JavaScript widget, crawlers may not discover them as reliably as normal anchor links.

Indexing Problems After a Site Migration

Migrations can create large-scale indexing confusion when URL changes, canonicals, redirects, sitemaps, and internal links disagree.

Migration checklist

Redirect every important old URL to its closest new equivalent.
Update internal links to new URLs.
Generate fresh XML sitemaps.
Confirm canonical tags use the new domain and URL format.
Remove staging noindex settings.
Check robots.txt on the production domain.
Monitor server errors and crawl activity.

Do not redirect all old URLs to the homepage. Preserve topic relevance whenever possible.

When to Use Request Indexing

Use the URL Inspection tool’s request option after you fix an important page or publish a high-value new page. It can help with discovery, but it does not guarantee indexing.

Good use cases

A corrected canonical, a page that was accidentally noindexed, an important new service page, or a major content refresh.

Poor use case

Requesting indexing repeatedly for hundreds of thin pages while the underlying quality or duplication problem remains.

A Real-World Example: 300 Pages Not Indexed

Imagine a site publishes 300 city pages for one service. Each page has the same paragraphs with only the city name changed. Search Console shows many as crawled but not indexed.

The first instinct may be to request indexing for all 300. A better diagnosis asks whether all 300 deserve separate URLs. If the company truly serves those areas, the team can consolidate weak pages into meaningful regional resources or rebuild high-value city pages with unique local information, service availability, case examples, logistics, and real customer needs.

The fix is not “crawl harder.” The fix is giving each indexed page a reason to exist.

Google Indexing Troubleshooting Checklist

Inspect the exact URL in Search Console.
Confirm a 200 response for live content.
Check noindex directives and SEO plugin settings.
Review robots.txt for accidental blocks.
Verify the declared and selected canonical.
Keep XML sitemaps clean and current.
Check internal links and URL consistency.
Look for duplicate or near-duplicate pages.
Review the rendered page for JavaScript failures.
Improve unique value when technical checks are clean.
Use redirects only to relevant replacements.
Request indexing after meaningful fixes, not as a bulk workaround.

Conclusion: Diagnose the Status Before Trying to Force the Index

Indexing problems become easier when you separate discovery, crawling, technical eligibility, canonical selection, and content usefulness. A discovered URL may need better internal linking. A crawled but unindexed page may need stronger differentiation. A canonical conflict needs consistent signals. A noindex page needs a technical correction.

Use Google Search Central’s crawling and indexing guidance for current platform behavior. Then fix the underlying cause rather than repeatedly submitting the same URL.

Your goal is not to index every page your CMS can generate. Your goal is to make the pages that matter easy to discover, technically clean, clearly canonical, and genuinely useful.