NY Web Consulting — Results Driven Online Marketing Let’s talk

Web design

Website redesign SEO checklist: protect your URLs, content, and search visibility

Plan redirects, preserve useful content, test forms, and check indexing before a website redesign goes live.

A hand carefully moves a small architectural model from one paper plan to another beside an orange pencil.
  1. Inventory
  2. Map and test
  3. Launch and monitor

A website redesign should make your business easier to understand and contact. But a new layout can also leave old links broken, useful information missing, or inquiry forms disconnected from the people who answer them.

The practical question is: what needs to keep working when the new site replaces the old one? Treat that as part of the design brief, alongside the look and feel. This website redesign SEO checklist gives business owners a clear set of items to review with their team before launch.

Inventory the pages you already have

Start with a list of existing URLs. Combine a crawl of the current website with its sitemap, search performance data, and landing pages used in advertising or email. Include downloadable files and pages that may no longer appear in the main menu.

For each important page, record its purpose, useful content, incoming links where known, and the action a visitor should take. Search traffic matters, but a page that receives only occasional visits may still support a valuable service or an established customer relationship.

Our website planning guide explains how to connect this inventory to the customer journey. Use the evidence to decide what to keep, improve, combine, or retire; a cleaner navigation menu does not require deleting every page outside it.

Keep useful URLs and map the ones that change

Keep an established URL when it still describes the page accurately. A redesign does not require a new address for every service or article.

When a URL must change, give it a relevant destination. For example, an old /web-design/ page could redirect to /services/web-design/ if the new page serves the same purpose. A retired article should go to a genuinely relevant replacement, rather than automatically sending every old article to the blog index.

Google recommends permanent server-side redirects when a page has permanently moved. Ask your developer to test the response and final destination, rather than checking only whether something opens in the browser.

Existing page Decision What to verify
A service page with the same address Keep and improve The URL loads the intended page.
A service page with a new address Redirect The old URL permanently redirects directly to its replacement.
Two articles combined into a stronger guide Consolidate Both old URLs lead to a page that answers their original topic.
Content removed with no relevant replacement Retire The URL returns an appropriate 404 or 410 response.

Update links inside the new website to point directly to the final addresses. Keep redirects for existing bookmarks and links from other websites, and avoid chains that pass through several old destinations.

Preserve the information customers came to find

A visually polished page can still be less useful than the page it replaced. Check that the new copy explains the service, who it suits, where it is available, and how to take the next step.

Retain accurate answers to common questions, approved project examples, contact details, and helpful supporting articles. Review titles and descriptions so they match the new page, and use a clear main heading rather than relying on text inside an image.

If AI helps rewrite the content, compare the draft with approved business information. Service boundaries, platform experience, and customer claims still need expert review. Our SEO and search visibility work connects those content decisions with technical priorities and useful inquiry paths.

Separate review access from search indexing

The review copy of a website should stay out of search results. If it contains private material, it should also have access protection: a noindex instruction is not a password.

Before launch, check the public site’s robots settings, page-level indexing instructions, canonical URLs, and sitemap. A common handoff mistake is carrying a staging noindex setting onto the live domain. Another is publishing canonical URLs that still point to a temporary preview address.

Make this a named launch task with an owner. Check the actual deployed pages after the domain switch, as well as the settings in the project. A sitemap helps search engines discover URLs; it does not guarantee that every submitted page will be indexed.

Test the whole inquiry journey

Open the website on a phone and follow the steps a prospective customer would take. Can they understand the offer, find a relevant service, and contact the right team without confusion?

Submit a real test inquiry through the main form and any compact forms elsewhere on the site. Confirm that verification works, the submission reaches the intended inbox, and the team can reply to the visitor. A success message alone does not prove inbox delivery.

Also check phone links, booking tools, download links, and campaign destinations. Where measurement is configured, verify that events represent the intended action and respect the site’s consent choices. A button click and a successfully delivered inquiry are different events.

Launch with a monitoring plan

Keep a record of the launch date, the redirect map, and who handles any issues. After release, check search indexing reports, broken URLs, important landing pages, and inquiry delivery. Compare changes in context: seasonality, campaign activity, and measurement changes can affect the numbers too.

Review results at page level so a problem with one service does not disappear inside a site-wide total. Keep the previous deployment available for rollback, with clear responsibility for deciding when a rollback is necessary.

Search visibility can fluctuate after significant changes. Google’s site migration guidance provides a detailed reference when URLs change. A hosting change that preserves URLs needs a different scope of checks from a move to a new domain; agree what is actually changing before combining several projects into one launch.

Bring the checklist into the design brief

Before approving a launch, ask for the URL inventory, redirect map, completed form tests, indexing checks, and a named follow-up owner. Those deliverables make the transition reviewable.

Our web design and development service plans the new experience around your business while accounting for the existing site’s useful content and links. If you are preparing a rebuild, tell us about your website so we can discuss the design and the transition together.

Back to resources

YOUR NEXT CHAPTER

Let’s talk about
where you want to go.

Start a conversation