The brief was about looks, not the job the site does
'It looks dated' is a reasonable reason to redesign, but not a complete brief. If nobody asks what the old site failed to do, the new one tends to look better and behave the same.
Before briefing anyone, write down three things: which enquiries you want more of, which pages people currently leave from, and which questions customers ask on the phone that the site should already answer.
Existing search traffic was lost
Search traffic can fall after launch if useful page addresses change without appropriate redirects, valuable content disappears or indexing settings are left incorrect. A fall alone does not establish the cause: check demand, tracking changes and search data as well as the migration.
Practical check: before launch, ask for a list of every old address and where it will point on the new site. If your supplier does not produce one, ask why.
Content was left until last
When the design is signed off before the words exist, copy gets cut to fit boxes and important detail disappears. A service page that once explained prices, process and coverage area becomes three short lines and an image.
Agree the content of the key pages, at least in outline, before or alongside the design.
Too much changed at once
Changing the design, structure, copy, platform and domain together makes it harder to isolate causes. Keep a record of what changed and retain valuable URLs and content where practical. Necessary changes can still proceed with an explicit migration and verification plan.
Nobody measured before or after
Without a baseline, comparisons are weaker. Use available search data and business enquiry records; add permitted tracking where appropriate. Record the launch date and tracking changes so a measurement change is not mistaken for a business improvement.
Use a launch acceptance list
Before launch, check each valuable old URL and its intended destination, new-page canonicals, sitemap entries and indexing settings. Keep permanent redirects relevant rather than sending every removed page to the homepage. A page with no replacement should return an appropriate not-found response.
Run an authorised test enquiry and confirm that it is stored and reaches the person responsible for replies. Test validation, a failed connection and a repeat submission. A thank-you message alone does not establish delivery. Agree who fixes launch defects and what cover ends when the project closes.
Hypothetical example: a builder removes a detailed extension page during a visual refresh. The replacement gallery looks better but no longer answers process and quote questions. Restoring that useful content and its enquiry route is a clearer intervention than changing the colour scheme again.
Launch was treated as the end
Agree a post-launch review using available enquiry, search and usability evidence. Separate defect fixes from new improvements and confirm who pays for each. The review period and any support arrangement belong in the agreement, not in an assumed promise of unlimited aftercare.
This article relates to our Web Design & Development work. To see these ideas in practice, see the full case study for Sycon Construction.
Get a Free Website Review
We'll look at your website and marketing from the customer's perspective and tell you what we would change first.
Get a Free Website Review