A redesign can improve how your website looks, reads and works. It can also change the pages people find through search, the information on those pages and the routes visitors follow to make an enquiry.
Protecting search performance starts with understanding the existing site. Leave that until launch week and important decisions may already have been made without the evidence they needed.
This checklist is for business owners and marketing teams commissioning a rebuild. It explains what to discuss with the people responsible for design, development and SEO, and what evidence to ask for at each stage.
Record what matters before changing it
Create a baseline that the project team can return to. Record the pages attracting relevant search visits, the enquiries they support and the searches bringing people to them. Include seasonal context where available; comparing a busy period with a naturally quiet one can give a misleading impression.
Alongside performance data, make a content inventory. Include service pages, articles, case studies and useful downloads. Ask staff which pages they send to prospects and which resources answer recurring questions. Commercial value is not always visible in traffic totals.
The output should be a shared list of content to preserve, improve, combine or retire. Give each decision an owner.
Agree what each important page needs to keep doing
A page may be valuable because it answers a specific question. Removing that answer to create a shorter layout can weaken the page’s usefulness even when its address stays the same.
For each important page, write a short acceptance note. For example: “This page must explain commercial lift servicing, identify the service area and provide a clear route to request a maintenance discussion.” This is an illustrative requirement, not a client case study.
These notes help the designer and copywriter preserve the purpose of the page while improving its presentation. They also give reviewers something more concrete to assess than whether the new version looks better.
Plan any changed URLs
Google’s site-move guidance recommends preparing a mapping between old and new URLs, updating references to those URLs and monitoring the move. It also warns that search rankings can fluctuate while changes are processed. No responsible migration plan can guarantee identical positions throughout a rebuild.
Keep existing addresses where they remain suitable. Where a page moves permanently, have the developer implement and test an appropriate permanent redirect. Google’s redirect documentation identifies server-side 301 and 308 responses as permanent redirects.
| Existing page | Proposed treatment | Review question |
|---|---|---|
| Useful service page with an appropriate address | Retain URL | Does the new version still answer the same need? |
| Page moving to a new address | Redirect to its replacement | Does the destination serve the same purpose? |
| Overlapping pages being combined | Review each old URL against the combined page | Has useful information been retained? |
| Obsolete content without a relevant replacement | Review retirement and error handling | Are there links or user needs still to address? |
Avoid treating the homepage as a universal destination for removed pages. A visitor following a specific service link needs a relevant answer.
Make the staging review practical
Review the working website using real tasks. Start at a service page, follow a related case study and submit an enquiry. Check a resource download and a page that previously performed well in search.
Record issues in a shared list with a named owner and a decision on whether they block launch. This prevents essential checks being lost among minor design preferences.
Include these questions:
- Have approved content and essential downloads been transferred?
- Do navigation and contextual links lead to the intended pages?
- Are page titles and headings appropriate to the content?
- Do forms work, and do messages reach the correct recipient?
- Are links, images and canonical references using the intended live addresses?
- Have the agreed mobile and accessibility checks been completed?
Check indexability when going live
Development environments need protection, but those settings must not unintentionally prevent the finished site appearing in search.
Google explains that a noindex instruction can exclude a page from search, and that Google must be able to crawl the page to see it. Blocking a URL in robots.txt is not an interchangeable method of preventing indexing. Ask the developer to verify the final live configuration rather than relying on a general “SEO enabled” setting.
This is a technical acceptance check. It should have a recorded result and a responsible person.
Give launch day a clear owner
Agree who can authorise launch, who changes the hosting or DNS settings if needed, and who checks the site afterwards. Record how to respond if a critical problem appears.
Test priority journeys on the live domain. A staging form may have worked while the live notification address, integration or email configuration differs. Check a selection of old links directly as well as clicking around the new navigation.
Keep a dated launch log. It becomes useful when investigating changes in enquiries, tracking or search performance.
Monitor pages and enquiries after launch
Review Search Console for changes in visibility and indexing. Compare important pages and relevant queries, alongside actual enquiries and analytics. A tracking change can look like a traffic loss, so check measurement before drawing conclusions.
Agree a follow-up schedule and who investigates issues. The handover should include responsibility for the first weeks after launch, even if the ongoing arrangement changes later.
If you are replacing an established site, bring its search performance into the brief from the start. Talk to Think Digital about your website redesign and the requirements for your new website.
Technical references: Google: site moves, permanent and temporary redirects, and noindex instructions.
