Your traffic dropped after a redesign. Here is what to check.

First: is it a real drop or a measurement one?

A redesign usually means a new analytics installation, and a new installation is a new opportunity to lose the measurement rather than the visitors. Check this before anything else, because it is quick and because every other diagnosis depends on the numbers being real.

The clean test is to compare a source that did not change with one that did. Search Console counts clicks from Google independently of anything on your site, so if Search Console clicks are flat while analytics sessions have collapsed, the visitors are still arriving and the tag is the problem. If both fell together, the drop is real.

The tag was not carried over to every template

Analytics is often added to a theme rather than to the pages, so a redesign that changes the theme drops the tag. It is common for the home page to keep it and inner templates to lose it, which produces a partial drop that looks like a ranking problem rather than a tracking one.

A new property, or a new stream, with no history

If the redesign came with a new Analytics property, the comparison you are looking at is between a full history and a fortnight of data. That is not a drop. Check you are reading the property that was live before the launch rather than one created alongside it.

Consent banners now blocking measurement

A new cookie banner that correctly withholds analytics until somebody consents will reduce recorded sessions, sometimes substantially, without changing actual visits at all. This is measurement working properly and it is not something to undo, but it does need accounting for before you conclude anything.

Second: can Google reach the new site at all?

Sites are built behind a noindex instruction so the half-finished version does not turn up in search, and removing it is the launch-day step most often forgotten. A site that has been quietly telling Google to go away for three weeks will lose its rankings, and it will do so silently, because the pages look perfectly normal to a visitor.

Search a site: query for your domain in Google, with no space after the colon. If it returns far fewer pages than the site has, or nothing at all, this is your answer and nothing further down matters until it is fixed.

The staging robots.txt is the same trap wearing a different hat. A file containing Disallow slash tells every crawler to read nothing, and it is correct while building and catastrophic afterwards.

Third: were the old URLs redirected to the new ones?

This is the biggest genuinely technical cause and the one that does the most damage, because it throws away everything the old site had earned. When a page moves from one address to another, a 301 redirect tells Google the new address is the same page, and the reputation the old page had built transfers. Without one, the new page starts from nothing and the old one becomes a 404.

The failure is rarely total. What usually happens is that the top-level pages were redirected and the deeper ones were not, so the home page is fine and the blog posts and product pages that actually earned the traffic are gone. That produces exactly the pattern of a drop that looks inexplicable from the home page.

Two things make it worse and are worth checking at the same time. Redirecting everything to the home page rather than to the equivalent page is treated as a soft 404 and passes nothing on. And chains, where an old address redirects to another old address which redirects again, lose value at each hop and are slow for visitors.

How to find what you lost

Search Console keeps 16 months of history, so the pages report from before the launch is a list of what used to earn clicks. Take the top fifty by clicks, request each one in a browser, and see where it lands. Anything returning a 404 or landing on the home page is a redirect you owe.

If the platform changed, the URL structure probably did too

Moving between platforms usually changes the shape of addresses — dates appearing or disappearing from blog URLs, a category segment being added, trailing slashes changing. Each of those is a different address to Google even though the page is identical, and each needs a redirect.

Fourth: did the content survive the move?

Redesigns are usually also rewrites, and the rewrite is often shorter. A page that ranked because it answered a question thoroughly will stop ranking if the answer was cut down to three lines and a photograph, however much better the new page looks.

The other frequent loss is structural rather than editorial. Headings carry meaning about what a page is about, and a design that replaces a heading with a styled image, or drops the page title in favour of a slogan, removes the signals the page was ranking on without visibly removing any content.

Compare a handful of pages that lost the most against what they used to say. The Wayback Machine holds copies of most sites and is the quickest way to see the old version. You are looking for missing substance rather than missing keywords.

Page titles replaced with brand names

A title of Home — Company Name where it used to say what the business does and where, on every page, is a common redesign casualty. The title is one of the strongest signals a page has about its subject, and identical titles across a site remove it entirely.

Pages that no longer link to each other

New navigation often drops the deeper pages from the menu, and if nothing else links to them either, they become orphaned. Google can still reach them from the sitemap but treats them as less important, and visitors cannot find them at all.

Fifth: it might not be the redesign

The launch date is a compelling explanation for anything that happens near it, and sometimes it is a coincidence. Google runs core updates several times a year, and a site that lost visibility in the same week as one may have lost it for that reason instead.

Seasonality is the other one. Comparing the fortnight after launch against the fortnight before is a comparison of two different periods, and for a lot of businesses those are not comparable. Compare against the same weeks last year as well before concluding anything.

The way to tell them apart is scope. A redesign problem is usually specific — particular templates, particular pages, everything under one directory. A core update usually moves a site as a whole and moves competitors too. If your loss is confined to one section, it is much more likely to be something you did than something Google did.

How long recovery takes, and what does not come back

Where the cause was indexing or redirects, recovery usually begins within a few weeks of the fix, because Google has to re-crawl before anything changes and re-crawling is not instant. Requesting indexing for the most important pages in Search Console speeds up the first few but is not a general solution.

What does not fully come back is anything lost to a long gap. Links pointing at a page that returned a 404 for six months may have been removed by the sites that placed them, and those do not return when the redirect finally appears. This is the argument for checking redirects in the first week rather than the third month.

It is also worth being straight about the ceiling: if the old site ranked partly on content that the new one genuinely no longer has, restoring rankings means restoring the content, not tuning the technical side.

The checks behind this guide

• No page is accidentally hidden from searchA noindex instruction tells Google to keep a page out of search results entirely. That is exactly right for a thank-you page or a checkout step, and catastrophic on a page you want found — it is invisible, and no amount of other work will change that until the instruction is removed. It is worth checking because it is usually left behind by accident after a redesign.
• Redirects go straight to their destinationEach redirect is another round trip before the visitor sees anything, which is most noticeable on a phone. Search engines also give up after a few hops.
• No internal links are brokenVisitors clicking these get an error page instead of what they wanted. Search engines following them waste effort on dead ends, and any value from links pointing at those pages is lost.
• No page returns a server errorA page returning a server error is failing outright rather than merely missing. Visitors see an error instead of your site, and repeated server errors cause search engines to slow their crawling or stop altogether — which affects pages that are working perfectly well.
• Every page is linked from somewhereA page listed in your sitemap that nothing on the site links to cannot be reached by anybody browsing normally. Search engines read the absence of internal links as a statement that the page does not matter, and treat it accordingly.
• Page titles are uniqueWhen several pages share a title, Google has to guess which one to show for a search — and they compete with each other rather than each ranking for what it is actually about.
• Pages have enough content to rankA page with very little text gives a search engine almost nothing to work with, so it rarely ranks for anything. This is worth checking rather than assuming: a contact page or a gallery is legitimately short, and padding it out would make it worse for the person reading it.
• Google indexes the pages it has looked atGoogle crawls far more pages than it indexes, and a page it has crawled and declined to index will never appear in a search result. It is not a penalty and there is usually no message about it — the page simply earns nothing. The common causes are pages that duplicate each other closely, pages with very little of their own content, and pages Google reached but judged not worth storing. Only Search Console knows this has happened; it is invisible from the outside.