SEO Consultant Handover Checklist: What to Collect When Work Ends

Why does a handover checklist matter?

Most business owners know exactly what they asked their SEO consultant to do and almost nothing about what the consultant actually did. That's fine while the relationship runs. It becomes a problem the moment it ends, because the consultant leaves with knowledge, access and sometimes whole assets that you thought were yours.

A handover checklist fixes that. It's a plain list of things to collect, check and close, so that the end of an engagement is tidy rather than tense. It's also the cheapest insurance you can buy against lost data, locked-out accounts and rankings that wobble for reasons nobody can explain.

When does it apply?

Whenever a consultant, freelancer or agency stops working on your site: a contract ending, a change of provider, a move in-house, a team member leaving or a project reaching its conclusion. The checklist is the same, whether the parting is friendly or frosty.

For the bigger picture of choosing a new provider and protecting rankings through the change, the guide to switching SEO providers without losing rankings sets out the strategy. This guide is the working checklist that goes alongside it.

Use it even when things are going well

A handover on good terms is the easiest time to get everything documented. Don't wait for a dispute.

What are the five areas?

Accounts and access. Documents and history. Work in progress. Tracking and reporting. And knowledge transfer. Each has its own tasks, and each has things that commonly go missing. The sections below go through them in turn, with a timeline at the end.

What is the timeline?

Handovers go wrong when they're squeezed. A calm one runs over weeks, with each stage leaving room for fixes.

Here's a sensible shape.

What happens when?

Shorter engagements can compress this, but keep the order. Collect before you close, and verify before you relax.

Put dates in writing

Agree deadlines with the consultant and tie final payment to delivery of the items on the list, where your contract allows it.

Who should be involved?

The business owner or manager, who decides. Whoever manages the website, usually a developer or marketing lead. The outgoing consultant and, if there is one, the incoming provider. And someone responsible for IT or security, who can check accounts and passwords. Small businesses may have one person wearing all those hats. That's fine, as long as the tasks are assigned.

Hold a short kick-off call, share the checklist and agree who owns each item.

Which accounts and access need attention?

This is the most important section, because lost access is the hardest problem to fix later. Treat it as a gating item: until accounts are secured, nothing else matters.

The aim is simple. Every important account should be owned by the business.

What should you confirm you own?

Domain registration and DNS. Hosting and any control panel. The CMS and its administrator accounts. Google Analytics. Google Search Console. Google Tag Manager. The Google Business Profile and other local listings. Advertising accounts. Email marketing and CRM systems. Rank-tracking and reporting tools, and any paid software accounts used on your behalf. Social profiles.

For each, record who the owner is, which email address is attached and what recovery options exist. If any sit under the consultant's name or email, request a transfer in writing now, not on the last day. The principles are in the guide on what access an SEO consultant should have.

Add a second owner everywhere

At least two people in your business should be able to administer each account. A single point of failure is a risk.

How does Search Console handle owners and users?

Google's help page, Managing owners, users, and permissions, describes the levels. Owners have full control: they can add and remove users, configure settings, view all data and use all tools, and verified and delegated owners have the same permissions. Full users can view all data and take some actions, such as submitting sitemaps and disavowing links, but cannot add or remove users. Restricted users have simple view rights on most data. Associates can take certain actions on behalf of the site, but cannot open the Search Console account or its data directly.

At handover, check that you hold ownership, then remove the consultant's user entry. If the consultant verified the property using their own method, such as a DNS record they control or a tag on their own account, confirm that you've added another verification method before they leave, otherwise ownership can lapse.

Check the associations too

Look for associated accounts and linked services in Search Console and Analytics, and remove any that belong to the consultant.

What documents and history should you collect?

Documents are the memory of the engagement. Without them, the next provider starts from scratch, and you pay for the same discovery twice.

Ask for the items below, in editable formats.

Which deliverables are standard?

Audit reports and recommendations. The roadmap, with status for each item. A change log listing dates, URLs, what changed and why. Keyword research and keyword-to-URL maps. Content calendars, briefs and drafts, including unpublished work. Redirect maps and migration records. Link-building and outreach records, including any purchased or exchanged placements. Reports and dashboards, with data exports for the full engagement. A list of tools and subscriptions used and who owns them. A well-run engagement normally produces clear SEO consulting deliverables such as audits, roadmaps, briefs and dashboards.

If something was promised and not delivered, say so in writing now, while you still have the relationship.

Ask for formats you can use

