Will replacing your SEO agency cost you rankings?
The handover checklist
| Step | When | What to secure or ask for | Why it protects rankings or AI visibility |
|---|---|---|---|
| 1 | Before notice | Add a company account as a verified Search Console owner, using its own verification method | An owner has full control of the property. A delegated owner holds rights only because a verified owner granted them |
| 2 | Before notice | Make a company account Administrator in Google Analytics | Only an Administrator can add and remove users, so an agency holding the only admin seat holds your data |
| 3 | Before notice | Confirm your business is the domain's registrant of record and holds the registrar login | Only the registered name holder, the administrative contact or someone they authorize can start a transfer |
| 4 | Before notice | Export 16 months of Search Console performance and the analytics history you rely on | Google suggests the "Last 16 months" view to judge a traffic drop in context. Analytics explorations only reach back as far as the retention setting |
| 5 | Before notice | Pull a full URL list from your CMS, plus your sitemaps and the top-traffic URLs from server logs or analytics | Google's move guidance builds the old-URL list from sitemaps, server logs or analytics, the Links to your site feature in Search Console and the CMS |
| 6 | Before notice | Record an AI answer baseline: the prompts that matter, per engine, and which brands and pages each answer names | Search Console counts AI Overview traffic inside ordinary Web search, so it cannot show AI answers on their own |
| 7 | Before notice | Read the contract for who owns content, reports and link records | No search engine rule decides this. It depends on your contract |
| 8 | During notice | Get copies of the redirect map, robots.txt, sitemap setup and any disavow file | A disavow file used incorrectly can harm performance, so you need to know what was submitted and why |
| 9 | During notice | Get server and CDN log access that continues after the contract | Logs show which AI crawlers fetched which pages, before and after the switch |
| 10 | During notice | Make no URL changes or migrations until the new team is in place | Changing URLs can cause ranking fluctuations while Google recrawls and reindexes |
| 11 | At cutover | Remove the old agency's users and delete their verification tokens | A removed owner can re-verify for as long as their token stays on the site |
| 12 | At cutover | Check robots.txt, noindex, snippet controls and AI crawler rules | A stray noindex drops a page from Google Search. A page must also be eligible for a snippet to appear in AI Overviews or AI Mode |
| 13 | At cutover | Submit the canonical sitemap again and test every redirect | The sitemap tells search engines which URLs you prefer. Untested redirects are how pages drop out of results unnoticed |
| 14 | First 90 days | Read performance against your exported baseline, and check seasonality before blaming the switch | Google lists seasonality and algorithm updates as normal causes of a drop |
| 15 | First 90 days | Check the same prompts again on each engine and compare with the AI answer baseline | Engines refresh at different speeds, so one blended reading hides which one moved |
What must you own before you give notice?
Access first. Everything else depends on it.
Search Console. Google lists four permission types. An owner "has full control over properties in Search Console" and can add and remove other users. A full user can view all data and take some actions. A restricted user gets simple view rights on most data. An associate can take certain actions on behalf of your site but cannot open or view your Search Console data directly. There are also two kinds of owner: a verified owner proved ownership with a token, and a delegated owner was granted ownership by a verified owner without one.
If the agency is the only verified owner and your team is delegated, your access depends on theirs. Fix it while the relationship is friendly by verifying a company account yourself. Google allows several people to verify the same property, with the same or different methods, and it advises adding more than one method in case one fails.
The step that is easy to miss: when you remove a verified owner, they lose access immediately. But Google warns that "as long as a user's verification token remains for a property, a deleted owner can re-verify ownership." Removing the user is step one. Deleting their token (the HTML file, meta tag or DNS record they added) is step two. Be careful which token you delete. Google also says removing your own DNS record or verification file loses your verification.
Google Analytics. The Administrator role has full control, including managing users. An Editor has full control of settings but cannot manage users. A Viewer can see settings and data. Put a company account in the Administrator role at account level, because roles are inherited downward by default.
History. Export your Search Console performance for the longest window the filter offers, and check your Analytics data retention setting. A standard Google Analytics 4 property keeps event-level data for 2 months or 14 months, and data past the window is deleted automatically every month. The setting leaves standard aggregated reports alone but limits explorations and funnel reports over longer ranges.
The domain. ICANN is clear that you must be the registrant of record or the administrative contact to start a transfer. If the agency registered your domain in its own name, fix that early. A contact-information change can block a transfer for 60 days.
Work product. Content drafts, link-building records and dashboards are a contract question. No Google document says what an agency must hand over. Check what your agreement says you own and ask for it in writing.
What causes ranking loss in a handover, and how do you prevent each?
Google's causes of traffic drops include technical issues, URL changes, seasonality and algorithm updates. A handover can trigger the first two and gets blamed for the others.
| Cause | What happens | How to prevent it |
|---|---|---|
| URLs change without permanent redirects | Rankings can fluctuate while Google recrawls and reindexes | Map every old URL to its new target. Use a permanent server-side redirect. Keep redirects for at least a year |
| A leftover noindex | Pages drop out of Google Search, and so out of its AI features | Remove any noindex that was only needed for staging or a migration |
| A leftover robots.txt block | Google cannot crawl the pages, so it cannot read their content. A blocked URL can still appear in results, but without a description | Remove any robots.txt block that was only needed for staging or a migration |
| Using robots.txt to hide pages | Blocked pages can still be indexed if other sites link to them | Use noindex, and leave the page crawlable so Google can see it |
| A verification method is removed | The business loses Search Console verification and its view of problems | Keep your own DNS record or file in place. Only delete the departing agency's tokens |
| Sitemap lists non-canonical URLs | Mixed signals about which URL should rank | List canonical URLs only, with accurate lastmod dates |
| An inherited disavow file nobody can explain | Links that help you may be disavowed | Review the file with the new team before trusting or deleting it |
| A seasonal dip read as handover damage | Panic changes that cause real damage | Compare year over year before acting |
Redirects deserve the most care. Google says a permanent redirect shows the new target in search results, while a temporary one shows the source page, and it recommends "a permanent server-side redirect whenever possible." A redirect is a strong signal that the target should become canonical. A rel=canonical tag is also a strong signal, and sitemap inclusion is a weak one. They work best together.
Fixes are not instant either. Google generally caches robots.txt for up to 24 hours, so a corrected file can take a day to register. Test single redirects with the URL Inspection Tool and large sets with a script.
If your domain and URLs stay the same, changing agencies is not a site move. The Change of Address tool, the 180-day redirect minimum and keeping the old domain registered for a year all apply to moving between domains. If the new agency proposes a domain change or URL restructure during the handover quarter, ask why it cannot wait. On a large site, Google recommends moving one section first to test the effect.
How do you keep AI search visibility during the switch?
A handover can wipe you out of AI answers while your Google rankings hold steady, so check it separately.
Check crawler access, bot by bot. OpenAI and Anthropic each separate search crawlers from training crawlers, and Perplexity says neither of its two bots is used to collect content for training AI foundation models:
- OpenAI's OAI-SearchBot surfaces sites in ChatGPT search. GPTBot crawls content that may be used to train models. ChatGPT-User handles certain user actions.
- PerplexityBot surfaces and links sites in Perplexity results, and Perplexity says it is not used to crawl content for foundation models. Perplexity-User supports user actions and generally ignores robots.txt.
- Anthropic's ClaudeBot collects content that could contribute to model training. Claude-SearchBot improves search results, and Claude-User supports Claude users.
OpenAI says each setting is independent, so you can allow OAI-SearchBot while disallowing GPTBot. Our reading of the three providers' documents: a blanket "block AI bots" rule, inherited from an old robots.txt or a firewall setting, can remove you from AI search answers when the only goal was to opt out of training. After a change, OpenAI and Perplexity both say it can take about 24 hours to take effect. Anthropic adds that blocking its crawlers by IP address may not work reliably, because it stops the crawler reading your robots.txt.
Check the controls that also govern Google's AI features. Google says that to limit what it shows from your pages you use nosnippet, data-nosnippet, max-snippet or noindex. A stray snippet control left by the previous provider limits AI Overviews and AI Mode too.
Record a baseline you can compare against. Search Console counts AI feature traffic inside overall Web search, so it cannot tell you whether you lost AI answers. No engine publishes an official method for this, so keep it simple: run the buyer prompts that matter on every engine you care about and record which brands and pages each answer names, before notice and after cutover. In our own tracking, each engine leans on a different set of sources, so read the results per engine. And keep server logs running, because they show which pages AI crawlers actually fetch. The server-log playbook for AI bot traffic covers how to read them.
Know where the experts disagree. Google says there are "no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." It adds that you do not need AI text files, new machine-readable files or special schema. A page has to be indexed and eligible for a snippet. Peer-reviewed research presented at KDD 2024 takes a different angle. The authors of the Generative Engine Optimization paper found that content-level changes measurably raised a source's visibility in generative engine answers, and that the effect varied by domain.
Both can be true: Google describes eligibility, and the paper measured relative visibility in a test. Google also says AI Overviews and AI Mode may use query fan-out, issuing multiple related searches across subtopics. A page that answers the head question and the sub-questions around it may have more chances to be pulled in. For a handover, the practical rule is the same either way: keep pages indexable, crawlable and snippet-eligible first, then judge any extra AI work on measured answers.
What does a safe switch timeline look like?
| Phase | When | What happens |
|---|---|---|
| Before notice | Now, while the relationship is working | Owner access, Analytics admin, registrar check, exports, URL list, AI answer baseline |
| Notice period | Whatever your contract sets | Redirect map, robots.txt, sitemap and disavow copies; log access; URL freeze |
| Cutover | One planned week | Remove old users and tokens, audit crawler and indexing controls, resubmit the sitemap |
| Early read | A few weeks after cutover | Compare against the baseline. Google advises waiting a few weeks to judge whether changes helped |
| 90 days in | Within the first 90 days | Search trends read against the same period last year; AI answers re-run per engine |
Google's starter guide says some changes take effect in hours and others take several months. If the new agency changes URLs, Google says a medium-sized site can take a few weeks or more before new URLs replace old ones in results, and larger sites longer. Time any such change for a lower-traffic period.
AI answers move at three speeds. A first citation can land within hours to a day. A steady slot in the cited set takes weeks. A dominant share of answer on a competitive prompt cluster takes months. We explain the difference in how long AI citations take. A handover that keeps pages live and crawlable should leave the slow work intact. A crawler block can undo it quickly.
What must a modern replacement cover for SEO and AI search?
If you are replacing an agency in 2026, look for one that covers SEO and AI search optimization (AEO, or GEO, generative engine optimization) under one plan. Judge every candidate on these five dimensions before anything else.
| Dimension | What good looks like | What to ask to see |
|---|---|---|
| Measurement | Search performance plus AI answers tracked per engine and per prompt, tied to signups and demos | A sample report showing per-engine answers next to pipeline |
| Execution cadence | Technical fixes and new pages shipping from the first week, with a weekly view of what shipped | What ships in week one and who approves it |
| Risk | Redirects, indexing controls and crawler rules checked before any change goes live | How they test redirects and review robots.txt changes |
| Reporting | Numbers you can check yourself in your own Search Console and Analytics | Whether reports link to your accounts or to theirs |
| Data ownership | Your accounts, your domain, your logs, with the agency as a user | Who holds Owner and Administrator on day one |
Push hardest on measurement. Visibility, clicks and impressions only matter when they are read against the revenue they bring in through signups, booked demos and other lead capture. An agency that reports mentions without that link has not shown you it works.
For what that looks like in practice, see LoudFace's SEO and AEO service, which covers both search and AI answers in one program.
Which questions should you ask a new agency, and what are the red flags?
Ask these during selection. The answers also tell you whether the handover will be safe.
- Who will hold Owner in Search Console and Administrator in Analytics? Red flag: the agency wants to own the property or the account "for simplicity."
- Will you change URLs in the first quarter? Red flag: a restructure is planned before anyone has read your traffic history.
- Which AI crawlers will you allow, and which will you block? Red flag: they cannot name the difference between a search crawler and a training crawler.
- How will you baseline AI answers before you change anything? Red flag: "AI visibility" reported as one blended score with no per-engine or per-prompt breakdown.
- What do you do with the disavow file you inherit? Red flag: delete it or keep it without looking.
- What will we own when the contract ends? Red flag: vague answers about content, reports or dashboards.
Two companion guides go further: the questions to ask an AI search agency before you sign and the red flags when hiring one.
How do you run a fair pilot?
A pilot lets you replace an agency without betting the whole site on a pitch.
Scope. Pick a bounded set: one product area, one cluster of buyer prompts, or a fixed list of pages to fix and write. Keep URL changes out of scope unless the pilot is about them.
Duration. Long enough to see an effect. Google says to wait a few weeks after a change before judging it, and a steady AI citation takes weeks. A pilot that ends days after launch measures nothing.
Success criteria. Write them before work starts, against the baseline you recorded: which pages ship, which queries and prompts you expect to move, per engine, and how you will read signups and demos from that section of the site.
Exit clause. Agree what happens if the pilot fails. You keep owner access throughout, the agency works as a user on your accounts, and the contract says who owns what the pilot produced.
Judge the pilot on what shipped and what moved. If you want the benchmark for a good first quarter, read what an AI search agency should deliver in the first 90 days.
Switching to LoudFace
If you move your SEO and AI search work to LoudFace, kickoff happens within 48 hours of signing. In week one we collect access to your CMS, Search Console, analytics and logs, technical fixes ship, and the first articles are drafted and reviewed with you. You see shipped progress within five days. Start with our SEO and AEO service.
Sources
- Google Search Console Help, Owners, users and permissions
- Google Search Console Help, Verify your site ownership
- Google Search Console Help, Change of Address tool
- Google Search Console Help, Disavow links to your site
- Google Analytics Help, Access and data-restriction management
- Google Analytics Help, Data retention
- Google Search Central, Site moves with URL changes
- Google Search Central, Redirects and Google Search
- Google Search Central, Consolidate duplicate URLs
- Google Search Central, Debugging drops in Google Search traffic
- Google Search Central, Introduction to robots.txt
- Google Crawling Infrastructure, How Google interprets the robots.txt specification
- Google Search Central, Block indexing with noindex
- Google Search Central, Build and submit a sitemap
- Google Search Central, AI features and your website
- Google Search Central, SEO starter guide
- ICANN, Transferring your domain name
- ICANN, Transfer policy
- OpenAI, Overview of OpenAI crawlers
- Perplexity, Perplexity crawlers
- Anthropic Help Center, How Anthropic crawls the web and how to block it
- Aggarwal et al., GEO: Generative Engine Optimization (KDD 2024)
