SEO Client Onboarding Checklist for Agencies
SEO onboarding should establish what the agency is responsible for, what evidence is available, and who can approve changes. Receiving a website URL and a keyword wish list does not mean the team is ready to edit the site or interpret its performance.
Start with business priorities and the agreed scope
Ask which products, services and locations matter to the engagement. Separate a business priority from a proposed tactic: ‘more service enquiries’ is an outcome, while ‘publish thirty articles’ is an activity that still needs justification. Record what the agency can investigate or change under the agreement.
Keep a place for previous work, known constraints and upcoming site changes. A migration, new product line or unavailable developer can change the order of work. The intake should surface these dependencies without promising a ranking improvement or a fixed number of new pages.
Onboarding readiness worksheet
Scroll sideways to read all three columns.
| Area | Evidence to request | Ready when |
|---|---|---|
| Scope | Services, markets, site sections and exclusions. | Client and agency can describe the same first deliverable. |
| Reporting | Named outcomes, reporting period and available data sources. | The team knows which measures are observable and which are missing. |
| Access | Account owner and invitation route for each necessary system. | The assigned person has tested the appropriate access. |
| History | Earlier audits, major site changes and relevant launch dates. | The team can annotate important context instead of guessing. |
| Content | Existing priorities, subject experts and review process. | A person can verify facts and approve proposed changes. |
| Implementation | Developer contact, release process and change restrictions. | Recommendations have an owner and a route to review. |
An access request is a tracked task
Ask who can grant access and which account or property is relevant. Use the system's own invitation process with permissions appropriate to the agreed work. Do not collect passwords, recovery codes or tokens in the questionnaire. Record requested, granted and tested as separate states.
If access is missing, say which activity it blocks. For example: ‘Search reporting access not yet tested; query baseline remains unavailable.’ Other work may continue, but a missing source should not become a zero in a report or an invented estimate.
Illustrative first-review log
Scroll sideways to read all three columns.
| Observation | Decision | Owner and next action |
|---|---|---|
| Client wants service enquiries, but only page views are available. | Treat the enquiry baseline as unmeasured. | Client analytics owner reviews how enquiries are recorded. |
| A site redesign is planned next month. | Review preservation needs before proposing new URL structures. | Agency and developer compare the current inventory with the redesign scope. |
| The client requests pages for every nearby town. | Evaluate whether each page has a distinct useful purpose. | Content lead reviews service coverage and overlap before briefing pages. |
Close onboarding with a reviewable packet
Summarize what is known
Record the agreed scope, available sources, date ranges and any known limitations. Separate observations from hypotheses.
Prioritize the first work
Choose tasks based on the evidence available and delivery constraints. Explain which missing inputs could change the order.
Assign open items
Give each blocker an owner, requested action and next review date. Confirm who approves changes and how the first report will be reviewed.
Before calling onboarding complete
- Necessary access has been tested, not merely requested.
- Baseline statements identify their data source and period.
- Content and technical changes have review owners.
- Unmeasured outcomes and missing evidence are visible.
- The client understands the first deliverable and its limits.
Put the guide into practice
Align target markets, organic goals, CMS ownership and reporting expectations before SEO delivery starts.
Define a website's goals, page scope, content ownership and launch requirements before design begins.
Prepare a client review with delivered work, evidence, blockers and proposed priorities for the next period.
Questions people ask
Should onboarding include keyword research?
It can collect business priorities and previous research. The research itself follows from scope, audience and evidence; a client-supplied keyword list is input rather than a finished strategy.
Can work begin before every account is connected?
Some review work can begin. Identify exactly what is blocked and avoid presenting conclusions that depend on unavailable data.
Does completing the checklist guarantee SEO results?
No. It establishes a workable starting point and clear responsibilities, not a ranking or traffic outcome.
Keep reading
Better forms.
Better data.
Start with a conversation, a document or a single page. Unlimited forms and 500 responses per month on Free. No card required.