SEO Client Onboarding Checklist

SEO Business & Delivery Toolkit, template 9 of 10

SEO Client Onboarding Checklist

Track every access, definition and baseline export a new SEO engagement needs, with owners and blockers.

Whether a new SEO engagement has everything it needs to start: access verified, definitions agreed and baselines captured, and what's blocking the rest.

  • Excel workbook (.xlsx), opens in Google Sheets
  • PDF field guide, 9 to 11 pages
  • Blank and worked CSV templates
  • DataForSEO import script

Free, no email required. Version 3.0, updated November 2026.

SEO Client Onboarding Checklist.xlsx
L13fx=IF(J13="","",IF(J13<>"Ready","n.a.",IF(AND(D13=1,K13=0),1,0)))

Start HereDashboardWorkspaceDelivery QAField Guide

The formula above is the real one from cell L13. Scroll it sideways to read the whole rule.

Connected to the DataForSEO API

This template is designed around one DataForSEO endpoint. Pull the data, convert it with one command, and the workbook does the rest.

Setup steps

DataForSEO On-Page APIA crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membershipon_page/task_post

Save the JSON responseThe full API response, kept as your source of truth.response.json

Run the import scriptOffline. No API calls, no credentials.dataforseo_import.py import --template 39 --csv

Paste at A13Dashboard, checks and action list update instantly.SEO Client Onboarding Checklist.xlsx

Column map for this template:Filled by the APIAudit trail (automatic)You add

Requirement IDRequirementSystemRequired for scopeAccess verifiedOwnerVerification evidenceOpen blockerSource reference
1 of 9 input columns come straight from DataForSEO (the audit trail; this one is a human sign-off workflow)

What the SEO client onboarding checklist decides

The first month of an SEO engagement is often lost to waiting: for Search Console access, for analytics permissions, for someone to explain what counts as a conversion. Every week of waiting is a week of strategy built on guesses.

This SEO onboarding checklist lists each requirement with the system, whether it's required, whether access is verified, owner, evidence and blocker. A requirement is complete only when access is verified with evidence. Required items still open are counted and listed on the Dashboard.

Who it's for

  • Consultants and agencies onboarding SEO clients
  • In-house SEOs joining a new company
  • Project managers kicking off SEO projects
  • Clients who want to know what to prepare

Where it fits in your workflow

The SEO client onboarding checklist answers one question. These three templates answer the questions around it:

  • SEO Roadmap Template: what to do in each 30-day phase, ranked by weighted monthly opportunity per hour, which initiatives are blocked by dependencies, and what 'done' means for each.
  • SEO Migration Checklist: whether the migration is safe to launch: which critical controls are still open, who owns them, and what evidence closes them.
  • SEO Forecast Template: how much additional traffic and monthly contribution a portfolio of keyword clusters could add, with every assumption visible.

What's inside the download

One ZIP with the workbook, a 9-column input template (blank and filled), the PDF field guide and an offline script that converts saved DataForSEO responses into the input CSV. The workbook has five tabs.

Workspace. The working table. 9 input columns, 3 calculated columns, room for 250 rows. Dropdowns, Yes/No fields and range checks catch bad inputs as you paste.
Start Here. What it decides, a four-step setup and the colour key.
Dashboard. KPI cards, charts, a ranked Top 10 and an automatic action list.
Delivery QA. Pass, fail or exclude each validation step with evidence, owner and date.
Field Guide. Every field explained, plus each formula in plain English.

How the SEO onboarding checklist calculation works

Requirement complete = 1 when access verified is 1 and evidence exists. Required item open = 1 when the item is required and not complete.

The key formula, exactly as it appears in the workbook

=IF(J13="","",IF(J13<>"Ready","n.a.",IF(AND(D13=1,K13=0),1,0)))
Result column Plain-English formula What it tells you
Requirement complete IF(AND(Access verified=1,Verification evidence ≠ ""),1,0) Usable access plus verification evidence.
Required item open IF(AND(Required for scope=1,Requirement complete=0),1,0) A required item remains open until verified with evidence.

How to use the SEO client onboarding checklist

  1. Send the list before kickoffShare the requirements with the client so access requests start early.
  2. Assign owners on both sidesEach item needs a named person who can grant or confirm it.
  3. Verify, don't assumeMark access verified only after you've logged in and checked. Record evidence.
  4. Escalate blockersRequired items with blockers go to the kickoff agenda.

The worked example in the Workspace tab. Clear the lime input cells, paste your CSV at A13 (values only) and every result recalculates.

