Follow this website redesign SEO checklist in three phases. Before launch, inventory every URL that earns traffic or links and map each one to its new home. On launch day, remove staging noindex, deploy 301 redirects and submit a sitemap. After launch, watch Search Console indexing, 404s and rankings for several weeks.
The checklist
- Crawl the current site and export every URL, title, meta description, H1, canonical and status code.
- Export the pages with clicks from Search Console and the top landing pages from analytics for the last 12 months.
- List pages with external links pointing at them, since those links depend on the old URLs.
- Build a redirect map that pairs each old URL with the closest matching new URL, starting with the highest-traffic pages.
- Compare old and new pages for body copy, headings, internal links and structured data before approving the design.
- Keep the staging site blocked from search, and write down how it is blocked so the block can be removed at launch.
- On launch day, remove staging noindex tags and robots.txt blocks, and confirm canonicals point to the live domain.
- Deploy server-side 301 redirects and test a sample of old URLs, checking each lands on its final page in one hop.
- Confirm the analytics tag fires on every template and that Search Console verification still works.
- Submit the new XML sitemap in Search Console and check that it lists only live, indexable URLs.
- Update the website link on your Business Profile and main directory listings if any URL they use has changed.
- For the next several weeks, check the Search Console page indexing report, 404 errors and key rankings each week.
- Keep every redirect in place for at least a year, and update internal links to point straight at the new URLs.
Before: inventory what already earns traffic
Rankings belong to URLs and the content on them. If a page that brings in calls disappears or changes address without a redirect, Google treats the new page as a stranger. So the first job is a full inventory, before the designer finalizes the sitemap.
Three lists matter: every URL a crawler finds, every page with clicks in Search Console, and every page other sites link to. Pages that appear on the second or third list and have no place in the new design need a deliberate decision, not an accident. A technical SEO audit of the old site gives you that baseline.
Timing matters in Naples. If most of your revenue lands between November and April, plan the launch for the summer so any post-launch dip happens in the slow months and is fixed before season.
The redirect map: Google's rules
Google's site move guidance is specific. Map every old URL to a new one, starting with the most important. Use server-side permanent redirects (301 or 308). Redirect straight to the final destination, avoid sending large numbers of old URLs to the homepage, and keep redirects generally for at least a year.
| Old page | Redirect to | Avoid |
|---|---|---|
| Service page, same service on new site | The new service page | The services hub or homepage |
| Old blog post kept | The same post at its new URL | A chain through an old category URL |
| Page retired with no equivalent | The closest relevant page | Mass redirects to the homepage |
| Old PDF or image with links | The new file location | Leaving it to return 404 |
The Change of Address tool in Search Console is only for moving to a new domain or subdomain, not for a redesign on the same domain or an HTTP to HTTPS switch.
Content parity: the quiet ranking loss
Many redesigns keep every URL and still lose traffic, because the new pages say less. A 900-word service page becomes three lines and a slider; the FAQ disappears into an accordion that was never built; the internal links in the old footer are gone.
Compare each important old page with its new version: body copy, headings, internal links, image alt text and structured data. Structured data should match visible text, so if the content moves, the markup moves with it. Page builders also tend to add weight, so check speed on the staging templates, not after launch. If you are rebuilding on WordPress, our SEO-ready WordPress development builds parity checks into the project.
Launch day: the staging block trap
Staging sites are blocked from search on purpose, with a noindex tag, a robots.txt disallow, or both. The most damaging launch mistake is carrying that block onto the live site. Google says that when it sees a noindex rule it drops the page entirely from search results, so a forgotten tag can pull your pages out of search as soon as Google recrawls them.
Note one more detail from Google: if robots.txt blocks a page, Google never sees its noindex rule. On launch day, check both, check that canonical tags point to the live domain and not the staging address, and fetch a few live pages with the URL Inspection tool in Search Console.
After: what to watch and for how long
Google says that for a medium-sized site, it can take a few weeks or more for most new URLs to show in search. Expect some movement in that window. What you are watching for is a trend that does not recover:
- Pages stuck as excluded or not indexed in the page indexing report
- 404 errors on old URLs you missed in the map
- Redirect chains where an old URL hops more than once
- Core Web Vitals regressions on the new templates
- Map and organic rankings for your main service terms
If you want the whole move handled, our site migration SEO service covers the map, the launch and the monitoring.