Google Search Console · Troubleshooting

Common Google Search Console Errors and How to Fix Them

Search Console flags plenty of issues, but not all of them are emergencies. Here are the most common Google Search Console errors, what they mean, how serious each really is, and how to fix the ones that matter.

Updated: July 2026
Written by: Andrew Odgers, Managing Director
Reading time: 9 minutes
The short answer

Common errors include discovered or crawled but not indexed, server and redirect errors, blocked pages, and coverage or enhancement warnings. Not all are serious: some are expected, others genuinely need fixing. Fix them by diagnosing the cause, addressing it, and validating in Search Console. Prioritise errors on important pages and those blocking indexing. Get help for persistent, complex or high-stakes issues.

Know what you are seeing

The common errors, and whether they are serious

Common issues include indexing errors like discovered or crawled but not indexed, server and redirect errors, blocked pages, and coverage or enhancement warnings. Most sites see a mix over time; because they range from serious to harmless, the first step is understanding what each one actually means, such as a discovered but not indexed error. Not every flagged item is urgent; some are expected, such as pages you deliberately excluded, while others genuinely need fixing. Severity varies a lot; because Search Console reports everything, judging which issues matter is more useful than reacting to all of them.

ER 01

Indexing errors

Not indexed states.

ER 02

Judge severity

Not all urgent.

ER 03

Fix the cause

Then validate.

Fixing, prioritising and getting help

How to fix them, what to prioritise, and when to get help

You fix indexing errors by diagnosing the cause, whether it is quality, crawl budget, blocked resources, or technical problems, then addressing that and validating the fix in Search Console. Diagnosis comes first; because the same symptom can have different causes, fixing the underlying reason is what resolves it, as covered in how to fix indexing errors. You should prioritise errors affecting important pages and those blocking indexing or harming users, and worry less about expected exclusions. Impact guides priority; because time is limited, focusing on issues that cost traffic or hurt experience gives the best return. You should get help when errors persist despite fixes, involve complex technical causes, or affect key pages and revenue. Some problems need experience; because misreading an error can waste effort or make things worse, expert help is worthwhile for stubborn or high-stakes issues.

SEO done properly, from £350 a month

Errors sorted,
calmly.

We monitor Search Console, tell the urgent issues from the noise, and fix what matters, so you are never left guessing whether a flagged error is a real problem.

Everything included in your plan:

Google Maps optimisation Full website management Local SEO campaign AI optimisation (GEO) Facebook, Instagram and LinkedIn Quarterly audits Monthly reporting
£350 per month

One clear retainer. No setup fee.

Frequently asked

Search Console errors

What are the most common Google Search Console errors?
Common issues include indexing errors like discovered or crawled but not indexed, server and redirect errors, blocked pages, and coverage or enhancement warnings. Most sites see a mix over time. Because they range from serious to harmless, the first step is understanding what each one actually means.
Are all Search Console errors serious?
No, not every flagged item is urgent; some are expected, such as pages you deliberately excluded, while others genuinely need fixing. Severity varies a lot. Because Search Console reports everything, judging which issues matter is more useful than reacting to all of them.
How do you fix indexing errors?
You fix them by diagnosing the cause, whether it is quality, crawl budget, blocked resources, or technical problems, then addressing that and validating the fix in Search Console. Diagnosis comes first. Because the same symptom can have different causes, fixing the underlying reason is what resolves it.
What should you prioritise?
You should prioritise errors affecting important pages and those blocking indexing or harming users, and worry less about expected exclusions. Impact guides priority. Because time is limited, focusing on issues that cost traffic or hurt experience gives the best return.
When should you get help with Search Console errors?
You should get help when errors persist despite fixes, involve complex technical causes, or affect key pages and revenue. Some problems need experience. Because misreading an error can waste effort or make things worse, expert help is worthwhile for stubborn or high-stakes issues.