Spreadsheets, documents and exports in open formats are better than screenshots and PDFs of dashboards.

What if documentation is thin?

Rebuild what you can. Export historic data from Search Console and analytics yourself. Use the CMS revision history, backups and the Wayback Machine to see past versions. Crawl the site to document current titles, canonicals, redirects and structured data. Then ask the consultant for a short recorded walkthrough to fill the gaps.

Thin documentation isn't unusual, and it's a reason to be more careful about the audit of the work, not a reason to panic.

What about work in progress and open recommendations?

Most engagements end mid-flight. Content is half-written, a redirect project is partly done, an outreach campaign has live conversations. If you don't capture those, the work stalls or, worse, gets duplicated.

A simple status table saves a lot of confusion.

How do you capture the status of each task?

List every open task with its owner, status, next step, dependencies and any deadline. Mark tasks as done, in progress, blocked or not started. Add notes on why decisions were made, because the reasoning is as useful as the result. Attach relevant files and links.

Ask the consultant to complete the table and review it with you on a call. Anything unclear should be resolved before they leave, while the context is still fresh.

Decide who takes what

For each open task, name the new owner: you, your team or the incoming provider. Unowned tasks are the ones that disappear.

Which tasks should not be left half-done?

Anything that changes the live site in a way that could leave it in an inconsistent state: partial redirects, half-applied template changes, a staged migration, a batch of title edits. Agree with the consultant either to finish and verify these before they leave or to roll them back to a stable state.

If a task can't be completed in time, document its exact status and the steps to resume or reverse it. A clearly documented pause is safe. An unexplained half-finished change is not.

How do you verify tracking and reporting?

Tracking breaks quietly during handovers, and nobody notices until the numbers look wrong weeks later. Check it directly.

A short test routine catches most issues.

What should you test?

That analytics still records page views, key events and conversions, such as form submissions and calls. That Tag Manager's container is intact and published, with a clear version history. That conversion goals match your business, and that spam and internal traffic are filtered. That Search Console is connected to analytics if you use that integration. That reporting dashboards still pull data, and that any scheduled reports still reach the right people.

Submit a test enquiry, make a test call and check that each appears. Compare a week of data against the same period before the handover for large unexplained differences. The approach is described in the guide to measuring organic leads in GA4.

Document the tracking setup

Record which tags, events and conversions exist, who owns each tool and where the logins are. It's the information most often missing from handovers.

What about dashboards and recurring reports?

If the consultant built a dashboard under their own account, ask them to copy it into yours, or rebuild it in a business-owned workspace. If reports are scheduled to send from their tools, move the schedules. Otherwise, reports stop on the day access ends, and nobody notices for a month.

Save a copy of key historic reports before access is removed. They form part of your benchmark for the next provider.

How do you handle knowledge transfer?

Documents capture facts. Conversations capture reasoning, quirks and the stuff nobody thought to write down. A short, structured handover session often adds more value than another stack of files.

Plan it deliberately.

What should a handover session cover?

A walk through the site's structure and the SEO strategy behind it. The reasons for key decisions: why certain pages exist, why others were merged or removed, why particular keywords were targeted. Known problems and risks. Relationships with developers, writers and suppliers. Quirks of the platform, plugins and hosting. What's working, what isn't and what the consultant would do next.

Record the session, with the consultant's agreement, and store the recording with the documents. Ask for a short written summary afterwards.

Include the incoming people

If a new provider or in-house lead is taking over, they should attend. A conversation with the person who knows the site is worth hours of reading.

What questions should you ask?

"What would break first if nobody looked at this for a month?" "Which pages or tasks are most sensitive?" "What have you tried that didn't work?" "What's waiting on someone else?" "Which Google updates or events affected us, and how?" "What would you change in the plan?" Honest answers to those are gold.

Capture them in the shared notes. They shape the new provider's first ninety days, and they stop the same mistakes being made twice.

How do you remove access safely?

Removing access is the final security step. It feels like a formality, and it's one of the most commonly skipped.

Do it in a sequence, and verify each step yourself.

What is the removal sequence?

First confirm everything else on the checklist is complete: documents received, ownership confirmed, tracking tested. Then, on the agreed date, remove the consultant's users from Search Console, Analytics, Tag Manager, the CMS, hosting, domain registrar, Business Profile and every other platform. Revoke API keys, OAuth connections and tool integrations. Change any shared passwords. Remove server, FTP and SSH access. Delete or reassign any scripts, plugins or tags that belong to the consultant's accounts.

