Redesigning your landing page without losing its search rankings: the complete checklist

A landing page that lives several years eventually deserves a redesign — our article on when to redesign a landing page covers the signals that trigger it. But a redesign that succeeds on the design side can be a disaster on the Google side: URLs changed without redirects, blocks of ranking content deleted because they "looked dated", headlines rewritten without looking at the queries that brought traffic. A page's search rankings are an asset built over months; they can be destroyed in one deployment. Here's the three-phase checklist — before, during, after — so modernization doesn't come at the price of your positions.

Before the redesign: photograph what exists

You can't preserve what you haven't measured. Before touching anything, three inventories are essential. First, Search Console: for each affected URL, export the queries generating impressions and clicks, with their positions — that's the list of what Google currently associates with your page, and therefore of what must be preserved. Second, the content inventory: which headings (title, H1, H2), which paragraphs, which FAQ questions match those queries? A text block that looks incidental to the eye may be exactly the one capturing a long-tail query. Third, inbound links: the external and internal pages pointing to the URL — an SEO tool or a simple crawl of your own site lists them. This survey takes an hour and turns the redesign from a gamble into a controlled operation.

The golden rule: don't change the URL if you can avoid it

The heaviest decision in a redesign is neither the design nor the copy: it's the URL. A preserved URL keeps its history, its inbound links and its positions; a changed URL restarts with a handicap, even when properly redirected. Research on web persistence shows the scale of the general problem: a 2014 study by Martin Klein and his co-authors in PLOS ONE, covering millions of links in scholarly articles, measured that roughly one article in five suffers from "reference rot" — links that no longer lead to the cited content; and a 2004 study by Ziv Bar-Yossef and his co-authors presented at the WWW conference documented how fast the web "decays", with pages disappearing or being emptied of their content. Every redesign that breaks URLs contributes to that decay — and suffers its consequences: every external link landing on a 404 is a lost SEO asset. If the URL absolutely must change (domain change, restructuring), individual 301 redirects — old URL to the equivalent new URL, not to the homepage — are non-negotiable.

During the redesign: what stays, what gets rewritten

• Stays: the page's intent. A page ranking for "price of X" must remain a page that answers the price of X — turning it into a generic brand page throws the positions away.
• Stays: the phrasings that match the queries. The title and H1 can be improved, but the words visitors type (surveyed in Search Console) must survive in them — you rewrite around the queries, not against them.
• Stays: the blocks capturing long-tail queries. FAQs, tables, specific sections — check your survey for which queries they serve before deleting them to "lighten" the page.
• Rewrites freely: everything else. Design, visual structure, social proof, CTAs, images — most of what improves conversion doesn't touch what Google reads first.
• Improves along the way: the technical layer. A redesign is the right moment to gain loading speed — a ranking and conversion factor at once, as our article on page load speed details — and to check the structured data and meta tags described in our landing page SEO guide.

One trap specific to technical redesigns: moving from a page rendered as HTML to a page that depends on JavaScript to display its content. Google executes JavaScript, but with delays and uncertainty; a landing page is much better off served as complete HTML — the default behavior of static Next.js pages like LanderKit templates, and one of the reasons for that stack choice, explained in our Next.js vs WordPress comparison.

Internal linking: the forgotten part

If other pages on your site point to the old URL or quote the old title, update them at the same time as the redesign: consistent internal linking helps Google understand the new version, and internal links passing through redirects dilute needlessly. Also think of the links you only half-control: ad campaigns (update the final URLs rather than relying on the redirect), email signatures, social profiles, and the XML sitemap, which must reflect the new URLs from the moment of deployment.

After deployment: watch the right metrics

The first two weeks after a redesign call for active monitoring. In Search Console: impressions and positions on the queries surveyed before the redesign (a temporary dip of a few days can accompany reindexing; a drop that settles in beyond two or three weeks signals a real problem), the coverage report to catch 404s, and URL inspection to verify the new version is indexed. On the conversion side, compare the conversion rate before/after at comparable traffic — that was the redesign's point — and the bounce rate by source. If the redesign targeted conversion, the ideal is still to validate it as an A/B test rather than a hard cutover: the old version serves as the control, and a failure is one click away from being rolled back.

The reassuring scenario: redesign in stages

The "big bang" redesign — everything changes the same day — is the riskiest for SEO and conversion alike: if positions drop, there's no telling which change caused it. When the page allows it, the staged redesign is safer: first the technical layer (speed, stack) with identical content, then the design section by section, then the copy — leaving each stage a week or two of data. It's slower, but every stage is reversible and attributable. And if you start from a LanderKit template for the new version — for instance SaaS Waitlist or Local Agency depending on your case —, the delivered source code lets you first reproduce your existing content identically in the new structure, before improving the rest: the technology changes, what Google reads doesn't (€89 each, €229 for the 10-template pack).