Skip to content

Search Console validation failed: what Validate fix checks

Why Search Console validation failed: what Validate fix rechecks, what each validation state means, how to find the failing URLs and when to start again.

By Crawlito · 9 min read

In short

  • Validate fix asks Google to recrawl only the URLs with known instances of one issue; Google says it does not queue the whole site.
  • Google's help page says validation stops when Google finds a single remaining instance of the issue, so one missed URL is enough to end a run.
  • Validation typically takes up to about two weeks in the Page indexing report and can take much longer; the Core Web Vitals report uses a 28-day monitoring session instead.
  • A restarted validation rechecks URLs marked Pending or Failed plus new instances; URLs marked Passed or Other are not rechecked.
  • Validation is optional: Google says it updates the count when it recrawls affected pages, even if you never click Validate fix.
On this page

A failed validation in Google Search Console means that, while rechecking the URLs affected by one issue, Google found pages where the issue was still present. Google's Page indexing report help says validation "will stop when Google finds a single remaining instance of that issue", so one URL you missed is enough. To recover, open the issue, click See details to find the URLs marked Failed, fix them, confirm the fix on the URLs still marked Pending, and click Start new validation.

The rest of this post explains what Validate fix actually does, what each state in the validation log means, and how to avoid a second failed run. For checking a single page, see the URL Inspection tool guide, which this post does not repeat.

What does Validate fix actually check?

Validate fix is a request scoped to one issue in one report. When you click it on the issue details page, Google rechecks the URLs it already knows are affected by that issue. Google's help page is specific about the scope: only known affected URLs are queued for recrawling, not the whole site.

The flow, as Google documents it, has three steps:

  1. A quick sample check. Search Console first checks a few of the affected pages. If the issue is still present on any of them, validation ends and the validation state stays as it was. This is why you can click Validate fix and see nothing change: the run never reached the Started state.
  2. Recrawling the affected URLs. If the samples pass, the state becomes Started and the remaining affected URLs are queued for recrawl.
  3. A verdict per URL. Each URL ends as Passed (the issue is gone), Other (Google could not reach the URL) or Failed (the issue is still there). A failed URL can end the whole run.

Two details change how you should read the result:

  • A sitemap filter narrows the run. If the report is filtered to one sitemap when you click Validate fix, validation covers only the URLs in that sitemap at the time of the request.
  • Validate fix is not Request indexing. Request indexing, in URL Inspection, queues one URL for crawling. Validate fix tracks whether an issue is gone across a set of URLs. Google's URL Inspection help suggests the order: fix the issue, test a few pages with the live test where the issue can be tested, then click Validate fix.

What do the validation states mean?

There are two sets of states: one for the issue as a whole and one for each URL in the validation log. The definitions below follow Google's help page.

Issue-level states

StateWhat it means
Not startedOne or more instances of the issue have never been part of a validation request
StartedValidation has begun and no remaining instance has been found yet
Looking goodEvery instance checked so far has been fixed
PassedAll known instances are gone, or the affected URL is no longer available; only reached after you clicked Validate fix
N/AGoogle found the issue fixed everywhere without a validation request
FailedGoogle says "a certain threshold of pages" still had the issue after you clicked Validate fix

Google does not publish what that threshold is. In practice, read Failed together with the instruction quoted above: a single remaining instance can stop the run.

Per-URL states

StateWhat it means
PendingQueued for validation and not yet rechecked
PassedThe issue is gone from this URL
FailedThe issue is still present on this URL
OtherGoogle could not reach the URL or, for structured data, could not find the item on the page any more; Google says this is not an error state and treats it as equivalent to Passed

The states are per issue, not per URL in general. Google notes that the same URL can be Passed for one issue and Pending for another, so check you are reading the log for the right issue.

A Passed state also does not change the issue's label. Google says the Error or Warning severity stays the same after validation passes; what drops to zero is the count of affected items.

Why did my validation fail?

Google's documentation gives the rule; the cause is usually one of a few patterns. These are diagnostic suggestions, not a Google list:

PatternWhat happenedHow to check
Partial fixThe fix reached one template but not every page with the issueFetch several Failed URLs from different sections
Cached old responseA CDN or page cache still served the broken version when Google recrawledCompare the response headers and body of a Failed URL with your origin
Status is intendedThe issue describes behavior you want, such as a page blocked by robots.txt on purposeDecide whether the status is a problem at all
Intermittent errorThe page works now, but failed during Google's recrawl, as with server errors under loadCheck server logs for the recrawl dates
Not something you can fixThe issue's source is Google, not your siteRead the Source column on the report summary

The last two need a word each. Google's help says that "in general, you can fix only issues where the source is listed as Website", and that it "might not always make sense" to fix and validate an issue, for example URLs that robots.txt blocks deliberately. Validating an intended status will fail every time. For intermittent server errors, the dedicated guide to server errors (5xx) in Search Console covers how to find them in logs.

