Quick Answer
A redesign SEO plan should account for existing URLs, useful content, internal links, metadata, canonical information and intended crawl and indexing access. Record the baseline, review changes in development, test the actual launch and monitor the affected pages afterward. Map changed URLs to relevant destinations. No checklist can guarantee unchanged rankings, but a documented plan helps prevent avoidable publishing and migration errors.
A layout change can affect how content and links are delivered even when the domain stays the same. A platform or URL change adds more dependencies. Assign a reviewer before implementation so these decisions reach the actual launch plan.
Download the editable website redesign SEO checklist (XLSX, approximately 6 KB). The workbook includes 30 checks with blank owner, status and evidence fields. Assign each check, record its status and add evidence as the work is completed.
Before design: preserve the evidence
- Inventory public URLs, page types, important files and useful content.
- Record available Search Console performance and indexing context with its property, dates and filters.
- Keep representative delivered titles, descriptions, canonical information, headings and internal links.
- Identify the business actions supported by important pages.
- Record which URLs and content are expected to remain, move, consolidate or be retired.
Include pages reached through old campaigns, external links or bookmarks, rather than relying only on the current navigation menu. Keep the inventory with the content and technical scope.
Define the changes before building them
Separate a layout redesign from a domain move, platform change and URL restructure. Google’s site-move guidance recommends changing one thing at a time where practical. If the project combines changes, document the dependencies and verification needed to distinguish problems.
Keep an established URL when it still represents the same useful content. A cleaner page title or new navigation label does not automatically require a new address. If a page moves, choose the relevant destination by its content and customer purpose.
Review the redirect decisions
Use a human-reviewed map of old and new addresses. Google’s redirect documentation explains permanent and temporary redirects and the signals they provide. A permanent page move generally calls for an appropriate permanent server-side redirect, such as 301 or 308.
Avoid sending unrelated removed pages to the homepage. Google’s move guidance warns that irrelevant destinations can confuse visitors and be treated as soft 404s. When no useful replacement exists, have the technical and content owners agree on the correct retired-page treatment.
- Illustrative redirect record
- Old path:
/services/old-name/. Intended new path:/services/current-name/. Decision: permanent move of the same service explanation. Verification to perform: old address returns the intended permanent redirect, destination loads successfully, and destination content and canonical information match the agreed page.
The redirect-map guide explains the supporting workflow in more detail. Update the site’s own links to the intended destinations instead of leaving avoidable internal redirect chains.
Before launch: test representative output
- Check the homepage and representative service, article, category, product or other templates in scope.
- Confirm important text and links are delivered and understandable.
- Compare titles, descriptions and headings with the approved content.
- Check canonical references, sitemap destinations and intended indexing instructions.
- Test mapped redirects and relevant retained URLs.
- Check mobile behavior, important forms and applicable performance and accessibility requirements.
- Identify development access restrictions that must change only through the approved production release.
Keep private development copies appropriately restricted. The deployment owner should have an explicit plan for public production access, intended indexing and production canonical URLs. A staging hostname or development noindex instruction can become a launch defect if carried into the wrong output.
At launch: verify the actual site
Retest the public responses and page output after deployment. A successful development check does not establish that the production domain, cache, redirects and configuration are identical. Verify the agreed sitemap and important URL destinations.
Use Search Console’s Change of Address tool only for the moves it supports. It is not a requirement for an ordinary redesign, a path-only change or an HTTP-to-HTTPS move. The responsible property owner should confirm applicability and permissions before using it.
After launch: monitor and investigate
Watch the agreed important pages, crawl and indexing information, actual customer tasks and search metrics. Preserve the release date and changes beside the observations. Google notes that search results can fluctuate while a significant move is processed; a matching date alone does not establish the cause of a decline.
Maintain redirects for an appropriate duration. Google recommends keeping them as long as possible, generally at least a year, and considering longer retention for visitors. Review the domain and infrastructure arrangements needed to keep them working.
Use the traffic-drop investigation guide to separate report scope, affected groups and possible causes. The broader launch checklist covers customer journeys beyond search.
Key Takeaways
- Preserve a useful URL and content baseline before redesign work.
- Map changed pages to relevant destinations and test actual responses.
- Check delivered content, metadata, canonical and indexing information before and after launch.
- Use Change of Address only for applicable moves.
- Keep release records and investigate changes without assuming a ranking guarantee.
Frequently Asked Questions
Will a redesign hurt SEO?
Its effect depends on what changes and how those changes are implemented and processed. Preserve useful content and addresses, verify the output and monitor the actual site without promising unchanged rankings.
Does every old page need a redirect?
Review each relevant URL. A moved or consolidated page needs an appropriate destination; an unrelated homepage redirect is not a suitable default for every retired page.
Should I submit Change of Address when only the layout changes?
No. Review the tool’s supported moves. A normal layout redesign without an applicable domain or subdomain move does not require it.
For a planned website redesign, agree on the URL inventory, search review and launch responsibilities in the scope. A website audit can identify issues that need investigation first.