Fill the SEO client onboarding checklist with DataForSEO

Every template in this library is built to run on DataForSEO data. This one uses DataForSEO On-Page API: a crawl of your site: URLs, status codes, canonicals, inlinks and sitemap membership.

This is a sign-off workflow. DataForSEO responses are the evidence you attach; the human checks stay manual by design.

  1. Request the dataSend this request with your DataForSEO API login (HTTP Basic auth).
    POST https://api.dataforseo.com/v3/on_page/task_post [ { "target": "yourdomain.com", "max_crawl_pages": 1000 } ]

    Post the crawl task, wait for it to finish, then request on_page/pages with {"id": "<task id>", "limit": 1000} and save that response.

  2. Save the full JSON responseSave the complete response, not just the task ID, next to the template folder.
  3. Convert it with the included scriptIt runs offline, makes no API calls and never sees your credentials.
    python3 Automation/dataforseo_import.py import --template 39 --csv --input my-filled.csv --output my-inputs.csv
  4. Add what the API can't knowRequirement ID, Requirement, System, Required for scope, Access verified, Owner, Verification evidence, Open blocker
  5. Paste at A13Clear the demo rows, paste the CSV values at Workspace cell A13 and the dashboard updates.
Fills automatically from DataForSEO You add
Source reference (audit trail) Requirement ID, Requirement, System, Required for scope, Access verified, Owner, Verification evidence, Open blocker

Source reference fills automatically with the task ID, endpoint, location, language, device and snapshot time, so every row is traceable. Before a big pull, estimate the cost with the DataForSEO pricing calculator. The same steps, plus an example request file, are in the download's Automation folder.

Worked example: Northbeam Outdoor

Every template ships filled with data from Northbeam Outdoor, a fictional outdoor-gear retailer that appears across all 40 workbooks, so you can see what useful output looks like before you add your own. This workbook has 12 example rows.

12Records
0Rows with input issues
2Open required items
8Requirements complete

Two required items are still open in the example: conversion definitions waiting on finance, and server log access that isn't enabled. Both block meaningful strategy work.

Input fields

Keep the columns in this order when you prepare a CSV. A missing observation stays blank; use 0 only for a measured zero or a verified No. Fields marked DataForSEO can be filled automatically by the included script.

CSV field Column Meaning and rule Source
requirement_id Requirement ID Stable onboarding requirement identifier. Your records
requirement Requirement Specific access or discovery acceptance condition. Your records
system System Source system or business owner. Your records
required Required for scope 1 when needed for the agreed engagement. 1 = Yes, 0 = No. Your records
access_verified Access verified 1 after the requested access or evidence is actually usable. 1 = Yes, 0 = No. Your records
owner Owner Person accountable for the next action. Your records
evidence Verification evidence Link to a permission check or approved business record. Never include passwords. Optional. Your records
blocker Open blocker Specific missing item or dependency. Enter NONE when resolved. Your records
source_ref Source reference Task ID, export filename and observation scope. Retain the untouched source response separately. Optional. DataForSEO: source_ref

Reading the result honestly

Access is complete only when it works for the needed property, scope and data range.

Limits. This is an evidence workflow. DataForSEO supplies independent crawl and market context, not private account access.

SEO onboarding checklist mistakes to avoid

Accepting 'you have access' without checkingPermissions are often lower than promised. Log in and verify.
Skipping definitionsWithout agreed conversion definitions, every report becomes a debate.
Not capturing baselines earlyExport 16 months of Search Console data on day one. It disappears after that window.

Tips from practice

  • Use the 90-day roadmap once onboarding closes.
  • Keep this checklist as part of your statement of work.
  • Re-run access checks quarterly; people and permissions change.

Frequently asked questions

What do I need from a new SEO client?

Search Console and analytics access, CMS access, conversion definitions, previous audits, brand and legal guidelines, Business Profile access for local businesses and baseline data exports.

What level of Search Console access do SEOs need?

Full user is usually enough for analysis. Owner is needed for some settings like change of address.

How long should SEO onboarding take?

One to two weeks when access is prepared in advance. Blockers usually come from permissions and definitions.

Why export Search Console data at the start?

Search Console keeps 16 months of data. Exporting early preserves the baseline for later comparisons.

Jourdan Rombough

Built by Jourdan Rombough, technical SEO and GEO consultant with 15+ years in search. About Jourdan or get an SEO plan.

More on digital marketing in our blog

See all posts