Starting an SEO project should not mean sending a password and waiting for a report you cannot interpret. A useful SEO client onboarding checklist helps a small business explain what matters, decide who can change the website and agree what the first piece of work will deliver.
Use this checklist before the first working session with a consultant or agency. It is a suggested preparation routine, not a promise of rankings or a replacement for your service agreement. You can complete it in a shared document without purchasing another project-management tool.
1. Explain the work you actually want more of
Give your provider a short description of your most important services, the customers you can serve and the enquiries you would rather avoid. A business that wants more commercial maintenance contracts needs a different conversation from one trying to fill spare residential appointments.
For a fictional cleaning company, a useful note might be: “We want enquiries for recurring office cleaning within our existing service area. We do not offer emergency flood cleanup.” That sentence gives a writer and an analyst more direction than “we want more traffic.”
- Which service is the first priority?
- Which locations can the team realistically cover?
- What makes an enquiry suitable for the business?
- Are there capacity limits or seasonal closures to consider?
2. Separate the agreed deliverable from the hoped-for outcome
Write down what the provider will produce and who will implement it. An audit can identify improvements without including development, copywriting or deployment. A keyword list is not the same deliverable as revised service pages.
For example, “review three service pages and provide a prioritised action list” describes work that can be checked. “Reach the first position next month” describes an outcome nobody can responsibly guarantee. If you are still comparing proposals, our guide to choosing SEO services provides questions to raise before committing.
3. Prepare access without sharing your personal login
Ask which systems the provider needs and why. Use individual invitations and the access appropriate to the task where the platform supports them. Keep ownership and recovery details under business control. Do not put passwords, recovery codes or payment details in the onboarding document.
Record the system name, invited business contact, intended role, purpose and review date. A reporting-only task may not require permission to edit the website. If broader access becomes necessary later, ask what action requires it before approving the change.
Have the recipient confirm access works before scheduling work that depends on it. An invitation sent to the wrong account is not a completed handoff.
4. Share the website history that may change the plan
List recent redesigns, domain moves, large content removals and known technical problems. Include previous reports if you have permission to share them, but distinguish confirmed issues from assumptions. “Contact form submissions stopped on Tuesday” is more useful than “Google dislikes the website.”
Also explain who manages hosting, forms and website code. Your SEO contact should know whom to involve if a recommendation affects a booking system or a page that generates enquiries.
5. Agree how progress will be discussed
Choose a small set of measures connected to the goal. Record the reporting period, relevant pages and any gaps in the data. If enquiry tracking is incomplete, note that limitation rather than treating an empty report as proof that no enquiries occurred.
Ask for a report that explains what changed, what was observed and what should happen next. Our SEO reporting guide for local service businesses explores that decision-focused approach. Comparing the same definitions over time is more useful than switching the headline metric whenever a different number looks better.
6. Name an approver and a publishing owner
Someone must check service claims, prices, locations and brand language. Someone must also approve and publish changes. In a small company these may be the same person, but the responsibilities should still be explicit.
Agree a realistic review window and a backup contact for absences. Avoid treating silence as permission to publish. Before a change goes live, decide how the previous version will be recovered if a form, layout or important link breaks.
A simple kickoff worksheet
Copy these prompts into your project document and answer them in plain language:
- Priority: The service and customer group we will focus on first are…
- Scope: This phase includes… It does not include…
- Inputs: The approved business facts, examples and existing materials are stored…
- Access: The required invitations are confirmed by…
- Approval: The person checking content is… The person publishing is…
- Measurement: We will review… for the period… with these limitations…
- Next action: The first deliverable is… Its owner is… Its agreed delivery date is…
Leave unknown answers marked as unknown, with a person assigned to resolve them. An honest gap is easier to manage than a confident guess that later becomes a requirement.
Common questions
Do I need to research keywords before onboarding?
No. Bring the language customers use, common sales questions and the services that matter most. If you already have keyword research, share its source and date. The provider should evaluate relevance rather than insert every phrase into your pages.
Should the agency receive full administrator access immediately?
Not automatically. Match permissions to the agreed work, retain business ownership and review access when the engagement changes or ends.
What should happen after the kickoff call?
Send a short written recap with decisions, unanswered questions, owners and the next delivery date. Keep it somewhere both sides can find. The result should be a clear starting point for the project, not another long document nobody uses.