A website redesign SEO checklist protects the useful pages, links and customer journeys your business has already built. Changing the appearance of a website can also change URLs, navigation, content, metadata and crawlability. Treat those changes as launch requirements, not tasks to fix after enquiries disappear.
This guide is for US small businesses and service companies replacing an existing site. It distinguishes a visual refresh from a URL migration and gives your developer, marketer and business owner a shared acceptance checklist. No checklist can guarantee unchanged rankings, but a disciplined process reduces avoidable technical mistakes.
Before design: record what the current site does well
Export a list of existing URLs from your sitemap and crawl. Review Search Console, analytics and business records to identify pages that attract useful visits, enquiries or purchases. Include pages with valuable backlinks, even if their recent traffic is modest.
Save the existing titles, descriptions, headings, canonical URLs and important content. Record the forms and conversion events that must keep working. If the site is small, a spreadsheet is often enough to connect each old URL to its planned destination and a responsible reviewer.
- Inventory indexable pages and important media URLs.
- Identify top enquiry and purchase entry pages.
- Document useful internal links and navigation paths.
- Capture a baseline for organic clicks and conversions.
- Separate intentional content changes from accidental omissions.
Website redesign SEO checklist for URL decisions
Keep existing URLs when the page’s purpose remains the same and there is no compelling reason to change them. A new design does not require a new slug. When a URL must change, map it to the most relevant new page rather than redirecting every old page to the homepage.
Google’s site-move documentation recommends preparing a URL mapping, using permanent server-side redirects where possible and monitoring the move. It also warns against irrelevant redirects and unnecessary redirect chains.
| Old page situation | Planned treatment |
|---|---|
| Same purpose, same content | Preserve the URL where practical. |
| Same purpose, changed URL | Redirect directly to the relevant new URL. |
| Several pages consolidated | Redirect to the genuinely relevant consolidated page. |
| Removed with no equivalent | Use an appropriate 404 or 410 response, not an irrelevant homepage redirect. |
For example, if a hypothetical contractor moves a roof-repair page into a new services section, its old link should lead directly to the new roof-repair page. Sending it to a general homepage makes the visitor repeat the search and may obscure the original page’s purpose.
Build and review the new site in staging
Keep staging out of search results using appropriate controls, then explicitly check which restrictions must be removed at launch. A forgotten noindex directive or blocking robots rule can stop otherwise complete pages from being indexed.
Compare the new pages against the content inventory. Confirm that important copy, useful headings, images and contact details have survived the redesign. Do not remove explanatory service content merely to create more whitespace; revise it with the user’s questions in mind.
Check canonical URLs, structured data and internal links. Internal links should point to final destinations rather than relying on redirects. Test mobile layouts, forms, checkout where relevant and analytics events with realistic data.
Run these tests before approving launch
- Redirects: request each important old URL and confirm the correct final destination.
- Status codes: useful live pages should return successful responses, not accidental errors.
- Indexing: verify live robots rules, page-level robots directives and canonicals.
- Sitemap: include intended live URLs and remove obsolete or staging entries.
- Navigation: confirm key service pages are reachable through useful internal links.
- Customer actions: submit forms, test notifications and confirm measurement events.
- Recovery: retain a backup and agree on the conditions for rollback.
Assign each test to an owner and record the result. A launch checklist without evidence is just a list of intentions. For a small site, a screenshot, response code or completed test order can provide a practical record.
Monitor after launch without overreacting to one day
Watch crawl errors, indexing, organic entry pages and business conversions. Inspect specific URLs when a page appears missing. Look for patterns such as an entire service section losing visibility or a form no longer reaching the sales inbox.
Google recommends keeping redirects for as long as possible, generally at least one year for a site move. Update your own internal links to new destinations rather than treating redirects as permanent navigation. Submit the new sitemap in Search Console where relevant.
A temporary traffic change does not by itself prove that the design caused a ranking problem. Compare similar periods, consider seasonality and check technical failures first. Keep a change log so the team can connect a symptom with a release rather than changing multiple settings blindly.
What not to change all at once
A simultaneous domain move, platform change, content rewrite and navigation overhaul makes troubleshooting harder. Where practical, reduce unnecessary changes and document the ones that are essential. Do not make cosmetic URL changes merely to insert more keywords.
For planning, use our website brief guide. After launch, our maintenance guide helps define ongoing monitoring and update responsibilities.
Frequently asked questions
Who should own the website redesign SEO checklist?
Assign a launch owner who coordinates the developer and SEO reviewer. Each URL mapping, indexing check and conversion test still needs a named person and recorded evidence.
Will a redesign automatically improve SEO?
No. Better usability and technical quality can help users, but rankings also depend on relevance, competition and other signals. A new appearance alone is not an SEO strategy.
Do I need redirects if URLs stay the same?
Not solely because the design changes. You still need to test canonical URLs, internal links, indexing rules and server responses.
Should every deleted page redirect to the homepage?
No. Redirect only to a relevant replacement or consolidated page. Google warns that irrelevant redirects can confuse users and may be treated as soft 404s.
Keep the website redesign SEO checklist with your release notes. Record when redirects and indexing rules change, then use that record when investigating a missing page or an enquiry-tracking problem. This prevents the team from repeating tests or making several speculative changes at once.
Plan an SEO-aware redesign
The Tetra Technology combines website development, hosting and SEO services. Review our redesign and SEO capabilities, then request a redesign assessment. Include your current domain, important conversion pages and planned platform changes so the project can preserve the things that already work.
