02 / Symptoms
What does the fault look like?
Pages not indexed
Pages that used to appear in Google no longer do.
Blocked by robots or noindex
A rule or tag tells Google to stay away.
Broken redirects and 404s
Old URLs lead nowhere, and their value is lost.
Wrong canonical tags
Google is told a different page is the real one.
Content missing after rendering
Google sees an empty page where you see a full one.
Slow or failing server
Errors and timeouts make Google crawl less.
03 / Diagnosis
How we find the fault
We match the date traffic fell to the date something changed on the site. A technical fault leaves a trail, and the trail points to the cause.
Our diagnosis is based on what Google actually crawled and indexed, not on a generic checklist of every possible problem.
Diagnosis checklist
- Search Console Pages report
- URL Inspection on lost pages
- Robots.txt, noindex and canonical tags
- Server logs and status codes
- Release and plugin history
04 / Method
The SEO Fire Fighter Method
Triage
We investigate and identify the root cause.
Put out the fire
We fix what is blocking your recovery.
Rebuild
We rebuild visibility and strengthen your site.
05 / Proof
Related problems we fix
“Nick and Simon with Local Blitz impressed me first with their knowledge and honest assessment of our current situation.”
Jessica Kohley, Google review of Local Blitz, 2017
Technical SEO fixes, fault by fault
A technical fault stops Google from finding, reading or trusting your pages. The content can be excellent and still earn nothing. Each fault leaves different evidence in Search Console, so we fix them one at a time and confirm each result.
Crawl and indexing problems
Google has to crawl a page before it can index it. Robots.txt rules, a noindex tag, login walls and server errors can all stop that. The Pages report under Indexing lists every reason a URL is not indexed, and the URL Inspection tool shows how Google last saw a single page. Two common labels are crawled but currently not indexed and discovered but currently not indexed. They mean different things, and the fix is different for each.
Robots.txt and noindex mistakes
A noindex tag is a direct instruction to keep a page out of results. A Disallow line in robots.txt stops crawling, which is not the same thing. A staging site setting that goes live with the launch is a classic cause of a sudden drop. We read both files and the page headers for every affected template, then remove the instruction that should never have shipped.
Redirects, 404 errors and soft 404s
When a URL changes, the old address needs a clean redirect to the closest matching page. Chains, loops and redirects that point everything to the homepage waste the value the old page had earned. Pages that return a normal status but show an empty or error style page can be treated as soft 404s. We map old URLs to the right new ones and clear the errors in bulk.
Canonical tags and duplicate content
A canonical tag tells Google which version of similar pages to keep. A wrong one, such as every page pointing at the homepage, can drop whole sections from results. Faceted filters, tracking parameters and print versions create duplicates that dilute signals. We decide which URL should win and make the site say so consistently.
JavaScript rendering and structured data
If key content or links only appear after scripts run, Google may not see them in time. We compare the raw HTML with the rendered page and fix what is missing. We also check structured data against Google's documentation, because errors can cost you rich results even when the page still ranks.
Site speed and server health
Slow responses and frequent server errors make Google crawl your site less. We look at the Crawl stats report and Core Web Vitals, and we fix what the evidence shows is holding pages back.
Not sure whether your drop is technical? That is exactly what the free SEO triage is for. If the trouble began with a launch, our traffic drop recovery service covers the wider picture.
Go deeper
Technical SEO guides and answers
- GuideCanonical Tag Mistakes
- GuideCore Web Vitals
- GuideCrawl Budget Guide
- GuideCrawled Not Indexed
- GuideDiscovered Not Indexed
- GuideDuplicate Content Fixes
- GuideFix 404 Errors at Scale
- GuideJavaScript SEO Rendering
- GuideNoindex and Robots Mistakes
- GuideSoft 404 Errors
- GuideStructured Data Errors
- Quick answerDo 404s Hurt SEO?
- Quick answerDuplicate content penalty?
- Quick answerSite Speed and Rankings
- Quick answerWhat a Noindex Tag Does
- Quick answerWhat Is Crawl Budget?
- Quick answerPages Not Indexed
06 / FAQ
Technical SEO questions
How do I know if the problem is technical?
Technical faults tend to be sudden and sharp. Pages vanish from the index, or whole sections lose traffic on one day, often the day after a release, plugin update or hosting change. Search Console shows it in the Pages report under Indexing, where the count of indexed pages falls or a new reason appears in the not indexed list.
Can a technical fault really cost me all my traffic?
Yes. One stray noindex tag, a robots.txt rule that blocks the whole site, or a canonical tag pointing at the wrong page can remove pages from results. The fix is often small. Finding it is the hard part, which is why we start with the evidence.
Will the fix bring my rankings back straight away?
No. Google has to crawl the fixed pages again and process them. Pages with a clear fault often return as they are recrawled, but we do not promise a date or a position. We confirm each fix in Search Console and watch the recrawl.
Do you need access to my site?
For a first look, usually only read access to Search Console. To make the changes we work with your developer or host, or with the access you choose to give us. Start with the free SEO triage and we will tell you what we need.
07 / Get started