Found
Why Your Website Traffic Dropped After a Redesign and What to Check First
Work out whether falling traffic comes from tracking, redirects, indexing or changed content after your redesign.

Milan Gohil
·
10 min read
OVERVIEW
Here is a short version of what I write.
If website traffic falls after a redesign, first confirm the measurement is reliable and identify which channels and pages lost visitors. Then investigate what changed on those pages instead of reversing the entire redesign immediately.
Check analytics and compare the timing of the drop.
Find affected landing pages and test their old URLs.
Review redirects, crawl access, indexing and page content.
Prioritise fixes and monitor recovery without assuming a guaranteed timeline.
You approved the redesign because the old website needed work. Perhaps it looked dated, was difficult to update or wasn’t bringing in enough enquiries. Now the new site is live, the pages look better, and the traffic report is falling. It’s understandable to wonder whether you’ve made an expensive mistake. If the website helps keep your business busy, a downward line can mean worrying about next month’s enquiries, not just this month’s numbers.
At this point, “give Google some time” may feel like an unsatisfactory answer. Sometimes time is part of the explanation. Sometimes there is a fault that needs attention now. You deserve to know which situation you’re in. The first job is to establish what has fallen, where the loss is happening and what changed on those pages. That gives you something concrete to act on before spending more money or undoing the entire redesign.
First find out whether the report reflects a real loss of visitors
Before assuming the new website has lost its rankings, check what the falling number measures. Is it all visits? Visitors from Google? Completed enquiry forms? A rebuild can change the way activity is recorded. The tracking code might be missing from some pages, or the cookie consent setup may have changed. In that situation, the report can fall even while people are still arriving. Start with two sources of information.
Google Analytics shows recorded activity on your website. Its Traffic acquisition report helps separate search visits from advertising, social media and other sources.
Google Search Console shows clicks from Google search results, along with the pages and searches involved.
If Analytics drops at launch but Google search clicks remain broadly steady, check measurement and whether the landing pages load properly. If both show a decline, look for the pages accounting for it. The figures won’t match exactly because the tools measure different things. Compare their direction over equivalent periods, using the correct properties and filters. A domain move may require checking both the old and new properties.
Also look at what your team is receiving. Are calls, enquiries or orders down? Steady sales do not rule out an SEO problem, but they help you understand how urgently the decline is affecting the business.

Put the drop on a timeline before blaming the launch
Write down the launch date and when traffic actually began falling. Add any important changes around the same time.
Page addresses or the domain changed.
Services or products were removed.
Content was shortened or combined.
Advertising stopped or a promotion ended.
Tracking, hosting or consent settings changed.
The site experienced downtime.
Compare equal periods with the same weekday mix. Two complete weeks before and after launch can provide an initial view; a quieter website may need more data to show a reliable pattern. You don’t have to wait two weeks to fix a broken page you have already found. Look further back as well. If the decline began before launch, or your business has the same seasonal dip each year, the redesign may not explain all of it. Changes in search demand and ranking systems are also possible causes.
This is worth doing before a difficult conversation with your developer. A timeline gives both sides something to investigate together.
Find the pages responsible for the loss
A total traffic figure can make a localised problem feel like the whole website has failed. In Search Console, compare the periods before and after launch and review the Pages results. Identify the pages with the largest loss of clicks, then consider how important those pages are to enquiries or sales. A popular article losing casual visitors and a service page losing potential customers deserve different business priorities.
Look for shared characteristics among the affected pages.
Were they all rewritten using the same template?
Were several services combined into one page?
Did their addresses change?
Were they removed from the main navigation?
Is the decline concentrated on mobile or in one country?
These patterns help narrow the investigation. They are clues rather than confirmed causes.
Follow the page when its address changes
Suppose /boiler-repair/ became /services/boiler-repair/. The old address may lose clicks while the new one gains them. Comparing only the old address would make a successful move look like a loss. Match important old pages with their replacements and review the combined performance. If several old pages now share one destination, count that destination once when comparing the group. The question is whether people can still find the service, wherever its page now lives.
Open the old links and see where they lead
Take a few of the old addresses that brought valuable traffic and open them in a browser. Do you reach the right replacement, the homepage or an error? A redirect automatically takes someone from an old address to a new one. When a page moves permanently, that destination should normally be its relevant replacement. Google recommends mapping old URLs to suitable new destinations during a move.
Think about the visitor as well as the technical setup. Someone looking for boiler repair should not have to search through a general homepage to discover whether you still offer it. Ask the developer to verify the technical response too. What looks fine in a browser does not always tell you whether a redirect or error is configured correctly.

