Website redesign checklist: keep your rankings and get more enquiries

By Paul Jeevanesan A., Founder and CEO, StudAI One · Updated 23 October 2026 · 9 min read

The short answer

A website redesign keeps its search rankings when you map every old URL to its closest new equivalent, set permanent server-side 301 redirects, carry over titles, descriptions and structured data, and monitor Search Console closely after launch. It wins more enquiries when you start from a measured baseline, simplify the enquiry or booking journey, and meet the Core Web Vitals and WCAG 2.2 AA targets. Expect some temporary ranking movement; Google says to expect it during site moves.

Key takeaways

Record a baseline of traffic, enquiries and page speed before you change anything.
Map every old URL to its new equivalent and use permanent server-side redirects, kept for at least a year.
Carry over metadata and structured data, which must match visible content.
Aim for LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less, and build to WCAG 2.2 AA.
After launch, watch the Page indexing and Performance reports in Search Console and fix 404s quickly.

Should you redesign or fix what you have?

A website redesign changes the structure, design and often the platform of a site. A fix improves the existing site without rebuilding it. Redesigns carry more risk to search traffic, so be sure you need one.

Fix or redesign?
Symptom	Usually a fix	Usually a redesign
Slow pages	Image compression, caching, removing heavy scripts	The platform or theme cannot be made fast
Few enquiries	Clearer calls to action, shorter forms	The structure does not match what customers look for
Out-of-date look	Refresh styles within the current templates	The brand has changed and the templates cannot follow
Hard to update	Training, a few new page templates	Every change needs a developer
Accessibility failures	Fix contrast, labels and focus states	Core components are inaccessible throughout

If most of your problems sit in the fix column, fix first. You can still redesign later, with better data about what visitors actually do.

Set goals and record a baseline first

Decide what the redesign is for in measurable terms, such as more booked consultations or more quote requests. Then capture where you are today, because after launch you will need to compare like with like.

Search Console clicks, impressions and queries for each page, exported for at least the last 12 months
Analytics: top landing pages and conversions such as form submissions, calls, WhatsApp clicks and bookings
Core Web Vitals for your main page types
Pages that other sites link to, so their links keep working
A full crawl of the current site, saved as a file

Agree who signs off content, design and launch. Freeze major content changes in the final weeks before launch so the URL map stays accurate.

Build a content inventory

A content inventory is a list of every URL on your site with its traffic, links and purpose. Combine your crawl with Search Console and analytics data, then decide what happens to each page.

Content inventory decisions
Decision	When	What happens to the URL
Keep	Performs well and is still accurate	Same URL if possible, or 301 to its new URL
Rewrite	Right topic, weak or dated content	Keep or redirect the URL; improve the page
Merge	Several thin pages on one topic	301 each old URL to the merged page
Remove	No traffic, no links, no purpose	Return 404 or 410, unless a close equivalent exists to redirect to

Do not delete a page just because its traffic is low. It may earn links from other sites, support sales conversations or answer a question customers ask before buying. Check links and purpose before removing anything.

Map URLs and set 301 redirects

Google's site move guidance (opens in a new tab) is the reference for this step. In short:

Prepare a URL mapping from every old URL to its new URL.
Set server-side permanent redirects (301 or 308) from old to new, following the mapping. Google recommends a permanent server-side redirect whenever possible and treats JavaScript redirects as a last resort (Google redirects guide (opens in a new tab)).
Redirect each page to its closest equivalent, not everything to the home page, and avoid chains of several redirects.
Update internal links so they point straight at the new URLs.
Submit the new sitemap in Search Console.
Keep the redirects for as long as possible, generally at least one year.
If the domain changes, use Search Console's Change of Address tool for the old site.

Keep metadata and structured data

Carry over page titles and meta descriptions that already perform, and improve the weak ones deliberately.
Keep one clear H1 per page and a logical heading order.
Set canonical tags on the new URLs, and hreflang if you have language or country versions.
Carry over structured data such as Organization, LocalBusiness, Product, Article or FAQ markup where it applies.
Follow Google's structured data guidelines (opens in a new tab): markup must be a true representation of the page and must not describe content that is not visible. It enables rich results but does not guarantee them.
Test key templates with the Rich Results Test and the URL Inspection tool before launch.

Meet Core Web Vitals and WCAG 2.2 AA

