The decision to move off Wix or Squarespace is almost never about Google. The old platform cannot handle bookings. It is slow. The design looks like something from eight years ago. You hire someone to rebuild it, the new site goes live, and three months later the phone is quieter.
That gap almost always comes down to one thing: the page addresses changed, and nobody mapped the old ones to the new ones.
What Google Actually Tracks
Google does not follow a business. It follows page addresses. Every click from a search result is attached to a specific URL. Every other site that links to you points to a specific URL.
Spend a few years on a Squarespace site and that history is tied to those exact addresses. Move to a new platform where the addresses are different, and Google's history is still pointing at the old locations. Without a redirect, those old addresses return nothing.
Google eventually removes dead pages from its index and the business starts from zero in search. Google's own site move documentation is direct on the timeline: for a medium-sized site, it can take a few weeks or more before Google starts showing the new addresses instead of the old ones, even when redirects are in place. Without them, there is no timeline.
The Three Ways a Move Can Go
Here is how platform moves play out in search traffic:
| What happened to the addresses | What Google sees | Effect on traffic |
|---|---|---|
| New platform, same addresses | No change | None |
| New platform, different addresses, redirects in place | Moved permanently | Weeks of fluctuation, then recovery |
| New platform, different addresses, no redirects | Dead pages | Drop starts immediately |
The third row is the most common outcome of a rebuild that skips the address question. A builder hands over a new site, it looks better, and the owner goes live. The old URLs are gone. Google has nowhere to send the visitors it had been sending.
Google's redirects documentation confirms that a permanent redirect tells Google to treat the new address as the correct one. But a redirect has to be written for every old address before the switch goes live, and left in place for at least a year.
What We Saw on Two Charter Moves
We have rebuilt two charter websites, moving each one off a platform that could not serve the business. In both cases we ran the same page addresses on the new site from day one. No redirects were needed because the addresses never changed.
| Charter | Moved from | Addresses | Result |
|---|---|---|---|
| An Oahu fishing charter | Squarespace | Unchanged | 5.1 times the appearances in results after twelve months |
| A charter on the East Coast | Custom booking platform | Unchanged | No drop after the move |
An Oahu fishing charter had a Squarespace site that had never been configured properly. It undersold a premium experience, and no title fix was going to change that. We built a new site around original photography and video, matched the existing addresses on the new platform, and ran an ongoing search program alongside it. Over the twelve months that followed, appearances in search results grew to 5.1 times the level from when we started.
A charter on the East Coast had a booking platform that could not reschedule a trip or issue a refund without someone logging in by hand. We rebuilt the site with custom booking software shaped around one boat and ran every trip page at its original address. Customers could continue using familiar links, and Google's history with those pages carried over to the new site.
In both cases the first step was to document every existing page address before touching anything, and treat those addresses as the main asset to protect. That is where most rebuilds skip a step.
When You Cannot Keep the Same Addresses
Sometimes matching the old addresses on the new site is not possible. A domain name change, two sites consolidating into one, a platform that cannot be configured to match the old structure: these are real cases.
In those situations, a redirect map is the substitute. It is a complete list of every old URL and the new address each one should point to. It is written before the switch goes live, tested after, and left in place for at least a year.
What a careful migration includes:
- Every old URL listed and redirected before the cut-over
- Every redirect tested as a visitor would follow it, after the switch
- Search Console numbers pulled before and after, from the same property, to confirm nothing was lost
A migration done right shows no drop in search traffic. That is measurable and verifiable.
What to Ask Before a Builder Starts
If someone has quoted you a rebuild, three questions tell you whether your search traffic is at risk.
First: will the page addresses on the new site match the ones on the current site? If yes, nothing is lost. If no, ask to see the redirect map before any work starts, not after.
Second: how long will the redirects stay in place? The safe answer is at least a year. A builder who plans to remove them after launch is cutting the cord early.
Third: how will you know if traffic dropped after the move? Without Search Console connected to both properties before and after the switch, there is no number to compare. A builder who does not set this up before launch has no way to prove the move went cleanly.
These are the same questions we work through on every website design and migration we take on. If you are still deciding whether the site needs a full rebuild or just repairs, that question comes before this one, and it is worth settling first.
Run the homepage check on your current site now to see what Google reads there today. For the full picture before any build conversation, the free audit covers every page and your Google listing.