Onboarding a new SEO client: access, baselines and the first 30 days

The first thirty days with a new SEO client set the tone for the whole relationship. A messy start (waiting weeks for access, making changes before measuring anything, promising results the site cannot deliver) creates problems that last for months. A structured start gives the client early confidence and gives you the information and baselines you will rely on later.

This plan works for freelancers and small agencies. Adjust the depth to the size of the site and the engagement.

Before the kick-off

Send the access list and a short questionnaire before the first meeting, so the meeting is spent on understanding the business rather than on passwords.

The access list

Access	Level	Why
Google Search Console	Full user (owner stays with client)	Performance, indexing, inspection
Analytics	Viewer or analyst	Outcomes and behaviour
Bing Webmaster Tools	User	Bing data and indexing
CMS or staging site	Editor, or developer contact	Inspect templates, make content changes
Tag manager	Read, or publish if you will manage tags	Tracking setup
Google Business Profile	Manager (for local businesses)	Local visibility
Hosting, CDN or server logs	Read access or exports	Crawling, speed, errors
DNS	Contact who can make changes	Verification, redirects, email-related records
Previous SEO work	Reports, audits, disavow files, link lists	History and risks

Ask the client to grant access to a dedicated agency account rather than a personal one, and make sure the client, not you, remains the verified owner of every property. The properties and permissions guide explains why.

The questionnaire

• What does the business sell, to whom, and where? Which products or services matter most for revenue?
• Who are the main competitors, online and offline?
• What does success look like in twelve months, in business terms?
• What has been tried before in SEO, and with what results? Any agencies, link buying, migrations, penalties?
• Who can approve content, make technical changes, and how long does that usually take?
• Are there seasonal peaks, launches or campaigns planned?

The kick-off meeting

With access and the questionnaire in hand, the first meeting can focus on what the documents cannot tell you. Useful topics:

• How customers really buy. What do they ask before buying, which objections come up, how long do they take to decide? Sales and customer service staff often know more about search intent than anyone in marketing.
• What the business is proud of and what it cannot do. Strengths become content angles; limits stop you from targeting queries the business cannot satisfy.
• How changes get made. Who writes, who approves, who deploys, how long each step takes, and which parts of the site are off limits.
• History. Past agencies, migrations, traffic drops and what was blamed for them.
• Expectations. What the client hopes to see in three, six and twelve months, which you can then make realistic together.

Take notes in a shared document and send a summary the same day. Clients notice when they are listened to.

Week 1: baselines before changes

Record the current state before changing anything. It takes a day and protects everyone later.

1. Search Console performance: export 16 months of data by page and by query, and a monthly summary of clicks, impressions, CTR and position. Note brand versus non-brand; see regex filters.
2. Analytics outcomes: organic sessions, conversions and revenue for the past 12 months, by landing page group.
3. Indexing: a screenshot or export of the Page indexing report.
4. Technical health: a full crawl and a technical score. Running the SEO checker on the main domain gives a dated score and issue list to compare against.
5. Priority queries: agree 10–30 commercially important queries and record their current average positions.
6. Backlinks: referring domains count and top linking sites, from one tool.
7. AI visibility, if relevant: a set of brand-free customer questions and whether the client is mentioned; see measuring AI visibility.

Store the baseline in a dated document shared with the client. When results are discussed in six months, this document settles questions that memory cannot, and it shows the client from the start that progress will be measured against facts.

Week 1–2: urgent checks

Some problems cannot wait for the full audit. Check in the first days:

• Sitewide noindex, robots.txt blocks or broken canonicals.
• Manual actions or security issues in Search Console.
• Large numbers of 404s on previously important URLs, often from a past migration.
• Expiring domains or certificates.
• Tracking that is broken or missing on key templates.

Fix or escalate anything critical immediately, and tell the client what you found and why it mattered.

Week 2–3: audit and research

• Technical audit, ordered by consequence; see the audit checklist.
• Content inventory: what exists, what performs, what overlaps, what is outdated.
• Keyword and competitor research for the client's priority products or services; see keyword research.
• Local presence for local businesses: Business Profile, citations, reviews.

Week 3–4: the plan

Turn findings into a 90-day plan the client can approve. Each item needs: what, why (expected effect on the agreed goals), effort, who does it (you, the client, their developer), and when. Rank items with a simple impact-effort method; see prioritising SEO fixes.

Include a handful of quick wins that can be done in the first month: fixing a broken redirect set, rewriting titles on high-impression pages with low CTR, adding internal links to underperforming key pages. Quick wins build trust while larger work is under way. Be careful not to promise traffic from them; promise completion.

Agree goals and reporting

End the first month with a written agreement on:

• Two or three outcome metrics and their current baseline.
• The priority queries and topics.
• The reporting rhythm and format; see reporting for clients.
• Who on the client side approves and implements what, and expected turnaround times.
• A date for the first quarterly review.

A worked example

A freelancer takes on a hypothetical kitchen-fitting company with three showrooms. Access arrives within two days because the request went out before the kick-off. The baseline shows that organic enquiries come almost entirely from brand searches and two location pages. In the first week, the urgent check finds that the third showroom's location page has carried a noindex since a redesign eight months earlier, which nobody had noticed; it is fixed on day four. The audit and research in weeks two and three find thin service pages, no content about the questions customers ask most (costs, timelines, planning permission), and inconsistent showroom addresses across directories.

The 90-day plan, approved at the end of the month, has three quick wins (the noindex fix already done, rewritten titles for the service pages, corrected listings) and two larger projects (rebuilt service pages with real project photos and costs, and a guide to planning a kitchen refit). The client knows exactly what will happen, in what order, and how progress will be measured against the baseline.

Common onboarding mistakes

• Starting work before access to Search Console and analytics is in place, so there is no baseline.
• Becoming the only owner of the client's Search Console property.
• Delivering a 150-row audit without priorities.
• Promising ranking or traffic numbers in the proposal.
• Not asking about past link buying or penalties, then discovering them later.
• Underestimating how long the client's developers take to ship changes, and planning as if they were your own team.

Set up monitoring from day one

Many engagements are damaged by something that happens on the client's side: a release that adds noindex, a plugin that breaks canonicals, a hosting change that slows the site. Set up scheduled monitoring for each client domain in the first week, so you find out before the client does. DeskSEO's scheduled monitoring re-checks domains and emails alerts when the score drops or a new critical issue appears; the plans scale from one domain to thirty.