SEO traffic-loss diagnosis and recovery

Establish what actually fell

I first distinguish a measurement problem from a search problem. Did organic visits fall, did Search Console clicks fall, or did enquiries fall while traffic stayed stable? We compare a suitable earlier period and, where relevant, the same season last year. The date range needs enough context to avoid mistaking a quiet week for a lasting change.

The investigation then separates affected pages, countries, devices and query groups. A site-wide failure needs a different response from one product family losing demand.

Reconstruct the change timeline

Useful evidence includes releases, hosting changes, redirect rules, content removals, migrations, consent changes and tracking deployments. I compare that timeline with crawl/indexing evidence and published search updates without assuming that two events occurring together prove causation.

A sudden drop after a deployment may justify immediate technical checks. A gradual decline across ageing content may require a broader assessment of relevance, competition and changing demand.

What the investigation covers

• Availability, response codes and important rendering failures.
• Indexing directives, canonical choices, redirects and sitemap changes.
• Losses by landing page, query, device, country and search appearance where data permits.
• Changes to useful content, navigation and internal links.
• Tracking and consent changes that affect reported visits or conversions.
• Security or manual-action notices visible in the reporting accounts.

The scope is agreed before starting. A complex multi-domain incident needs more investigation than one accidentally blocked section.

A recovery plan your team can use

The output should identify the strongest supported explanation, alternative explanations and the evidence still missing. Actions are ranked by urgency and likely importance, with ownership, dependencies and validation steps. A technical correction may be straightforward; earning back search visibility can still take time.

For example, restoring an unintentionally removed category page is different from deciding whether an obsolete product page should exist at all. The aim is useful coverage and a functioning customer journey, not recreating every historical URL indiscriminately.

Diagnosis and delivery are separate decisions

The existing SEO & AI Visibility Review can be an appropriate starting point when its standard scope fits the incident. Wider investigations and continuing recovery work are scoped separately. Once the cause is sufficiently understood, I can implement suitable changes, work with your developers or lead validation.

Preserve exports and deployment records before changing more things. They make the investigation easier and give us a baseline against which to assess subsequent work.