Website Redesign Checklist for Forms, Mobile Layouts and Content

A website redesign can improve clarity, mobile usability and the way customers contact you. It can also remove useful pages, break old links or accidentally hide the new website from search engines. The safest starting point is to understand what the existing site already does before replacing its appearance.

This website redesign SEO checklist is for a business owner preparing to work with a designer or developer. It focuses on preserving useful content and customer journeys while making deliberate improvements. No migration plan can guarantee unchanged rankings, but a documented process reduces avoidable mistakes.

Record the current website before changing it

Make a list of the existing public URLs. Include service pages, useful articles, product pages and important downloadable files. Note which pages receive enquiries, have meaningful search visibility or are linked from other websites. If analytics is available, save a baseline for comparison.

Review the content as well as the traffic. A page with modest visits may answer an essential customer question or be linked from proposals and social profiles. Do not delete it solely because it is not a top landing page.

Record the important journeys: finding a service, opening the menu, submitting an enquiry, completing a booking or placing an order. These are the tasks the new design must still support. A redesign acceptance checklist should include business behaviour, not only visual approval.

Decide what to keep, improve, merge or remove

Give each existing page a deliberate decision. Keep pages that remain useful. Improve pages with an unclear offer or outdated details. Merge pages only when they genuinely answer the same need. Remove content that no longer has a valid purpose, while considering what should happen to its old address.

Do not rewrite everything merely to make it sound different. Preserve accurate explanations, useful examples and important information. A visual redesign can use the same URL and much of the same core content while improving hierarchy, navigation and readability.

Be especially careful with service names. Your internal terminology may have changed, but customers may still search for the old service description. Explain the relationship in the page content where appropriate rather than making the previous offering disappear without context.

Create a URL mapping sheet

These are illustrative paths, not instructions to change your own site. Your mapping should use the real existing URLs and the actual destinations. Avoid sending every removed page to the homepage. A visitor following an old service link should reach the most relevant replacement when one exists.

Google’s site-move guidance recommends planning the URL mapping, implementing redirects and monitoring the transition. It also notes that search fluctuations can occur while Google processes changes. Use the guidance for the technical migration details.

Build and review the redesign safely

Use a staging or draft environment so the current website can continue serving customers while work is reviewed. Ensure test pages do not become an accidental public duplicate of the site. Keep a record of any access restrictions or indexing controls used during development.

Review realistic content in the new templates. A design tested only with short headings and perfect images may fail when a real service title wraps onto several lines. Include long form labels, missing optional images and the product variations your customers actually use.

Test the mobile layout early. Navigation, contact actions, tables and sticky elements are frequent sources of friction. Do not leave these checks until the final hour, when every correction feels like a launch delay.

Check the search-facing details

Review the title, main heading, canonical URL and description for important pages. Ensure internal links point to the intended public destinations. Check that image paths and downloadable files still work after any move.

Confirm that the sitemap contains the intended live URLs and that the public pages are accessible. Remove development-only indexing restrictions at launch where appropriate. Keep the site’s ownership verification method intact when changing themes or hosting arrangements.

Structured data should describe the content that actually appears. Do not carry over outdated business details, invented reviews or a false address. A redesign is a good opportunity to make the website more accurate, not merely more decorated.

Use a controlled launch sequence

1. Confirm the backup and the person responsible for recovery.
2. Approve the new pages and key customer journeys.
3. Apply the planned URL handling and publish the redesign.
4. Check the site while logged out.
5. Test enquiries, menus and any transactional flows.
6. Check the sitemap, important URLs and Search Console reports.

Schedule the launch when support is available. A complex change immediately before a period when nobody can respond creates unnecessary risk. For a store, account for orders and data that may change during the transition.

If something is wrong, assess the impact before making another broad change. A single broken contact link needs a targeted correction. A wider deployment failure may require the recovery plan. Preserve enough information to understand what happened.

Monitor after launch using the baseline

Check for broken links, unexpected redirects and customer reports. Compare important landing pages and enquiry patterns with the baseline, allowing for normal variation. Do not interpret one quiet day as proof of a search problem or one busy day as proof of SEO success.

If the redesign also involves moving servers or changing the domain, treat that as a separate migration task. Start with the WordPress website migration service and map the hosting or domain change before launch.

Use Search Console to review how Google is processing the site, but distinguish a submitted sitemap from confirmed indexing. A URL can be discoverable without already appearing in search results. Keep technical errors and ordinary processing delays separate in your issue log.

Continue reviewing the copy and navigation as real visitors use the redesign. The launch is a milestone, not the end of learning. A useful improvement might be a clearer service explanation or a shorter enquiry form rather than another visual overhaul.

Should every redesign change the URLs?

No. If existing URLs are clear and useful, keeping them can simplify the project. Change addresses for a reason, then plan how old links will be handled.

Can a redesign guarantee more enquiries?

No. It can improve the conditions for conversion, but results also depend on your offer, traffic and response process. Define the intended improvement and measure the relevant journey.

Explore our website design service and working process. To discuss a redesign, send your current website and the problems you want solved.

Use a content-retention decision for every useful URL

Mark pages as retained, improved, consolidated or intentionally retired. Map changed addresses to relevant destinations and keep the approved reasons. Include service explanations, image descriptions, metadata and contextual links; a visual screenshot cannot establish that those fields survived the rebuild.

Test several screen widths with real material

Long service names, unbroken URLs, tables, embeds and actual images reveal problems that short demonstration content hides. Check navigation, focus, tap targets, sticky elements and unintended horizontal overflow. Preserve intentional scrolling inside components such as tables while fixing page-level overflow.

Separate preview approval from live verification

The live host, caches and integrations can behave differently from staging. Confirm the backup and recovery arrangements, obtain launch approval and repeat the important URL and inquiry tests on production. A form’s success screen and recipient delivery are separate observations; record both.

For a project-specific assessment, review the relevant StartMyWeb service and send your website and requirements. Delivery is remote from Bengaluru, India; scope and timing are agreed in the proposal.