Treat a same-CMS visual redesign as an SEO event: freeze the current URLs and templates, constrain the build, then launch with a 30-day crawl and coverage watch.
I wrote the long version because teams keep treating this as a slogan instead of a sequence. The short version is still useful: decide what the page or site is actually for, then protect the URLs, the offer, and the HTML Google can fetch.
What this actually means
Same-CMS website redesign SEO: freeze URLs, constrain templates, QA staging, then watch Search Console for 30 days. Not a platform migration plan.
Most of the damage I see is not a missing plugin. It is a missing owner. Someone redesigned the template, dropped a title, hid the copy behind a click, or launched without a redirect map. Then they asked why traffic moved.
The parts I would not skip
- A same-CMS visual redesign still changes the HTML Google ranks, even when slugs stay put.
- Freeze crawl data, Search Console, nav, and schema before anyone opens Figma.
- Constrain templates, crawlable links, and LCP during design, then QA staging as if it were live.
- Launch with a sequence and a 30-day coverage watch, not a reveal-day hope.
If you only do one thing, do the inventory first. Crawl the current site. Export Search Console. Write down the URLs that already earn clicks or conversations. Those pages are the contract. Everything else is decoration until that list is safe.
How I would use this
I treat this as a working note, not a manifesto. Use it before you hire, before you migrate, or before you open a new design file. If the current site already works, do not blow it up for a moodboard.
This is an adapted version of a longer guide. The full walkthrough, examples, and implementation notes live on my site.
Read the full article: Website Redesign SEO: What to Fix Before, During, and After Launch
Top comments (0)