You keep your rankings by keeping every important URL alive, either at its old address or redirected to a specific new one with a 301 status code. A new design does not cost you rankings. New, un-redirected URLs do. List every URL that gets traffic or links, decide its new address, set a 301 redirect for each, and confirm Google sees the move. Launching the new site without the mapping step is the most common way sites lose search traffic in a builder switch.
Which URLs do I need to list first?
Get a full list of your current URLs before you touch the new site. Combine two sources:
- Google Search Console's Pages report (or the Performance report filtered by page) shows every URL that is indexed or getting clicks and impressions. This is your priority list.
- A crawl of your current site (any crawler that follows links, run against your live domain) catches pages Search Console has not picked up, including ones with external backlinks but few or no visits.
Note each URL's type (homepage, blog post, product, category or tag, form landing page), since builders often restructure whole URL patterns per type, not page by page.
How do I map each old URL to a new one?
Decide each URL's exact new address before launch. A 301 redirect that lands on a different page than the one Google indexed is a weaker signal than one that lands on the true replacement.
Example (hypothetical): a site moving its blog from Squarespace to a new platform, illustrating the mapping, not a real migration.
| Old URL (Squarespace) | New URL | Redirect type | Notes |
|---|---|---|---|
/blog/how-we-price-jobs | /blog/how-we-price-jobs | 301, same path | No change needed if the new site can match old slugs |
/blog/spring-cleaning-tips | /guides/spring-cleaning-tips | 301 | Blog moved under /guides |
/shop/product-a | /store/product-a | 301 | Store section renamed |
/blog?tag=pricing | /blog/category/pricing | 301 | Tag URL becomes a category page |
/old-landing-page | (retired, no equivalent) | 301 to closest parent, e.g. /services | Only when there is truly no replacement; do not redirect unrelated pages to the homepage as a default |
Where a page has nothing to replace it, redirect to the most relevant surviving page (a parent category, not the homepage by default). Google's site-move documentation explains that this kind of mapping, not a blanket homepage redirect, carries ranking signals forward (Google Search Central).
What URL patterns did my old builder use?
Redirect sources are easier to find when you know the pattern your old builder used:
- Squarespace blog posts publish as the blog page's slug followed by the post's slug, for example
/blog/example-post. You can edit the default format per site, though existing posts do not change retroactively (Squarespace). - Wix blog posts use a
/post/prefix by default (for example/post/post-title). Wix says you can rename that segment but not remove it entirely (Wix). - Webflow CMS Collection pages follow whatever URL structure you set per Collection. Redirects for a slug change can be created automatically if you check "Permanently redirect the old URL to this new one" in Page settings (Webflow).
How do I set the 301 redirects on the new platform?
The steps depend on the destination platform.
Squarespace destination: open the Developer tools panel, then URL mappings, and enter one rule per line in the format /old-url -> /new-url 301. Squarespace also accepts patterns such as /blog/[name] -> /posts/[name] 301 for a whole section. Squarespace requires the old URL to no longer exist on the site and the new one to exist (Squarespace).
Wix destination: go to SEO & GEO in the site dashboard, scroll to Tools and settings, open the URL Redirect Manager, then create a single redirect (old URL, new URL) or a group redirect for a whole path pattern. Wix notes that changing a Wix Blog post's slug does not create a redirect automatically. You have to add it in the URL Redirect Manager (Wix).
Webflow destination: add redirects under Site settings → Publishing → 301 redirects, with an "Old Path" (must start with /) and a destination page. Adding redirects needs a paid Site plan or a paid Workspace plan. Webflow recommends wildcard rules for whole path patterns (like everything under /old-blog/) to keep the rule count down, and notes that redirects are relative to the root domain and do not apply to localized slugs (Webflow).
Self-hosted WordPress destination: WordPress core has no built-in single-page redirect screen. The common approach is a dedicated plugin such as Redirection, which manages 301s and logs 404s from the WordPress admin (WordPress.org), or a rule at the web-server level (.htaccess on Apache, or your host's equivalent) if you manage that directly.
WordPress.com destination (whole-domain move): if you are moving an entire .wordpress.com address (not individual pages) to a different domain, WordPress.com's Site Redirect feature forwards the domain and all its permalinks. It works at the domain or directory level, not for individual files or pages (WordPress.com).
How do I check the redirects worked?
- File a Change of Address in Search Console, from a domain-level property, if you are also changing domains. Google says this tells it to prioritize crawling the new site over the old one and forwards your old site's signals to the new one. Google says to keep the redirects for at least 180 days, and longer while old URLs still get search traffic. After 180 days it treats the two sites as unrelated (Google Search Console Help).
- Spot-check individual URLs with the URL Inspection tool in Search Console to confirm Google can crawl and index the new address, and to request a recrawl of changed pages (Google Search Console Help).
- Re-crawl your own new site with the tool you used for the inventory. Confirm every mapped old URL returns a real 301 to the intended new URL: not a 302, not a redirect chain (old, intermediate, final), and not a 404.
- Watch Search Console's Pages report for a spike in "Not found (404)" or "Page with redirect" over the following weeks. That signals a missed mapping.
- Check your server or host logs for requests to old URLs that were never mapped. Real visitors and crawlers surface gaps your inventory missed.
What if I missed a URL?
Add the missing mapping as soon as you find it. A redirect map is rarely complete on day one, and every day a URL stays unmapped costs link equity and visitors. Nothing is unrecoverable if you still know what the old URL was and where the equivalent content now lives.
The redirects live on the new platform, so you can add one at any time. What you can lose is the knowledge of the old URL. Keep your URL inventory, a crawl export and a content export of the old site after you cancel it, so a 404 in Search Console can be traced to its replacement page.
Do not redirect large numbers of unrelated old URLs to the homepage as a shortcut. Google and users treat that as a weaker signal than a specific redirect, and it makes real broken links harder to find in your reports.
Where can I find a guide for my specific move?
These guides cover the move alongside the URL work: move from Squarespace to WordPress, move from Wix to WordPress, move from WordPress to Webflow, and move blog posts off a website builder.