A website traffic drop after redesign is rarely caused by the design itself. It is caused by broken 301 redirects, a staging noindex tag shipped to production, or URL changes nobody mapped. Before you fix anything, confirm the drop is real by comparing Google Search Console clicks against GA4 sessions.
You opened Google Search Console on Monday and the graph looks like a cliff. The new site launched two weeks ago. It is faster, it looks better, the client loved the demo. Organic clicks are down 60 percent. A rebuild is a serious investment. Look at what a website costs in Thailand and you see why losing its traffic hurts.
A website traffic drop after redesign feels like a verdict on the new site. It almost never is. The design is usually fine. What broke is the handoff between the people who built the site and whoever owned the SEO, and in Thailand that gap runs wider than most places, because the build and the search work go to two different vendors or the search owner does not exist at all.
This guide is a triage sequence, not a checklist. Work it in order. The first step takes twenty minutes and it saves a meaningful share of teams from chasing a problem they do not have.
Start there.
First, confirm the drop is real and not a tracking error
Check your tags before you touch a single redirect. A real share of the drops we get called about at Inspira Digital Agency are not SEO drops at all. They are GA4 or Google Tag Manager tags that never made it onto the new build.
The developer rebuilt the templates. The tracking snippet lived in the old theme. Nobody moved it. Sessions collapse to near zero on launch day and everyone assumes rankings died.
Run three checks:
- Open the site, run GTM Preview, confirm the container fires on a page load.
- Open GA4 Realtime and load a page yourself. If you do not appear, the property is not receiving data.
- Compare Search Console clicks to GA4 sessions over the same 28 days.
These three checks are the same opening moves in a full SEO audit. Rule out the cheap explanation before you commit a week to the expensive one.
Tracking problem vs. real SEO problem
| Signal | Tracking problem | Real SEO problem |
|---|---|---|
| Search Console clicks | Flat or near flat | Falling |
| Search Console impressions | Flat | Falling |
| GA4 sessions | Cliff edge, often on one exact date | Gradual slide over one to three weeks |
| Drop shape | Vertical, all channels at once | Organic only |
| Index coverage report | Unchanged | Valid URLs dropping |
That last row matters most. Search Console does not depend on your tags. If clicks and impressions hold steady while GA4 collapsed overnight, Google still ranks you and your analytics lied. Fix the container and move on with your life.
If Search Console is falling too, you have a real problem. Now find out which one.
Why traffic drops after a website redesign: the five real causes
Five things cause the overwhelming majority of post-redesign losses. Work them in this order, because this is roughly the order of how often each turns out to be the actual culprit.
1. Broken or missing 301 redirects
This is the one. If you only check one thing, check this. The old site had URLs that earned rankings and backlinks over years. The new site changed them. Without a 301 from every old URL to its closest new equivalent, Google finds a 404, keeps the old URL in the index for a while, then drops it. The rankings do not transfer. They evaporate.
Redirect chains cause a slower version of the same bleed. Old URL redirects to an interim URL redirects to the new page. Google follows a few hops and then loses interest. Map every old URL to its final destination in one hop.
2. Staging noindex or robots.txt disallow shipped to production
Every staging site carries noindex or a blanket Disallow: / in robots.txt. That is correct behaviour. The failure is shipping it live. Check yoursite.com/robots.txt and view source for a robots meta tag right now. It takes ten seconds and it explains more launch disasters than anything except redirects.
3. URL structure changed without a mapping document
A CMS change from WordPress to Webflow, or a restructure from /services/seo/ to /what-we-do/seo/, resets the URL layer entirely. Someone must produce a spreadsheet of every old URL and its new counterpart before launch. When that document does not exist, redirects get guessed at, and guessing at scale produces 404s.
4. Content pruned or thinned during the rebuild
Redesigns consolidate. Twelve thin service pages become one strong one. That is often good for users and bad for the long tail those twelve pages quietly ranked for. Be honest about this tradeoff instead of treating it as a bug. Each of those twelve pages matched a different search intent, and one consolidated page cannot serve all twelve.
5. Lost internal linking depth
The old site had a footer with 40 links and a sprawling blog sidebar. The new site has a clean nav with six items. Pages that sat two clicks from the homepage now sit five. Crawl budget follows internal links, and pages Google reaches less often rank worse.
The pattern underneath all five is the same: nobody scoped the SEO work into the build. If you are planning a rebuild rather than recovering from one, put redirect mapping in the contract before you sign it. Our web design team treats the redirect map as a deliverable, not a favour.
Redirects and indexation explain most drops. A .co.th move adds a category of problem that no global guide covers.
.co.th migration SEO: what changes that a redesign does not
A .co.th migration is not a redesign with a different domain. It changes a signal a redesign never touches: geotargeting.
Moving from a .com to a .co.th hard-locks your site to Thailand, and you cannot undo it in Search Console. Google treats generic top-level domains like .com as country-neutral, which lets you set an international targeting preference or leave the site open to every market. A .co.th is a country-code top-level domain. Google reads it as a Thailand signal automatically, and the international targeting setting is not available for ccTLDs at all. That is the tradeoff nobody presents at the kickoff meeting. If your business sells only inside Thailand, the .co.th is a trust and relevance win. If you serve Singapore, Vietnam, or expats researching from abroad before they arrive, you have permanently narrowed your reach, and no amount of technical SEO reverses it. Decide this before the migration, not after. Google’s own site move documentation is explicit that a domain move is one of the highest-risk changes a site can make.
Does Change of Address work for a .com to .co.th move?
It works for the redirect signal, not for the country signal. Search Console’s Change of Address tool tells Google that Property A moved to Property B and asks it to transfer signals faster. Use it. Set it up after the redirects are live, never before.
What it does not do is preserve your international reach. People assume the tool carries over their geotargeting settings the way it carries over the domain association. It does not, because on a ccTLD there is no geotargeting setting to carry. The tool completes successfully, reports no errors, and your non-Thai visibility declines anyway. It fails silently because from Google’s side nothing failed.
The THNIC paperwork problem
Here is the Thailand-specific cause that no international guide mentions. Registering a .co.th requires company registration documents through THNIC. Not a credit card and a checkout page. Actual paperwork, verified, with a queue.
So the launch date floats. The team plans for the 1st, the documents clear on the 12th, and the client already announced the new site. Everything compresses. The first task cut under that pressure is always redirect mapping, because it is invisible to the client and it takes the longest. Schedule pressure, not incompetence, is the mechanism.
Bilingual URL structures break quietly
Thai and English sites get restructured together during a rebuild. /th/services/ becomes /services-th/, hreflang tags keep pointing at the old paths, and the Thai pages orphan themselves out of the index while the English side looks healthy. Audit both language trees separately.
If you are mid-migration and any of this is unfamiliar, stop and map your URLs. If you already launched, you have a week of work ahead. And if the .co.th is locked in, commit to the market you chose. Local SEO in Bangkok is where the remaining upside sits.
INSPIRA INSIGHT
At Inspira, we’ve seen the same failure repeat when working with Bangkok property and hospitality brands moving to a .co.th. The redirects existed, but only for the top-level pages the client reviewed in the demo. Every deep page, the individual listings and the Thai-language duplicates, went straight to a 404. Nobody noticed because the client tested by clicking the nav. Here’s what that taught us: test migrations against a crawl of the old sitemap, never against the menu. The pages that earn your long-tail traffic are the ones nobody clicks in a demo.
Xavier Cloitre, Founder and Marketing Director, Inspira Digital Agency
How to recover SEO after a redesign: a 7-day triage plan
Speed matters more than sophistication here. Google recrawls, finds 404s, and drops URLs from the index progressively. Every week you wait costs you more than the week before.
- Day 1. Verify tracking. Run the three checks above. Rule out a false alarm before you spend a week on a real one.
- Day 2. Audit redirects against the old URL list. This is the highest-value day of the seven. You cannot redirect URLs you cannot name, so start by rebuilding the list of what existed. Pull the old XML sitemap from the Wayback Machine if the dev team did not keep one. Export every URL that has received a click in the last 16 months from Search Console. Run Ahrefs Best by links on the old domain to find the pages holding your backlink profile. Merge the three lists and deduplicate. Now crawl that list in Screaming Frog in List mode against the live site. Any row returning 404, 410, or a 200 on a page that is not the true equivalent is a broken promise to Google. Fix those first, ranked by the traffic and links each URL carried. See Ahrefs’ research on redirects for chain behaviour.
- Day 3. Check indexation. Open the Index Coverage report in Search Console. Look for growth in Excluded, specifically “Crawled, currently not indexed” and “Discovered, currently not indexed”. Verify robots.txt. Verify canonical tags point to self, not to staging URLs.
- Day 4. Submit the new XML sitemap. Confirm it contains only canonical, indexable, 200-status URLs. Remove the old sitemap. Submit Change of Address if the domain changed.
- Day 5. Rebuild internal links. Find the pages that dropped furthest and count the internal links pointing to them now versus before. Restore depth.
- Day 6. Check Core Web Vitals and rendering. A JavaScript-heavy rebuild can leave content invisible to Googlebot. Use the URL Inspection tool and read the rendered HTML, not the source.
- Day 7. Log file analysis, if you can get the logs. Server logs show you what Googlebot actually crawled and what it got back. Nothing else gives you that.
Seven days gets you a diagnosis and most of the fix. It will not get you all your traffic back, and you should know now which part is gone.
What you can’t recover (and when to stop trying)
Some of it is not coming back. Say that out loud early, because a team chasing 100 percent will burn three months on the last 8 percent.
Three losses are usually permanent:
- Rankings a competitor took while you were broken. Position 3 went to someone else during your six weeks of 404s. They now have the click history and the engagement signals. You have to win it back on merit, not on recovery.
- Long-tail traffic from consolidated pages. You merged twelve pages into one. Those twelve ranked for queries the one page will never target. That traffic was real and it is gone, and the consolidation may still have been correct.
- Authority from backlinks pointing at URLs you chose not to redirect. A 301 to an irrelevant page passes little and risks being treated as a soft 404. If there is no true equivalent, the link equity has nowhere to go.
Set a benchmark instead of a fantasy. Take your pre-launch organic sessions, subtract an honest estimate of the pruned long tail, and call 85 to 90 percent of that number a full recovery. Then measure against it.
That benchmark is what turns a panic into a project. And judge the rebuild on leads, not sessions. A site that recovers 88 percent of its traffic and converts more of it into enquiries is ahead, not behind.
Frequently Asked Questions
How long does it take to recover traffic after a website redesign?
If redirects are fixed within the first two weeks, most sites see recovery begin in four to eight weeks and stabilise around three months. The timeline depends on how fast Google recrawls your site, which depends on your size and authority. Sites that wait two months before diagnosing take longer, because Google has already dropped the old URLs from its index by then.
Will my traffic come back on its own after a migration?
Some drops recover on their own. A temporary crawl slowdown after launch usually settles within weeks. Redirect failures and indexation errors never self-heal. They compound, because Google keeps recrawling, keeps finding 404s, and keeps removing URLs from the index. “Give it time” is the most expensive advice in this industry. Diagnose first, then decide whether waiting is reasonable.
Does moving to a .co.th domain hurt SEO?
Not inherently, and it can help within Thailand. A .co.th sends a strong local relevance and trust signal to Thai searchers. The real cost is reach. A .co.th is hard-locked to Thailand and cannot be retargeted internationally in Search Console. If you serve customers outside Thailand, that visibility does not come back. The damage in practice comes from rushed redirects, not from the domain itself.
Do I need to redirect every old URL?
No. Redirect every URL that earned traffic, holds backlinks, or has a true equivalent on the new site. Skip URLs that were duplicates, expired campaign pages, or genuinely worthless. Redirecting an irrelevant URL to the homepage is worse than letting it 404, because Google treats it as a soft 404 and passes nothing. Prioritise by clicks and referring domains.
Conclusion
A website traffic drop after redesign is almost always a mechanical failure with a findable cause. Not a mystery, not a penalty, not the new design. Something stopped resolving, and every day it stays broken, Google removes more of your URLs from its index. The speed of your diagnosis matters more than the sophistication of your fix. You now know the order to check things in, which losses are recoverable, and which are not. Start with tracking, then redirects, then indexation.
If you have worked the triage and traffic is still flat, the crawl missed something. Inspira Digital Agency runs a technical migration audit that pulls server logs, historical URL data, and backlink mapping to find what a standard crawl cannot see. Request a migration recovery audit.
