Google’s site-move documentation says to keep redirects in place “generally at least 1 year”. Pull out your website contract and look for that year. If it isn’t written down, nobody is obligated to keep those redirects live, and you decide whether anyone does when you sign, not when you leave.
Your rankings and your measurement history are won or lost in the contract, before the migration starts. The platform swap is the easy part. Any competent vendor can stand up a new site. The URL map, the redirect plan, the inventory feed, and whose name sits on the analytics account are the hard parts, and you settle all four at signature.
Dealers change website vendors for good reasons. The old platform buries inventory three clicks deep, the BDC (business development center) complains the lead forms fail on mobile, or the per-rooftop pricing stopped making sense as the group grew. The new vendor’s demo looks sharp. Then the site launches and organic traffic drops, and nobody can say whether units slipped because the market cooled or because the old vehicle pages now return “page not found” errors.
The stakes compound across a group. One rooftop losing a share of its organic traffic hurts. Ten rooftops losing it at once, during the same migration, in the same quarter, shows up in gross before anyone connects it to the website. And by then the old vendor has shut off the old server, the redirects are gone, and the analytics account that held years of history belonged to the vendor all along.
What gets lost when you change website vendors?
Four things, and only one of them is the website.
First, URLs. Every vehicle detail page, every service special, every “Ford dealer near Mesa” landing page has an address that Google has crawled, indexed, and ranked. When the new platform generates new addresses, every ranking attached to an old address is at risk. Google’s guidance is direct: “It’s important to map your old site’s URLs to the URLs for the new site.” No map, no transfer.
Second, measurement history. If the vendor created your GA4 (Google Analytics 4) property under its own account, your traffic history, your conversion data, and your source attribution live in a property you may never touch again. Even inside GA4, the data retention setting runs at two or 14 months and “only affects explorations and funnel reports.” Standard reports keep their aggregate data, but the detailed exploration data you’d use to compare behavior before and after the migration ages out on that clock.
Third, the inventory feed. Your DMS (dealer management system) pushes units to the website through a feed the vendor configured. If the feed logic, the photo pipeline, and the pricing rules live only in the vendor’s system, your new vendor rebuilds them from scratch, and every day of rebuild is a day your inventory is wrong online.
Fourth, access itself. Google Business Profile, Search Console, the domain registrar, DNS (domain name system, the record that points your domain at a server). Any one of these registered to a vendor employee’s email is a hostage.
What must you capture before the contract ends?
Capture everything while the old site is still live and the relationship is still polite. Six items:
- A full URL inventory. A crawl of every live page on the current site, exported to a spreadsheet. It can run to thousands of rows for a multi-rooftop group.
- Your top organic pages. Pull from Search Console the pages that earn clicks from search, ranked. These are the pages your URL map must protect first.
- An analytics export. Download the standard reports that matter to you: traffic by source, conversions, top landing pages, by month, going back as far as the property allows. Remember the retention limits on exploration data.
- Your leads. Every lead record in the website platform’s CRM (customer relationship management) tools, exported in a format your next system can import.
- Google Business Profile access. Confirm an email address your dealership controls is the primary owner on every rooftop’s profile. Not a manager. The owner.
- DNS and registrar access. Confirm who can log in to the domain registrar. If the answer is “the vendor,” fix it before you give notice.
None of this requires technical staff. All of it requires doing it before the contract ends, because the vendor’s obligation to help ends when the contract says it does.
How does the URL map work?
A URL map is a spreadsheet with two columns: the old address and the new address it should redirect to. The new vendor implements it as 301 redirects, the permanent kind. Google’s documentation says a permanent redirect signals that the target page should be canonical, the version Google shows in results. A temporary redirect keeps the old page in results, which is the opposite of what a migration needs. Insist on permanent.
The mapping rule is one to one wherever a page has equity. Your “used trucks under $30,000” page that ranks? It maps to the equivalent page on the new site, with matching content. Your service scheduling page? Same. The lazy alternative, pointing every old URL at the new homepage, is the one Google’s site-move guide warns against by name: don’t redirect many old URLs to one irrelevant page “such as the home page of the new site,” because it “can confuse users and might be treated as a soft 404 error.” A soft 404 is Google’s term for a page it treats as not found even though it loads. Rankings built over years get thrown away there.
Vehicle detail pages need their own rule. A sold unit’s page goes to the closest live page: the same model still in stock, or the model’s inventory listing page. Never the homepage. A shopper who searched for a specific used F-150 and lands on your homepage bounces. The same shopper landing on your live F-150 inventory might buy a different one.
Expect turbulence either way. Google says to “expect temporary fluctuation” in site ranking during a move, and that a small to medium site “can take a few weeks for most pages to move.” Google’s timeline assumes a correct map. Without one, there’s no reason to expect the fluctuation to stay temporary.
One clarification that trips people up: Google’s Change of Address tool applies only when the domain or subdomain changes. A vendor swap that keeps yourdealership.com on a new platform doesn’t use it. The redirects and the map do the work.
Whose accounts are they?
Whatever the contract and the account settings say. If the vendor created an account, assume it’s the vendor’s until you see your dealership listed as the owner. Who should own the ad and analytics accounts has its own full answer. For a migration, the short version is the ownership check in the capture list earlier: GA4 property, Search Console, Google Business Profile, registrar, DNS. Run it now, not at notice. Every account that carries your dealership’s data should have the dealership as owner and the vendor as a user you can remove.
What changes for a franchise dealer?
Franchise programs add a layer an independent store never deals with. OEM (original equipment manufacturer) certified-vendor programs can tie co-op funds to an approved list of website providers, which narrows your choice of platforms. The terms vary by brand and change over time, so read your current program documents rather than treating any summary, including this one, as settled. What the programs don’t change: the URL map, the redirect plan, and account ownership are still yours to demand, whichever certified vendor you pick. A short vendor list is not an excuse for a thin contract.
A note on where my method comes from, since the industry matters. I ran marketing for La Mesa RV, an 11-store RV dealer group, for three and a half years. I’ve never worked at an auto dealer, and RV retail is not auto retail. But the mechanics of a platform change are the same: inventory feeds from a DMS, vehicle pages that rank and then sell, local search across rooftops. In June 2022 we re-platformed the La Mesa RV site and kept every page and every URL, changing only the logo and the palette, specifically to carry the search equity across untouched. When we redesigned in June 2024 and URLs did have to change, the redirects were planned with the redesign, not patched after launch. The discipline transfers. The franchise constraints are the part you layer on top.
What belongs in the contract?
Negotiate the exit at signature, while you still hold a buyer’s bargaining power. Three clauses:
Export on exit. The vendor delivers, at termination, a full export of your data: leads, analytics access or exports, content, the URL inventory, and the inventory feed specifications. In a usable format, within a defined number of days.
Redirects, written into both contracts. Google says to keep redirects “generally at least 1 year.” Once your domain points at the new platform, the new vendor hosts the redirects, so the one-year minimum belongs in the new contract. The old contract should require the final URL list and cooperation through cutover, so the map is ready on day one.
Accounts in the dealer’s name. GA4, Search Console, Google Business Profile, and tag management created under dealership-owned accounts from the start, with the vendor granted access it can lose. Written into the agreement, not assumed from goodwill.
Google’s own guidance says to bring in SEO (search engine optimization) help “when you’re considering a site redesign (the earlier, the better)”. The earliest point is before the contract exists. The whole migration is won there.
Who owns the move?
A migration like this is a project with one owner, or it fails in the gaps between owners. The vendor builds the site, the BDC fields the leads, the controller reads the contract, and nobody holds the URL map. A fractional chief marketing officer (CMO) owns the whole sequence: the contract terms before signature, the capture list before notice, the URL map before launch, and the traffic reporting after, measured against an export taken while the old site was still live. The window to do it right opens once. If you’re weighing a vendor change across your rooftops, the time to put someone in that seat is before anyone signs anything.