Most redesigns are judged on the day they launch. Traffic is judged three months later—and that is where many projects quietly fail.
A new theme, a cleaner navigation, and faster pages can still lose rankings if the migration breaks the signals search engines already trust. After leading SEO-safe redesigns for enterprise and award-winning sites, I treat migration as its own workstream, not a task squeezed in before launch.
Start with an inventory, not a design
Before anyone opens Figma, export everything the current site is ranking for and everything it links to. You cannot protect what you have not measured.
- Every indexable URL, from a crawl and the XML sitemap
- Top landing pages by organic sessions and conversions
- Queries and positions from Search Console
- Internal links, canonical tags, and existing redirects
- Structured data currently in use
This list becomes the contract for the project. Any page on it either keeps its URL or gets a deliberate, mapped replacement.
Map every URL before you build
Redirects are not cleanup work. They are architecture. Build a redirect map early and review it with the content team, because URL decisions shape templates, taxonomies, and navigation.
- Keep URLs unchanged wherever the content still exists
- Map changed pages one-to-one with a
301to the closest equivalent - Avoid sending old pages to the home page—it reads as a soft 404
- Remove redirect chains so every old URL resolves in a single hop
Preserve content signals
A page that ranks for a reason should keep that reason. When content is rewritten, keep the primary topic, headings, and key internal links. Design can change completely; meaning should not.
Rebuild the technical foundations
A redesign is the best moment to fix what the old theme got wrong. I build these into the theme itself so they cannot be forgotten on a single page:
- Clean heading hierarchy generated by templates, not editors
- Automated schema for organization, articles, services, and breadcrumbs
- Correct canonicals and pagination
- Fast, stable pages: optimized images, deferred scripts, no layout shift
Stage, test, and launch deliberately
Crawl the staging site and compare it with the original inventory. Every missing URL, new 404, or changed title should be explained before launch day.
On launch, submit the new sitemap, validate the redirect map against live URLs, and keep the old crawl for comparison. The first two weeks matter most.
Measure after launch
Rankings often wobble for a few days as search engines re-crawl. What matters is the trend. Watch impressions, crawl errors, and top landing pages weekly, and fix gaps immediately.
Done well, a redesign is not a risk to SEO. On one platform I rebuilt, organic traffic grew 40% within three months—because the migration kept everything that already worked and the new theme removed what held it back.
Frequently asked questions
Will a redesign always cause a temporary ranking drop?
Not always. Small fluctuations are normal while pages are re-crawled, but a careful URL map, preserved content, and clean redirects usually keep the dip short or avoid it entirely.
How long should I keep 301 redirects?
Keep them permanently where possible. Old URLs keep receiving links and bookmarks for years, and removing redirects throws that value away.
Should I change URLs to make them cleaner?
Only when the benefit is real. Clean URLs are nice, but unchanged URLs are safer. If you change them, map every one with a single-hop 301.