A contractor can change marketing agencies without sacrificing the website or its search visibility, but the order matters. Confirm ownership and administrator access before giving notice. Build a complete asset register. Back up the working site, not just screenshots or static files. Map every current URL, test the replacement site before launch, keep redirects under your control, and overlap the old and new teams long enough to verify forms, calls, analytics, and search tracking.
Do not start the separation with a redesign. Start with custody. You need control of the domain, website, hosting, business listings, measurement accounts, and lead paths before anyone loses access.
The main risk is an access gap
Most agency changes are not full domain migrations. The contractor keeps the same domain while the people, hosting, content system, or marketing tools change. That is good news. Keeping the same useful URLs removes one large source of search disruption.
The failure point is usually operational. The old agency controls a registrar login. Nobody at the contractor’s company has WordPress administrator access. The contact form sends into an agency mailbox. Google Analytics exists, but the contractor cannot add a user. A call-tracking number is printed across the site, yet nobody has established whether it can be ported.
A tense departure makes those gaps harder to solve. Find them while the relationship is still functioning.
Our contractor website ownership checklist covers the contract questions to settle before signing. This guide addresses the other end of the relationship: how to leave with a working business asset.
Verified platform facts, snapshot August 27, 2026
The platform rules are narrower than the usual sales warnings about “losing all your SEO.”
| Verified fact | KKS analysis |
|---|---|
| Google recommends preparing a URL map, testing the new site thoroughly, using redirects, and monitoring the move. Google also warns that significant site changes can cause temporary ranking fluctuations while pages are recrawled and reindexed.[1] | Preserve good URLs unless there is a documented reason to change them. A new agency does not need a new address for every page. |
| When hosting changes without URL changes, Google recommends copying and testing the site first, then changing DNS, monitoring old and new hosting, and shutting down the old system only after users and Googlebot receive the correct content.[2] | A hosting move needs an overlap period. Cancelling the old host before the new copy passes live tests creates avoidable downtime. |
| Google recommends permanent server-side redirects when a page’s search URL must change.[3] | Redirects belong in the migration plan before launch. They should not be improvised after 404 errors appear. |
| Google Analytics access can be granted at the account or property level. Adding or changing users requires the Administrator role at the relevant level.[5] | Seeing reports is not control. The contractor needs an administrator account that the departing agency does not own. |
| A Google Business Profile can have multiple owners but only one primary owner. Managers cannot add or remove users.[6] | The contractor should hold primary ownership. Agency personnel normally need managed access, not custody of the listing. |
| Google Tag Manager warns that a business can be locked out when its sole administrator leaves and recommends at least two active administrator accounts.[7] | Use one company-controlled administrator and a second recovery administrator. Remove the old agency only after the new access works. |
None of these sources promises that rankings will remain perfectly flat. That promise would be dishonest. They do show which parts of the move can be controlled.
Phase 1: build the asset register before notice
Create one record with the asset, public URL or account ID, legal owner, current administrator, recovery email, billing owner, renewal date, and transfer status. Do not store passwords in the spreadsheet. Use a password manager for credentials and the register for custody.
At minimum, inventory:
- domain registrar, DNS host, nameservers, and domain renewal;
- web host, CDN, SSL certificate, backups, and staging site;
- WordPress or other CMS administrator accounts;
- theme, child theme, plugins, custom code, and license keys;
- all live pages, posts, media, forms, downloads, and redirects;
- Google Business Profile, Bing Places, and major trade listings;
- Google Analytics, Search Console, Tag Manager, Ads, and Merchant Center when used;
- call-tracking numbers, recorded greetings, routing rules, and number-porting terms;
- form destinations, CRM connections, online booking, email delivery, and spam controls;
- creative files, logos, photos, video, ad copy, reports, and keyword research;
- agency-created email addresses and any account that uses them for recovery.
Mark each item green, yellow, or red. Green means the contractor can sign in and add another administrator. Yellow means access works but ownership, billing, recovery, or export rights are unclear. Red means the contractor cannot control or retrieve the asset.
The red items set the departure timetable. A polished new homepage does not compensate for a domain that the company cannot renew.
Phase 2: collect a working website package
Ask for more than “the website files.” A usable WordPress handoff normally needs the database, uploads, theme and child-theme files, active plugin list, custom code, redirects, form settings, and a record of external services. It also needs the information required to run those components legally after the agency leaves, including any license limitations.
WordPress has a built-in export that can create a WXR XML file containing posts, pages, custom post types, comments, custom fields, categories, tags, taxonomies, and users.[8] That export is useful, but KKS does not treat it as a full operational backup. It does not, by itself, prove that the theme, plugin files, media library, configuration, forms, redirects, or server behavior can be restored exactly.
Request these deliverables:
- A recent full backup with a database and site files.
- A WordPress WXR export as a second, portable content copy.
- A list of active plugins, versions, license owners, and renewal dates.
- Theme and child-theme files, plus the source files for custom design work.
- Current redirect rules and any redirects managed outside WordPress.
- Form configuration, recipient addresses, integrations, and recent test results.
- A list of scheduled tasks, webhooks, API connections, and external scripts.
- A list of anything that will stop working when the agency account closes.
If the site is not portable, establish what does transfer. Our analysis of static files versus a working CMS handoff explains why a visual copy and an editable production system are different assets.
Phase 3: preserve the URL and search record
Export the current URL list before changing content. Pull URLs from the XML sitemap, CMS, analytics landing-page reports, Search Console, backlink data, paid landing pages, and a crawl of the live site. No single source catches everything.
For each URL, record:
- current HTTP status;
- page title and canonical URL;
- indexability;
- organic clicks or impressions when available;
- meaningful external links;
- internal links pointing to it;
- conversion role;
- keep, improve, merge, redirect, or retire decision;
- exact destination when redirected.
The safe default is to keep a useful URL at the same address. If a page must move, map the old URL to the closest relevant new page. Do not send every retired service page to the homepage.
Google says a site move is processed per URL and recommends mapping old URLs to corresponding new URLs.[1] That is the right mental model. A redirect map is not one rule saying “old site goes to new site.” It is a page-by-page custody record.
Use a permanent server-side redirect for a permanent page move.[3] Update internal links so they point directly to the final canonical URL. A redirect should catch stale bookmarks and outside links, not become the site’s normal navigation system.
The Search Console Change of Address tool is for a domain or subdomain move, such as moving from one domain to another. It is not required merely because the agency changes while the domain remains the same.[4]
Phase 4: test the replacement before the cutover
The new operator should restore the site in a protected staging environment and test it without relying on the production site as a safety net. Google recommends testing pages, images, forms, and downloads before a hosting change.[2]
Run a practical acceptance test:
- crawl every staged URL and compare it with the current inventory;
- confirm one H1, the intended title, and the intended canonical on each important page;
- submit every form using a labeled test lead;
- call every tracked number and confirm routing;
- test online booking from a phone and desktop browser;
- verify analytics and conversion events in their live debug tools;
- inspect robots.txt, noindex rules, XML sitemaps, and structured data;
- check images, PDFs, project galleries, and before-and-after sliders;
- verify mobile navigation, click-to-call buttons, and sticky CTAs;
- confirm 404 handling and every planned redirect;
- search the staged source for old agency email addresses, domains, phone numbers, and tracking IDs.
A test lead is not complete because the form displayed a green confirmation. Confirm the message reached the intended inbox or CRM, carried the correct fields, and triggered any promised notification.
Phase 5: sequence the cutover
A controlled handoff follows a simple order.
1. Establish company-controlled administrators
Add and verify the contractor’s administrator accounts in Analytics, Search Console, Tag Manager, Business Profile, the CMS, hosting, registrar, DNS, call tracking, and CRM. Do not remove the old agency yet.
2. Freeze unnecessary production changes
Pick a cutover window. Record any lead, content, form, or order data that changes after the final backup. A quiet weekday may be better than Friday afternoon for a contractor whose weekend emergency calls matter.
3. Take the final backup and export
Capture the database, files, content export, redirect map, DNS records, and account-user lists. Hash or timestamp the package so everyone knows which copy became the migration baseline.
4. Change one major dependency at a time
Move hosting or change DNS. Then test. Change forms or call routing. Then test. Remove old users last. When everything changes at once, a missed lead has no obvious cause.
5. Keep the old environment available
Google recommends monitoring traffic on both old and new hosting and shutting down the old infrastructure only after the new environment serves users and Googlebot correctly.[2] The commercial version is just as important: keep rollback possible until calls, forms, booking, analytics, and search crawling have been verified.
What to monitor for the first 30 days
Record a baseline before the change. Then compare the same measures daily during the first week and weekly after that.
Watch:
- uptime and server errors;
- 404s and redirect failures;
- submitted forms, delivered forms, and booked appointments;
- call volume and routing failures;
- indexed pages and sitemap processing;
- Search Console clicks, impressions, and important query groups;
- organic landing-page traffic;
- analytics and tag collection;
- Google Business Profile calls, website clicks, and booking actions when available;
- security, backup, and plugin-license failures.
Do not react to one quiet morning by rewriting every service page. Google says ranking fluctuations can occur during a significant move while the site is recrawled and reindexed.[1] First check whether the technical system and lead paths work. Then separate a real trend from normal daily movement.
When to give the old agency notice
Give notice after the contractor can answer yes to these questions:
- Can the company renew and control the domain without the agency?
- Can a company-controlled administrator add or remove users from every critical account?
- Has a full working backup been restored and tested?
- Is every current URL accounted for?
- Are redirects prepared for every necessary URL change?
- Have forms, calls, booking, analytics, and Search Console been tested?
- Are contract notice periods, final invoices, license terms, and data-return duties documented?
- Is there a rollback window if the cutover fails?
This is operational planning, not legal advice. If the contract is disputed or the agency claims ownership of a critical asset, have counsel review the signed agreement before taking an irreversible step.
KKS position: improve after continuity is secure
A new agency will want to show progress. That instinct can produce a premature redesign, a new navigation system, renamed service pages, and a different tracking stack during the same week. Resist it.
First preserve what works. Measure the baseline. Fix broken custody and conversion paths. Then decide whether the site needs repair, a managed growth program, or a rebuild.
KKS manages contractor websites through evidence-selected growth actions rather than a fixed article quota. The first action after an agency exit may be a service page. It may be a redirect repair, a form correction, a declining-page refresh, or a cleaner booking path. Read what monthly contractor website management should control before comparing retainers.
Check access before you give notice
Have KKS review the website and lead path while the current agency relationship is still functioning. The free audit includes a manually reviewed 15-factor website and lead-path scorecard, comparison with up to three relevant local competitors, and a sequenced 90-day action plan. KKS recommends repair, management, a rebuild, or no engagement based on the evidence.
Request My Free Contractor Audit
If the current site is healthy and portable, the recommendation may be to keep it.
Frequently asked questions
Will changing marketing agencies hurt contractor website rankings?
Changing agencies alone does not require new URLs or a new domain. Risk rises when the move creates downtime, missing pages, changed URLs without relevant redirects, crawl blocks, lost content, broken internal links, or weaker pages. Significant site changes can also produce temporary ranking fluctuations while Google recrawls and reindexes the site.[1]
Should I tell the agency before securing administrator access?
Secure and test company-controlled access first, within the rights granted by your contract. Early notice can start account closure, license removal, or staff offboarding. The goal is not secrecy. It is avoiding a period when neither team can operate the site.
Is a WordPress export enough to move the website?
Not usually. The WordPress WXR export can carry posts, pages, custom post types, comments, custom fields, taxonomies, and users.[8] A working migration may also require the database, uploads, themes, plugins, custom code, configuration, forms, redirects, licenses, and server settings.
Do I need Search Console’s Change of Address tool when changing agencies?
No, not when the site stays on the same domain. Google says the tool is for moving a site from one domain or subdomain to another.[4]
When should the old agency lose access?
Remove old users after the new administrator accounts work, the final backup is secured, the cutover has passed live tests, and the contract allows removal. Keep a dated user-access record so the contractor can show who retained control after the handoff.
Sources
- Google Search Central: Site moves and migrations. Accessed August 27, 2026.
- Google Search Central: Changing hosting without changing URLs. Accessed August 27, 2026.
- Google Search Central: Redirects and Google Search. Accessed August 27, 2026.
- Google Search Console: Change of Address tool. Accessed August 27, 2026.
- Google Analytics: Manage users and access. Accessed August 27, 2026.
- Google Business Profile: Manage owners and managers. Accessed August 27, 2026.
- Google Tag Manager: Managing users and permissions. Accessed August 27, 2026.
- WordPress: Tools Export screen. Accessed August 27, 2026.