The URL inventory, 301 redirect map, pre-launch checks and first-month monitoring that keep your search traffic after a redesign.
It happens more often than anyone admits. A company launches a gorgeous new website on Monday. By the end of the month, enquiries have dropped by half. Someone finally checks Google and finds that the pages which used to rank on page one now lead to a "404 — Page not found" error.
Nothing was wrong with the design. The problem was that years of search visibility were attached to the old URLs, and nobody told Google where those pages went. The fix is not complicated, but it has to be planned before launch — not discovered after.
Here's the process we follow on every redesign, whether it's a small business site or a large catalogue.
Why redesigns lose rankings
Google ranks individual pages, and it remembers them by their address. Over time, each URL collects signals: links from other websites, a history of people clicking and staying, and Google's understanding of what that page is about. A redesign risks throwing that away in a few common ways:
- URLs change without redirects: /services/web-design.php becomes /web-design, and the old address simply dies.
- Content is removed or thinned out: a detailed 1,200-word service page is replaced by three lines and a stock photo.
- Titles and headings are rewritten without the words people search for.
- The staging site is left blocked from Google, and the block is launched with the new site.
- Internal links, sitemaps and structured data are forgotten.
None of these are about design. They're about continuity — making sure everything Google already trusts carries over.
Most of the SEO work happens before launch. The first month after launch is for checking and fixing.
Before you design anything: take an inventory
1. Crawl and export every URL
Get a complete list of the current site's pages. A crawler tool (Screaming Frog is a popular one, free for small sites) finds everything that links together. Add URLs from your sitemap and from Google Search Console's Pages report, which also shows pages Google knows about but your menus may not link to anymore.
2. Find the pages that matter
In Search Console's Performance report, sort pages by clicks over the last 12–16 months. In Google Analytics, look at which pages bring visitors from organic search and which lead to enquiries or sales. Mark your top pages clearly — these must be treated with extra care.
3. Check which pages have backlinks
Pages that other websites link to carry authority. Search Console's Links report shows your most-linked pages. Losing one of those without a redirect throws that value away.
Save a copy of the old site's titles, meta descriptions, headings and main content before anything changes. It's far easier to compare old and new when you have both side by side — and it's your safety net if rankings drop.
Keep URLs where you can
The simplest way to avoid problems is to keep the same URLs for pages that still exist. If /about still describes your company, leave it at /about. Only change URLs when there's a real benefit — a cleaner structure, a move from messy parameters to readable addresses, or adding language folders like /th/ and /en/.
Build the redirect map
For every old URL that changes or disappears, decide where it should go and set up a 301 redirect — a permanent redirect that tells browsers and Google "this page has moved here". Google passes the old page's signals to the new address when the redirect points to an equivalent page.
Every old URL gets a home. The red row is the classic mistake: redirecting everything to the homepage.
A few rules make the difference between a clean migration and a messy one:
- Redirect to the closest equivalent: the old "wedding cakes" page goes to the new "wedding cakes" page — not the homepage.
- Don't redirect everything to the homepage: Google often treats mass redirects to the homepage as soft 404s, and the value is lost.
- Avoid chains: A → B → C slows things down and leaks value. Point A straight to C, and update older redirects too.
- Use 301 (permanent), not 302 (temporary): 302s tell Google the old page will come back.
- Let truly obsolete pages go: a product you no longer sell with no equivalent can return 404 or 410. That's fine — just not for pages with traffic or links.
Carry the content over properly
The new site should cover everything the old ranking pages covered — ideally better. If a service page ranked because it answered detailed questions, keep those answers (tidied up, updated, better designed), not a shorter "cleaner" version.
- Keep the words people search for in titles, headings and body text.
- Write a unique title and meta description for every page.
- Keep or improve structured data (business details, FAQs, articles, products).
- Keep image alt text and, where possible, the same image file names for important images.
The pre-launch checklist
This is where most disasters are prevented. Test on the staging site, then again on launch day.
Run this list on the staging site and again immediately after launch.
Launch day and the first month
Launch early in the week and early in the day, when your team and developer are available — never on a Friday evening before Songkran. Then:
- Remove any staging blocks: check robots.txt and "noindex" tags immediately after launch.
- Test the redirects: run your old URL list through a crawler and confirm every one returns a 301 to the right page.
- Submit the new sitemap: in Search Console, submit the new XML sitemap and request indexing for your key pages.
- If the domain changed: verify the new domain in Search Console and use the Change of Address tool.
- Watch Search Console daily for two weeks: look at the Pages report for new "Not found (404)" errors and fix them with redirects.
- Compare rankings and clicks weekly for a month: some movement is normal; steady drops on specific pages point to a missing redirect or missing content.
It's normal for rankings to fluctuate for a few weeks after a big migration while Google re-crawls and re-evaluates the site. A well-planned redesign usually settles back to where it was — and often higher, because the new site is faster and clearer.
Redesign as an SEO opportunity
Done well, a redesign is one of the best things you can do for search. Faster pages (see our guide to website speed), clearer structure, better mobile experience and stronger content all help. On our own site we recently moved from old-style "#" links to proper page addresses — exactly because Google couldn't index the individual pages before.
If you're planning a redesign and want to keep what's working while fixing what isn't, talk to us. We include the URL inventory, redirect map and post-launch checks in every redesign — see our services.
Frequently asked questions
Will I lose my Google ranking if I redesign my website?
Not if the migration is planned: keep URLs where possible, 301-redirect every changed URL to its closest equivalent, carry over the content and titles that ranked, and monitor Search Console after launch. Short-term fluctuation is normal.
How long do 301 redirects need to stay in place?
Keep them for at least a year, and ideally permanently. Other websites, bookmarks and old emails will keep using the old addresses long after Google has updated.
Should I change my domain name during a redesign?
Only if there's a strong reason. A domain change adds risk and extra steps (redirecting every URL and using Search Console's Change of Address tool). Changing design and domain at the same time makes problems harder to diagnose.
What is a redirect map?
A spreadsheet listing every old URL and the new URL it should redirect to. It's the single most important document in a website migration.