"Won't this wreck my rankings?" is close to the first question every agent asks once a rebuild moves from idea to plan. It's a reasonable thing to worry about after spending years getting a site to show up for "[city] real estate agent." Here's what actually causes a ranking drop during a redesign, and what doesn't.
What actually causes the drop
A new layout, new colors, and new photos don't hurt rankings on their own.
What hurts rankings is when a page's URL changes and nothing tells Google
where the old page went. If yoursite.com/listings becomes
yoursite.com/properties with no redirect between them, Google keeps trying
to serve a page that no longer exists. Any ranking, any backlink, any trust
that page had built up gets stranded on a dead URL.
The same thing happens on a smaller scale with a blog post that gets a new slug, or a service page that moves under a different section of the site. Each broken link is a small loss. Enough of them at once and the loss shows up as a real traffic drop.
This is also why "just rebuild it on a new platform" sometimes goes badly. Switching from one website builder to another often changes the URL structure automatically, sometimes without anyone noticing until traffic drops weeks later. A platform's default URL pattern (adding a category folder, changing how listing pages are named) can quietly break every link Google has indexed, even when nobody touched a single redirect on purpose.
Build the redirect map before anyone touches the site
The protection against all of this is a boring spreadsheet, made before the
new site exists. Column one: every URL the current site has that matters.
Column two: where each one will live on the new site. Google Search Console
supplies the raw material; its performance report lists every URL that has
received search impressions, which is as close as you can get to a list of
the pages Google actually values. Add the current sitemap and a quick
site:yourdomain.com search to catch anything the report missed.
Not every row deserves a redirect. An agent site accumulates hundreds of expired listing URLs over the years, and those were always temporary; letting them return a not-found response is normal and expected. The rows that matter are the durable ones: the homepage, area and neighbourhood pages, service pages, the agent bio, and any blog post that ranks or has links pointing to it. Those pages hold the site's accumulated value, and each one needs a specific destination, decided before launch rather than discovered as a problem after.
What a careful rebuild does differently
The fix isn't complicated, it's just easy to skip under a deadline:
- Keep URLs the same wherever possible. A redesign can change everything about how a page looks without touching its address.
- Set up a 301 redirect for every URL that has to change, pointing the old address to its closest equivalent on the new site, not just the homepage. A redirect to the homepage tells Google the old page is gone; a redirect to the matching new page tells Google the content moved.
- Keep internal links pointing at the final URL, not at an old one that then bounces through a redirect. Chained redirects add delay and risk for no benefit.
- Submit an updated sitemap to Google Search Console once the new site is live, so Google has a current map of what exists.
How long the transition actually takes
Google's own documentation on site moves with URL changes puts it plainly: a small to medium-sized website can take a few weeks for most pages to move in Google's index, and larger sites take longer. Google's guidance is direct about the reason: Googlebot has to visit each URL on both the old and new site at least once before it considers the move complete, so some patience is part of the process, not a sign something went wrong.
That's a normal part of any legitimate site change, done properly. It's different from the traffic loss that happens when redirects are missing entirely, which doesn't resolve on its own over time. It just stays lost until someone finds and fixes it.
How to tell a normal dip from a real problem
The two situations look identical in a traffic chart for the first couple of weeks, which is why launches cause so much anxiety. The difference shows up in the details. After launch, watch two things in Search Console: the indexing report, where a growing pile of not-found errors on pages that used to matter points at missing redirects, and the performance report, where a healthy move shows impressions shifting to the new URLs rather than disappearing.
The hands-on version is even simpler. Keep the pre-launch URL list, and a week after launch, open a sample of old URLs in a browser. Each one should land on its matching new page. Any that error out or bounce to the homepage are found problems with a known fix, and fixing them promptly matters, because a missing redirect costs a little more for every week it stays missing.
A few things that don't actually hurt rankings
It's worth separating the real risk from the things agents worry about that usually aren't the problem:
- A new visual design. Google doesn't rank a page on how it looks. It reads the content, the structure, and the code behind it.
- Faster load times. A rebuild that makes pages load faster is a ranking improvement, not a risk, since page speed is one of the signals search engines do weigh.
- Reorganized navigation, as long as every page a visitor could reach before is still reachable after, even if it takes a different click path to get there.
The common thread is the same one from the redirect section: content and structure changes are fine. Silently deleting or moving a URL without a signal pointing to where it went is what actually costs rankings.
What happens to the old site and domain during a Saige rebuild
The instant preview Saige generates is built from the existing site's content so an agent can see the rebuild before committing to anything. Nothing changes on the live site during that step. Moving the domain over and actually going live happens later, as a separate, deliberate step the agent controls, which is also covered on the FAQ page. Because the rebuild starts from the existing site, the existing URL structure is the default, and any address that does change gets its redirect as part of the launch rather than as an afterthought.
The takeaway
A redesign is risky when URLs change quietly and nothing redirects the old ones. It's not risky just because the design changes. Anyone rebuilding a real estate website, whether that's a full platform switch or a fresh coat of paint on the same pages, should ask one specific question before launch: what happens to every URL that currently ranks? If there's a clear answer for each one, the redesign is on solid ground.
Related: Making your agent website readable by AI crawlers · What is AEO for real estate agents · How AI search is changing real estate marketing · How a Saige website rebuild works
