WEBSITES / SEARCH
Website Redesign & Relaunch SEO Checklist
Before a website redesign or relaunch, record your important URLs, map any moves, check indexing settings and test the live release. This guide includes a downloadable checklist, a redirect mapping example and checks for before launch, launch day and the following weeks. Use it for a visual redesign, a platform migration or a site move, adapting the checks to what actually changes.
Start here: checks before, during and after a relaunch
- Before launch: save the search baseline and URL inventory, approve redirects, preserve useful content and review the production indexing settings.
- On launch day: test old and new URLs, canonicals, internal links, language versions, downloads and the complete inquiry route.
- After launch: inspect priority URLs in Search Console and compare the same pages and queries over complete periods. Investigate errors before making further changes.
Capture the current site before changing it
Save an inventory of public page URLs, page titles, language, main purpose and destination action. Add useful search queries and landing-page data from Search Console when available. For a new site with no history, record that limitation instead of inventing a performance baseline.
Prioritize pages that lead to relevant inquiries, not just pages with large visit counts. Record whether a visitor can contact you, download a brief or understand a service from each important landing page. Those tasks should survive the redesign.
Make a decision for every old URL
Use a working table with old URL, proposed URL, action, reason, owner and test result. The action might be keep, replace with a relevant page, or remove without a replacement. Avoid changing an address merely to make a new folder structure look cleaner.
Google’s site-move guidance recommends mapping old URLs to their replacements and implementing redirects. For permanent moves, use server-side permanent redirects where possible. A redirect does not guarantee that rankings will stay unchanged.
Hypothetical example: an old /services/erp.html page becomes /en/services/erp-development/. The new page should still answer ERP-related needs. Sending every retired service page to the homepage loses that specific destination for visitors.
Check each language as a separate customer journey
For an English and Spanish site, review both versions from the navigation through the contact step. A translated headline is not enough if a button leads to a form in the wrong language or a download still contains the old business details.
Check that each language switch opens the equivalent page, that each page identifies its preferred URL, and that language alternates agree. Keep commercial details accurate for the market you actually serve; do not add an office location that does not exist.
Prepare a launch acceptance list
Give each check a named owner and a place to record evidence. Run the list against the release that will actually go live, not an earlier design preview. Verify contact actions using test details and ensure a draft email is not described as an already-submitted inquiry.
- Open important pages directly and through navigation on desktop and mobile.
- Test old links, downloads, language switches and relevant redirects.
- Confirm the live pages intended for search are accessible and do not retain staging noindex settings.
- Review headings, descriptions, page-specific content and the sitemap.
- Check the real contact path and the availability of the previous release.
Compare outcomes after launch
Record the launch date and keep the old-to-new URL table. Review indexing, search impressions and inquiries separately: a technically accessible page is not proof that it is indexed, and visibility is not proof of a qualified lead.
Investigate drops by page and query before rewriting the whole site again. Check whether a valuable page disappeared, a destination changed, or a contact action broke. New sites may initially have little data; preserve the baseline and use observations rather than a promised ranking to decide the next change.
A website relaunch SEO plan your team can approve
Before design sign-off, separate a visual redesign from a move that changes page addresses, content or the publishing system. If a useful URL can stay, keep it. If several changes are necessary, record which change belongs to which release so a problem has a traceable starting point.
Use the following handover plan as a suggested working schedule, not a promise of ranking recovery. One person should own the launch decision; a completed checklist needs evidence, not just a tick.
| When | Check | Evidence to keep |
|---|---|---|
| Before development | Inventory important URLs, queries, languages and working inquiry routes. | Dated export and the owner of each important page. |
| Before launch | Review replacement content, direct redirects and production indexing settings. | Approved URL map and results against the release candidate. |
| Launch day | Open old links, verify final destinations and submit a clearly labelled test inquiry. | Status results, final URLs and confirmation that the inquiry reached its recipient. |
| First week | Review key URLs and investigate unexpected errors or missing pages. | Search Console observations and a list of issues with owners. |
| Following weeks | Compare the same pages, countries and queries over comparable periods. | Separate records of search visibility, clicks and qualified inquiries. |
A redirect mapping example: keep, move or retire
All URLs in this table use example.com and are fictional teaching examples, not pages on the Linx Labs website or redirects to copy into your site. Give every important old URL an explicit decision. For a permanent move, a 301 or 308 should lead directly to a relevant final page that returns 200. Update internal links to the final address rather than relying on the redirect.
If there is no relevant replacement, a genuine 404 or 410 can be appropriate. Do not redirect unrelated retired pages to the homepage. Test the exact old paths, including important language variants; a chain or loop can be missed when you only open the new homepage.
| Old URL | Decision / destination | Acceptance check |
|---|---|---|
| https://example.com/en/contact/ | Keep https://example.com/en/contact/ | The page opens and the contact route works. |
| https://example.com/services/web.html | 301 or 308 → https://example.com/en/services/web-development/ | One permanent redirect to a relevant 200 page. |
| https://example.com/es/diseno-web/ | 301 or 308 → https://example.com/es/services/web-development/ | The destination and inquiry flow remain in Spanish. |
| https://example.com/expired-offer/ | Retire; no equivalent replacement | 404 or 410; remove obsolete internal links. |
What to investigate if traffic drops after a redesign
First establish whether the drop concerns search impressions, search clicks or submitted inquiries. If clicks are similar but inquiries disappear, test the form and notification route before blaming rankings. If a particular page loses impressions, inspect that URL, its indexing status, replacement content and any redirect.
Compare the same search type, country and device, using complete periods and allowing for reporting delay. Record other changes such as removed content or seasonal demand. With a small sample, one high-position impression is not a stable ranking and zero clicks does not isolate a title problem.
A redesign can reduce avoidable migration mistakes; it cannot guarantee unchanged positions or a first-place result. Use the evidence to fix a specific issue before changing the entire site again.
TAKE IT WITH YOU
Your project checklist
- Save dated Search Console exports and record the search type, countries, devices and comparison period.
- Inventory important URLs, page content, titles, language versions and inquiry routes.
- Keep useful existing URLs where possible and assign an owner to each changed page.
- Map each moved URL to a relevant final destination; record retired pages without a replacement.
- Test permanent redirects for a direct path to the intended 200 page, without chains or loops.
- Preserve useful page content and review each title, description and main heading.
- Check production robots rules and remove unintended staging noindex restrictions from public pages.
- Verify canonical URLs and equivalent language alternates against the final public addresses.
- Update internal links and the sitemap to the preferred live URLs.
- Test priority pages, downloads and contact forms on mobile and desktop using labelled test details.
- Record launch approval and rollback conditions; inspect priority URLs and submit the sitemap in Search Console.
- After launch, investigate indexing errors and compare matched pages and queries; track inquiries separately from search clicks.
Use this checklist as a starting point. Adapt it to your systems and responsibilities; it is not a completed implementation plan.