Contact us

Redesign launch guide

Website redesign. Keep what earns its place.

Before replacing a website, identify what customers already use and what search already finds. This website redesign SEO checklist turns that inventory into launch decisions, checks and a clear handover—not a promise that rankings will stay unchanged.

First decide: repair, redesign or rebuild?

If the problem is a confusing headline, a broken form or an oversized image, fix that first. A full rebuild is justified when the structure, publishing tools or functionality cannot support the business. An attractive new homepage alone is not a reason to replace every working page.

  • Repair: the structure works, but specific content or interactions fail.
  • Redesign: the offer and customer journey need a clearer presentation.
  • Rebuild: the current system cannot support required functionality or maintainability.

Before design: make a page decision register

List each current URL alongside its purpose, search clicks, enquiries, important links and proposed treatment. Use actual Search Console and enquiry records where available. Label missing measurement as unknown rather than assuming the page has no value.

For each URL, choose keep, improve or propose a move. Record the replacement and approval for any move. This register becomes the test list at launch; it prevents valuable service details from disappearing inside a visual refresh.

  • URL and customer question answered
  • Available search and enquiry evidence, with date range
  • Content, downloads and links worth preserving
  • Proposed destination, decision owner and approval
  • Launch check and result

During the build: test the answer and the action

Check that important text and links appear in the delivered page, not only after an animation or interaction. Give each page a clear heading, useful title and description, and its own canonical address. Structured data must describe what visitors can actually see.

Test real customer journeys at phone, tablet and desktop sizes. A contact button is not an enquiry: verify the form result, where the enquiry arrives and how a failed submission behaves. Keep names, emails and message contents out of analytics.

  • Compare old and new page content against the decision register.
  • Check navigation, internal links, downloads and any approved redirects.
  • Check image sizes, readable text, keyboard access and ordinary scrolling.
  • Keep staging restrictions intentional and remove them from public launch pages.
  • Check analytics page views and successful-enquiry events without duplicates.

At launch: verify the public version

Test the public domain after deployment, not just the preview. Confirm important pages return successful responses, moved pages redirect to the intended destination and truly missing pages return a real 404. Check canonical addresses, crawl permissions and the sitemap against the approved page inventory.

Keep the previous release and the decision register available so a broken journey can be repaired or rolled back. Assign someone to review launch failures; an unchecked list is not a completed launch.

After launch: watch pages, not just total traffic

Compare search clicks and impressions for important pages, inspect indexing issues and verify that enquiries still reach the right team. Use 30- and 60-day checkpoints rather than declaring the redesign a success on launch day.

A fall in one page's search visibility may be hidden by traffic to another page. Separate technical failures from changing demand and avoid attributing every movement to the redesign. Google documents that significant site moves can cause temporary ranking fluctuations.

OTO's own site: a practical preservation example

OTO Studio's website connects project previews, service pages, enquiries and an internal CRM. Presentation changes therefore need to preserve more than a screenshot: project links still need to open, visitors still need to scroll normally and enquiry paths still need to work.

That is the useful lesson for a redesign: make acceptance checks around what the business actually does. Our published project pages demonstrate design and customer journeys; they are not evidence of an independently measured SEO increase.

OTO Studio's Big Bites Shawarma website project
Big Bites Shawarma: a published project focused on the menu and ordering journey. View the case study →

Frequently asked questions

Does a website redesign affect SEO?
It can. Changing URLs, removing useful content, blocking crawlers or breaking links can affect search visibility. Keeping an address does not guarantee unchanged rankings. Google may need to recrawl and reassess changed pages, so record a baseline and monitor after launch.
Should every old page redirect to the homepage?
No. Where a page has moved, redirect to its relevant replacement. Sending unrelated pages to the homepage does not preserve the original answer. Pages without a replacement need an explicit content decision, not a blanket redirect.
Can we redesign without changing our domain or URLs?
Often, yes. A new visual design does not require a new domain or a new address for every page. Keep useful URLs where practical and separate visual changes from any proposed content consolidation.
How do we know the redesign worked?
Check that customers can complete the intended action, then compare qualified enquiries, search clicks and important landing pages against the baseline. Review at 30 and 60 days, allowing for seasonality and other campaign changes. A successful technical launch is not proof of a ranking or revenue increase.

Related