Web Design

Can I redesign my website without losing my Google rankings?

Rankings can survive a redesign when every address Google already knows still leads somewhere useful and the text that earned those rankings comes across.

Get a free audit See pricing

Yes, a redesign can keep its Google rankings when every old URL that changes gets a permanent server-side redirect to its matching new page and the text that earned those rankings comes across intact. Google's site-move guide says any significant change can bring ranking fluctuations while Google recrawls and reindexes the site. The work that protects rankings starts before launch: every old URL goes on a list, the list becomes a redirect map, and the staging copy stays out of Google behind a noindex rule or a password that comes off when the new site goes live.

Redesign or repair: the decision before any mockup

The first decision is whether the site needs a redesign at all, because a redesign can change several things Google reads at once: the addresses pages answer at, the words on them, the internal links between them and the title tags. Google says it uses links as a relevance signal and builds the title shown in results partly from the title element and headings, so a template that rewrites menus and titles is a search change too.

Google's site-move guide advises changing one thing at a time, and its starter guide suggests waiting a few weeks before judging whether a change helped. A repair fits those limits: fix the specific page, title or link, then measure. A crawl block, orphan pages or missing schema on a site that otherwise works calls for technical local SEO, not a rebuild.

A redesign earns its risk when the structure itself is the problem: Google's starter guide says organizing a site logically when redoing it can help search engines and users understand how its pages relate. Whether a site has ranking history worth protecting is the question we answer in the free audit, and the recommendation, a redesign or a fresh build, follows from what serves its rankings; the SEO web design page sets a page-builder site beside the static pages we build. A new domain or business name in the same plan stacks a second change on the first, and a domain or name change has rules of its own.

Every address the old site answers at goes on one list

A redesign that protects rankings starts from a complete list of the old site's URLs, because Google calls mapping old URLs to new ones important, and an address left off the list is one nobody plans a destination for. Google's site-move guide names where to look: sitemaps submitted in Search Console, server logs or analytics for the URLs that get the most traffic, Search Console's Links to your site feature, and the content management system's own URL listing. Hosted images and PDFs belong on the list too, since Google says they may already get Search traffic or links.

Squarespace's help on keeping rankings after a move to its platform (last updated May 22, 2026) suggests one spreadsheet row per old URL, with the new URL added in the last column as pages are built, which turns the list into the redirect map. WordPress's documentation (last updated June 8, 2024) says the URL to each post "should be permanent and never change", and an address that never changes needs no redirect at all.

One permanent redirect per old address, aimed at its closest match

Every old URL in a redesign gets one decision: keep it, send it to a new address with a permanent redirect, fold it into a page that now covers the same content, or retire it. Google recommends server-side permanent redirects from the old URLs to the new ones, with client-side redirects as a last resort; its redirect guide warns that rendering can fail, so Google might never see a JavaScript redirect. A permanent redirect shows the new target in search results, Google says, where a temporary one shows the source page, and on lost link value its site-move guide is direct: "301 and other permanent redirects don't cause a loss in PageRank".

Two habits undo a good map. One is chaining: Google advises redirecting straight to the final destination and, where a chain cannot be avoided, keeping it short, "ideally no more than 3 and fewer than 5" redirects. The other is pointing many old URLs at the home page. Squarespace's URL mappings help (last updated September 8, 2026) lists a deleted page redirected to the homepage as one use of a 301, but Google says many old URLs sent to one irrelevant URL such as the home page can confuse users and might be treated as a soft 404. Google allows several old URLs to point at one new page that consolidates their content, and for content not coming across at all, its guide says the old URLs should return a 404 or 410.

Switching builders without changing the domain

Switching builders or content management systems on the same domain still changes URLs wherever the new platform names pages differently, and Squarespace's help (last updated May 22, 2026) says switching platforms or rebuilding a site can affect rankings if the URL structure changes, "no matter what platform you choose". Google's site-move guide says to set up the new CMS "preferably the same as the old site used", a preference rather than a rule against switching. Each platform's help sets what can be carried across and how redirects get made:

Wix (help pages undated, read October 3, 2026): A Wix site has to be hosted and operated on Wix's servers, though the domain can be managed elsewhere, so leaving Wix means rebuilding the pages. Wix creates a 301 automatically when a page's URL slug changes, except for Wix Blog pages, and 301 redirects work with custom domains alone.
Squarespace (help last updated September 8, 2026 for URL mappings and February 12, 2026 for export): URL mappings make 301 or 302 redirects from pages that are deleted or disabled, cannot redirect image or file URLs, and hold 400 KB, which Squarespace says is usually around 2500 redirect lines. Its .xml export is meant for WordPress, and index, info, portfolio and store pages do not export.
WordPress (last updated June 8, 2024): Tools, Export creates an XML file of posts, pages, custom post types, comments, custom fields, categories, tags, custom taxonomies and users.

