The first month is about verifying access, agreeing priorities and shipping a small, testable batch. A long report with no owner is not a successful kickoff.
Week one: access, ownership, and expectations
A good onboarding process verifies access to Search Console, analytics, the website, Business Profiles when relevant, and the task tracker. It documents who approves changes and what the agency is authorized to implement. Do not hand out administrator access unnecessarily or allow the absence of access to become invisible.
- Access inventory and permissions
- Named points of contact
- Scope, priorities, and dependencies
Baseline without cherry-picking
The baseline should note the measurement date, query location, devices, key landing pages, conversions, and branded versus non-branded searches. A single average keyword position is not enough to understand the situation. Existing performance issues and analytics limitations belong in the baseline, too.
- Search and traffic source definitions
- High-value pages and queries
- Working conversion events
A short audit that leads to action
The first audit should prioritize a few high-confidence fixes rather than bury the client under hundreds of automated warnings. Each critical issue needs evidence, potential impact, who can fix it, and how to verify the result. A recommendation is not the same as implementation.
- Prioritized issue log
- Approved first work cycle
- Definition of done
First batch of work and QA
The most useful first-month milestone is accepted work: pages updated, a content brief approved, a technical error corrected, or profile data reconciled. Document the before-and-after state and any blocked requests. Search performance often responds on a different timeline from the delivery calendar.
- Published or approved assets
- Review status and re-tests
- Risks and next-month queue
What you should not expect
Be skeptical of guaranteed number-one rankings, precise traffic promises without a credible model, or claims that every task will produce immediate leads. A reputable provider can commit to defined deliverables and a transparent process, while reporting search outcomes as measured rather than controlled.
- No ranking guarantees
- No hidden scope additions
- No reports that only list activities
A realistic first-month work-cycle calendar
Treat the first 30 days as a controlled setup and first delivery cycle, not a guarantee that rankings will move by a certain date. Dependencies may shift the schedule.
| Example or checkpoint | Recommended action | Review or acceptance |
|---|---|---|
| Days 1–5: access and baseline | Confirm owners, permissions, target pages, existing traffic/ranking reports | Approved access register and baseline snapshot |
| Days 6–10: prioritization | Triage indexation, content and conversion issues against business goals | Signed-off task queue with acceptance criteria |
| Days 11–20: initial execution | Ship one bounded batch with QA notes and change history | Evidence of implementation, not just a completed checkbox |
| Days 21–30: review | Retest, inspect blockers, and agree the second work cycle | Decision log with measurable next actions |
The clearest first-month question is whether the work was delivered accurately and approved, not whether a search engine has already rewarded it. Keep a separate record of observed changes in rankings and leads.
Download: First-month SEO work cycle (CSV)
Relevant reference material
A useful first-month handoff record
At the first review, ask for a compact decision log, not a spreadsheet that claims dozens of completed tasks. A realistic record says what was fixed, what is pending, what evidence exists and which dependency is next.
- Completed: a corrected canonical or title change, with a live URL and review date.
- Waiting: a template change that needs developer approval, including the exact blocker.
- Observed: ranking or traffic data, labeled as a baseline rather than proof of causation.
- Next: the one or two fixes with the strongest evidence and an assigned owner.
Download: First-month tracking plan (CSV). Use the example to guide a review; no campaign outcome is implied.
Frequently asked questions
Should there be a ranking increase in month one?
There is no universal timeframe. Access, implementation, competition, and indexing all affect what can be observed.
Should an SEO agency provide a report immediately?
A baseline and first-work summary are reasonable, even if outcome trends are too early to interpret.
What if development access is delayed?
The dependency and owner should be documented; the agency can prepare approved work without claiming a fix was deployed.