Back to articles

Search Console Validate Fix: What It Checks, Why Validation Fails

SEOReport Team·
search-consolevalidate-fixpage-indexing-reportindexingtechnical-seo

How Validate fix in Search Console rechecks a Page Indexing issue, what each validation state means, why validation failed, and how to verify a fix first.

"Validate fix" asks Google to recrawl the URLs listed under one Page Indexing issue and confirm the issue is gone from each of them. Google says it typically takes up to about 2 weeks and sometimes much longer, and it stops as soon as Google finds one URL that still has the issue. So the real work is making sure your fix reaches every URL the issue covers, which you can check yourself before you click.

What happens after you click "Validate fix"

The button sits on each issue's details page, reached from a row in "Why pages aren't indexed". Google's Page Indexing report documentation (checked October 2026) describes the sequence:

  1. An immediate spot check. "When you click Validate Fix, Search Console immediately checks a few pages." If any of them still shows the issue, validation ends at once and the state stays where it was.
  2. A queue of known URLs. If the spot check passes, the state becomes "Started", and Google queues the URLs it knows have this issue for recrawling. It does not recrawl your whole site.
  3. URL-by-URL results. Each recrawled URL either no longer has the issue, still has it, or could not be reached. If the first URL rechecked is fixed, the issue moves to "Looking good". A URL that still has the issue moves it to "Failed" and ends the validation.
  4. A notification at the end. Search Console notifies you when validation succeeds or fails.

Two details matter. If you filtered the report by a sitemap before clicking, validation covers only the URLs in that sitemap at the moment you clicked. And Google keeps crawling normally during validation: a new URL it finds with the same issue counts as another instance of that issue.

yesnoyesnonoyesClick Validate fixIssue still on the first fewpages checked?Validation ends, stateunchangedStartedGoogle recrawls thequeued URLsIssue still on a recheckedURL?FailedLooking goodAll queued URLs checked?PassedFix the remaining URLs,then Start new validation
Diagram source
flowchart TD
    A["Click Validate fix"] --> B{"Issue still on the first few pages checked?"}
    B -->|yes| C["Validation ends, state unchanged"]
    B -->|no| D["Started"]
    D --> E["Google recrawls the queued URLs"]
    E --> F{"Issue still on a rechecked URL?"}
    F -->|yes| G["Failed"]
    F -->|no| H["Looking good"]
    H --> I{"All queued URLs checked?"}
    I -->|no| E
    I -->|yes| J["Passed"]
    G --> K["Fix the remaining URLs, then Start new validation"]

What each validation state means

Search Console tracks state at 2 levels: the issue as a whole, and each URL inside the request. Paraphrasing Google's definitions:

Issue"Not started"Some URLs with this issue have never been part of a validation request
Issue"Started"Validation is running and no remaining instance has been found yet
Issue"Looking good"Every URL checked so far is fixed
Issue"Passed"All known instances are gone, or the URLs are no longer available
Issue"N/A"Google saw the issue fixed on all URLs without a validation request
Issue"Failed"Pages still had the issue after you clicked
URL"Pending"Queued; the issue was present the last time Google looked
URL"Passed"Google rechecked and the issue is gone
URL"Failed"Google rechecked and the issue is still there
URL"Other"Google could not reach the URL

"Other" is not a failure: Google treats it the same as "Passed", and it does not end the validation. "N/A" is a reminder that validation is optional: Google notices fixes during regular crawling and can bring an issue's count to zero without a request.

How long validation takes

Google's documentation says validation "typically takes up to about two weeks, but in some cases can take much longer". Google gives no per-URL schedule. Because the request stays open until every queued URL has been recrawled, an issue whose URLs Google rarely visits, such as deep archive pages, can stay open longer than one on pages Google crawls often.

Do not click "Validate fix" again while a request is running; Google asks you to wait for a cycle to finish before requesting another.

To shorten the wait, Google suggests submitting a sitemap that contains only your most important pages, then filtering the report by that sitemap before validating, so the request covers fewer URLs. For a handful of critical pages, "Request indexing" in URL Inspection asks for a recrawl of that one URL; it has a daily limit and, in Google's words, "does not guarantee that the page will appear in the Google Index".

Which issues to validate, and which to leave alone

Validation passes only when the URLs stop having the issue, so an intentional status fails by design. Before clicking, decide whether the issue is a defect at all:

  • "Page with redirect" is normal for URLs you deliberately redirected; the Page with redirect guide separates the two cases.
  • "Alternate page with proper canonical tag" is usually Google working as intended, as covered in Alternate page with proper canonical tag.
  • "URL blocked by robots.txt" and "URL marked 'noindex'" are often deliberate; Google's documentation notes that robots.txt-blocked URLs are probably blocked on purpose. See URL marked 'noindex'.
  • "Crawled - currently not indexed" is Google's own indexing decision, and it often includes pages you do not need indexed, such as thin archive or filter pages. Validate only after improving the pages you want indexed; the crawled, not indexed guide explains how to tell them apart.

Why validation fails: 6 common causes

Google's documentation defines "Failed" by a threshold of pages still having the issue, but also says validation stops at a single remaining instance. Plan as if one unfixed URL fails the request.

1. The fix covered one template, but the issue spans several. An issue such as "Soft 404" or "URL marked 'noindex'" groups URLs by symptom, not by cause. Fixing the product template leaves the same issue on category pages built from a different template. The examples table in the report shows at most 1,000 URLs and, per Google, does not necessarily show every URL with the issue, so a fix built only from that list can miss whole URL patterns.

2. A cache still serves the old response. A page cache, CDN or static HTML cache can keep serving the old noindex tag, the old 404 or the old redirect for hours or days after the deploy. Google recrawls the URL and receives the cached version. robots.txt has its own delay: Google's robots.txt documentation says it generally caches the file for up to 24 hours. After changing robots.txt, use "Request a recrawl" in the robots.txt report.

