Website redesign
Website redesign SEO checklist: protect the pages people already use
Short answer: A redesign needs a page-by-page plan as well as a new look. Record the URLs and content you already have, decide what stays or moves, test enquiries on the new site and check the published result. A sitemap submission helps discovery; it does not guarantee indexing or preserve a ranking by itself.
By YungsEnterprises · Practical buying guide
Record what exists before changing the design
A page that looks dated can still answer an important question, receive enquiries or have links pointing to it. Start by listing the current public URLs, the purpose of each page and its main enquiry action. Keep the list even if the new design uses a different menu.
Use the existing sitemap, Search Console and available analytics as evidence. Separate observed traffic from assumptions, and note which figures include your own testing. If a page has no usable history, mark the evidence as unknown rather than declaring it worthless.
- Record the URL, page title, primary topic and intended customer action.
- Note forms, booking links, downloads and important images used by each page.
- Record the reporting period and any known limits in the available data.
- Give every page a decision: keep, improve, combine, replace or retire.
Make a destination decision for each changed URL
A redesign does not require every URL to change. Where the page still serves the same purpose, keeping its useful address can simplify the work. When a URL must move, identify the closest relevant replacement before launch.
Google recommends mapping old URLs to new destinations, using permanent server redirects where possible and updating internal links and canonicals. Avoid sending unrelated retired pages to the homepage. A redirect, a canonical and a sitemap serve different purposes; adding one does not replace the others.
| Existing page | Decision | Launch check |
|---|---|---|
| /services/old-name | A directly relevant replacement exists | Check the permanent redirect reaches the final page. |
| /contact | Keep the purpose and address | Confirm the correct form receives an enquiry. |
| /outdated-offer | No equivalent offer remains | Confirm the intended missing-page response instead of an unrelated redirect. |
Keep the useful answer as well as the visual design
For each service page, write down the question it should answer: what the service does, who it suits, what the buyer supplies and the next step. A short, attractive headline needs supporting text that explains the actual offer.
Check the finished page title, description, main heading and social preview against that purpose. Remove old service counts or prices only where the underlying offer has actually changed and the new facts are approved. Do not fill missing proof with invented results, reviews or client logos.
Important explanations should be readable text. A video or animated demo can show an idea, but a buyer should still understand the scope and next step without operating it.
Test the entire enquiry path in the new design
A button opening a form is only the first check. Verify validation, a successful server acknowledgement, the receiving record and the person responsible for the next action. Keep native quote forms, general enquiries and demo requests distinct when they use different receiving paths.
Use a clearly marked test record and account for existing notifications before submitting. Exclude that record from acquisition reporting. A successful test confirms the path you exercised; it does not prove every form, booking calendar or follow-up workflow works.
- Open the relevant page on a phone-sized screen and follow its actual call to action.
- Check errors retain the entered information and success appears only after acknowledgement.
- Verify the enquiry in the receiving system, including the message and service context.
- Confirm the next owner and follow-up rule separately from form receipt.
Check the published site separately from the preview
A preview and a public release can show different builds. After publication, open the real domain and test the important routes, navigation and enquiry actions again. Keep a record of the release and what was actually checked.
Check that public pages can be crawled, the sitemap contains intended canonical URLs and temporary indexing restrictions have been removed where appropriate. Inspect changed pages in Search Console and monitor crawl or indexing problems. Submission and eligibility do not guarantee indexing or rankings.
Agree the launch record and the next review
Keep the old-to-new URL plan, the release date, the form-check result and the owner of remaining issues together. If the site moves between providers, confirm domain access, hosting, exports and who can make a correction after launch.
Review comparable periods once useful data is available. A short-term change in visits can have several causes, especially around a redesign. Inspect the affected pages and enquiry records before attributing the result to one design change.
YungsEnterprises scopes a managed website around the agreed build and ongoing care. A migration, complex integration or ongoing SEO campaign should be identified explicitly in the proposal. Use the existing inclusions guide and pricing page to prepare that conversation.
Further reading
Related reading
Turn the questions into a clear scope
Tell us what your business needs. We will discuss the feasible approach and confirm scope and pricing in writing.