Search Console full of red
Google sends you letters about your site. In a language nobody speaks.
Search Console is Google telling you exactly what it thinks of your site — and burying the message in taxonomy: 'Excluded,' 'Crawled — currently not indexed,' 'Alternate page with proper canonical tag.' Some of that red is a genuine emergency. Most is bureaucratic noise. Knowing which is which is the entire skill.
Diagnosis within one business day (Mon–Fri). Flat quote before any fix.
What’s actually happening
The console's reports sort into three severities that Google doesn't label honestly. Emergencies: manual actions, security issues, and sudden coverage collapses — these mean traffic is being lost now. Real-but-calm problems: server errors (5xx), redirect chains, wrongly-noindexed money pages, mobile usability failures — worth fixing on purpose, this month. And administrative noise: most 'Excluded' categories, which are Google narrating its own filing decisions — 'alternate page with canonical' is the system working, not failing.
The costly mistake runs in both directions. Panicking over noise wastes money — plenty of 'fix my Search Console errors' work is performed on entries that were never problems. But numbness to the dashboard misses the day a real signal arrives: the coverage graph cliff, the security flag, the crawl-error swarm after a migration. The console rewards a reader who knows the difference — and it's the first place we look on any visibility job, because it's Google's own testimony.
The usual causes, ranked
After twenty-seven years of these calls, the odds are well mapped. Start at the top.
Server errors during crawls
5xx entries meaning Google visited and your site failed to answer — hosting instability documented by a third party. A swarm of these is a real fire.
Redirect chains and loops
Migration leftovers sending crawlers on multi-hop journeys or circles — link equity leaking at every hop.
Noindex where it shouldn't be
'Excluded by noindex' on pages you want found — the report entry that actually is the emergency it looks like.
The great Excluded pile
Canonicals, 'crawled — not indexed,' duplicates — mostly Google describing normal filing. The pile grows with site size and alarms owners in direct proportion.
What you can safely try first
Nothing below can make things worse — that’s the selection criterion. Anything riskier belongs in professional hands, on a backup.
- 1
Check the two panels that are always urgent
Manual Actions and Security Issues. Empty? Breathe. Anything present outranks every other entry in the console.
- 2
Read the coverage graph's shape, not its colors
Valid pages trending stable-or-up beats any amount of red below. A cliff in the Valid line is the report that matters most.
- 3
Sort errors by the pages you care about
A 404 on a retired tag archive is nothing; a noindex on your services page is everything. Severity is location times category — the console only gives you category.
Stop and call when…
- A manual action or security flag exists — that's a formal process, done once, done right
- Coverage cliffed and the cause isn't obvious — cross-referencing crawl data, logs, and deploy history is the job
- Errors regenerate after fixes — treating symptoms of a structural problem (faceted URLs, parameter sprawl) that needs an architectural answer
From there it’s our job: a look within one business day, flat quote, and the $149 flat repair covers most cases of exactly this.
Error Fix — buy it now, skip the hunt.
One error message, found and gone: memory limits, stuck updates, failed publishing, upload and SSL errors, broken forms.
A full backup before we touch anything, the fix tested on desktop and phone, and a short note on what broke and why. We start within one business day (Monday–Friday) of payment. Full refund if we can't fix it.
Questions we hear a lot.
Do I need every error cleared to rank well?
No — and chasing a clean console is a waste of budget. Sites rank fine with hundreds of 'Excluded' entries because most exclusions are correct filing. What you need cleared: the urgent panels, server errors, and misapplied noindex on pages that earn money. Triage beats tidiness, every time.
'Crawled — currently not indexed' on real pages: how bad?
It's Google saying 'saw it, filed it under not-yet' — a quality-and-demand verdict, not an error. Scattered instances are normal; a growing pile of your genuinely valuable pages in that bucket is feedback about content depth or internal linking. The fix is making pages more worth indexing, not a technical toggle.
What does the $149 triage include?
Every report read and sorted into the three severities, the genuinely broken items fixed (redirects, noindex, sitemap, crawl targets), validation requested through the console so Google re-checks, and a plain-English map of what remains and why it can stay. You keep the map — future red arrivals stop being mysterious.
Related symptoms & help
Errors travel in packs. If this one visited, check its friends.
- Crawl ErrorsThe crawl-side pile, in depth.
- Sitemap ErrorsWhen the map you submitted is wrong.
- DeindexedThe console's worst-case letter.
- SEO RecoveryWhen triage reveals a visibility rebuild.
- Website RepairThe whole bench.
- Shopify Not on GoogleShopify hidden from Google
- Slow wp-adminwp-admin taking forever
- Plugin ConflictsTwo plugins, one broken site
Turn the red into a to-done list.
Send the symptom, get a look within one business day and a flat quote from the developer who's fixed this exact thing more times than either of us can count.