Alistair.PEditor
An SEO account handover often looks complete on paper while still leaving the incoming person with no clear sense of what matters now. There may be folders, reports, keyword lists and task boards, yet the practical judgement behind recent decisions sits in somebody's head. For a small agency, that creates avoidable risk: work can be repeated, priorities can drift and client expectations can be interpreted differently after ownership changes. A useful handover should transfer the operating picture, not just the archive. That means distinguishing current objectives, observed facts, approved decisions, system access and the few next actions that genuinely need attention.
Start with the client's current commercial priorities
Explain what the client is trying to achieve now, which services or markets matter most and which constraints shape the work. Avoid presenting the account as a collection of disconnected SEO tasks. The incoming owner needs to understand why particular pages, campaigns or technical issues have been prioritised so they can make sensible decisions when new requests appear. A brief summary should distinguish business objectives from promises about rankings. An agency may be tasked with improving clarity and discovery for approved services, but cannot guarantee a particular position in external search results.
Record material service changes and the business person who can verify them. If an offering is discontinued, the incoming account manager should know which page claims require review. If the company serves a defined geographic area, do not quietly extend that coverage to cities that marketing research identified as attractive keywords. Note who can approve new locality or eligibility statements. A handover should not simply reproduce a long historical strategy that no longer matches the client's business.
Separate verified findings from working assumptions
Record what has actually been observed in analytics, search data, site behaviour or implementation history, and keep that distinct from hypotheses still being tested. A handover becomes unreliable when an old theory is repeated as fact. Where evidence is incomplete, say so plainly and identify what would confirm or disprove the assumption. One example: a decline in defined page-group clicks over a month can be observed in Search Console, but attributing the decline to an algorithm change may remain speculative.
Give the incoming owner links to the actual source and the relevant filters, not only a screenshot of a graph. Google's Search Console Performance report documentation defines impressions, clicks, CTR and average position, and the next analyst should understand how the outgoing team applied those concepts. A proprietary visibility metric may measure something different, so avoid presenting it as Google's official position. Record uncertainty about seasonality, tracking and site releases. A useful handover leaves enough context for another professional to revise the diagnosis rather than inherit it as dogma.
Show what has changed and what is still pending
List material changes that have recently gone live, work that is awaiting implementation and decisions that still depend on the client or another supplier. This helps the new owner avoid judging results before a change has had a fair chance to operate or requesting the same action twice. Dates can be useful where verified, but the important point is the sequence and dependency, not a decorative timeline.
Separate recommendation, approval, database save, deployment and public acceptance. A content revision stored in Production may still not appear on a cached page; a redirect recommended in an audit may never have been implemented by the developer. A completed ticket does not prove every customer path works. Note the exact affected URLs and verification evidence, and identify open exceptions honestly. Google's site-move guidance is useful context for a migration, but cannot certify a client's actual old-to-new mapping. The handover should state which checks happened, by whom and under what conditions.
Make ownership visible across agency and client teams
SEO delivery often crosses content, development, analytics and client-side approval. Identify who currently owns each material next step and who has decision authority where work is blocked. A task without a clear owner can sit untouched even when everybody assumes somebody else is handling it. For a proposed new service description, the editor may own wording while an authorised client operations contact verifies the actual offer. For redirects, a technical implementer may own routing while an editorial reviewer confirms successor relevance.
Use a short responsibility matrix, not an unmaintained organisation chart. Show the responsible role, needed input and escalation route. Keep individual contact details in an authorised internal record and do not disclose irrelevant personal information to new external suppliers. Some teams have one person serving several functions, but factual approval and deployment evidence remain separate. Record which decisions need client authority and which changes can be made under an existing approved workflow.
Explain reporting choices and known data limitations
Describe which reports the client relies on, what each view is intended to show and any known gaps that affect interpretation. If tracking, attribution or tagging has limitations, make them visible rather than allowing the incoming person to treat every number as equally reliable. The goal is continuity of judgement, not preservation of every historic dashboard.
Explain property identifiers, authorised date windows, campaign filters and significant measurement changes without copying full customer datasets unnecessarily. A change in consent collection or analytics event configuration may alter reported conversions without a matching change in customer behaviour. If the team previously used a particular attribution convention, state it. Separate search visibility metrics from actual qualified enquiries and revenue. Where a dashboard definition cannot be verified, mark the limitation and identify the person who can confirm it. An accurate explanation of what cannot be compared is more valuable than forcing historical numbers into one continuous chart.
Capture relationship context without turning it into gossip
Useful handover notes can include preferred communication routes, recurring approval bottlenecks and areas where the client regularly needs more explanation. Keep the record professional and relevant to delivery. Avoid subjective labels or speculation about individuals; document observable working patterns that help the next owner communicate effectively. A concise note that the client prefers approved decisions summarised in writing is actionable. An unsubstantiated judgement about someone's personality is not.
Respect privacy and access boundaries. The UK ICO guidance on data minimisation supports retaining only information needed for a legitimate purpose, subject to relevant circumstances and obligations. Do not place credentials, private disputes or identifiable customer enquiries into a broadly shared account handover. Where sensitive material genuinely matters for delivery, use approved restricted channels and identify the responsible custodian.
Confirm that access is correctly controlled
A handover is not complete if the new owner has files but cannot view authorised data or if the previous supplier retains unnecessary administrator privileges. Inventory Search Console, analytics, CMS, tag management, shared assets and other systems relevant to the actual engagement. Distinguish client-owned accounts from agency-licensed tools, and make sure transfer rights match provider terms and the contract.
Google's Search Console user and owner permission guidance describes different capabilities; an SEO analyst does not automatically require property ownership. Confirm a legitimate client owner before removing a former administrator, then review delegated and service account access as appropriate. Record pending revocation separately from completed actions. Do not share passwords as a shortcut or claim every right was removed without checking current system permissions. The new account owner needs enough access to do the agreed job, not unrestricted control over unrelated client data.
Make the content inventory and source context usable
Provide a concise map of important service pages, active guides, pending updates, approved comparisons and significant factual sources. Identify content that has known review triggers, such as technical platform changes or service eligibility decisions. An incoming editor should not have to rediscover which overlapping articles were consolidated or which source documents the last team used. The inventory should reveal intended page purposes and natural relationships rather than only keyword labels.
For external illustrations, retain the original creator, file source and licence details. For technical instructions, identify appropriate primary documentation and the version being described. Do not promise that a historical screenshot reflects the current interface. Keep internal editor notes separate from the public copy, and flag any known renderer defect that could expose those notes. If content updates were saved but frontend checks remain open, make the status explicit rather than assigning the new colleague a false baseline of completed QA.
Finish with the next three decisions
A strong handover ends with a short set of concrete decisions or actions that will move the account forward. That gives the incoming owner a starting point and makes gaps obvious. The wider documentation remains available for reference, but the immediate operating picture should be clear enough that the account can continue without a pause for reconstruction.
For each priority, state the exact question, available evidence, person authorised to decide, implementation owner and acceptance condition. An example might be confirming whether an old service has an approved replacement before changing redirects. Another could be resolving access to a measurement property before reporting month-to-month performance. A third might be verifying the current public contact route after a website release. These examples are illustrative, not actual tasks on this client's account. Keep priority order based on consequence and dependencies, not the order in which a task appeared in a spreadsheet.
Complete the transition with a working check
Ask the receiving person to demonstrate that they can locate the relevant records, understand the main open risks and access the permitted tools. Have them explain the current plan back to the outgoing owner or project lead, identifying missing information while there is still an opportunity to correct it. A signed folder-transfer checklist alone is not evidence of operational continuity.
Record any open exception and its owner. A large unverified performance claim should not be turned into client-facing certainty. A public page change should not be marked complete solely because its database field was updated. The handover's value is that the new owner knows what has been done, what was observed, what is uncertain and what needs a real decision next. For a small agency, this is the difference between transferring files and genuinely transferring responsibility, while protecting client trust and data.