SEO Onboarding Checklist for New Clients and Projects

An SEO onboarding checklist should leave a new project with clear goals, working account access, a trustworthy baseline and a named person who can approve changes. Collecting a questionnaire is only the start. The test is simple: can your team explain what happens next without chasing another password or reopening the sales conversation?

This guide is for businesses and individuals starting with an SEO agency, consultant or new internal team. Use the copyable checklist below during kickoff, then keep the access register and decision log with your project files. The suggested timing is a planning example, not a promise about how quickly search results will improve.

SEO onboarding checklist: the kickoff handoff

Copy this table into your project workspace. Replace each role with a real name and give every unfinished item a due date. Mark something complete only when the evidence in the last column exists.

Keep blocked items visible. An invitation that nobody has accepted is not working access. A traffic export without a date range is not a usable baseline. Keep that evidence beside the checklist after the kickoff call.

1. Agree on the commercial goal before opening tools

Start with the business model. Ask which services or products the business can actually deliver, which customers are a good fit, and whether there are capacity limits. A campaign that attracts enquiries for an unavailable service creates work without helping the business.

Choose one primary outcome for the initial plan. For a service business, that might be qualified consultation requests rather than every form submission. For a shop, it might be completed purchases, with cancellations and refunds considered separately. Record who owns the outcome definition and where the final numbers come from.

Next, write down what the engagement includes. Separate technical recommendations from implementation, content briefs from finished copy, and reporting from analytics repairs. Name the person who approves website changes and the developer who can ship them. If nobody has implementation time, put that constraint in the plan before assigning a long list of fixes.

Ask this at kickoff: "What would make this project useful even if search traffic takes longer than hoped?" The answer often exposes a practical first priority, such as fixing an enquiry path or getting reliable reporting in place. Do not turn that conversation into a guaranteed ranking target. Google's advice on hiring an SEO explicitly warns against guarantees of first place in search results.

2. Request access with a reason for each permission

Use a shared access register, not a chat thread full of credentials. Record the platform, account or property identifier, business owner, invited email address, assigned role, purpose and removal date. Have the business invite named accounts through each platform's user controls rather than sharing a person's login.

For an initial SEO audit, Google's hiring guidance says to grant read access to Search Console and not write access at that stage. Its Search Console permissions documentation distinguishes owners, full users and restricted users: a full user can take some actions, while a restricted user has simple view rights on most data. Do not assume that "full" means view-only.

Keep ownership with the business and agree any later permission increase against a specific task. If the SEO team needs to submit something or change a setting, document that request separately. Someone should be able to explain why the extra access is needed.

For Google Analytics, identify the correct property before sending invitations. Google's Analytics access documentation says the Viewer role can see settings and data and work with reporting views and explorations. Choose the role against the actual task. Reading reports alone is not a reason to request administrator access.

• Test each invitation using the actual account that will do the work.
• Record the Search Console property and Analytics property ID so similar account names do not cause confusion.
• Separate CMS editing from plugin installation, DNS changes and production releases.
• Use the business's approved password manager for any secrets that cannot be handled through invitations.
• Document who removes access when a person leaves or the engagement ends.

3. Collect the history that changes the plan

Request previous SEO reports, completed audits and a list of changes already made. Ask about domain moves, redesigns, deleted pages, agency handovers and tracking changes. Save dates where possible. A sharp change in a chart needs context before anyone calls it a new SEO problem.

Collect the practical constraints too: content approval steps, regulated claims, seasonal demand, development freezes and services the business no longer offers. Ask which pages the sales team shares with prospects and which questions customers repeat. These inputs are discovery material, not proof that a particular keyword has demand.

A short intake questionnaire can cover the essentials:

1. Which offers and audiences are in scope?
2. What makes an enquiry qualified, and who checks that?
3. Which website or tracking changes happened recently?
4. Who owns the website, analytics and search accounts?
5. Who can approve copy and release technical changes?
6. What must remain unchanged, and why?

Review the answers in a call. If the contract says one market and the questionnaire lists five, resolve the mismatch before research expands to all five.

4. Save a baseline you can compare later

Create a dated baseline folder before implementation starts. Include the reports that will support the agreed outcome, plus notes about gaps in the data. Save the exact reporting dates, filters, property identifiers and time zone alongside each export.

Google's Search Console getting-started guide describes the tool as a source of information about how Google crawls, indexes and serves a website. Use its indexing and performance information to understand the starting point. Do not treat every excluded URL as a defect; first decide whether that URL is supposed to appear in search.

Keep search clicks, analytics sessions and business outcomes as distinct measures. Write down what each report counts rather than expecting separate systems to agree exactly. If the lead definition changed last month, label the break in the baseline instead of presenting a clean but misleading trend.

For a small project, the starting packet might include Search Console performance exports, a list of priority landing pages, analytics acquisition reports and a business-approved conversion definition. It does not need dozens of charts. It needs enough context that another person can repeat the comparison later.

Before relying on enquiry reporting, test the important user paths with the analytics owner. Record what fired, where the event appeared and what remains uncertain. Our GA4 audit checklist provides a separate measurement review; onboarding should identify that work rather than silently assume it is complete.

5. Turn discovery into an approved first work plan

Keep the initial review separate from a full technical audit. During onboarding, identify immediate blockers and agree how deeper work will be scoped. A newly discovered issue is not automatic permission to change production.

Give each proposed task a plain-language reason, affected pages, owner and acceptance check. Add dependencies and an effort estimate where the team can make one responsibly. For example: "Developer checks the priority service page's indexing settings; SEO lead confirms the intended page state; client approves any change before release." That is more actionable than "fix indexing."

Use the technical SEO audit checklist when the engagement moves into diagnosis. This onboarding list has a different purpose: getting the right people and evidence ready to act on the findings.

Agree a reporting rhythm that fits implementation capacity. A weekly working update can list completed work, blocked decisions and the next release. A less frequent outcome review can examine the agreed business measures. The cadence is a project choice, not a Google requirement.

SEO onboarding checklist: a sample first-week schedule

This sequence is an example for a modest website with available decision makers. Larger sites, ownership disputes or missing historical data may need a longer handoff. Move the dates; keep the dependencies.

• Before kickoff: confirm the contract, send the intake questionnaire and identify account owners.
• Kickoff day: agree the outcome definition, scope, decision maker and communication channel.
• Next working sessions: accept and test invitations, collect past work and record missing access.
• After access works: export the baseline and inspect measurement gaps with the relevant owner.
• End of the initial handoff: approve the first work plan and record unresolved dependencies.

Do not squeeze a missing dependency into a false completion tick. If Search Console access is still pending, assign an owner and a next check date. The team can draft interview questions or review supplied content while waiting, but the search baseline remains incomplete.

When is SEO onboarding actually complete?

Use a short signoff note: "We have confirmed scope, tested the access needed for the agreed tasks, saved a dated baseline, recorded measurement gaps and approved the first work plan." Attach the access register and link to the decision log. List exceptions underneath, with owners and dates.

That note should also explain what has not happened. Onboarding completion does not mean an audit is finished, a website has been fixed or rankings will rise. It means the project can begin with fewer unanswered operational questions.

For an agency change, ask the business owner to review outgoing access separately. Keep historical reports and agreed deliverables before closing accounts, then confirm who owns ongoing subscriptions. The handoff ends when the business knows where its records are and who can act on its behalf.