The contract was signed on a Friday. Three weeks later you're still waiting for Search Console access, the first audit hasn't run, and the client has started asking, politely, what they've paid for. Onboarding is the one part of an engagement you control completely, so run it as a fixed five-day sequence that's the same for every client, and by the end of the week the client has seen a baseline, a plan and their own view of progress.
Why the first week decides the first year
Results arrive slowly. Google's own "Do you need an SEO?" guidance says that in most cases it takes four months to a year to implement improvements and then see their potential benefit. Client confidence forms long before that, and when there's nothing visible to form it around, clients fill the gap with doubt. What you can show in week one is process: you asked for the right things, you measured where they started, you have a plan with owners, and they can see it whenever they like.
Week one is also when access is easiest. The person who signed is still paying attention and the client is motivated. Every day of delay makes the same request harder, and an engagement that starts without access spends its first month waiting instead of working.
A fixed sequence does one more thing: it makes onboarding something any account manager can run from a checklist, which is what lets the agency grow past its founder.
Day one: access and ownership
Send the access request the day the contract is signed, or before. Ask for:
- Google Search Console. Ask the property owner to add your agency account as a user. Search Console supports adding users with full or restricted permission, so nobody needs to share a password.
- Their analytics, added the same way, as a user on the property.
- Google Business Profile, if they serve a local area, with your account added as a manager.
- An editor-level login to their CMS for your team, not the owner's admin account.
- A named contact for hosting and DNS, for the day a fix needs the server.
- The people: who approves content, who does development, who signs off the invoice.
Never accept passwords by email; if something must be shared, use a password manager. Then create the client's project in your own system the same day: one project per client, in one workspace your whole team can reach, so every piece of work that follows has a home.
Chase by the end of the day. Most access delays are a forgotten email, not a reluctant client.
Days two and three: the baseline
Every report you send later needs a "before", and the baseline is it. Without one, your first monthly report is a number with no meaning.
- Run the first full audit of the site: crawl, indexing, on-page, speed, structured data. Record the starting grade and the top findings with the date.
- Confirm the keyword list with the client. You want the terms that bring the customers they actually want, not the ones that sound impressive. Capture current positions for those terms so movement is visible later.
- Note who really ranks for those terms. It's often not the competitors the client names.
- Check the things that block everything else:
robots.txt, the sitemap, and whether the money pages are indexable. How Google ranks a page explains why these come first. - Pull what Search Console already knows: which pages are indexed, which queries bring impressions, and any errors it's reporting.
- Put the audit on a monthly schedule now, so the re-audit lands next month without anyone needing to remember.
Store the baseline in the client's project with its date. It's also the first deliverable the client sees, so write the top findings in plain words from the start.
Day four: the plan
Turn the accepted findings into a plan, not every finding. Triage each into three piles: things the client's developer must do (templates, redirects, speed), things your team does (content, on-page, meta), and things for a later phase. Order the first two piles by impact and effort; Prioritising fixes by impact covers how. Sketch the first quarter of content, which Content calendars that ship turns into a process.
Give every task an owner and a month. That list is the scope in writing from Scoping and pricing SEO, and it's what you'll point to when a request arrives in month two. Set the date of the first monthly report now and put it in both calendars.
Day five: kickoff and their view
The kickoff call is short and follows the same agenda every time: the baseline in plain words, the plan with owners, what you need from the client and by when, the monthly rhythm, and the report date. Set the expectation that the first months are fixes and foundations. A client told this on day five doesn't panic on day sixty.
Then give them their view. Most clients want a read-only link to the live report and nothing more. A marketing manager who checks weekly may want their own login, scoped to their project only. Offer the lighter option first: a heavier surface for a light-touch client creates support questions, not confidence. Whatever you give them, open it yourself first and check it shows what you'd show in a review meeting and nothing you wouldn't.
Connect their CMS before the call ends, so the first article in month one doesn't wait on another access request.
What to take away
- Results take months, so the first week has to show process: access secured, a baseline recorded, a plan with owners, and a view the client can open.
- Ask for access on day one, as a user added to each property rather than a shared password, and chase the same day.
- The baseline is the "before" for every report that follows; record it with a date and schedule the re-audit before you move on.
- Give each client the lightest view that fits them, and check it yourself before they do.
Next
With the client onboarded, the next chapter turns the audit into the thing that wins the account and the first deliverable that proves it: The audit as a sales tool.