SEO-friendly website redesign: what must not be lost during an update
SEO rankings are an asset built over months and lost in one bad launch. The list of what typically gets lost in a redesign is well known in advance — and it can be run as a checklist before publishing.
Pages with accumulated ranking weight
Copy on category and service pages that has ranked for specific queries for years should not be rewritten 'for freshness' at the same time as the visual redesign. Changing the design and changing the copy should, where possible, be separate stages, because if rankings drop after launch, it becomes impossible to tell whether the layout or the new copy is at fault.
If the copy genuinely needs updating, do it as a separate stage a month or two after rankings stabilise on the new design, not simultaneously with it.
The h1-h2-h3 heading structure
When building the new layout, designers often alter heading hierarchy for visual effect — making several blocks on a page h1, say, or using h2 purely as large text with no structural meaning. Search engines use that hierarchy to understand what a page is about, and disrupting it dilutes relevance.
The rule is simple: one h1 per page reflecting the main query, with a logical h2-h3 nesting beneath it. The designer needs to be told explicitly which text is which heading level, not just how it should look visually.
Internal linking
An old site typically accumulates many internal links between blog posts, service pages and categories — part of what helps search engines understand site structure and pass weight between pages. These links are often lost in a redesign if the new layout is built without accounting for the old connections.
Before starting, export a map of the current site's internal links and explicitly carry the key ones into the new build — it is a structural task, not a visual one, and easy to miss if nobody owns it explicitly.
Speed and structured data
A redesign is a common cause of slower load times when the new visuals add animations, large images and new libraries without optimisation. Speed is a direct ranking factor and needs testing in PageSpeed Insights before publishing, not after complaints about falling rankings.
Schema.org markup — company data, reviews, products, FAQs — is often hand-configured on older sites and gets lost when switching to a new engine or template. Before launch, explicitly verify that all markup in use has been carried over and passes the Rich Results Test.
The pre-launch checklist
Build a short five-item list: 301 redirects tested on key pages, ranking copy carried over unchanged, heading structure logical, internal links intact, speed and structured data verified. Close out each item individually rather than a blanket 'everything's ready'.
Monitoring rankings for the first two weeks after launch is not a formality but part of the project. If something on the list was missed, that window is the only chance to fix it quickly, before search engines lock in the new, lower ranking.