How to Fix Indexing Issues in Search Console

Open the Search Console indexing report for a site that publishes regularly and you will almost always find one of two patterns. Either the total indexed page count is climbing steadily, or it is flatlined or falling while you keep publishing. The second pattern is the one that drives most of the desperate help posts, and it almost never has a single cause. The 2026 version of this story has gotten more interesting because Google's quality floor for indexation moved up. Pages that would have been indexed in 2022 with mediocre content get stuck in Discovered or Crawled, currently not indexed status today. Status-by-status diagnosis is the only way to fix it.

Quick Answer: Indexing issues in Google Search Console resolve through a status-specific workflow. Discovered, currently not indexed usually means crawl budget pressure or low priority signal, fixed with internal linking and sitemap submission. Crawled, currently not indexed usually means the quality floor issue, fixed with content depth and E-E-A-T improvements. Page with redirect requires redirect chain audit and consolidation to single hop. Soft 404 means content is too thin or pattern matches a known low-value template. URL Inspection tool is the per-page diagnostic. Some pages should be deliberately left unindexed (admin, thank-you, filter combinations) and the Indexing API is only useful for JobPosting and live BroadcastEvent content.

Reading the Search Console Indexing Report in 2026

The Indexing report under Pages in Search Console is the starting point for every diagnostic. The report groups URLs into Indexed and Not indexed buckets, then within each bucket categorizes by reason. The categorization is what makes the report useful because the fix for each reason is different.

The categories that show up most often in Not indexed:

• Discovered, currently not indexed
• Crawled, currently not indexed
• Page with redirect
• Soft 404
• Excluded by noindex tag
• Blocked by robots.txt
• Duplicate without user-selected canonical
• Duplicate, Google chose a different canonical than user

Within each category, you can drill into the specific URLs and see the URL Inspection result for each. The diagnostic workflow runs from the most common category downward, fixing the URLs in batches by category rather than one at a time.

Two patterns worth noting about how Google reports indexing in 2026:

• The reported indexed count lags reality by several days. A page that just got indexed may not show in the report yet.
• The report shows a sample of affected URLs, not the full list, when the affected count is large. Use Export to get the full sample available.

Discovered, Currently Not Indexed, Causes and Fixes

Discovered means Google found the URL through a sitemap or external link but has not crawled it yet. The most common causes are crawl budget pressure on large sites, low-priority signal on small sites, and very fresh pages that are still in the discovery queue.

The fixes by likelihood:

1. Confirm the URL is in your XML sitemap and the sitemap is fresh (last modified within 30 days)
2. Add internal links from at least three relevant pages with descriptive anchors
3. Submit the URL through URL Inspection's Request indexing button (limit 10 per day per property)
4. Confirm the page does not redirect, return 404, or carry a noindex tag
5. Check whether the page is part of a section Google deprioritized (low-quality pages nearby drag the whole section)

For sites under 10,000 pages, the issue is rarely crawl budget. The fix is internal linking. For sites over 100,000 pages, crawl budget is genuinely tight and the larger conversation in the crawl budget optimization guide covers the systemic fixes.

A useful diagnostic for Discovered status is to check whether the URL appears in the server access logs as a Googlebot fetch. If Googlebot has not visited the URL in 30 days, the issue is discovery and the fix is to surface the URL more aggressively through internal links and sitemap. If Googlebot visited but the URL is still in Discovered, the report is lagging and the URL will likely move to Indexed within days.

Crawled, Currently Not Indexed, the Quality Floor Issue

Crawled, currently not indexed is the most painful status because it means Google looked at the page and decided not to add it to the index. The cause is almost always quality, not technical. Google's quality assessment runs on a combination of content depth, E-E-A-T signals, topical fit with the rest of the site, and the engagement signals it has on similar pages.

The fixes that actually work, ranked by impact:

• Expand the content from 500 words to 1500 words with substantive new material (not padding)
• Add specific examples, data, and original observations (E-E-A-T uplift)
• Improve the byline with author bio, schema, and sameAs links
• Add three to ten internal links from authoritative pages on the same site
• Update the date and modify-time after the content changes are real
• Resubmit through URL Inspection

The fixes that rarely work:

• Pinging the URL through third-party tools
• Adding the URL to the sitemap a second time
• Submitting to the Indexing API (only works for JobPosting and BroadcastEvent)
• Asking Google support (no individual case escalation for indexing)