Core Web Vitals are Google's three measures of real-world page experience. web.dev (opens in a new tab) recommends measuring them at the 75th percentile of page loads, separately for mobile and desktop.

Core Web Vitals 'good' thresholds
Metric	Measures	Good
Largest Contentful Paint (LCP)	Loading	Within 2.5 seconds
Interaction to Next Paint (INP)	Responsiveness	200 milliseconds or less
Cumulative Layout Shift (CLS)	Visual stability	0.1 or less

Test on real phones over a mobile connection as well as with lab tools, because the thresholds describe what visitors actually experience. Good scores help, but Google says they do not guarantee top rankings and that it always seeks to show the most relevant content (page experience (opens in a new tab)). Our Core Web Vitals guide explains how to improve each one.

For accessibility, build to WCAG 2.2 level AA, published as a W3C Recommendation on 5 October 2023. New level A and AA criteria (opens in a new tab) to check in your designs include:

2.4.11 Focus Not Obscured (Minimum): sticky headers and banners must not hide the focused element
2.5.7 Dragging Movements: anything done by dragging needs a single-pointer alternative
2.5.8 Target Size (Minimum): pointer targets of at least 24 by 24 CSS pixels, with listed exceptions
3.2.6 Consistent Help: help options appear in the same place across pages
3.3.7 Redundant Entry: do not make people re-enter information they have already given
3.3.8 Accessible Authentication (Minimum): no memory or puzzle tests to log in without an alternative

Design the enquiry journey and campaign landing pages

Give every page one primary action, such as book a call, request a quote or message on WhatsApp.
Keep forms short; ask only what you need for the first reply.
Offer the contact routes your customers prefer: phone, form, WhatsApp or online booking.
Send people to a confirmation page or fire a tracked event after each enquiry, so conversions can be measured.
Build a lead generation landing page for each paid campaign: match the ad's wording, focus on one offer, remove distractions and keep it fast.

For Google Ads landing page design, the page should deliver exactly what the ad promised. Our paid ads service covers campaign landing pages.

Launch-day checklist

Remove any staging noindex tags and password protection from the live site.
Check robots.txt allows the pages you want crawled.
Test a sample of old URLs from the mapping, including your top pages, and confirm each returns a single 301 to the right page.
Submit the new sitemap in Search Console and Bing Webmaster Tools.
Check that analytics, conversion tracking and ad tags are firing.
Submit a test enquiry through every form and booking flow, and confirm it arrives.
Check canonical tags, structured data and page titles on key templates.
Run a quick accessibility and speed check on the main page types.

Post-launch monitoring in Search Console

Check the Page indexing report (opens in a new tab) for 'Not found (404)' errors and fix them with redirects to the right page. Old URLs listed as 'Page with redirect' are expected.
After fixing an issue, use Validate fix; Google says validation typically takes up to about two weeks.
Compare clicks and impressions by page against your baseline, weekly for the first few months.
Watch the Core Web Vitals report for regressions on the new templates.
Keep checking conversions, since rankings and enquiries can move independently.
Check Bing Webmaster Tools as well; Microsoft Copilot grounds its web answers through Bing, as explained in our guide to how AI assistants recommend businesses.

If you want a redesign planned and built this way, our website design and development service starts with a free 30-minute call and gives a fixed written quote within 2 working days once we have the information we need.

Frequently asked questions

Will a website redesign hurt my SEO?

It can if URLs change without redirects or content is removed. With a full URL mapping, permanent server-side redirects, carried-over metadata and close monitoring, most of the risk can be managed, though Google says to expect some temporary fluctuation.

How long should I keep 301 redirects after a redesign?

Google's site move guidance says to keep redirects for as long as possible, generally at least one year. Many sites keep them permanently because links from other sites keep using the old URLs.

Should I change my URLs during a redesign?

Only if the new structure is clearly better for visitors. Keeping existing URLs avoids redirect work and risk. If you do change them, map every old URL to its closest new equivalent.

What Core Web Vitals scores should a new website hit?

Aim for Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile on mobile and desktop.

Does my redesigned website need to meet WCAG 2.2?

WCAG 2.2 AA is the current W3C recommendation and a sensible target for any new site. Whether it is a legal requirement depends on your country and sector, so check what applies to you.

Sources

Checked on 23 October 2026. Platforms and rules change; check the source before acting on anything time-sensitive.