SEO Client Onboarding Form Template
Send this after the SEO contract is signed, not before. It collects the things the first month actually depends on — every subdomain and country domain in scope, how you will be invited to analytics and Search Console, what the client counts as a conversion, what the last agency left behind, and who is allowed to ship a technical change. Access is granted by invitation; no field asks for a login.
Last updated
Fields in this template
- Client or Company Namerequired
- Primary Contact Namerequired
- Primary Contact Emailrequired
- Primary Domainrequired
- Additional Domains and Subdomains in Scope
- Domains or Sections Explicitly Out of Scope
- How Will Analytics Access Be Granted?required
Invite our named email as a user on the existing GA4 property · Grant our named email admin on the analytics account · You will run the reports and share them with us · No analytics installed yet — we will set it up · Not decided yet
- Email Address to Invite for Analytics and Search Consolerequired
- How Will Search Console Access Be Granted?required
Invite our email as a full user on the existing property · Invite our email as a restricted user · Add us as an owner via domain verification · No Search Console property exists yet · Not decided yet
- Who Controls the Domain’s DNS?required
- Other Tools We Should Be Added To
Google Tag Manager · Bing Webmaster Tools · Google Business Profile · Looker Studio · Ahrefs · Semrush · A CDN or WAF dashboard (Cloudflare or similar) · The CMS itself · Call-tracking or CRM reporting · None of these
- Target Countries or Marketsrequired
- Languages the Site Servesrequired
- What Counts as a Conversion?required
- Is Conversion Tracking Already Working?required
Yes, and we trust the numbers · Yes, but we do not trust the numbers · Partly — some conversions are tracked · No · Not sure
- Approximate Value of One Conversion
- Has Anyone Worked on SEO for This Site Before?required
Yes — an agency or consultant · Yes — in-house · Both · No
- What Was Done, and What Is Still Live?
- Has the Site Ever Had a Manual Action or Suspected Penalty?required
Yes, and it was resolved · Yes, and it is unresolved · Suspected but never confirmed · No · Not sure
- Details of Any Manual Action, Traffic Drop or Suspected Penalty
- Has the Site Been Migrated or Replatformed?required
Yes, in the last 12 months · Yes, more than 12 months ago · A migration is planned · No · Not sure
- Migration Details
- CMS or Platformrequired
WordPress · Shopify · Webflow · Squarespace · Wix · Drupal · Magento / Adobe Commerce · HubSpot CMS · Headless CMS with a custom front end · Custom-built (Laravel, Rails, Next.js…) · Other · Not sure
- Other Platform
- Who Can Deploy Technical Changes?required
Our agency, directly in the CMS · The client’s in-house developers · A third-party development agency · The client’s IT team via a ticket queue · Nobody identified yet
- Typical Turnaround for a Technical Changerequired
Same day · Within a week · Within a sprint (2–3 weeks) · Monthly release train · Longer or unpredictable
- Is There a Staging Environment We Can Test On?required
Yes · No · Not sure
- Is There an Existing Content Calendar?required
Yes — and we will share it · Yes, but it is informal · No · Not sure
- Content Calendar Link
- Who Approves and Publishes Content?required
- May We Edit Existing Pages, or Only Add New Ones?required
Edit anything · Edit anything except the homepage and product pages · Propose edits; you apply them · New pages only · Not decided yet
- Top Competitors in Searchrequired
- Anything Else We Should Know?
Who uses this template
About this template
An SEO client onboarding form is what you send after the contract, once the audit request that won the work has done its job. The audit request existed to qualify a lead: one website URL, a goal, a budget band. This form exists to start delivery, and the difference shows in the first section — an SEO engagement is almost never scoped to a single URL. Subdomains, country domains, a blog on a different platform and a legacy microsite nobody mentioned each behave as a separate property, and finding them in month four instead of week one is the most common avoidable cost in a retainer.
The access questions matter as much as the scope ones. Analytics and Search Console are both invitation-based, so there is never a reason to ask a client for a Google password, and this form does not. It asks which named address to invite, at what level, and who can approve it — plus who controls DNS, because a domain-level Search Console property is verified with a DNS record and every migration redirect eventually lands in the same place. A named user can also be removed cleanly when the engagement ends, which a shared login cannot.
The history section is the part clients most often skip and most often need. A manual action from three years ago, a disavow file still uploaded, a migration where the redirect map was never kept — these are live conditions on the site, not background colour, and they change what the first ninety days should be spent on. Paired with the deployment question, they set realistic expectations: a technical finding that nobody has the access or the release slot to ship is a report, not a result, and it is better to know that in week one.
15 form ideas you can build with this template
Ecommerce SEO Retainer Onboarding
Captures the store platform, faceted-navigation constraints and who can deploy template changes across thousands of product pages.
International SEO Onboarding
Uses the languages and markets fields to establish the hreflang model and the separate Search Console property per country domain.
Post-Migration Recovery Onboarding
Leads with the migration section: old domain, date, whether a redirect map survives, and what the traffic did afterwards.
Penalty Recovery Onboarding
Focuses on the manual action history, any disavow file still uploaded, and whether a reconsideration request was ever filed.
SaaS Organic Growth Onboarding
Separates the marketing site from the docs and app subdomains, and records who deploys to each.
Local Multi-Location SEO Onboarding
Adds Google Business Profile to the access checklist and records the per-location content owners.
Publisher and Media SEO Onboarding
Treats the CMS edit permissions question as central, where thousands of legacy articles are in scope.
Lead-Gen SEO Onboarding
Leans on the conversion definition and conversion value fields to prioritise pages by pipeline rather than traffic.
B2B Technical SEO Onboarding
Puts the deployment path and staging environment questions first, because the roadmap is entirely engineering-dependent.
Franchise SEO Onboarding
Records the brand-level domain and franchisee subdomains separately, with different approval chains for each.
Replatforming Project Onboarding
Used before a planned migration rather than after one, to fix the redirect map ownership while it can still be planned.
Content-Led SEO Onboarding
Centres on the existing content calendar, the approval and publishing owners, and whether existing pages may be edited.
Agency Handover Onboarding
Built for the case where another agency is being replaced — what they did, what is still live, and which accounts they still hold access to.
Nonprofit SEO Onboarding
Handles the common situation where analytics was set up by a volunteer and nobody currently holds admin.
Retainer Renewal Refresh
Re-sent annually to catch a replatform, a new market, changed conversion definitions and a new deployment owner.
What's included
How to create an SEO client onboarding form
- 1
Click 'Use this template' to open the form pre-built in formformform.
- 2
Replace the placeholder access email with the shared address you want invited on analytics and Search Console.
- 3
Trim the CMS dropdown to the platforms you support, and edit the tools checklist to the stack you actually run.
- 4
Adjust the technical-change turnaround options to the release rhythms your clients really have, so the answer stays honest.
- 5
Add conditional logic in the editor after cloning if you want the migration and penalty detail fields to appear only when the preceding question says yes — templates ship flat, and branching is added afterwards.
- 6
Set the notification email to the strategist who will run the account, not the person who sold it.
- 7
Send it with the countersigned contract and say plainly that the first-month plan is written from these answers — it is the fastest way to get a long form completed.
Best practices for your SEO client onboarding form
Ask for every subdomain by name. Clients answer "our website" and mean the marketing site; the blog on a different platform and the German country domain are usually where the traffic actually is.
and anything genuinely outside that should go through a password-manager share agreed separately.
Follow up on any "Not sure" against DNS control before month one closes. Domain verification, hreflang and every future redirect depends on someone being able to make a DNS change.
Take the "we do not trust the numbers" answer seriously and audit measurement before promising a lift. Reporting against tracking the client already distrusts is a quarter of work nobody will believe.
Read the deployment answer before writing the technical roadmap. Recommendations sized for an agency with CMS access look very different from ones queued behind a monthly release train.
Ask what is still live from previous SEO work, not just what was done. A disavow file, an old robots.txt rule or orphaned schema outlives whoever added it, and inherited artefacts explain more anomalies than strategy ever does.
Keep the conversion value field optional but chase it later. A rough figure per conversion is what turns a keyword priority list into a commercial argument.
Never describe an SEO engagement, or this form, as making a client compliant with anything. Record the requirement, do the work, and let the certifications belong to whoever actually holds them.
Frequently asked questions
How is this different from an SEO audit request form?
The audit request runs before the sale: one website URL, a primary goal, current challenges, a timeline and a budget band, all designed to qualify a lead in under two minutes. This form runs after the contract and is built for delivery — every domain and subdomain in scope, the access grant process for analytics and Search Console, conversion definitions, penalty and migration history, deployment path and content permissions. Send the audit request to a stranger and this one to a client.
Why does the form ask who controls DNS rather than for the registrar login?
Because you never need the login. A domain-level Search Console property is verified with a single DNS record, and a named person who can add one is all that requires. Knowing who that person is also tells you how long a migration redirect will take to ship, which is more useful than a credential you would then be responsible for storing.
Should the penalty and migration questions be required?
The yes/no questions ship required and the detail fields ship optional, which is the right split — a client who does not know the history can still answer "Not sure" honestly, and that answer is itself information. Requiring detail on a history the client genuinely does not have produces a fabricated answer rather than a blank one.
Can the client attach a redirect map or keyword list?
Add an Upload field in the editor after cloning and they can attach files up to 2 MB each. Spreadsheets of any size are usually better shared as a link, which is why the template asks for a content calendar link — add the Upload field alongside it if you want both routes open.
What if the client cannot deploy technical changes at all?
Then the answer has done its job in week one rather than month three. An engagement with no deployment path is a content and off-page engagement whether or not anyone says so out loud, and it is far better to reshape the roadmap at onboarding than to deliver a technical audit that sits in a queue for a quarter.
Is what the client submits kept private?
Submissions travel over HTTPS into your formformform account rather than an inbox, end-to-end encryption can be turned on per form so only you can read them, EU hosting is available, and formformform is GDPR compliant. SOC 2 and ISO 27001 belong to the hosting provider, not to formformform. The strongest protection here is still the design of the form itself: it does not collect a single credential.
Related templates
Let potential SEO clients describe their website challenges and goals upfront.
Request blog posts, emails, ad copy, and more from your content team with full context.
Capture campaign briefs with objectives, budget, channels, and timeline in one form.
Gather competitive intelligence directly from customers who use you and your rivals.
Collect domain, hosting, CMS, analytics and approval details from a signed web client — without asking for a single password.
Onboard a signed social client: channels, business-manager access, brand voice, off-limits topics, approvals, cadence, baselines and a crisis contact.
More Marketing form templates
Free forever. No credit card required. Customize everything.
Use this template