Not every deleted page needs bringing back. A discontinued service may have been removed intentionally. What matters is knowing which valuable pages were lost accidentally and which changes were deliberate.
Check what Google can access on the new site
You may be able to open a page while Google encounters a restriction left over from development. One setting worth checking is noindex. It tells search engines not to include a page in search results. Leaving it on a public service page can undermine that page’s visibility, even though the page looks normal to a visitor. For affected pages, ask the technical team to check for
Accidental crawling or indexing restrictions.
Login requirements and server errors.
Important content that fails to load for Google.
Settings that identify the wrong page as the preferred version.
That last item is called a canonical. It helps indicate which version of similar pages should be treated as the main one. It deserves checking when a redesign changes templates or page structure. Search Console’s URL Inspection tool can show information about the indexed page and test the current live version. A successful live test does not guarantee indexing or a return to the old rankings.
You don’t need to become an SEO specialist to ask for a clear answer. Request the affected addresses, what was found and how the fix will be verified.
See whether the new page still answers the customer’s question
A redesign can remove useful information with the best of intentions. Someone wants less clutter, shorter pages and a cleaner first impression. The problem comes when the details customers needed disappear too. Imagine a commercial cleaning page that previously explained the types of premises served, locations covered, evening availability and specialist cleaning options. After the redesign, it contains a short statement about tailored cleaning and a contact button.
The page looks simpler. A facilities manager now has to enquire just to find out whether the company serves their building and location. Compare the old and new versions against the searches that used to bring people in.
Does the page still explain the specific service?
Are important locations, specifications or eligibility details missing?
Can a customer find the evidence and practical information needed to take the next step?
Do relevant pages elsewhere on the site still link to it?
Restore information because it answers a useful question. Making the page longer for its own sake won’t tell you whether you have solved the problem. If the redesign relies heavily on JavaScript, have the developer check that the important content and links appear in the version Google can render.
Work through one example before changing everything
Here is an illustrative scenario, not a Webshunya client result. A business sees Google search clicks fall from 4,000 to 3,000 across equivalent periods after its redesign. Understandably, the owner is worried about the whole project. The page-level review finds
A group of four service pages accounts for 800 lost clicks, including its new destination.
The rest of the site accounts for the remaining 200.
Those four services were combined into one broad page.
The replacement has little detail about the individual services.
The next step is to review those services, their old search queries and the new page. The team can then decide whether separate pages are warranted or whether the shared page can properly answer those needs.

There may be other problems to find, and restoring separate pages would not guarantee recovery. But the owner now has a focused investigation rather than a proposal to redesign the website again.
Ask for a recovery plan you can follow
When you are already worried about the investment, another list of technical tasks can feel like more uncertainty. Ask for the findings to be written in a form that connects the problem to the work being done.
What you need to know | What a useful answer looks like |
|---|---|
What has been confirmed? | The old repair URL redirects to the homepage. |
Why does it matter? | Visitors using that address no longer reach the repair service directly. |
What will change? | Point the old URL to the relevant current repair page and check the destination. |
Who is doing it and when? | A named person and an agreed completion date. |
How will we check the work? | Test the redirect and destination, then monitor the affected pages’ search performance. |
Fix confirmed faults first. Record when changes go live, and keep following both search traffic and the enquiries or sales those pages support. Be cautious with a promise that all traffic will return by a particular date. Your team can commit to investigating, fixing identified problems and reporting progress. Search recovery depends on factors they cannot fully control. You do not have to choose between quietly waiting and starting over. You can ask for evidence, agree the next action and see whether it addresses the problem you actually have.
Frequently asked questions
Is some traffic loss normal after a redesign?
Fluctuations can happen when URLs change and Google processes the move. That does not make every decline harmless. Check tracking, redirects and indexing before accepting that waiting is the right next step.
How long should I wait before investigating?
Start checking when you notice a meaningful decline, especially if enquiries or sales are affected. You may need more data to judge the trend, but there is no benefit in leaving a confirmed broken link, access restriction or tracking fault unresolved.
Will fixing the problem bring all the traffic back?
It may help, but no one can honestly promise complete recovery without understanding the cause. Fixing measurement restores reporting. Repairing redirects or missing content addresses different problems. Confirm the repair first, then follow the affected pages over time.
Should I switch back to the old website?
Find out what is wrong before deciding. A specific fault may be easier to fix than a full rollback. If the new site is seriously disrupting the business, discuss the available options with the technical team and protect orders, enquiries and content added since launch.
What if traffic is steady but enquiries have fallen?
Check the customer journey. Test forms, phone links, bookings and confirmation messages, then review whether the new pages give people enough information to contact you. Also compare actual enquiry records with reporting so a measurement change is not mistaken for lost demand.
Sources and further reading
All Blogs
All Blogs & Articles
© 2026 Webshunya Studio®. All rights reserved.