The hardest version of this issue is when an entire section of the site is in Crawled, currently not indexed. This usually means the section as a whole sits below the quality floor and Google deprioritized it. The fix is to audit the section, improve or remove the bottom 30 percent of pages by quality, and reaccept that a thin section drags the whole section down.

This is closely related to the content audit work covered in the content audit template guide, because the same scoring rubric identifies the pages that need to be improved or pruned.

Page With Redirect, Chain Detection and Resolution

Page with redirect means Google found the URL but the URL redirects to another URL. The status is informational rather than a problem when the redirect is a clean single hop. It becomes a problem when the redirect is a chain, the redirect loops, or the destination is itself redirected or 404.

The diagnostic workflow:

1. Check the URL with a redirect tracer (free tools include httpstatus.io and Screaming Frog list mode)
2. Identify the full chain from origin URL to final destination
3. Resolve every multi-hop chain to a single 301 hop
4. Update all internal links to point at the final destination, not the redirecting URL
5. Update the sitemap to contain only canonical final URLs

Common redirect mistakes that create chains:

• HTTP to HTTPS, www to non-www, and trailing slash redirects stacked rather than combined
• Old URL structure to new URL structure with intermediate intermediate steps from a prior migration
• Marketing tracking redirects that bounce through analytics platforms before landing on the destination
• Auth redirects that loop unauthenticated users

The performance and crawl cost of a chain matters. Each hop adds 200 to 800ms of latency and consumes crawl budget that could have gone to a different URL. The cleanup pays off in crawl efficiency on large sites and in page load speed on user-facing flows.

Soft 404, When Content Is Too Thin

Soft 404 is Google's pattern match for a page that returns a 200 status code but looks like a 404 page based on content patterns. The triggers are usually one of:

• Page is empty or near-empty (under 100 words of visible content)
• Page says some form of "Not found", "Sorry, no results", or "0 results"
• Page is a template that returned empty because the underlying data unit is missing
• Page is a search result page that returned no hits

The fixes:

• For genuinely empty pages, return a 404 status code (the cleanest fix)
• For pages that should not exist, redirect to the most relevant existing URL
• For thin pages on a real entity, expand the content above the quality floor (500 words minimum)
• For search and filter pages, noindex if the results are sparse, allow indexing if the results are useful

The pattern that catches a lot of sites by surprise is the search result page. If your internal search returns zero or very few results for a popular query and the page is indexable, Google will eventually flag it Soft 404. The fix is either noindex on the search result template or a fallback content block that explains the topic when results are thin.

URL Inspection Tool Workflow Step by Step

URL Inspection is the per-page diagnostic that gives you the canonical answer for any URL. The workflow runs four tests in order.

1. Search Console reported status. Open URL Inspection for the URL and read the headline. "URL is on Google" means indexed. "URL is not on Google" with a reason gives you the category to debug.

2. Coverage details. Click the Coverage panel to see the most recent crawl date, the discovered date, the indexing status, and any specific reason Google listed.

The Request indexing button at the top of URL Inspection submits the URL for priority crawling and re-evaluation. The limit is roughly 10 to 12 submissions per day per property. Use it for high-priority pages after fixing the underlying issue, not for general bulk indexing.

Quality Upgrades That Get Pages Indexed (With Examples)

When a page is stuck in Crawled, currently not indexed and the content is the cause, the specific upgrades that move pages into the index are usually concrete and small. Pages rarely fail to index because they are missing a single thing. They fail because they are below the quality floor across multiple dimensions and need a coordinated lift.

Worked example one. A 500-word blog post on "best Astro themes" sat in Crawled, currently not indexed for three months. The lift that indexed it: expanded to 1800 words with specific theme reviews, added author bio with schema, added three internal links from related Astro guides, added two screenshots from real theme demos, updated the publishDate to reflect the rewrite.

Worked example two. A pSEO city page sat in Crawled, currently not indexed alongside 200 sibling pages. The lift that indexed the section: rewrote the template to add 600 words of unique narrative per page, added conditional content blocks for cities with metro systems, deindexed the bottom 40 percent of pages that had thin underlying data, added a hub page linking to the surviving pages.

The pattern across these examples is that the lift is multi-dimensional. Adding 1000 words alone often does not work. Adding 1000 words plus E-E-A-T signals plus internal linking plus images plus a content date refresh tends to work within four to twelve weeks.

Pages You Should Deliberately Keep Unindexed

Not every page should be indexed. Some pages dilute site quality if indexed and the right move is a noindex tag rather than an attempt to lift them.

