September 08, 2026
14 min read
By Kokil Thapa | Last reviewed: September 2026
A new SEO retainer fails in the first two weeks more often than in month six. The reason is rarely keyword research. It is a missing Search Console property, a client who thought SEO meant paid ads, or an audit that started before anyone confirmed CMS access. A structured SEO client onboarding process checklist turns that fragile first fortnight into a repeatable handoff. Whether you run a small agency in Kathmandu or freelance for clients abroad, the same sequence applies: confirm scope, collect credentials, establish baselines, audit, plan, and report. This guide walks through that sequence with copy-paste templates, real file paths, and the gotchas I have seen on production sites from legal-tech portals to WooCommerce stores.
Quick answer: An SEO client onboarding process checklist covers contract and scope confirmation, credential collection (Search Console, Analytics, CMS), baseline reporting, a technical and on-page audit, competitor review, a prioritised 90-day roadmap, and a recurring reporting cadence—completed before any link-building or content work begins.
What is an SEO client onboarding process checklist?
An SEO client onboarding process checklist is the ordered set of tasks you complete when a client signs an SEO agreement. It sits between the sales call and the first optimisation sprint. Its job is to remove ambiguity, document starting conditions, and protect both parties from scope creep.
Think of it as three layers. Layer one is commercial: signed agreement, payment terms, and a single written statement of what SEO does and does not include. Layer two is operational: access to analytics, search tools, hosting, and the CMS. Layer three is analytical: baseline traffic, rankings snapshot, crawl data, and a prioritised backlog.
On real client projects, I treat onboarding as a fixed-duration phase—usually 5 to 10 business days—not an open-ended discovery period. That boundary keeps the client engaged and prevents the classic trap of endless auditing with no deliverables. If you need a broader audit framework, pair this checklist with the technical SEO audit checklist for 2026.
Who needs this checklist
Freelancers onboarding their fifth client use the same checklist as agencies scaling to fifty retainers. The difference is tooling, not steps. A solo practitioner might store credentials in a password manager and reports in Google Drive. An agency adds a project template in their PM tool and a shared client portal.
If you are new to winning SEO work, read how to get clients as a freelancer in Nepal first. Onboarding only matters after the contract is signed.
What documents and access do you collect during SEO client onboarding?
Credential collection is the step most likely to stall an engagement. Send one access request email with every item listed. Do not drip-feed requests across three weeks—the client will lose patience and you will lose momentum.
Commercial documents
- Signed statement of work or service agreement with deliverables, timeline, and revision limits
- Invoice or first payment confirmation—do not start production work on a verbal yes
- Primary and backup contact names with response-time expectations
- Brand guidelines, tone notes, and any compliance restrictions (common on law-firm and finance sites)
Use a contract template as your starting point. For SEO-specific clauses, see the SEO freelancer contract template for Nepal. Web developers crossing into SEO should also review the client contract template for freelance web development.
Technical and analytics access
Request every item below in one message. Mark each as required or optional so the client knows what blocks progress.
- Google Search Console — Full user access on the correct property (domain preferred over URL-prefix)
- Google Analytics 4 — Editor or Administrator role; confirm data exists and is not duplicated across properties
- Google Business Profile — Manager access for local clients; see the local business GBP guide
- CMS admin — WordPress, Shopify, or custom Laravel panel depending on stack
- Hosting or server panel — For robots.txt, redirects, and cache rules when CMS access is insufficient
- DNS registrar — Only if migration, CDN, or subdomain work is in scope
- Previous agency handover — Keyword lists, backlink reports, content calendars, and ad account separation notes
Store credentials in a dedicated password manager vault per client. Never paste production passwords into Slack, WhatsApp, or email threads. For JSON config exports from analytics or crawl tools, use the JSON formatter to validate structure before archiving baseline files.
Access request email template
Subject: SEO onboarding — access checklist for [Client Name]
Hi [Name],
To complete your SEO baseline and audit, please grant the following access
to [your agency email]:
Required (blocks start):
- Google Search Console — Full user on sc-domain:example.com.np
- Google Analytics 4 — Editor on property G-XXXXXXXX
- WordPress admin — Editor role at /wp-admin
Optional (needed for speed work in week 2):
- Cloudflare dashboard — Read-only
- Previous SEO reports (PDF or spreadsheet)
Please reply once each item is done. Target: [date + 3 business days].
Thanks,
[Your name]
How do you establish SEO baselines before making any changes?
Baseline data is your defence against unrealistic expectations. Without it, a client sees a traffic dip in month two and assumes you broke the site. With it, you can show seasonality, a Google update, or a tracking change.
Metrics to capture on day one
Export these numbers before you touch a title tag or redirect. Save screenshots and CSV files dated with the onboarding start date.
- Organic sessions and conversions — last 16 months in GA4 to cover seasonality
- Top landing pages by organic traffic and by revenue or leads
- Indexed page count and coverage errors from Search Console
- Core Web Vitals field and lab data for templates that drive traffic
- Top 50 keyword rankings from Search Console queries plus a rank tracker snapshot
- Backlink profile summary — referring domains, anchor distribution, toxic flags
- Indexed vs submitted URLs, sitemap status, and robots.txt fetch result
For GA4 setup and reporting views, follow the Google Analytics 4 for SEO data analysis guide. Confirm that organic traffic is tagged correctly and that key events (form submits, calls, purchases) fire before you report conversion metrics.
Baseline report structure
Keep the first client-facing baseline report to eight to twelve pages. Executives read the summary. Your team reads the appendix.
- Executive summary — three bullets on current state and biggest opportunity
- Traffic and conversion trends — month-over-month and year-over-year charts
- Technical health score — crawl errors, indexation, speed, mobile usability
- Content and keyword gap — top queries vs target map
- Competitor comparison — three to five direct competitors, not random high-authority sites
- Recommended 90-day priorities — ordered by impact and effort
On legal-tech portals I have maintained, baseline reports also note regulatory language constraints and page types that cannot be rewritten without lawyer approval. Capture those content boundaries during onboarding, not after you submit copy recommendations.
How do you run the technical and on-page audit during onboarding?
The onboarding audit is narrower than a full annual audit. You are looking for blockers and quick wins, not rewriting the entire information architecture in week one.
Technical audit priorities
Work through this list in order. Stop and escalate to the client if you find indexation collapse, manual actions, or widespread duplicate content.
- Crawl the site with Screaming Frog or Sitebulb — export 4xx, 5xx, redirect chains, and orphan pages
- Verify robots.txt allows key paths and blocks staging, faceted noise, and admin URLs
- Check canonical tags on templates — especially paginated archives and product variants
- Review XML sitemaps for stale URLs, missing sections, and incorrect lastmod values
- Test HTTPS, www vs non-www, and trailing-slash consistency — one preferred host only
- Inspect structured data on high-value templates — Article, Product, LocalBusiness, FAQ where appropriate
- Flag page-speed issues on money pages — align with the SEO page speed optimization checklist
For Laravel or custom PHP sites, also verify route caching, dynamic sitemap generation, and that middleware is not injecting noindex headers on public pages. The SEO setup guide for Laravel sites covers application-level patterns I use in production.
For WordPress 7.1 and WooCommerce 11.1 stacks, check plugin-generated sitemaps, category thin pages, and media attachment URLs. WordPress-specific hardening belongs in a separate security pass—see the WordPress security hardening checklist if you also manage the host.
On-page audit priorities
Sample the top 20 organic landing pages plus every template type: homepage, category, product or service detail, blog post, and contact.
- Title tags and meta descriptions — unique, within pixel limits, aligned to intent
- H1 hierarchy and heading structure on each template
- Internal links to and from priority URLs — see internal linking strategy for SEO wins
- Image alt text, compression, and modern formats on high-traffic pages
- Thin or duplicate content — parameter URLs, print views, tag archives
Document findings in a spreadsheet with columns for URL, issue, severity, owner, and status. Severity should use three tiers only: blocker, high, low. Twenty severity levels paralyse clients.
How do you build the 90-day SEO roadmap and reporting cadence?
Onboarding ends with a written plan the client approves. Verbal agreement is where scope creep begins.
Keyword and competitor research during onboarding
Build a keyword map tied to URLs, not a flat list of search volumes. Group terms by intent: informational, commercial, transactional, and local.
Use Search Console query data as your primary source—it reflects what Google already associates with the site. Supplement with third-party tools for gap analysis. The keyword research free tools guide covers a sensible stack for budget-conscious clients.
For eCommerce onboarding, add category-level mapping and faceted navigation rules. The eCommerce SEO guide for product pages explains template-level optimisations that belong in month one.
90-day roadmap template
| Phase | Weeks | Focus | Example deliverables |
|---|---|---|---|
| Foundation | 1–4 | Fix blockers and tracking | Redirect cleanup, canonical fixes, GA4 events, sitemap repair |
| Optimisation | 5–8 | On-page and content | Title rewrites, new landing pages, internal link passes |
| Growth | 9–12 | Authority and expansion | Digital PR, local citations, content cluster launch |
Match effort to client capacity. A two-person Nepal business cannot publish eight blog posts monthly. Plan for four solid pages and technical fixes instead. Our planning and research service often feeds this roadmap when the client needs discovery before execution.
Reporting calendar
Set reporting rhythm during onboarding, not after the first month ends.
- Weekly internal — Task log, blockers, hours or points completed
- Monthly client report — Organic traffic, rankings movement on priority terms, work completed, next-month plan
- Quarterly review — Roadmap reset, competitor refresh, budget and scope check
Include Nepal seasonality where relevant. Dashain and Tihar slow many local businesses. Tourism sites spike in pre-monsoon windows. A baseline that ignores seasonality sets false expectations.
Onboarding vs ongoing work
| Criteria | Onboarding (weeks 1–2) | Ongoing retainer (month 2+) |
|---|---|---|
| Primary output | Baseline report + approved roadmap | Executed tasks from backlog |
| Client time required | High — access, kickoff, approval | Low — monthly review call |
| Link building | Not recommended | After technical foundation is stable |
| Content publishing | Audit only unless blockers need fixes | Scheduled per content calendar |
| Success metric | 100% access + signed roadmap | Rankings, traffic, leads, revenue |
What are the most common SEO client onboarding mistakes?
Most onboarding failures are process failures, not skill gaps. These recur across agency and freelance engagements.
Starting work without written scope
A client asks you to "just fix SEO" while the contract only mentions blog posts. Two months later they refuse to pay for redirect work. Fix this on day zero. List included services: technical fixes, content, links, local, reporting. List exclusions: paid ads, social media, unlimited revisions.
Skipping baseline exports
You cannot prove progress without a dated starting point. Export GA4, Search Console, and rank data before any change. If the client later changes analytics plugins or migrates hosts, you still have the original snapshot.
For migration clients, run a parallel onboarding track using the SEO migration checklist for zero traffic loss. Onboarding on a site mid-migration is a different beast.
Auditing before access is complete
Partial access produces partial audits. Worse, you present findings the client cannot verify. Gate the audit kickoff behind a checklist: GSC verified, GA4 confirmed, crawl allowed by robots.txt.
Overpromising timelines in the kickoff call
Nobody ranks page one for competitive terms in 30 days. Set expectations using baseline difficulty and competitor authority. Reference E-E-A-T signals and authority building when explaining why YMYL niches move slower.
Ignoring stakeholder map
On corporate and law-firm sites, the marketing contact is not the final approver. Ask who signs off on copy, who controls the CMS, and who owns the developer queue. I have seen month-long delays because meta description changes needed IT ticket approval nobody mentioned at kickoff.
Neglecting on-page checklist alignment
Your onboarding audit should feed directly into ongoing work. Map findings to the on-page SEO checklist for Nepal so nothing falls through when the retainer rhythm starts.
External references worth bookmarking for the analytics and search steps: Google Search Console property setup documentation and GA4 reporting identity and data collection guidance. For structured data validation, use Google's structured data documentation.
Key Takeaways
- Complete contract, access, baseline, audit, and roadmap before any link-building or content sprint.
- Send one consolidated access request email—GSC, GA4, CMS, and hosting—within 24 hours of contract sign.
- Export dated baseline traffic, indexation, and ranking data before changing a single on-page element.
- Deliver an eight-to-twelve-page baseline report plus a three-phase 90-day roadmap the client approves in writing.
- Set monthly reporting and quarterly review cadence during onboarding, not after the first month ends.
- Map stakeholders and content approval paths on kickoff to avoid multi-week delays on simple SEO fixes.
People Also Ask
How long should SEO client onboarding take?
Most engagements need 5 to 10 business days from contract sign to approved roadmap. Allow extra time if IT departments control access or if the site is mid-migration. Do not extend beyond two weeks without a written reason—the client loses confidence and your team loses focus.
What should an SEO onboarding questionnaire include?
Cover business goals, target customers, service areas, competitor names, past SEO work, CMS and hosting details, content approval workflow, and brand restrictions. Add niche questions for local (GBP locations), eCommerce (platform and SKU count), or multilingual sites (hreflang status).
Should you charge separately for SEO onboarding?
Either bundle onboarding into month one of the retainer or charge a fixed setup fee covering baseline audit and roadmap creation. A separate fee filters clients who are not serious and compensates for the heavy upfront work. Publish transparent ranges in your SEO services pricing guide for Nepal so prospects expect it.
When can you start link building for a new SEO client?
Start after blockers are fixed, tracking is verified, and the client approved the roadmap—typically week five or later. Building links to a site with noindex errors or redirect loops wastes budget and creates reporting noise you cannot explain away.
Ship onboarding like a production handoff
A repeatable SEO client onboarding process checklist protects your margins, your client relationships, and your sanity. The sites that grow steadily are rarely the ones with the flashiest pitch deck. They are the ones where someone documented baselines, fixed indexation first, and agreed on a 90-day plan before chasing vanity keywords.
If you want help running onboarding on a Laravel, WordPress, or WooCommerce property—or you need a technical baseline before hiring in-house—review our search engine optimization services in Nepal or browse Notary Nepal and other portfolio projects where structured SEO onboarding preceded long-term growth. For performance-critical fixes identified during audit, pair SEO with testing and optimization and speed optimization workstreams.
Ready to standardise your next handoff? Contact us with your current client count and stack—we will map which checklist steps belong in week one for your workflow.
Frequently Asked Questions
The ordered tasks between signing an SEO agreement and the first optimisation sprint—confirming scope, collecting credentials, establishing baselines, auditing, planning a 90-day roadmap, and setting reporting cadence.
Collect commercial documents first: signed statement of work, payment confirmation, primary and backup contacts, brand guidelines, and compliance restrictions for regulated niches like law firms. Request all technical access in one email—Google Search Console with domain property preferred, Google Analytics 4 with Editor or Administrator role, Google Business Profile for local clients, CMS admin, hosting panel, DNS registrar if migration is in scope, and previous agency handover files. Mark each item required or optional so the client knows what blocks progress. Store credentials in a dedicated password manager vault per client, never in Slack, WhatsApp, or email threads.
Typically 5 to 10 business days—a fixed phase, not open-ended discovery.
Export all baseline metrics before touching a title tag or redirect. Save dated screenshots and CSV files from Google Analytics 4, Search Console, and your rank tracker. Capture organic sessions and conversions over the last 16 months to cover seasonality, top landing pages by traffic and conversions, indexed page counts, Core Web Vitals, top 50 keyword rankings, backlink profile summary, and sitemap status. Confirm GA4 organic traffic tagging and that key conversion events fire correctly. Without this dated starting point, you cannot defend against unrealistic expectations when traffic dips or tracking changes later.
Export organic sessions and conversions for the last 16 months in GA4, top landing pages by organic traffic and by revenue or leads, indexed page count and coverage errors from Search Console, Core Web Vitals field and lab data for high-traffic templates, top 50 keyword rankings from Search Console queries plus a rank tracker snapshot, backlink profile summary including referring domains and toxic flags, and indexed versus submitted URLs with sitemap and robots.txt fetch results. On regulated sites, also document content boundaries and page types that require legal approval before copy changes.
The onboarding audit targets blockers and quick wins, not a full information architecture rewrite. Crawl with Screaming Frog or Sitebulb and export 4xx, 5xx, redirect chains, and orphan pages. Verify robots.txt allows key paths, check canonical tags on paginated and product templates, review XML sitemaps for stale URLs, test HTTPS and www consistency, inspect structured data on high-value templates, and flag page-speed issues on money pages. Escalate immediately if you find indexation collapse, manual actions, or widespread duplicate content. For Laravel sites, verify route caching and noindex middleware. For WordPress and WooCommerce stacks, check plugin sitemaps and thin category pages.
Sample the top 20 organic landing pages plus every template type: homepage, category, product or service detail, blog post, and contact. Review title tags and meta descriptions for uniqueness and intent alignment, H1 hierarchy on each template, internal links to and from priority URLs, image alt text and compression on high-traffic pages, and thin or duplicate content from parameter URLs, print views, or tag archives. Document findings in a spreadsheet with URL, issue, severity, owner, and status columns. Use three severity tiers only—blocker, high, and low—so clients can act without paralysis.
Build a keyword map tied to URLs grouped by intent: informational, commercial, transactional, and local. Use Search Console query data as your primary source and supplement with third-party tools for gap analysis. Structure the roadmap in three phases: Foundation in weeks 1–4 for redirect cleanup, canonical fixes, GA4 events, and sitemap repair; Optimisation in weeks 5–8 for title rewrites, landing pages, and internal link passes; Growth in weeks 9–12 for digital PR, local citations, and content clusters. Match deliverables to client capacity—a small team cannot publish eight posts monthly. Get written client approval before execution begins.
Onboarding in weeks one and two produces a baseline report plus an approved roadmap and requires high client involvement for access, kickoff, and approval. Link building is not recommended during this phase, and content work is audit-only unless blockers need immediate fixes. Success is measured by 100 percent access collected and a signed roadmap. An ongoing retainer from month two onward executes tasks from the backlog with low client time beyond monthly review calls. Link building starts after the technical foundation is stable. Success shifts to rankings, traffic, leads, and revenue movement.
Starting work without written scope causes billing disputes when redirect or technical work falls outside a vague blog-post contract. Skipping baseline exports leaves you unable to prove progress after analytics plugin changes or host migrations. Auditing before access is complete produces unverifiable partial findings—gate the audit behind confirmed Search Console, GA4, and crawl access. Overpromising page-one rankings in 30 days sets false expectations, especially in YMYL niches where authority builds slowly. Ignoring the stakeholder map delays approvals when the marketing contact cannot sign off on copy or CMS changes without a lawyer or developer.
After the technical foundation is stable in month two or later—not during onboarding weeks one and two.
Send one access request email listing every item at once rather than drip-feeding requests over weeks. Use a clear subject line, list required items that block start separately from optional items needed in week two, specify exact roles such as Full user on Search Console and Editor on GA4, include property identifiers like sc-domain:example.com.np, set a target completion date three business days out, and ask the client to reply once each item is done. This single-message approach prevents stalled engagements and keeps momentum through the fragile first fortnight.
Freelancers onboarding their fifth client and agencies scaling to fifty retainers use the same steps—the difference is tooling, not sequence. A solo practitioner might store credentials in a password manager and reports in Google Drive. An agency adds a project template in their PM tool and a shared client portal. The checklist applies whether you run a small agency in Kathmandu or freelance for clients abroad. Onboarding only matters after the contract is signed, so winning the work comes first. The checklist turns the fragile first fortnight into a repeatable handoff regardless of team size.
Keep the first client-facing baseline report to eight to twelve pages. The executive summary needs three bullets on current state and biggest opportunity. Include traffic and conversion trends with month-over-month and year-over-year charts, a technical health score covering crawl errors, indexation, speed, and mobile usability, a content and keyword gap section comparing top queries against your target map, competitor comparison against three to five direct competitors—not random high-authority sites—and recommended 90-day priorities ordered by impact and effort. Executives read the summary; your team reads the appendix with raw exports and crawl data.
Define the reporting rhythm during onboarding, not after the first month ends. Schedule weekly internal reviews covering task logs, blockers, and hours or points completed. Deliver monthly client reports showing organic traffic, rankings movement on priority terms, work completed, and next-month plan. Hold quarterly reviews to reset the roadmap, refresh competitor analysis, and check budget and scope. Account for Nepal seasonality where relevant—Dashain and Tihar slow many local businesses while tourism sites spike in pre-monsoon windows. A baseline that ignores seasonality creates false expectations when traffic naturally dips or surges.
0 Comments
Leave a comment
Your email is not published. Comments appear once they have been read. Sign in to have your details filled in.
