SEO traffic recovery after a drop, a hack or a migration

First, confirm the drop is real

SEO traffic recovery starts with a question that sounds too simple: did the visitors leave, or did the counting change? Before touching the site, I rule out four things.

• Broken tracking. A redesign or a plugin update removed the analytics code from some pages.
• A consent banner change. A new cookie banner means fewer visits are recorded, while the same number of people arrive.
• Seasonality. Summer, Ramadan and public holidays move demand every year. I compare with the same weeks a year before.
• Brand versus non-brand queries. Search Console shows whether you lost people searching your name, or people searching what you sell. They have different causes.

If Search Console shows fewer clicks and fewer impressions, the drop is real.

The three common causes of a Google traffic drop

After a migration or redesign

The most common one, and the most fixable. Addresses changed and nobody redirected the old ones. Titles and text that ranked were rewritten or lost. A noindex tag from the staging site went live with the launch. Internal links still point to old addresses.

After a hack

Spam pages appear in Google under your domain. Links to other sites are injected into your pages. Search Console shows a security warning. The order is clean-up first, then removal of the spam from the index, then hardening so it does not return.

After a Google update

Nothing on your site changed, but the results did. I look at which pages and queries lost, what Google shows now, and what competitors show that you do not.

What I need from you

A diagnosis without data is a guess. To start I need four things.

• Access to Search Console and analytics. Read access is enough. If Search Console was never set up, I set it up, although the history before that date is limited.
• The date of the drop. The week is enough. A sudden fall and a slow slide point to different causes.
• What changed around then. A new design, a new domain, a change of host or platform, a plugin, a new person editing the site. Small changes count.
• Backups, if there are any. An old copy of the site shows the addresses, titles and text that used to rank.

If you have none of this, tell me. There are other ways to rebuild the picture, and they take longer.

What recovery looks like

You receive three things.

The first is a named cause, with evidence: the pages, the queries, the dates and the change that matches them. If there are two causes, I say which one weighs more. If the evidence is not clear enough to name one, I say that too.

The second is a fix list in order, with what each fix takes and who should do it. Where the problem is structural, a technical audit is part of the same work.

The third is an honest statement. Recovery takes time after the fixes, because Google has to crawl the site again and reassess it. It cannot be guaranteed. Some pages return, some return lower, and after an update some need better content before they return at all.

How to avoid the next drop

Most of the drops I see could have been avoided with four habits.

• A redirect map before any migration. Every old address is listed next to its new one before launch, and tested on the day.
• Backups. Automatic, stored away from the server, and restored once as a test so you know they work.
• Updates. The platform, the theme and the plugins kept current. Out-of-date plugins are a common way in for a hack.
• Monitoring. Someone looks at Search Console regularly, so a fall is noticed in days and not in months.

If you are planning a redesign, the cheapest moment to involve me is before it starts. Protecting the pages that rank costs far less than winning them back.