Then log in as an owner on each platform and check the user list. Update your access register with the date and the person who verified it.

Don't forget invisible access

OAuth connections, API keys and third-party apps can retain access after a user is removed. Review connected apps in your Google account and in each platform's settings.

What about shared credentials?

If you ever gave the consultant a password, change it, even if you also revoked the user. Move credentials into a password manager, rotate any that were shared and turn on multi-factor authentication. Check whether the consultant's own devices or tools stored the credentials, and ask them to confirm deletion.

It's a few minutes of work that closes a risk completely. And if you're unsure whether something was shared, assume it was and change it.

What should you check after the handover?

The handover ends on the last day, but the risk doesn't. A short review a few weeks later catches anything that slipped through.

Put it in the diary now.

What goes into the post-handover review?

Compare current analytics and Search Console figures with the benchmark. Check indexing status, sitemap health and any new errors. Crawl the site to confirm redirects, canonicals, robots.txt and tracking tags are as expected. Look at the Business Profile for unexpected edits. Verify that reports are still arriving. Review the change log for anything made after the handover. And ask the new provider or in-house lead whether any gaps have appeared.

Hold the review two and four weeks after the end date. If anything looks wrong, trace it against the change log and the checklist, and raise it with the previous consultant promptly while their memory is fresh, ideally under a short, agreed post-handover support arrangement.

Close the file

Once everything checks out, sign off the checklist, store it with the documents and note any lessons for the next handover.

How do you make the next one easier?

Keep the account register, change log, benchmark and roadmap current as part of normal work. Ask every provider to document changes as they go. Review access quarterly, and remove people promptly when they finish. A business that treats these as routine can switch providers in days rather than weeks.

If you'd like help building the process, or a second pair of eyes on the handover itself, an independent SEO audit provides a clean baseline for the next stage, and a well-run SEO consulting process documents its work from day one.

What does a worked example look like?

A story helps the checklist land. This one is hypothetical, built from typical patterns, and the details are illustrative.

It follows a small business through a tidy handover.

What was the situation?

A small London training company had used a freelance SEO consultant for eighteen months. The freelancer was relocating abroad and ending the contract with four weeks' notice. The owner had never looked at the accounts, other than receiving monthly reports.

On day one of the notice period, the owner made a list of every platform and checked who owned each. Analytics and Search Console were under the owner's email. The Business Profile had the consultant as a manager, not an owner, which was fine. But the rank-tracking dashboard and a shared content calendar sat in the freelancer's accounts.

The early catch

Because they checked in week one, there was time to move the dashboard and calendar, instead of discovering the gap on the last day.

How did it go?

The owner sent the checklist to the freelancer and agreed dates for each stage. The freelancer delivered a change log, a roadmap with status, keyword maps and a list of open tasks. They recorded a forty-minute walkthrough of the site and strategy, which the owner shared with a new part-time marketing hire. Together they tested tracking by submitting a test enquiry and checking that it appeared in analytics.

On the final day, the owner removed the freelancer's access from every platform, rotated two shared passwords and logged in as an owner to verify. Two weeks later, they ran the post-handover review, found one scheduled report still sending from the freelancer's tool and moved it. The site's performance stayed steady throughout.

Nothing about the process was clever. It was a list, a timeline and the habit of verifying, which is all a good handover needs. Keep the checklist, update it after each engagement and you'll rarely face the question "who owns that?" again.

What contract terms make handovers easier?

The cheapest way to ensure a smooth handover is to agree it before the work starts. A few clauses in the original contract turn a difficult conversation into a routine one.

You don't need legal drafting. You need clarity.

Which clauses help most?

Ownership of deliverables: everything created for you belongs to you, including audits, briefs, dashboards and content. Account ownership: all accounts are set up in your name. A handover obligation: the consultant will provide a change log, documents and a knowledge-transfer session on request. A notice period that allows an overlap. A confidentiality and data-handling clause. And a statement of what happens to access and credentials when the work ends.

If you're renewing an existing contract, add them now. A short schedule attached to the agreement is enough, and good providers rarely object, because it makes their own exit tidier too.

Tie payment to delivery

Where it's fair, link the final invoice to completion of the handover checklist. It keeps both sides focused on a clean finish.

What if the contract is silent?

Ask anyway, politely and in writing. Most consultants will cooperate, because a smooth exit protects their reputation. If they won't, you still have leverage over the final payment and over their references. Keep the request reasonable and specific, with dates, and save every message.