3. The sitemap still lists URLs that keep the issue. Teams fix the pages they keep and forget the sitemap entries for pages they removed, redirected or noindexed. Those URLs still have the issue when Google rechecks them, so they fail the request, and filtering by that sitemap does not help because they are in it. A deleted page keeps returning 404, and validation does not make Google forget it: redirect it to an equivalent page, or drop it from the sitemap and leave that 404 unvalidated.

4. New URLs with the same issue appear during validation. If a CMS keeps generating tag pages, filter combinations or paginated archives with the same defect, Google finds them through normal crawling and counts them as new instances. Fix the source that creates them, not only the existing URLs.

5. The fix landed on a different host or version than Google checks. A change deployed to https://www.example.com does nothing for URLs listed as http://example.com/... if that host serves its own copy. A rollback, a plugin update that restores a setting, or a fix visible only to logged-in sessions has the same effect.

6. Some URLs in the issue are meant to keep it. An issue such as "URL marked 'noindex'" can mix product pages you just opened with thank-you or account pages that should stay noindexed. Validating the whole issue fails on the pages you kept. Filter by a sitemap that lists only the URLs you changed, then validate.

Sitemaps that still list URLs you meant to fix

In 29 external sites whose sitemap pages SEOReport fetched (May–October 2026), 8 (28%) had at least one sitemap URL that redirects, is marked noindex, or is blocked by robots.txt.

Sitemap entries that send mixed signals, 29 external sites, May–Oct 2026

Each such entry asks Google to index a URL that another signal says not to index, and will fail validation of the matching issue; clean them before validating with a sitemap filter. The XML sitemaps guide covers keeping the list to final, indexable URLs.

Verify the fix yourself before you click

Run the checks Google will run, on one URL from every template the issue touches. Start with the raw response:

bash
# Status and headers, without following redirects
curl -sI https://www.example.com/products/blue-widget/
# Every redirect hop, if there are any
curl -sIL https://www.example.com/products/blue-widget/ | grep -iE '^(HTTP/|location)'
# A robots meta tag or canonical in the HTML the server returns
curl -s https://www.example.com/products/blue-widget/ | grep -iE '<meta[^>]+robots|rel="canonical"'

Read the headers for evidence of a cache:

http
HTTP/2 200
content-type: text/html; charset=UTF-8
cache-control: public, max-age=86400
age: 41230
x-robots-tag: noindex

An age header means the response came from a cache; 41,230 seconds is about 11 hours old. Here the noindex header is still being served, so purge the cache before validating.

Then confirm with Google's own fetch. In URL Inspection, click "Test live URL", then "View tested page" to see the HTML and, under "More info", the HTTP response headers Google received. The live test only confirms that Google can access the page for indexing. It does not check sitemaps, duplicate status or Google's canonical choice, which is decided at indexing time.

Finally, check what still points at the old URLs: sitemap, navigation and internal links. A spot check, by hand or with an AI assistant, confirms one URL; an issue that spans templates needs one check per template, the coverage problem behind why one AI session cannot audit a whole website. A full SEOReport diagnosis examines the pages your sitemap lists, names each one that answers with an error, redirects, carries noindex or is blocked by robots.txt, and states how many pages it examined. Google's validation remains the record of whether Google agrees; a later report, or weekly monitoring, shows whether the finding has cleared on your side.

What to do when validation failed

yesnoyesyesnonoValidation failedSee details: list the FailedURLsIs the status intentional onthese URLs?Leave them; validate onlythe URLs you changed, viaa sitemap filterDoes Test live URL stillshow the issue?Do the URLs share atemplate or host?Fix the template or host ruleFix each URL and thesource creating themFixed or cache cleared afterthe recheckStart new validation
Diagram source
flowchart TD
    A["Validation failed"] --> B["See details: list the Failed URLs"]
    B --> C{"Is the status intentional on these URLs?"}
    C -->|yes| D["Leave them; validate only the URLs you changed, via a sitemap filter"]
    C -->|no| E{"Does Test live URL still show the issue?"}
    E -->|yes| F{"Do the URLs share a template or host?"}
    F -->|yes| G["Fix the template or host rule"]
    F -->|no| H["Fix each URL and the source creating them"]
    E -->|no| I["Fixed or cache cleared after the recheck"]
    G --> J["Start new validation"]
    H --> J
    I --> J

On the issue's details page, click "See details" to open the validation details page. It lists each URL in the request with its state. Group the "Failed" URLs by path pattern; a shared pattern points to one template or rule.

When the fix is complete, click "Start new validation" there. Google rechecks URLs marked "Pending" or "Failed", plus new instances, and does not recheck URLs already marked "Passed" or "Other". Expect another wait of days to weeks.

Common questions

Does "Validate fix" get my pages indexed faster?

Not directly. It queues the affected URLs for recrawling and tracks whether the issue is gone. Whether a fixed URL is then indexed is a separate decision Google makes during indexing.

Why is validation still running after 3 weeks?

The request stays open until Google has rechecked every queued URL, and some are crawled rarely. Open "See details", pick a URL still marked "Pending" and check its "Last crawl" date in URL Inspection.

What does "Other" mean on the validation details page?

Google could not reach the URL during the recheck. It does not fail the validation, and a new validation does not recheck it. If it does not answer reliably when you test it, fix that separately.

Validation passed, but the issue came back. Why?

Google found new URLs with the same issue during normal crawling, or a change on your site reintroduced it. Check whether they share a template with the URLs you fixed, and fix that source before validating again.

Get the complete diagnosis of your site

An evidence-backed report and a prioritized action plan, on a plan with monthly credits.