Your new SEO provider sees a redirect they would remove. The outgoing team installed it during a booking-system change, but the reason lives in an old email. The wrong edit could send customers back to a retired page.
Collect the work history before the handoff. Access lets the new provider enter the systems; context helps them avoid undoing useful changes or repeating work you have already paid for.
Ask for a packet organized around continuity
Use this illustrative packet for a service business moving between providers. Adjust it to the actual scope and agreement rather than demanding unrelated tools or private material from the provider.
| Packet item | Useful contents | Acceptance check |
|---|---|---|
| Account inventory | Company owner, named users, connected tools | Company administrator can retain control and remove outgoing access |
| Change log | Date, affected URL, change, purpose, verification | New provider can explain the current redirect example |
| Open work | Current task, approval state, blocker, next action | No approved task disappears between teams |
| Content assets | Published pages, editable drafts, permissions, source notes | Team can distinguish live content from unapproved drafts |
| Measurement notes | Property, event definitions, reporting periods, known limits | New team does not mistake a button click for a completed lead |
In the redirect example, the change log should explain which old URL it replaced and which customer action the destination supports. A crawler export without that context leaves the new team guessing.
Transfer open decisions as well as files
Suppose the outgoing provider prepared a new emergency-repair page, but the owner has not confirmed after-hours availability. Put that draft in the packet as awaiting a business decision. Do not let the new team publish it because it appears in a folder called “ready.”
Separate work requested, approved, deployed, and checked. Those states mean different things. Record who owes the next action and whether a deadline still applies. This gives the new provider a usable starting list rather than a second audit of unfamiliar artifacts.
For published content, preserve the current URL and relevant history. A provider transition alone is not a reason to rename pages or replace working content. Ask for evidence before approving a change that can affect customer paths.
Confirm control before removing access
Have your company administrator verify access to the website, Search Console, analytics, Business Profile, and any paid tools you will keep. Confirm which subscriptions continue under company billing and which will end with the outgoing engagement.
Google's SEO hiring guide recommends clear explanations of changes. That clarity matters during departure as well as delivery.
Schedule a defined overlap if the agreement and both providers permit it. The incoming team can inspect the packet, ask about unexplained material changes, and demonstrate access before the outgoing team loses its permissions. Your administrator should review connected integrations separately from named user accounts.
Finish with a small handover acceptance test
Ask the incoming provider to trace one published change, one open task, and one measurement definition using the packet. Check that your administrator can control access without either provider's assistance. Resolve gaps or record an interim arrangement and the person responsible.
This is a continuity exercise, not a demand that the new provider agree with all prior decisions. Once they understand the history, they can recommend changes with a clearer basis.
Our SEO provider questions help assess the incoming team's judgment. Discuss a supported handoff and ongoing scope through The Ops Guide's SEO services.