Google notes that platforms like Blogger or Shopify may already have built-in redirect tools. Our builds are fast static pre-built pages, not a page builder with a stack of plugins, so moving a site onto one is this same kind of switch, and anything that changes address gets a redirect.

Staging stays out of Google through noindex or a password

A staging copy of a new site has to stay out of Google while it is built, and robots.txt is the wrong tool for that. Google's robots.txt introduction says the file "is not a mechanism for keeping a web page out of Google", that a blocked URL can still appear in results without a description, and that a page is kept out with noindex or password protection. For a test site on a temporary hostname such as beta.example.com, Google's hosting guide says to add noindex to the HTML or HTTP headers so it is not indexed by accident. The two methods do not stack: noindex needs a page robots.txt leaves open, because Google has to crawl a page to see its meta tags.

The bigger danger is the block that rides along to launch. Google's site-move guide tells owners who block crawling or use noindex during development to prepare the live robots.txt and a list of the URLs whose noindex rules come off when the move starts, and its troubleshooting list puts it plainly: "Don't forget to remove any noindex or robots.txt blocks that were only needed for the migration." Google also says it may take months for Googlebot to revisit a page, depending on its importance, so a page dropped over a stray noindex cannot come back before Google crawls it again.

Launch day checks and what Google documents about the weeks after

Google's site-move guide sets the launch checks: each new URL should carry a self-referencing canonical and internal links should point at the new URLs, and once the redirects are active, canonical tags should use the new URLs and any noindex rules added to keep them out of the index early should be updated. It says to test the redirects, with command line tools or scripts for many URLs; a check of the status code each old address returns settles what matters, a 301 to the right page or an error. Every page we build that should exist returns a real 200 with a correct canonical. Then the new sitemap goes to Search Console, and links to the old URLs, social profiles included, get updated.

For the weeks after, Google says it temporarily crawls a migrated site more heavily than usual, that the move happens URL by URL and is complete once Googlebot has visited every old and new URL at least once, and, as a general rule, that a small to medium-sized website can take a few weeks for most pages to move. Google says visibility may fluctuate during the move: "This is normal and a site's rankings will settle down over time." A drop that keeps falling instead of settling needs a diagnosis, and reading a traffic drop after a new website launches turns to the indexing reasons Search Console reports for the missing pages.

Every redesign plan starts from the site as it stands, and a free SEO audit finds what ranks before anything is rebuilt.

Sources

Frequently asked questions

How long should redirects stay in place after a redesign?

Google's site-move guide, which covers URL path changes on the same domain as well as domain moves, answers "as long as possible", generally at least one year, which it says lets Google transfer every signal to the new URLs, links from other websites included. The 180-day figure on Google's Change of Address page belongs to that tool, which is for moves to a new domain or subdomain, not to a redesign that keeps the domain.

What should happen to pages a redesign deletes on purpose?

Google's site-move guide says old URLs whose content is not moving to the new site should return a 404 or 410 on the new site. Where several old pages were merged into one new page that covers the same content, those old URLs can redirect to the merged page.

Can a staging site hurt the live site's rankings?

An indexed staging copy is the risk Google documents: its hosting guide says to add noindex to a test site's pages so it is not indexed by accident, and its robots.txt guide says a page blocked there can still appear in results. The larger risk runs the other way: a noindex rule or robots.txt block that protected staging is carried to the live site at launch, and Google drops the pages it finds marked noindex.

Does a permanent redirect lose link value?

No. Google's site-move guide says 301 and other permanent redirects don't cause a loss in PageRank. Google's redirect guide adds that a permanent redirect shows the new target in search results and is a signal that the target should be canonical.

Should the new site use the same content management system as the old one?

Google's site-move guide says to set up the CMS preferably the same as the old site used, which is a preference rather than a rule, and it advises changing one thing at a time. A platform change on the same domain is handled like any other URL change: every address the old platform used, including blog posts, images and PDFs, goes on the list and gets a destination.

When should an SEO be involved in a website redesign?

For owners who hire one, Google's page on hiring an SEO says a great time is when a site redesign is being considered, "the earlier, the better", so the site can be designed to be search engine-friendly from the bottom up. The same page says a good SEO can also help improve an existing site, and that a small local business can probably do much of the work itself.

Ready to get found?

See where you stand in Google and AI search

We will run a free audit of your local rankings and your visibility across ChatGPT, Gemini, Perplexity, and Google AI Overviews, then show you the fastest path to more booked jobs.

Get my free audit Call (239) 747-0465