Keep every URL that already earns clicks, impressions or links: that is the heart of how to redesign a website without losing Google rankings. Map each changed URL one-to-one to its closest new page with a 301 redirect, carry over titles, headings and body content, and test before launch. Google Search Central recommends preparing a URL mapping first.
Your current website may look dated, load slowly and embarrass you on sales calls. It is also, right now, the thing Google trusts. Every ranking you hold sits on specific URLs, specific titles and specific body copy that have been indexed and linked to for years. A redesign puts all of it on the table at once.
Search often becomes a late checklist item, somewhere after wireframes and before launch. That order is how a business loses a decade of rankings in one afternoon of DNS changes. Pages disappear, URLs change, nobody keeps a record of what used to exist, and the drop only becomes obvious weeks later when the phone stops ringing.
This guide is for owners and managers of small Canadian businesses who are planning a redesign and cannot afford to lose the traffic they already earn. We have built and redesigned websites on Webflow, WordPress and Shopify since 2021 for clients across Canada, including repairs on migrations that went wrong. Here is the process we use, in order.
Redesigns lose rankings when the new site breaks the connection between what Google has indexed and what you now serve. The causes are mechanical, and there are four of them.
URLs change. A new platform, a new navigation or a tidier folder structure renames pages. Every renamed page with no redirect becomes a 404, and the links and history pointing at it stop counting.
Pages disappear. A ten-page redesign of a forty-page site quietly deletes thirty pages, often the service and location pages that were doing the ranking work.
Content gets cut. Design-led rebuilds shorten copy to fit a layout. The paragraphs that matched the search query go with it.
Nobody checks. The site launches, the team celebrates, and no one opens Search Console until a slow quarter prompts the question.
None of that is a design problem. It is a migration problem that happens to arrive with new visuals, which is why we treat ranking protection as part of scope on every web design project rather than a post-launch favour.
Record the current state of the site before a single page is rebuilt, because once the old site is gone the evidence is gone with it. You need four things: what Google sends you, what pages exist, who links to you, and what each page currently says.
Google Search Central's site move guidance says to prepare a URL mapping from your current URLs to their new format and to test the new site thoroughly before you start the move. That mapping is impossible without a baseline. Capture it in one spreadsheet that the design team, the developer and the owner can all see.
When we rebranded CLG Injury Law, a personal injury and disability firm with six offices across New Brunswick, Nova Scotia and PEI and nearly four decades of history, the brief was to modernise without losing anything the firm had built. On the website side that meant exactly this inventory first: every page and URL already earning search traffic identified before the new Webflow build began.
Use one rule: any page with impressions, clicks or a backlink keeps its URL or gets a one-to-one redirect. Everything else is merged into the nearest page or retired. That single rule settles arguments about which pages "feel" important, because the decision comes from data you exported in the previous step.
Run each URL through the table below and write the decision in the same spreadsheet. Near-duplicates get merged behind one surviving URL so the signals land on one page instead of three. Thin pages that earn nothing get archived rather than rebuilt, which shrinks the build and the ongoing maintenance.
| Page signal in the last 90 days | Decision | URL treatment |
|---|---|---|
| Clicks, or impressions worth having | Keep | Same URL, page rebuilt around the same topic |
| No traffic, but an external backlink | Keep | Same URL, or a one-to-one redirect to the closest live page |
| Near-duplicate of a stronger page | Merge | Redirect to the surviving page, one canonical |
| No clicks, no impressions, no links | Retire | Archive the content, redirect only if a sensible parent page exists |
On our own site this autumn we exported every URL from Search Console and the sitemap, kept every page with a click or meaningful impressions in the previous 90 days, archived about 300 thin pages that had neither, and redirected about 50 URLs left over from an older version of the site. One of those old URLs still carried our strongest local backlink and was returning a 404 until we redirected it.
Scope follows this table, and so does budget: fewer pages to rebuild is a cheaper build than rebuilding everything. Our business website projects typically begin around $5,000 CAD, quoted as one fixed price after a free consultation, and we break down what moves that figure in our guide to how much a website costs in Canada.
A redirect map is a spreadsheet that pairs every old URL with the single new URL that replaces it, so no visitor and no crawler lands on a dead page after launch. One row per old URL, one destination per row, no exceptions. Build it during the design phase, not on launch night.
Permanent redirects show the new target in search results, and Google's documentation on redirects and Google Search notes that server side redirects have the highest chance of being interpreted correctly, with HTTP 301 listed as a permanent type. That is the redirect you want on every moved page.
Keep the map after launch. It is the first document you open if impressions drop.
A platform move changes how URLs are generated, how templates render content, and how redirects are stored. It should not change the URLs that already rank, the page titles, or the body copy that earns impressions. Treat the platform as an implementation detail and the URL list as the contract.
Each builder generates paths from its own templates, so blog posts, service pages and CMS collection items frequently land on a different path once rebuilt elsewhere. Auto-generated slugs are the usual culprit: the new CMS names the page for you, and the old path quietly dies. Decide the slug for every page from your redirect map, then build to it.
Redirect handling differs too. On Webflow, importing a redirect file overwrites the existing list, so we export the current redirects first, merge them with the new rows, then import the combined file. Plugin-based features on WordPress also need a plan: schema, forms and anything a plugin was injecting into the old pages has to exist on the new ones before launch, not after.
Moss Hachey Law in Fredericton is a useful example. Their previous site was on Squarespace with slow load times and limited SEO control, so we moved it to WordPress and rebuilt it around local SEO, speed and lead capture from ads and search. The platform changed; the pages that mattered carried their content and their place in search with them. You can see the detail in the Moss Hachey website case study, and we apply the same sequence to every law firm website design project where practice-area pages hold the rankings.
Seven things move from the old page to the new one, and a page is not finished until all seven are verified in the published source code. Checking the design tool preview is not the same as checking what the server sends, because that is what Googlebot reads.
None of this stops you improving the design. A redesign can sharpen UI and UX, speed and conversion while the text, structure and markup that Google already rewards stay in place. Changing the layout is safe; deleting the substance is not.
Launch day is a sequence, not an event. Work through it in order and have the redirect map, the URL list and Search Console open the whole time.
One more rule worth borrowing from Google's site move guidance: change one thing at a time. A new domain, a new CMS and a new layout on the same day makes a drop impossible to diagnose.
Watch impressions on your top pages in Search Console, daily, for the first two weeks. A dip in the first days is normal as Google recrawls and reprocesses the new URLs. Impressions that have not recovered by week four mean something is wrong, and in practice it is either a redirect or a content cut.
Three reports carry the answer. The performance report, filtered by page, shows which specific URLs lost impressions. The page indexing report shows pages newly marked not found, redirected or excluded. The URL Inspection tool shows the status of a URL in the Google index, lets you inspect a live URL to test whether it might be indexable, shows the Google-selected canonical in the indexed data, and lets you request indexing.
When we repaired a law firm migration that had left hundreds of old URLs returning 404, rankings and impressions recovered within weeks of one-to-one 301 redirects going live. The fix was the map, not new content.
For local service businesses in Saint John and across Atlantic Canada, we usually find the whole picture rests on a handful of city-and-service pages, so check those first and check them individually. Our web design team in Saint John, NB treats the 30 days after launch as part of the project, not a separate engagement.
A redesign is a migration wearing new visuals. The design work decides how the site feels; the inventory, the keep-merge-retire decisions, the one-to-one redirect map and the carry-over list decide whether you keep the traffic you already paid for in time and content. Do the inventory before anything is designed, write the map during the build, test it on staging, and read Search Console daily for the first two weeks. If impressions have not come back by week four, go back to the map.
If you are planning a redesign in New Brunswick or anywhere in Atlantic Canada and you want the rankings protected as part of the project, book a free consultation with our team in Saint John.