For anything involving sizeable sums or unresolved ownership, take legal advice. For everyday handovers, a courteous, well-organised request gets almost everything you need.

What about handing over to an in-house team or a new hire?

When the next owner of SEO is someone inside your business, the handover has a teaching element. They need to understand not just what exists but how to run it.

Plan for learning as well as logistics.

How do you set up an in-house owner for success?

Give them access to every account, in their own name, with the right permissions. Walk them through the dashboards and reports that matter, and the routines behind them: monthly reviews, post-release checks, indexing monitoring. Share the roadmap, the change log and the benchmark. Introduce them to the developers, writers and suppliers they'll work with.

Ask the outgoing consultant for a few follow-up sessions, spaced over the first month, so the new owner can bring questions as they arise. It's a modest cost and speeds up learning enormously.

Write down the routines

Document the weekly, monthly and quarterly checks as a short runbook. A new owner with a clear routine is far less likely to miss something important.

What support might they still need?

Occasional expert input on complex issues: migrations, international setups, technical problems or Google updates. Consider keeping a consultant on a light, flexible arrangement for second opinions. For a team new to the discipline, a short course or workshop, such as the SEO training for in-house teams offering, builds the skills they'll lean on every week.

The aim isn't to avoid expertise. It's to use it where it adds the most, while the day-to-day work sits with people who know the business.

What are the common handover mistakes?

Handovers fail in predictable ways. Knowing the list lets you steer round it.

Most come down to leaving things too late or trusting without checking.

Which mistakes cost the most?

Starting the checklist on the last day. Assuming accounts are in your name without looking. Accepting a PDF of a dashboard instead of the underlying data. Removing access before tracking has been tested. Letting half-finished changes sit unrecorded. Skipping the knowledge session because everyone's busy. Forgetting OAuth connections and API keys. And never running the post-handover review, so small problems become long-term ones.

Each of those is cheap to avoid and expensive to fix. The checklist exists to prevent them.

The verification habit

If you take one habit from this guide, make it this one: never accept "it's done" without checking it yourself on the platform.

How do you keep it friendly?

Approach the handover as a shared project with a shared goal: a clean finish that protects your business and the consultant's reputation. Be specific, say thank you, set dates and follow up politely. Most consultants want to leave things in good order, and a clear checklist makes it easy for them.

If things have soured, stay factual and documented, keep to the checklist and escalate only if you need to. Calm, specific and written is the best posture in almost every case.

What does a copy-and-paste handover template look like?

A checklist is more useful when you can fill it in. The structure below turns the guide into a single document you can share with the consultant and tick off together. Adapt the items to your site.

Keep one copy in your records and one with the consultant.

What sections should the template have?

Start with a header: business name, consultant name, contract end date, handover owner on each side and the date the template was agreed. Then five sections, each a table with an item, an owner, a due date, a status and a verification column.

The accounts section lists each platform with the owner, the email attached, the consultant's current access level and the action required. The documents section lists each deliverable with the format and location. The work-in-progress section lists each open task with its status and new owner. The tracking section lists each test and its result. The closure section lists each access removal with the person who verified it and the date.

Add a sign-off block

At the bottom, a short statement and two signatures, one from each side, confirming the handover is complete. It's informal, and it focuses minds.

How do you use it day to day?

Share it on the first day of the notice period and review it in a weekly call. Update statuses as items complete, and record any exceptions with a reason. Don't mark an item verified until someone on your side has checked it directly. Keep the finished template with the account register and the change log.

When the next engagement starts, reuse the same template in reverse: set up accounts in your name, agree the documents you'll receive and put the handover obligations in the contract from day one. That's how one good checklist becomes a permanent habit, and why businesses that keep their records tidy can change provider without drama.

Review it once a year

Even without a handover, a yearly pass through the accounts and documents sections keeps everything current, and it makes any future exit far quicker.

How do you handle sensitive information in the handover?

Handovers move a lot of data: customer enquiries, analytics, credentials and sometimes personal details in reports or spreadsheets. Treat it with care. Share files through a secure, business-owned workspace rather than by email attachment, limit access to the people who need it and delete copies you no longer require.

Ask the consultant to confirm in writing that they've deleted or returned any client data held on their own systems, in line with the confidentiality and data-handling terms of the contract. It protects you under data protection rules and gives you a clear record that the engagement ended cleanly.