Some reasons are also judged at indexing time rather than at fetch time. Google's URL Inspection help says "Crawled - currently not indexed" and "Discovered - currently not indexed" cannot be tested with the live test, and Google describes "Crawled - currently not indexed" as a common message, because Google does not index every page. If that is the issue you validated, read crawled, currently not indexed or discovered, currently not indexed before treating a failed run as a defect.

How to find the URLs that failed

Google's steps for a failed validation are short:

  1. Open the Page indexing report and click the issue.
  2. On the issue details page, click See details to open the validation history.
  3. Find the URLs marked Failed in the per-URL list. Google does not document a filter by state, so you may need to read or export the list.
  4. Fix those pages.
  5. Confirm the fix also holds on every URL still marked Pending.

Before you restart, test the Failed URLs yourself rather than trusting a deploy note. A quick loop over the exported URLs shows the status code and final URL that a plain request receives:

bash
while read -r url; do
  curl -s -o /dev/null --max-time 20 \
    -w "%{http_code} %{url_effective} $url\n" -L "$url"
done < failed-urls.txt

This proves what your server returns to this request, not what Googlebot received on the recrawl date. For an issue such as a noindex tag or a redirect, search the saved HTML or headers for the specific cause as well. For the single most important URLs, run the live test in URL Inspection where the issue can be tested live.

If several issues failed at once, sort them by how many important pages they affect before you fix anything. The approach in prioritizing audit fixes applies here too.

When to restart validation, and what a restart covers

Start a new validation only once you believe every remaining instance is fixed. Google says to wait for a validation cycle to finish before you request another, even if you have fixed more in the meantime.

To restart, open the failed validation's log with See details and click Start new validation. Google documents what the new run includes:

URL state in the last runRechecked on restart?
FailedYes
PendingYes
New instances found since the last runYes
PassedNo
OtherNo

Because Passed URLs are not rechecked, a restart is not a full re-audit. If a later deploy breaks a URL that passed, Google will find it on a normal crawl and it will reappear as a new instance, not through your restarted validation. That is a release-process problem, and the checks in AI search regression testing are one way to catch it before Google does.

Google's help also offers a way to get a faster read on the pages that matter most: create and submit a sitemap containing only your most important pages, filter the report by that sitemap, and validate. A smaller set can finish sooner.

How long validation takes, and whether you need it

Google says Page indexing validation "typically takes up to about two weeks, but in some cases can take much longer". Google says it sends progress notifications by email as validation proceeds, and a notification when it succeeds or fails. While a run is in progress, Google asks you not to click Validate fix again until the attempt succeeds or fails. Google's recrawl guide gives the same message for single URLs: requesting a recrawl several times does not get a page crawled faster, and crawling can take from a few days to a few weeks.

Other reports work on a different clock. The Core Web Vitals report help describes a 28-day monitoring session based on field data, and says starting it does not trigger re-indexing.

Validation is optional. Google's help says you can fix issues without validating: Google updates the count of affected URLs when it recrawls them, and an issue that Google finds fixed everywhere without a request shows the N/A state. What validation adds is a deliberate recheck, a per-URL log and email updates. An issue stays in the report until 90 days after its last instance disappears; if it recurs inside that window, Google treats it as the same open issue.

Google does not describe any of these states as a ranking signal, and a Passed validation does not mean a page will be indexed or shown. It means the specific issue is no longer found on those URLs.

Frequently asked questions

Why did Search Console validation fail after I fixed the issue?

Google found the issue still present on at least one affected URL during the recheck, and its help page says a single remaining instance stops validation. Open See details, filter to Failed URLs and test those pages directly, since partial deploys and cached responses are common causes.

Does a failed validation hurt my rankings?

Google does not describe validation state as affecting ranking. It reports whether an issue is still present on the affected URLs; the underlying issue, not the validation result, is what affects those pages.

How long does Validate fix take?

Google says Page indexing validation typically takes up to about two weeks and can take much longer. Core Web Vitals validation uses a 28-day monitoring session.

Which URLs are rechecked when I start a new validation?

URLs marked Pending or Failed, plus new instances found since the last run. URLs marked Passed or Other are not rechecked.

Do I have to click Validate fix at all?

No. Google says you can fix issues without validating, and the count updates as Google recrawls the affected pages.

Check the pages before you validate again

A second failed run usually means the fix was never live on every page. Before you click Start new validation, run the free check on one of the Failed URLs; it covers a single page and needs no account. For a site with many affected templates, an audit covers up to 500 pages and comes as a PDF with evidence and prioritized fixes to work from.

Filed under Strategy and audits. Topics: search-console, google, troubleshooting, indexing