Search Console says "Validation failed". Here's what that means and how to tell whether your fix worked.

You did the responsible thing. Search Console named a problem, you fixed what it named — changed the setting, removed the tag, corrected the page — and you pressed the button marked Validate fix, because that is what the interface offers. Then you waited, because that is what the interface said to do.

Some days later, an email. Its subject line names your site and gives away the ending:

The subject line

Some fixes failed for Page indexing issues on site …

Inside, it repeats which issue you asked about, and then the explanation amounts to one sentence:

As specific as the email gets

Some of your pages are still affected by this issue.

Which pages? It doesn’t say. Why? It doesn’t say that either. Back in Search Console the row now reads Failed; open the issue itself and a strip across the top says it in full: Validation failed. The feeling is of a grade you didn’t earn.

First — which “validation” failed?

Search Console uses the same word for more than one thing, and much of what you’ll find by searching this phrase answers the wrong one.

If you never got past adding your site — the screen asking you to upload a file, paste an HTML tag or add a DNS record wherever you bought your domain — that is ownership verification. It failed because Google couldn’t confirm the site is yours; redo that one step, or pick a different method from its list. (And a red box titled “Validation failed” during a site move is a third, unrelated thing again.)

This article is about the other one: Search Console reported an indexing problem, you fixed it, you asked Google to check — and that check came back “Failed”. Different mechanism, different meaning, and much less damning than it sounds.

What pressing the button actually started

When you press Validate fix, Google takes the list of pages affected by that one reason and starts re-reading them. Its own estimate is “up to about two weeks, but in some cases can take much longer” — and people in Google’s own support forums report waits of months. (If yours has been sitting at “Started” for weeks, the wait itself has its own article.)

One detail almost nobody knows: the moment you press the button, Search Console immediately peeks at a few of the pages. If the problem is still sitting on one of them, the request dies on the spot — and the state doesn’t even change. Pressing Validate fix and watching nothing happen isn’t a glitch. It’s an answer.

The whole journey has six possible states. Google’s help page defines them in its own terms; here they are in plain words, side by side:

• Your move “Not Started” — nobody has asked Google to re-check. Issues can sit here for years — less because everything is fine than because the button never explains itself.
• Waiting “Started” — the request was accepted and checking is under way; no page has been caught still carrying the issue yet.
• Waiting “Looking good” — partway through, and every page checked so far has come back clean.
• Nothing to do “Passed” — every page it checked came back without the issue. That word is doing quiet work; the catch comes at the end of this article.
• Nothing to do “N/A” — the problem went away on its own before you pressed anything. Google noticed and quietly closed the case.
• Worth an hour “Failed” — at least one page still carried the issue when Google reached it. The one you’re holding.

What “Failed” actually means

Here is the mechanic that explains almost every confused forum thread about this state. Google’s definition of “Failed” hedges — “A certain threshold of pages still contain this issue” — but the process described on the very same help page is blunt:

Google’s help page, on missing one fix

If you missed a fix, validation will stop when Google finds a single remaining instance of that issue.

One page is enough. Validation doesn’t weigh the forty-nine pages you fixed against the one you missed. The moment it finds a single page where the issue still stands, the check stops — the pages behind it in the queue are never looked at — and the whole batch is stamped “Failed”. Or the other version: you really did fix all fifty, but an old fifty-first page nobody remembered carries the same problem. Also failed — pages Google discovers along the way join the same list.

So “Validation failed” does not mean your fix was wrong. It is not a punishment, either: nothing new happens to your site while the row sits red — those pages were already off Google’s list before you pressed anything, and the button never put them at risk. “Failed” means exactly this and nothing more: on at least one page, at the moment Google looked, the issue was still there. Which page is the entire question — and the answer sits one click away, behind See details.

In practice, a failed validation is usually one of these:

• The fix didn’t reach every page. You corrected the template, but a handful of old pages were built by hand and carry the problem on their own.
• The fix never took effect. A common version: a caching layer still serving the old copy. What you see in your editor and what Google reads from your site are two different documents.
• The fix went live after Google had already re-checked that page. Validation runs over weeks; a page checked on day two knows nothing about the correction you shipped on day four.
• The problem is genuinely still there. The setting didn’t do what its name suggested, or it covered some pages and not others. Not a moral failing — half of these settings are worded so that a person can’t tell what they cover.
• There was never a fault to fix. Some reasons aren’t errors at all. “Crawled — currently not indexed” means Google read the page and simply chose not to list it — no rule broken, no instruction to remove. There is nothing to correct, so validating a “fix” fails on schedule, sometimes across thousands of pages at once.

Most of that list is logistics — timing, caching, coverage — not wrong decisions. That is the real reason not to read “Failed” as a grade on your work.

What to do with a failure

Open the details. The email doesn’t name the page, but the console does. The issue’s page carries a dark strip reading Validation failed, with the date it started and the date it failed; click SEE DETAILS there — Google’s own documentation confirms this is where you “can see which URL caused the validation to fail”.

Look at that page honestly. The same two questions as when the email first arrived: is this a page you actually care about, and is the reason one that needs a person? A validation that failed on a leftover page nobody visits is nothing; one that failed on your best-selling product page is everything. And if it stopped on a page you don’t care about, you are allowed to stop too — a red “Failed” row costs your site nothing, and leaving it red is a decision, not neglect.

Check the page as it is right now. Paste its address into URL Inspection at the top of Search Console and press Test live URL. That reads the page as it exists this second and shows whether your change is actually on it — the tag gone, the setting off, the page answering. A clean result doesn’t guarantee the next validation will pass, but a dirty one is an instant answer: your fix never landed — cache, template, wrong setting — and you found out right away instead of after another two weeks.

Then restart, from the right place. On that same details view, Start new validation — the button is labelled START NEW VALIDATION — begins a fresh cycle. It re-checks the pages that failed and the ones still waiting in the queue, plus anything new Google has found since — pages that passed, or that Google couldn’t reach (those count as passed), are left alone. The clock still resets to weeks, which is why restarting before checking the failed page by hand is how people end up in a loop of failed validations, each one weeks apart, each one saying nothing new.

The question the report can’t answer

Look closely at what validation measures and you’ll see the limit. It re-reads pages and reports a state: issue present, issue absent, page gone. It watches the warning. It never saw your fix.

That cuts both ways. A validation can fail even though your change was correct — one stale page, one cache. And a validation can pass even though you fixed nothing: Google’s rules count a page as fixed if the page is simply no longer available — deleted, locked behind a login, or marked “don’t list this”. Remove the affected pages, and “Passed” arrives on schedule. Google isn’t being careless there; that is simply everything a system that watches warnings can see from the outside.

Which means the question you actually care about — did the thing I changed work? — needs a different kind of answer. Not “is the warning still showing”, but: here is what this page said before, here is what it says now, and here is the verdict, spelled out per page. Validation was never built to answer that. It watches the warning; the fix was always yours.

Written by Oleh Koval at Specia1ne, who reads these reports for a living.