SEO Client Onboarding Checklist: The First 30 Days

The first 30 days of an SEO engagement set the tone for everything after. A slow, disorganised start costs weeks of results and plants doubt in the client's mind. A structured one gives the team everything it needs, records a fair baseline, and shows early progress.

This checklist runs day by day through the first month. It is written for agencies, but it works equally well for in-house teams starting with a new site.

Before kickoff

Prepare so the first meeting is productive.

• Send the access request list and the onboarding questionnaire with the contract.
• Create the client's vault in the password manager and its project in the task system.
• Run a quick external check: is the site indexed, does robots.txt block anything obvious, does it rank for its own brand name.
• Run a handful of AI prompts about the client's category to see whether it appears.

Week 1: Access and goals

Days 1–2: Kickoff meeting

Agree the essentials in writing.

• Business goals. Revenue, leads, bookings or sign-ups, and their rough current numbers.
• Priority products or services. What the client most wants to sell, and where margins are highest.
• Target customers and locations.
• Main competitors, including the ones the client loses deals to.
• Constraints. Legal review, brand guidelines, development resources, content approval.
• Who approves changes, and how quickly.
• Reporting cadence and format.

Days 2–5: Access

Request delegated access wherever possible, rather than shared logins.

• Confirm each access works on the day it is granted.
• Record everything in the client vault.

Week 2: Tracking and baselines

Days 6–8: Check tracking

Nothing can be measured if tracking is broken.

• Analytics records conversions correctly: form submissions, purchases, calls and bookings, tested end to end.
• Search Console is verified at the domain level and the sitemap is submitted.
• AI assistant traffic has its own channel in analytics. See how to track ChatGPT traffic in GA4.
• Cross-domain and subdomain tracking works where relevant.
• CRM connection, where available, links leads to landing pages.

Days 8–12: Record baselines

Record the starting point for every metric you will report.

• Traffic and conversions by channel for the last 12 months, plus the same period a year earlier.
• Search Console clicks, impressions and CTR for priority query groups.
• Rankings for a tracked keyword set grouped by topic.
• AI visibility: a prompt set of 30 to 60 questions run across the main engines, with mentions and citations for the client and competitors. See AI share of voice.
• Search Console generative AI report: impressions in AI Overviews and AI Mode.
• Technical health: a full crawl and audit. See our technical SEO audit checklist.

Store the baseline in a dated snapshot. It is the most useful document of the whole engagement.

Week 3: Critical fixes and quick wins

Days 13–16: Fix what is broken

Start with anything that caps every other result.

• Important pages or sections that are noindexed or blocked.
• AI search crawlers blocked in robots.txt or by bot protection. See AI crawler user agents.
• Key content missing from the server-rendered HTML.
• Server errors and broken templates.
• Redirect chains or broken redirects on important URLs.

Every change should go through the agreed approval process and be logged.

Days 16–20: Quick wins

Low effort, visible impact.

• Rewrite weak title tags and meta descriptions on pages that already rank on page one or two.
• Fix internal links pointing to redirects or 404s from important pages.
• Add internal links to priority pages from high-traffic pages.
• Rewrite the opening of two or three priority pages answer-first. See answer-first content.
• Align the brand's canonical facts on the about page and main profiles. See entity SEO for LLMs.

Week 4: Plan and first report

Days 21–26: Build the 90-day plan

Turn the audit and baseline into a prioritised plan.

• Score all issues by impact, urgency and effort.
• Map content gaps against the client's prompt set and priority keywords.
• Plan monthly priorities for the next quarter.
• Agree goals that combine outcomes and visibility, not traffic alone. See proving SEO value when clicks fall.

Days 27–30: First report and review

• Deliver the first report using the standard structure. See our SEO client report template.
• Present the baseline, what was fixed, early signs of impact and the 90-day plan.
• Confirm the reporting cadence and the next review date.

The onboarding questionnaire

Send these questions before kickoff and use the answers to prepare.

1. What are your business goals for the next 12 months?
2. Which products or services matter most, and why?
3. Who are your best customers, and where are they?
4. Who do you compete with, and who do you lose to?
5. What has worked or failed in SEO before?
6. Have there been migrations, redesigns or penalties in the past?
7. Who needs to approve website changes, and how long does it take?
8. What do you want to see in reports?
9. Are there legal, regulatory or brand constraints on content?
10. How do customers currently find you, in their own words?

Adapting onboarding by client type

The 30-day sequence stays the same, but the emphasis shifts.

Local businesses. Put Google Business Profile access, review volume and consistency of name, address and phone details near the top of week one. Local AI answers lean heavily on business profiles and reviews, so include "near me" and city-specific prompts in the AI baseline.

E-commerce. Add product feed and merchant centre access to the access list, and record baselines for category and product page traffic separately. Check early whether product details and prices are in the raw HTML, since themes and apps often inject them with JavaScript.

B2B and SaaS. Connect analytics to the CRM during week two so leads can be traced to landing pages and pipeline. Weight the prompt set towards comparison and "alternatives to" questions, which carry the most buying intent.

Multi-location and franchise brands. Agree early who controls each location's pages and profiles. Inconsistent location data is the most common entity problem for these clients and one of the quickest to fix.

Clients coming out of a failed migration or penalty. Record the baseline from before the problem as well as today, so recovery can be shown, and spend week three on the specific cause before quick wins elsewhere.

Setting expectations

Onboarding is the right moment to set realistic expectations:

• Critical technical fixes can show effects within weeks.
• Content and authority work usually takes three to six months to show clearly.
• AI visibility on live-retrieval engines can move faster; unprompted brand mentions take longer.
• Informational traffic may decline as AI answers expand, even when the work is going well.

Writing these down in the kickoff notes saves difficult conversations later.

A worked example

For a fictional regional law firm, onboarding found that the firm's practice-area pages loaded their content through a JavaScript widget, so AI crawlers saw almost nothing, and that a security plugin returned 403 errors to PerplexityBot. Both were fixed in week three. By the first report, the firm was being cited by Perplexity for two of its practice areas for the first time, and two rewritten practice pages had moved from page two to page one. Small, early, visible progress like this builds the trust that the slower work depends on.

Common onboarding mistakes

• Starting work before recording baselines. Progress can never be shown fairly.
• Shared logins instead of delegated access.
• Broken conversion tracking left unfixed. Every later report is undermined.
• No agreed approver. Changes stall for weeks.
• Promising traffic growth without checking how AI answers affect the client's queries.

How Rankwyn helps

Rankwyn connects a new client site in minutes, runs the baseline audit and AI visibility snapshot automatically, and puts the first fixes into an approval queue, so the onboarding checklist above takes days instead of weeks. See the multi-site control plane.

Key takeaways

• Run onboarding in four weekly phases: access and goals, tracking and baselines, fixes and quick wins, plan and first report.
• Request delegated access with a standard list, and confirm each access works on the day it is granted.
• Fix tracking before recording baselines, and include AI visibility in the baseline.
• Fix anything that caps results first, then ship visible quick wins.
• Set realistic expectations in writing at kickoff, including the effect of AI answers on informational traffic.

The bottom line

A strong onboarding gives the team access, a trustworthy baseline and a clear plan, and gives the client early proof that the engagement is working. Follow the same 30-day sequence for every client, record the baseline before you change anything, fix the blockers first, and end the month with a plan the client has agreed to.