SEO Onboarding Checklist

My onboarding checklist has nine items, not fifty. The first block is access. You need admin-level access to Google Search Console, GA4, the CMS, and if the client is local, Google Business Profile. Without these you cannot verify crawling, indexing, or traffic sources. I once waited three weeks for a client to hand over Search Console access because the previous agency had set up the property under their own email. That lost us a full reporting cycle.

Once access is confirmed, collect baseline data. I pull organic sessions, keyword rankings for the top 20 terms, and conversion rates for the last three full months. On a recent client in the [SEO](/seo/) space, that baseline showed 70% of traffic came from four blog posts, which changed our priority from technical fixes to content consolidation immediately.

Then I run a quick technical audit. I check crawlability with a [Google Search](/google-search/) crawl report, look at server logs for wasted crawl budget, and review redirect chains. A common find: 301 chains that add 500ms to page load. I prioritise issues that block indexing over those that affect user experience because unindexable pages earn nothing.

Stakeholder alignment is next. I schedule a kickoff call with the marketing lead, the developer, and the decision-maker. On that call I confirm business goals — not "increase traffic" but "grow organic revenue from product pages by 20% in six months" — and assign ownership for each KPI. I also set communication rules: weekly Slack check-ins, monthly reporting, no emergency requests outside that cadence unless the site is down.

Finally, I build a 30-60-90 day roadmap. The first 30 days cover access, baseline, and quick technical wins. The next 60 focus on content gaps and internal link optimisation. The final 30 measure results against the baseline and adjust. This structure is straight out of [SEO best practices](/seo-best-practices/) but adapted to each client's maturity. If the site is new, the first 30 days shift entirely to on-page fundamentals.

Onboarding is done when you have three things: confirmed access, a baseline you trust, and a roadmap the client has signed off. Many practitioners keep onboarding open, adding items like "complete full content audit" or "fix all 404s." That is a mistake. Onboarding is not an audit. Audit work belongs in the execution phase, under the roadmap.

Here is the decision rule: if the task requires more than two hours of analysis or implementation, it does not belong in onboarding. For example, a full index coverage report takes 30 minutes. Adding that to the checklist is fine. Rewriting the homepage is not. I draw this line because I have seen teams spend six weeks on "onboarding" — by which point the client has lost trust in the process.

What about edge cases? If the client is migrating domains, onboarding must include a redirect mapping test. That can take a day. I include it anyway because if the redirects fail, the baseline is meaningless. But I flag it as a one-off and adjust the roadmap to start after the migration validation.

Another stopping point: when you have identified the three highest-impact issues and either fixed them or scheduled them. Do not exhaust the full checklist if the client is paying you to grow traffic, not list problems. I once kept a client in onboarding for four weeks because I insisted on completing the [Semantic SEO](/semantic-seo/) audit before any content work. We missed a seasonal window. Now I stop as soon as the roadmap is live and the client can see the next action.

The counter-argument is that onboarding should be thorough to prevent scope creep. I agree, but thorough does not mean infinite. A 90-day roadmap is the best scope document you have. Once it is approved, onboarding is complete.

I used to start audits before confirming access. I would run a full crawl, pull a backlink profile, and analyse keyword gaps — all while waiting for the client to grant Search Console admin rights. On one account I spent 12 hours on a technical audit only to discover I could not see the actual index status because the property was verified under a different email. That report was worthless. Now I freeze all work until access is confirmed. No access, no analysis.

I also gave vague goals. "Increase organic traffic" sounds good in a kickoff call but leads to disagreements later. The client expected a 50% lift in three months; I planned for a 15% lift. We had no baseline to argue from. Now I tie every goal to a specific metric and a time frame: "increase organic traffic from product pages by 20% within six months" with a baseline number.

Overloading the intake form was another mistake. My first version had 45 questions covering everything from target persona to preferred meta description format. Clients completed it under duress, and I rarely used half the answers. I cut it to seven core questions: current traffic, top three competitors, primary KPI, budget, timeline, past SEO work, and biggest pain point. This takes 10 minutes to fill and gives me enough to build the roadmap.

Finally, I skipped stakeholder alignment on small engagements. I assumed the marketing manager had authority to approve the roadmap. When the CEO later rejected the content focus, we lost two weeks. Now I insist on a kickoff call with the decision-maker, even if it delays the start by a few days. [Learn SEO](/learn-seo/) from that mistake: alignment upfront saves rework later.

One more thing: I used to treat checklists as gospel. If a client said "we already have GA4 access," I still listed it as unchecked. That wasted time on verification. Now I trust the client's confirmation for low-risk items and only verify high-risk ones like Search Console ownership.