Pages that should always carry noindex:

• Admin, account, and login URLs
• Thank-you and confirmation pages after a conversion
• Internal search result pages with low result count
• Filter and sort URL combinations on faceted navigation that produce many similar pages
• Print versions and PDF mirrors of HTML pages
• Test or staging URLs accidentally exposed to crawlers
• Tag pages with fewer than three articles

Pages that should usually carry noindex but with case-by-case judgment:

• Author archive pages on small sites with one or two authors
• Date archive pages
• Empty category pages
• Pagination beyond page two for low-traffic listings
• Confirmation flows in multi-step checkouts

The noindex implementation that works most reliably is a meta robots tag in the page head with content="noindex, follow". The follow part keeps internal link equity flowing through the noindexed page. Robots.txt blocks are not the right tool for noindex because they prevent crawling and Google may still index based on external signals if the URL has inbound links.

Indexing API, When It Actually Helps

The Indexing API is Google's mechanism for pushing high-velocity content updates and Google explicitly limits its supported use to JobPosting and BroadcastEvent (live streams). Using the Indexing API for general blog or product content violates the documented usage policy and historically has produced no benefit even when sites have tried.

The cases where the Indexing API actually helps:

• Job board with high turnover where postings need immediate indexing and removal
• Live event sites where BroadcastEvent schema and content need to be live within minutes
• News sites that have integrated through the News Publisher Center workflow (different API but same indexing speed benefit)

The cases where the Indexing API does not help and may cause problems:

• General blog content
• E-commerce product launches (the right tool is sitemap and crawl health)
• Landing page launches
• Any content where the use case is "I want this indexed faster"

For the cases where the Indexing API does not apply, the standard tools (XML sitemap submission, URL Inspection request indexing, internal linking from existing high-authority pages) are the supported path. Sites that have built workflows around abusing the Indexing API for non-supported content types tend to lose those workflows quietly when Google enforces the policy.

For the broader concepts that pair with indexing diagnostics, the what is indexing primer covers the fundamentals. The what is index coverage primer covers how Google reports the status. Astro SEO Blog covers crawl-side issues in the companion crawl budget guide.

FAQ

Why does Google index some pages immediately and others never? Google's index allocation is a quality and relevance decision per URL, not a guarantee. Authoritative sites get faster indexing on new URLs because the site-level signal supports the page. New or thin pages on new domains often wait weeks. The fix is internal linking, content quality, and time.

Will requesting indexing on every page hurt my site? No, but it is rate limited to roughly 10 to 12 requests per day per property, so it does not scale. Use it for the few pages where you have made meaningful improvements and want priority re-evaluation. Bulk submission through sitemap is the scalable path.

How long should I wait before deciding a page will never be indexed? For new content, 30 days is the typical patience threshold. Within 30 days most healthy pages either get indexed or carry an obvious diagnostic signal in URL Inspection. After 30 days without indexing, intervene with content improvements rather than waiting longer.

Does my XML sitemap actually help indexing? Yes for discovery, modest for indexation. The sitemap tells Google which URLs exist and when they last changed. It does not override quality decisions. A page in the sitemap with thin content still does not get indexed. The sitemap is necessary but not sufficient.

Is the Indexing API ever worth trying for non-JobPosting content? No reliably. Google has been explicit that the API is scoped to JobPosting and BroadcastEvent, and the indexing benefit for other content types has not materialized in tests. The risk is using up your daily quota and getting an unsupported-content-type response.

My pages were indexed and now they are not. What happened? The most common causes are content quality degradation (the page is now thin relative to competitors), site-level quality drop (other pages on the site dragged the section down), and technical regression (a recent code change inadvertently added noindex or robots.txt block). URL Inspection identifies which of the three it is.

Should I delete pages that Google refuses to index? Sometimes. If the page has no real entity behind it and adding content would feel forced, deletion (with a 410 status) is honest. If the page has a real entity and the issue is quality, improvement is the better move. If the page is one of many in a thin section, pruning the bottom and improving the rest is often the right play.

Sources and Further Reading

Astro SEO Blog covers related diagnostic work in the crawl budget optimization guide, the content audit template, and the internal linking guide, all of which intersect with indexation.

External references for canonical guidance:

• Google Search Central's documentation on the Indexing report for the canonical category definitions.
• Google Search Central's URL Inspection tool guide for the per-page workflow.
• Search Engine Land's indexing coverage for industry analysis of indexing behavior.