Website redesign checklist: protect search and inquiries

Record what works before changing it

A redesign should begin with the current site. Save a list of its public URLs, the pages people visit, the searches that bring them there, and the forms or telephone links that generate inquiries. If you have Google Search Console, export the available page and query reports before launch.

Keep copies of useful service descriptions, project photographs, downloadable documents, and account details. Confirm who controls the domain and hosting. These practical details prevent a design project from becoming an emergency migration.

Give every useful old page a destination

Keep an established URL when the page still serves the same purpose. When a page moves, map its old address to the closest relevant new page with a permanent redirect. Sending every old URL to the homepage makes it harder for visitors to find what they requested.

Update internal links to point directly to the new addresses. Check canonical tags, the sitemap, and any staging restrictions before release. Google's site-move guidance explains the URL mapping and migration process; a redesign does not guarantee an immediate ranking improvement.

Keep the information customers need

Review the new layout as someone unfamiliar with the company:

• Can you tell what the business does and which areas it serves?
• Are important services described on useful, distinct pages?
• Can you find relevant work, pricing or scoping information, and contact details?
• Does each page have an obvious next step?
• Are business details and appointment arrangements consistent?

Avoid replacing meaningful service copy with slogans alone. Strong photography can support an explanation, but visitors still need readable information about the offer.

Test the inquiry path on a phone

Read the page on a narrow screen. Check navigation, readable text, image sizing, visible focus, and fields that can be used with a keyboard. Try invalid input as well as a valid submission in an approved test environment. Verify that a successful submission actually reaches its intended destination.

Check telephone and email links. Confirm success messages and failure recovery. If payment is involved, use the provider's test setup and verify cancellation as well as completion. Do not use a real customer's details for testing.

Measure performance before prescribing changes

Use PageSpeed Insights and available field data to identify slow images, layout movement, or delayed interaction. Fix the observed problem instead of adding plugins on speculation. A responsive design and a fast score still need useful content and working functionality. See Google's page-experience guidance.

Release with a short verification list

After deployment, check the important public URLs, redirects, forms, metadata, sitemap, and mobile navigation again. Submit the updated sitemap in Search Console and inspect key pages. Continue watching indexing, search clicks, and inquiries so problems are caught after launch as well as before it.

For an upcoming move, discuss your website redesign. Our Rochester Hills web development service covers the site itself, while technical SEO addresses discovery and URL consistency.