Business guide
Website traffic dropped after a redesign? Diagnose the change before rewriting everything
Separate missing analytics from lost Google visibility, then inspect redirects, indexing settings and changed content with a dated investigation plan.
Find out which number actually fell
"Traffic is down" can mean fewer analytics visits, fewer Search Console clicks, fewer impressions or fewer enquiries. Those are different symptoms. Record the launch date and identify the affected report before changing anything else. Check whether tracking, consent behaviour or the analytics property changed during the rebuild.
If analytics visits fall while Search Console clicks stay broadly similar, start by investigating measurement. If search impressions and clicks both fall for the same useful pages, investigate visibility as well. If visits remain but enquiries fall, test the contact journey. Do not assume a ranking problem explains every post-launch change.
Compare useful pages and searches over comparable periods
Choose periods with a sensible match for weekdays and business seasonality, and exclude unfinished reporting days where possible. Break the result down by page, query, country and device when enough data exists. An overall average can hide that one removed service page accounts for much of the decline.
Look at the existing searches the business cares about, not just the total number of keywords. If a page moved, include its old and new addresses in the investigation. Keep notes of promotions, holidays or other known changes in demand so the redesign is assessed alongside the broader context.
Check launch mistakes before making broad content changes
Open representative old URLs and confirm they reach the intended relevant replacement. Check for broken redirects, unexpected errors or links to the staging address. Inspect important live pages for unintended noindex directives, incorrect canonical references or access restrictions. Ask the maintainer to check the served result rather than relying on an editor preview.
Use Search Console URL Inspection and indexing reports to gather evidence. A sitemap submission does not establish that every page is indexed. If a serious technical mistake is present, correct it and record the date; do not wait for a general "settling period" while customers encounter broken pages.
- Only analytics fell
Check tags, property selection and measurement changes.
- Search visibility fell
Inspect URLs, indexing, redirects and changed content.
- Enquiries fell
Test forms, calls, bookings and delivery.
After recording the evidence, make a targeted fix and compare the same measures again.
Review what the redesign removed or made harder to find
Compare old and new versions of the affected pages. Did a service explanation disappear? Were useful guides removed from navigation? Did several distinct pages become a generic page with less detail? Check whether mobile visitors can still find the next step and read the information they need.
Prioritise changes supported by the evidence. Restoring a missing service section or repairing a broken link is easier to evaluate than rewriting the entire site immediately. Significant moves can also cause temporary search fluctuations, so distinguish confirmed defects from movement that still needs observation.
Keep a short investigation and recovery log
For each issue, record the evidence, affected URLs, proposed fix, responsible person and verification result. Repeat the relevant checks after deployment. Explain separately what has been repaired and what remains uncertain; no one can promise that every ranking will return on a fixed date.
My website review work can help separate measurement, technical search and enquiry problems after a rebuild. Bring the launch date, previous site information and access to the relevant reports. A focused diagnosis gives the next change a reason, rather than starting another redesign because the first graph looks worrying.