An SEO agency handover is complete when the business can access its systems, understand the work already done and continue essential tasks without depending on an undocumented account. A folder of reports is helpful, but it is not enough. The handover needs verified access, clear ownership, operational context and a planned sequence for changing permissions.
Set the scope and identify the business owner
List the services ending or changing and name the person authorised to accept the handover. Separate SEO reporting from website maintenance, hosting, paid media and content production if different suppliers own those activities. An assumption that “the agency handles it” can conceal dependencies that fall outside the contract being replaced.
Agree a handover schedule, an inventory format and how unresolved items will be tracked. Include the incoming supplier where appropriate, but keep a business representative responsible for acceptance. The company should understand what it controls even if it delegates day-to-day operation to someone else.
Inventory accounts and ownership
Record the account or property name, identifier, purpose, business owner, current administrators and required access level. Include Search Console, analytics, tag management, the CMS and any reporting connectors. Where SEO work depends on domain settings, hosting or deployment tools, document the responsible owner and escalation route.
Do not put passwords or recovery codes in a general handover spreadsheet. Prefer named accounts and the platform's access controls. When secrets genuinely need transfer, use the business's approved secure process. The inventory should explain where access is managed, not become an uncontrolled copy of every credential.
| Asset | Acceptance evidence |
|---|---|
| Search property | A business-controlled owner can access the correct property. |
| Analytics and tags | Named staff can inspect configuration and published versions. |
| Content and files | Approved source material and editing access are available. |
| Reporting connections | Refreshes work without an unexplained personal account. |
| Outstanding work | Every open issue has evidence, status and a responsible person. |
Verify Search Console ownership carefully
Google's documentation on Search Console permissions distinguishes verified owners, delegated owners and users. Check which role the business holds and which verification methods are in use. Access to a report is not the same as control over the property or the ability to manage other users.
Establish business-controlled ownership before changing the outgoing agency's access. When removing a verified owner, review the relevant verification tokens as Google documents; removing an entry alone may not prevent verification again while their token remains. Do not delete unfamiliar DNS records or site files indiscriminately, because they may support other legitimate services or owners.
Recover the reasoning behind completed work
Request the current page map, audit findings, approved redirect records, content briefs and change history. Ask which recommendations were implemented, which were rejected and which remain proposals. A historic audit without status information can lead the incoming team to repeat work or undo a deliberate decision.
Keep evidence attached to significant changes. If pages were consolidated, preserve the reason and destination mapping. If a technical workaround exists, document the underlying constraint and how it should be tested after a future release. This context often matters more than the volume of documents transferred.
Make reporting reproducible
Document report sources, filters, date settings and definitions of conversions or accepted enquiries. Confirm who owns dashboards and whether their data connections rely on the outgoing agency's account. A shared dashboard can remain visible after a handover while silently failing to refresh, so test the connection rather than assuming visibility establishes continuity.
Record known measurement gaps and important changes to definitions. Preserve relevant baseline exports with their scope and dates. Do not merge reports from different methodologies without explanation. The incoming team needs to know what comparisons are valid before interpreting an apparent improvement or decline.
Identify subscriptions and operational dependencies
List tools, plugins and services paid for through the agency, including licence terms and renewal responsibility. Determine whether the business needs its own subscription, an account transfer or a replacement. Check the effect of cancellation before ending access, especially where a tool supplies redirects, forms, monitoring or scheduled exports.
Include automated tasks and alerts. Identify where failures are sent, which mailbox receives notifications and who responds. Move essential notifications to an accountable business-owned destination through the approved process. A monitoring system that still alerts a departed supplier does not provide a usable handover.
Test access before revoking it
Have the receiving team sign in with their own accounts and perform representative authorised tasks. They should be able to inspect key reports, locate configuration, find source documents and understand open issues. Use non-destructive checks where possible; there is no need to publish a live change merely to demonstrate that a permission exists.
Then remove permissions that are no longer required in an agreed sequence. Record completion and any exceptions, such as temporary access for an unresolved support task. Review recovery contacts and ownership separately from ordinary user lists. Retain a clear route for resolving missing information after the formal handover date.
Accept the handover with an exceptions list
Confirm what has been received, what has been tested and what remains outstanding. Give each exception an owner and a target resolution date. The business can then distinguish an accepted limitation from an accidental omission, and the incoming team can begin with a reliable view of the systems and work it inherits.
Visuosofts' SEO services can be discussed alongside a documented transition. Use enquiry-focused SEO reporting to agree the next reporting framework. Contact Visuosofts with your account inventory and outstanding work to discuss the requirements for a practical handover.