Key takeaways
- Onboarding runs from the signed contract to the first change you make on the site, and most of its value is in things you cannot go back for later
- Ask for Search Console and GA4 access at the lowest level that does the job, with a named login for every person, never a shared password
- The questionnaire only needs the questions whose answers change the work: what earns money, what is off limits, who deploys, and what happened to the site before you arrived
- Save the baseline before your first change: a crawl with its settings written down, a Search Console export summed by date, and the indexing counts, because none of them can be rebuilt afterwards
An SEO client onboarding checklist covers everything between the signed contract and the first change you make to the client's site: the access you ask for, the questions you need answered, the kickoff call and the baseline measurements. Most onboarding guides treat this as admin. The part that matters most is the last one. The site as it was on the day you started can only be measured on that day, and every report you send for the rest of the engagement is compared against it.
This checklist is in the order we would run it for an agency taking on a new SEO retainer. Each section explains why an item is there, so you can cut the ones that do not apply to a given client.
The SEO client onboarding checklist, in order
- Send the welcome email with the access list and the questionnaire attached, and a date for the kickoff call.
- Request access: Search Console, GA4, CMS, staging, Bing Webmaster Tools, and Google Business Profile for local clients. Ask who controls hosting and DNS.
- Collect the questionnaire answers before the kickoff, so the call is spent on the answers that need discussion.
- Run the kickoff call to agree goals, the pages that earn money, how changes ship and what you report on.
- Save the baseline before anyone changes anything: a crawl, a Search Console export and the indexing counts.
- Set the reporting rhythm: crawl date, report date and the metrics the report will carry.
- Ship the first fix and record it against the baseline.
Steps 2 and 3 run in parallel. Step 5 cannot start until step 2 is done, which is why access requests go out on day one.
Access to request, and at what level
Ask for every account in a named login for each person who needs it. A shared password breaks the day someone leaves either team, and the client has no record of who did what.
| Platform | Ask for | Why that level |
|---|---|---|
| Google Search Console | Full user on the Domain property | Full users can submit sitemaps and request indexing. Restricted is enough if you only report. Owner is not needed, and an owner can add you in a minute (Google's permission levels). |
| Google Analytics 4 | Viewer, or Editor if you will fix tracking | Viewer reads every report. Only ask for Editor if key events or conversions need setting up (GA4 roles). |
| CMS (WordPress, Shopify and so on) | An editor or admin account in your name | You will change titles, meta descriptions, redirects and internal links. Plugin installs need admin. |
| Staging site | The URL and its login | You want to check changes before they go live. Staging usually sits behind a login or HTTP authentication, so a crawler needs the credentials too (crawling a staging site behind a login). |
| Hosting and DNS | A name, not credentials | Redirect rules, security headers, robots.txt served by the server and domain changes often live here. You need to know who to ask and how long they take. |
| Bing Webmaster Tools | Read-only, or Read-write to submit URLs | Its crawl and index data comes from a second search engine, and it can import a Search Console verification in a few clicks. |
| Google Business Profile | Manager (local clients only) | Local rankings depend on it as much as on the site. |
Also ask for anything the previous agency left behind: past reports, a redirect map from the last migration, and a disavow file if one was ever submitted. A disavow file you do not know about can explain a link profile that looks wrong.
The onboarding questionnaire: only the questions that change the work
Long questionnaires get half-answered. Ask the questions whose answers change what you do, and leave the rest for the kickoff call.
- Which pages earn the money? A product range, a booking page, the contact form. This decides what gets fixed first more than any severity label will.
- What happened to the site in the last two years? Redesigns, platform moves, domain changes, a drop in traffic someone remembers. A migration explains most sudden changes in a Search Console chart.
- Is anything planned in the next six months? A redesign announced in month three can undo the first quarter's work.
- What is off limits? Legal pages, brand wording, a section another team owns. Find out before you send a fix list that touches them.
- How does a change reach the live site, and how long does it take? If every title change needs a developer ticket and a two-week release cycle, the plan has to fit that.
- Are any pages hidden from search on purpose? Internal pages, a members area, campaign landing pages set to noindex. A crawler flags all of them, and you want to know which flags are intentional before you report them.
- Which other domains belong to this client? A microsite, a country domain or a blog on a subdomain changes the scope of the crawl.
- Who are the competitors they lose deals to? That list is often different from the one you would find by searching for their keywords.
The kickoff call agenda
An hour is enough when the questionnaire came back first.
- Introductions and roles (5 minutes). Who on each side approves changes, who makes them, and who reads the report.
- Goals (15 minutes). Turn "more traffic" into something you can report: enquiries from organic search, rankings for a named set of queries, or visibility for a product range.
- The questionnaire answers that need discussion (15 minutes). Usually the off-limits list and the deploy process.
- How changes ship (10 minutes). Who has access, what needs sign-off, and how long a typical change takes.
- Reporting (10 minutes). What the monthly report contains, when it arrives and who receives it.
- Next steps (5 minutes). Outstanding access, the baseline date and the date of the first audit review.
Do not present findings at the kickoff. Without the baseline crawl you are working from a quick look, and a client remembers the first numbers they hear.
Capture the baseline before you change anything
The baseline is the one onboarding job with a deadline you cannot move. Once the first fix ships, the "before" state is gone, and so is the evidence that your work changed anything.
Save three things.
A full crawl, with its settings written down. Page limit, JavaScript rendering, user agent and any include or exclude rules all change what a crawl finds. A crawl next month with different settings is not comparable to this one, so record the settings with the run and repeat them. In Crawl Cove the run keeps its settings, and every later run says whether it was crawled the same way or which settings differ. The first client setup is a domain and a Start button, so the baseline crawl can run the same day access arrives.
A Search Console performance export. Search Console keeps 16 months of performance data, so anything older than that is already gone and the oldest month you can see disappears a little more each day. Export clicks and impressions by date and by page now. Take totals from the date view: the query view leaves out anonymised queries, and on a small site that can be most of them. When we pulled our own crawlcove.com data by query in August 2026 it showed 0 clicks over 87 days. The same period pulled by date showed 19.
The indexing counts. Note how many pages Search Console reports as indexed and not indexed, with the reasons, on the baseline date. The Page indexing report only charts a few months of history, so a screenshot or a note is the only long-term record you will have.
If the client already has analytics, export organic sessions and conversions by landing page for the same period. Search Console data runs about two days behind, so date the export and leave it at that.
The first 30 days
- Week 1: access confirmed, questionnaire answered, kickoff held.
- Week 2: baseline crawl and exports saved, findings reviewed against the pages that earn money.
- Week 3: a prioritised fix list agreed with the client, in the format of an SEO audit report: summary, ranked issues, fix steps and how each fix will be verified.
- Week 4: the first fixes shipped and a re-crawl date set, so the first monthly report can show what changed against the baseline.
From then on, crawl on the same day each cycle so each month's comparison is like for like. Tracking issues per client over time covers keeping that record without a spreadsheet, and presenting an SEO audit to a client covers the first review meeting.
Common onboarding mistakes
- Fixing before measuring. The quick wins in week one are the easiest ones to prove, and the first to go unproven without a baseline.
- Reporting intentional settings as errors. A noindex on a members area is a decision. Ask before you report it as a problem.
- Accepting a shared login. It works until someone changes the password, and then nobody knows who changed what.
- Promising timelines before you know the deploy process. A plan built on weekly changes fails on a site that releases monthly.
- Using a different crawl setup each month. Raising the page limit in month two makes the site look worse, because the crawler found more pages.
Copy this checklist
SEO client onboarding checklist
Access
[ ] Search Console: Full user on the Domain property
[ ] GA4: Viewer (Editor if tracking needs fixing)
[ ] CMS: named editor or admin login
[ ] Staging: URL and login
[ ] Bing Webmaster Tools: read-only or read-write
[ ] Google Business Profile: Manager (local only)
[ ] Name of whoever controls hosting and DNS
[ ] Previous agency reports, redirect maps, disavow file
Questionnaire
[ ] Pages that earn money
[ ] Site history: migrations, redesigns, traffic drops
[ ] Changes planned in the next six months
[ ] Off-limits pages and wording
[ ] How changes are deployed, and how long they take
[ ] Pages hidden from search on purpose
[ ] Other domains in scope
[ ] Competitors they lose deals to
Kickoff
[ ] Roles, goals, deploy process, reporting rhythm agreed
Baseline (before any change)
[ ] Full crawl saved, settings recorded
[ ] Search Console export by date and by page
[ ] Indexed and not-indexed counts, with reasons
[ ] Organic sessions and conversions by landing page
First 30 days
[ ] Prioritised fix list agreed
[ ] First fixes shipped
[ ] Re-crawl date set with the same settings
Crawl Cove is built for this workflow when you have more than one client: each client gets its own workspace, crawl history and reports. See how it works for agencies, or start a 14-day trial with no card required and crawl your next client's baseline with it.
Frequently asked questions
- How long should SEO client onboarding take?
- Plan on one to three weeks from signature. Access requests are usually the slow part, because they wait on whoever at the client owns each account. The baseline crawl and the Search Console export take an afternoon once access is in place, so do them as soon as it arrives rather than at the end.
- What access do I need from a new SEO client?
- Search Console (Full user if you will submit sitemaps or ask for reindexing, Restricted if you only report), GA4 (Viewer for reporting, Editor only if you will fix tracking), a named CMS login, a staging URL and its login if one exists, and the name of whoever controls hosting and DNS. Local clients add Google Business Profile, and Bing Webmaster Tools is worth asking for alongside Search Console.
- Should I audit the site before or after onboarding?
- Both, for different reasons. A light audit before the pitch decides the scope. The baseline crawl during onboarding is the measurement every later report is compared against, so it has to be run with settings you will repeat, after access is in place and before anything changes.
- What should a kickoff call cover?
- Goals and the pages that earn money, how changes reach the live site, what is off limits, the reporting rhythm, and who answers questions on each side. Leave strategy for the first audit review; a kickoff that tries to present findings before the baseline exists ends up guessing.
- What is the most common onboarding mistake?
- Changing something before the baseline is saved. The first fix you ship is usually the easiest win of the whole engagement, and without a "before" measurement you cannot show it happened.