Insight

White-Label SEO Client Onboarding Checklist: The First 30 Days

Plan the first 30 days of white-label SEO with a client intake checklist, scoped access, clear approvals and weekly deliverables.

A checklist clipboard and a folder represent handing an SEO engagement to the delivery team.

After the client signs, the agency should turn the scope into a delivery brief, verify access through named accounts and agree who can approve changes. By day 30, aim to hand the client a dated baseline, a prioritised backlog, evidence of completed work and a short list of decisions for the next month.

The agency account lead owns client communication. The white-label delivery lead owns the evidence, recommendations and quality checks. The client keeps control of its accounts and names who can approve content and production changes.

What information should the agency collect after the client signs?

Collect the signed scope, business priorities, site history, measurement definitions and named decision-makers. Ask the account lead to verify that the partner's brief matches the agreement before work starts.

Copyable intake checklist

  • Scope and boundaries. List the domains, priority markets, deliverables, exclusions and dates. Confirm whether the partner advises, drafts or implements. Record any launch or trading dates that constrain releases.

  • Business context. Ask which products or services matter most, who buys them, which outcomes count and where the client can fulfil demand. A UK-wide website may still have a tightly defined service area.

  • Site and campaign history. Collect recent migration and redesign dates, previous audit findings, open developer tickets, known tracking changes and existing content plans. Flag work already promised to another team.

  • Measurement. Agree what counts as a qualified enquiry, booking or sale, who checks that definition and which system records it. Ask for agreed, appropriately scoped reports if the partner needs CRM context.

  • People and approvals. Record the agency account lead, partner delivery lead, client decision-maker, publishing owner and backup approver. Agree where decisions are logged and who handles urgent issues.

  • Content and permissions. Collect brand guidance, approved claims, examples, source requirements and access owners. Record what the partner is authorised to see and what it may share back to the agency.

Use a single brief the account lead can confirm with the client. If keyword research is in scope, give the partner the agreed buyer questions and markets before it maps pages. If the contract includes content production, agree who validates product claims and signs off the brief.

Which Search Console, analytics and CMS permissions does delivery need?

Start with named, task-specific accounts on the correct property or environment. Verify each invitation by having the recipient open the agreed report or complete a permitted staging task.

  • Search Console. Keep an active verified owner with the client. Start with Restricted user access if it covers the reports needed. Request Full user only for a documented task that requires its wider rights. Google lists each role's capabilities in its Search Console permissions guide.

  • GA4. Assign Viewer on the relevant property for standard reporting. Consider Analyst if the partner needs to create or collaborate on explorations. Check inherited access and any cost or revenue restrictions with the property owner. The GA4 role and data restriction reference lists the distinctions.

  • CMS. Give the delivery team a drafting route on staging where possible. In standard WordPress, a Contributor can work on their own posts without publishing. An Editor can publish and manage other users' posts. If the task needs media uploads, custom fields or another capability, have the site owner verify a scoped role or assign that step to the publishing team. See the WordPress roles reference.

Two keycards and closed drawers illustrate scoped access for an SEO engagement.

Keep an access register with the system, property, named account, role, purpose, grantor and review or expiry date. Review it on role changes and at offboarding. Remove the account or downgrade its role, revoke project-specific credentials or tokens as appropriate, and record who verified the change. If a departing user had verified Search Console ownership, check for their unused verification tokens with the client owner. Leave the client's verified access intact.

How should agencies divide client communication, approvals and delivery?

The agency account lead runs client meetings and owns scope decisions. The delivery partner prepares the analysis, briefs, implementation notes and QA evidence. The client approver authorises business claims or production changes within the agreed scope. A named publisher or developer releases approved changes.

Agree when the partner can join a call and how the agency will present its role under the agreed terms. Give the partner one route for questions and blockers. Explain how an out-of-scope request moves from estimate to approval before anyone changes the site. Store the final decision on the ticket alongside the version approved.

Hypothetical change ticket

A partner proposes a revised title for a UK service page. The ticket holds the live URL, existing and proposed text, the reason, the approver and a rollback value. The account lead confirms that the new wording reflects the service area. The named publisher applies the approved version. Delivery checks the live title and records the result and date. If the service area is disputed, the ticket stays open for a decision.

What should be in the first month’s SEO baseline and backlog?

The baseline should record the site's starting point with dated, reproducible evidence. The backlog should turn that evidence into actions with an owner, priority, dependency and acceptance check.

Save the property, data range and filters for each export. A starting window could be the latest complete 28 days, with a prior or year-on-year comparison where data and seasonality make that useful. Capture Search Console clicks and impressions for priority landing pages, organic sessions and agreed key events from GA4, plus indexability and canonical checks for a sample of important URLs. Record tracking gaps, changes in consent or tagging, and unusual events such as a migration. If key-event data is unreliable, show the limitation and assign a measurement check.

Write tickets users can verify. If a priority service URL points its canonical at an unrelated page, ask the technical lead to confirm the intended canonical before promoting the fix. Record affected URLs, evidence, who approves the change, the release owner and how to confirm the live result. If AI search visibility is in scope, record its sample and settings separately so the first review can distinguish the evidence by source.

WeekLead ownerOutput and acceptance check
Week 1Agency account leadConfirm scope and approvers. Test access to the agreed properties and assign a date and owner to any missing access.
Week 2Delivery leadArchive a dated baseline and evidence for priority issues. Ask the account lead to confirm measurement definitions and limits.
Week 3Delivery lead and named publisherAgree the first backlog items. Release only approved work and attach live QA or a named dependency to each ticket.
Week 4Agency account leadPresent the baseline, completed changes and open decisions. Agree the next backlog and access changes with named owners.
Four calendar tiles illustrate the four weekly milestones in the onboarding plan.

What should the first client review cover?

Review the agreed deliverables, what shipped, what remains blocked and which decisions the client needs to make next. Show one baseline example and one completed ticket with live QA. List the dependencies and target dates for anything still open.

Close by confirming the next priorities and the people who own approvals. Treat day 30 as a deliverables milestone. Use any early search or conversion movement as context alongside data quality and known changes. Confirm which temporary permissions can be removed and when the remaining roles will be reviewed.

When bringing in a partner, agree the intake, boundaries and approval flow before the first kickoff. See Nozentra's agency partnership.

Keep reading
6 min read

White-Label SEO Pricing for UK Agencies: How to Compare Quotes

Compare wholesale SEO quotes in GBP, account for setup and agency hours, and calculate gross margin and markup with a worked three-month example.

SEOAgency Partnerships
Read article
5 min read

AI Visibility Audit Checklist: What an Agency Should Deliver

Review an AI visibility audit with a checklist for prompt selection, citation accuracy, crawler eligibility and a prioritised action plan.

AI SearchSEOAgency Partnerships
Read article
5 min read

How to Choose a White-Label SEO Partner for Your Agency

Compare white-label SEO partners with an agency vendor scorecard and a paid pilot that tests evidence, quality control, client boundaries and handover.

SEOAgency PartnershipsWhite-Label SEO
Read article