How to redesign a SaaS website without losing your rankings

Pull twelve months of Search Console data and sort by clicks. In most SaaS sites, a handful of pages account for the large majority of organic traffic — and they’re rarely the homepage. They’re usually a comparison page, a specific feature page, and two blog posts written three years ago.

Those pages are assets. Anything that changes about them is a risk that needs a reason.

Separately, pull your backlink profile. A page with fifty referring domains carries authority that transfers through the site’s internal linking. Delete it and you lose that, even if the page itself was ugly.

For each URL earning traffic or links, pick one:

• Keep as-is. Same URL, restyled. The safest option, and the right one for anything with strong rankings.
• Keep and improve. Same URL, better content. Adding depth to a page that already ranks is the highest-return SEO work there is.
• Merge. Two thin pages competing for one query become one strong page, with a redirect from the loser.
• Retire. Only when the page earns nothing and has no links. Redirect it to the closest relevant page, not the homepage.

This is the point where a redesign either becomes maintainable or becomes the next redesign. Design a set of reusable sections — heroes, feature blocks, proof, pricing, FAQ, CTA — rather than a handful of bespoke page layouts.

Two reasons. First, your team can then build new landing pages without a designer, which is what lets you actually execute an SEO content plan. Second, consistency across pages is what makes a site feel considered rather than assembled.

While designing, keep four SEO constraints in view:

• One h1 per page, real h2s for sections — not styled divs.
• Meaningful text above the fold, not baked into a hero image.
• An image budget. Decide the maximum weight for a hero before you design one.
• Internal linking surfaces — a footer and a related-content block are design decisions.

If your new site renders content client-side, you’re betting your indexation on the crawler executing your JavaScript promptly and consistently. Sometimes it does. Often it does so late, and inconsistently across pages.

Server rendering with static generation where the content allows removes the bet entirely. The HTML that arrives already contains the content, and interactivity layers on top.

Build a spreadsheet with every old URL and its new destination. Every one — not just the ones with traffic, because links point at pages nobody visits.

Rules that matter:

• Use 301s, not 302s.
• No chains. Old → new directly, never old → interim → new.
• Test the whole map on staging before launch, not after.
• Keep the redirects in place permanently. There is no expiry date on an old link.

Rankings move for a few weeks after any significant change. Don’t panic in week one and don’t declare victory in week two.

Watch: indexed page count, organic clicks by page, average position for your top queries, Core Web Vitals, and conversion rate by page. Compare like-for-like against the same period last year, not against last month, so seasonality doesn’t fool you.

If a specific page drops and doesn’t recover in six weeks, diff it against the archived version and look for what left — usually content that was doing more work than anyone realised.