SEO Project Kickoff Checklist for Agencies (Onboarding)

The first two weeks of a new client engagement decide how the next six months feel. When access arrives late, the team improvises. When goals are vague, every monthly call becomes a debate about what success means. When nobody asks about past link work, the surprise tends to show up in month three, at the worst possible time. A good seo project kickoff checklist removes most of these surprises before they happen.

This guide is written for agency leads, account managers and freelancers who onboard SEO clients. It covers the kickoff meeting, the order in which to request access, how to define goals, which baseline numbers to capture and what the first 30 days should contain. It deliberately stays out of two neighboring topics: how to run a link building operation and how to build a monthly report. Both have their own guides, linked where they become relevant. You will find a client information form and a one-table checklist near the end that you can copy into your own process.

The SEO Project Kickoff Checklist: Meeting and Expectation Setting

A kickoff meeting is not the sales pitch repeated at greater length. It is an alignment session in which both sides confirm they are describing the same project. Send a short agenda ahead of time and make sure three roles are in the room: the person who decides, the person who can change the website, and the person who owns content. If one is missing, decisions made in the meeting tend to be reopened a fortnight later.

A workable agenda follows this order:

1. Scope: what you will do, what you will not do and the period covered.
2. The client's business: what they sell, to whom, and what role they expect organic search to play.
3. History: earlier agencies, past redesigns or migrations, known problems.
4. Approvals: who signs off, how long a sign-off normally takes, who to call when something urgent breaks.
5. Access and calendar: which accounts are needed, who grants them and by when.

The most important sentence in the whole meeting concerns outcomes and timing. Google's own page on whether you need an SEO professional says no one can promise a particular ranking, and it suggests asking any provider what results they expect, over what timeframe, and how they will measure success. Treat that as a script for your own side of the table. Instead of promising a position by a date, say what you will measure in month one, what you expect to change in month two and how often you will share findings.

End the meeting by sending a written recap with decisions, requested access, owners and dates. That recap becomes the single reference point whenever someone remembers the conversation differently.

Access Requests: Search Console, Analytics, CMS and Server

The order of access requests is a risk decision, not a courtesy. Ask first for read-only access that cannot break anything, and request write access only when a specific task needs it and you can explain why. Google's guidance for audits makes the same point about Search Console: grant read access at the start, not write access. The same logic carries over to every other system. The source is Google Search Central's page on whether you need an SEO (Opens in a new tab).

A sensible sequence looks like this:

• Search Console: user permission, not ownership. Ask whether the property is a domain property or a URL-prefix property.
• Analytics: viewer level is enough at first. Check whether conversion events exist at all.
• CMS: an editor account that lets you see how content is entered; admin rights only once a concrete change is agreed.
• Server and CDN: often unnecessary. Working through the client's developer for logs and redirect rules is usually safer for both sides.
• Tag manager and ad accounts: view-only, and only if the work touches them.

For every grant, record who gave it, at what level and for what purpose. That register becomes your offboarding list when the engagement ends. Ask the client to share access through a shared admin or role account rather than a single person's login, because personal accounts disappear when people change jobs and your project stalls with them.

You can also work before access arrives. Public pages can be crawled, brand searches can be reviewed and competitors can be observed, so a delayed login pauses part of the work, not all of it.

Defining Business Goals and KPIs

The most common onboarding failure is a goal that reads like a wish: more traffic. Write the goal on three layers. The business layer is what the company needs, such as qualified inquiries. The marketing layer is what organic search contributes toward it, such as form submissions from organic visits. The SEO layer holds the indicators you can influence, such as impressions and clicks on target pages. Each layer should serve the one above it, so that if an indicator improves while the business layer stays flat, the structure itself reveals the gap.

Two filters help when choosing indicators: can the agency plausibly influence it, and can it be verified in the source system? Rank on its own is a weak target because it shifts with personalization and location. Impressions, clicks and average position in Search Console come from one place and compare cleanly month to month. If link work is in scope, the guide to backlink campaign KPIs shows how to separate metrics that describe the link effort from metrics that describe business results.

Ask for written answers to these questions in the KPI definition:

• Where is each indicator measured and from which date does it count?
• Which pages or page groups are in scope?
• Will branded and non-branded searches be tracked separately?
• What range of change would both sides consider reasonable, and who accepts that range?

The last question prevents the most arguments. Talking about ranges and rhythm instead of fixed numbers keeps the conversation honest. A sample sentence for the agreement: "For the first three months we will track the trend in impressions and clicks on the target page group and interpret it at the end of each month." That sentence contains a measurement commitment without an outcome promise.

The Baseline Snapshot: Starting Measurements and First Audit

You capture a baseline for a simple reason: if you do not record where things stand today, you cannot show what your work changed three months from now. A baseline is a dated photograph that you refresh with the same method throughout the engagement. Change the tool, date range or filter between photos and the comparison stops being fair, so write down exactly which ones you used.

A baseline pack usually includes:

• Search Console impressions, clicks and page-level distribution for the longest period available.
• Analytics organic sessions, landing pages and conversion events.
• The number of indexed and non-indexed pages, with the reasons given.
• Technical basics: status codes, redirect chains and sitemap condition.
• A backlink profile summary: referring domains and main sources, taken from a named tool and dated. Third-party metrics are tool-specific and are not Google values.

The first audit follows. Its purpose is not to fix everything but to sort blockers. Is anything stopping crawling or indexing? Are the pages tied to business goals reachable? Is a template-level error repeating across the site? Sorting findings into three buckets, fix now, plan and monitor, makes the client conversation far easier.

Do not confuse the baseline report with the monthly report. The baseline defines the starting point once; the monthly report continues on a rhythm. For the structure of the recurring document, see the guide on creating a monthly SEO report. This article only covers the starting measurement.

The Competitor and Market Frame

The competitors a client names are often not the sites that actually appear next to them in search results. Build the list from two sources: the client's business knowledge and the search results for the target queries. The first tells you how the client sees the market, the second tells you how a search engine sees it. The difference between the two lists is valuable material for the first meeting.

Deep competitor analysis is not required at kickoff. Noting what page types three to five competitors lead with, which topics they concentrate on and what kinds of link sources they have is enough for a first frame. When you move on to the link side in depth, the step-by-step method in how to do a competitor backlink analysis takes over from there.

Capture the market frame on a single page:

• In what language and with what intent does the audience search: learning, comparing, buying?
• Is there seasonality, and when does demand rise?
• Is the scope local, national or multilingual?
• Which competitors are large brands and which are realistic reference points?

The competitor frame is not a copy list. Its purpose is to see where the client can credibly differ and which gap they could occupy more clearly. The output is a short note that influences which pages and topics move up in the first 30 days.

Content and Link Inventory

An inventory is a count of what the site already owns. For content, a page list with type, last update, target query and current performance is enough. For links, collect the main external sources, the pages receiving them and the anchor texts in use. Reading both together is powerful: a page with many links but thin content, or a strong article with no internal links, is a candidate for an early and low-risk improvement.

Give every page a simple decision tag: keep, update, merge, remove or redirect. These tags are not executed at once. They simply create the priorities for the next stage. When new content is needed, each topic needs a structure the writer can follow, and the guide on how to write an SEO content brief covers that handover.

Suggested inventory columns:

1. URL and page type (blog, product, category, service).
2. Main topic and target query.
3. Last update date and owner.
4. A summary of internal and external links pointing to it.
5. Decision tag and a one-line reason.

On large sites the inventory will not be complete, and that is acceptable. Start with the page groups that matter most to the business goal and plan to widen the scope. A partial inventory that is kept up beats a perfect one that never begins.

Risks: Past Penalties and Earlier Link Work

The most expensive surprise in a new engagement is a burden left by a previous period. The goal here is not to find someone to blame; it is to reduce unknowns. Ask the client directly: what link work did earlier agencies or freelancers do? Were there paid placements, mass directory submissions, comment and forum links, or links within a network of sites? If there is no written record, "we do not know" is also an answer worth logging.

Read three sources together: the manual actions report in Search Console, the referring domain list in a link tool and any old invoices or contracts the client holds. An empty manual actions report does not prove a clean link history; it only shows there is no notice in that report. Quality or spam scores from link tools are tool-specific and are not Google values, so use them as clues for spotting suspicious patterns, not as verdicts.

Keep these lines in the risk register:

• Known past issues and their dates.
• Suspicious link patterns with examples.
• Any large migration or redirect history.
• Contractual or legal obligations, such as an unfinished payment to a previous agency.

The register also decides what you will not do early on. Trying to add new links quickly to a site whose history you do not yet understand is an easy way to enlarge a problem. When link acquisition does start, the operating model in a scalable link building process for SEO agencies is the one to switch on after the first month closes.

The First 30 Day Work Plan

The first 30 days are for strengthening the foundation, not finishing big projects. The plan should be simple enough for one person to track. A weekly structure usually runs like this:

1. Week 1: access, the goal and KPI document, capturing the baseline.
2. Week 2: first technical audit, risk register, first version of the content and link inventory.
3. Week 3: prioritizing findings, competitor and market note, a quick-win list.
4. Week 4: first client presentation, scheduling approved work, the plan for month two.

Put only low-risk, reversible items in the quick-win list: broken redirect fixes, missing titles and descriptions, internal link gaps. High-impact but risky changes, such as a new URL structure or a redirect map, should only be planned in month one. For a brand new site that needs a longer arc, the 90 day link building roadmap for new websites can frame months two and three.

Every line in the plan carries a task, an owner, a dependency and a due date. The dependency column matters most, because projects are usually delayed not by the agency's speed but by an approval or access that sits on the client side. A dependency column shows the source of delay in week one rather than week six.

Reporting Rhythm and Approval Flow

Agree the reporting rhythm at the start, otherwise you will later hear both "why do you tell us so little" and "why so many reports". A simple structure is a short weekly status note, a commented monthly report and a quarterly strategy review. Keep the weekly note to three lines: what was done, what is pending and what needs a decision.

Put the approval process in writing:

• Which changes the agency may make without sign-off, such as correcting a title tag, and which need approval, such as URL changes, new pages or redirects.
• How long approvals are expected to take and what happens when that time passes.
• Who to contact in an emergency, for instance a page accidentally set to noindex.
• Where the change log lives.

The change log is an underused tool. When traffic moves, it answers the question "what changed that week". It is also the practical form of what Google's guidance expects from a provider: someone who will share every change they make and explain the reasoning.

If third-party content placements will run under the client's brand through your agency, also decide how those items appear in reporting; the process described in white label sponsored posts for agencies shows who owns which approval step. Then share the report format with the client in week one and get a yes. Otherwise the first report will be spent debating layout instead of findings.

A Client Information Request Form

The information form is a document you can send in one message after the meeting and collect answers in one place. Keep it short. A client may take a week to return a twenty question form, but can answer eight questions the same day. Split it into required and optional parts.

Required part:

• The main site address, any extra domains and language versions.
• The CMS in use and who manages the site.
• The owner of the Search Console and Analytics accounts.
• Main products or services and priority pages.
• Major site changes in the last two years: redesign, migration, domain change.
• Earlier SEO work and the parties involved.

Optional part:

• Priority competitors and sites the client admires.
• Brand voice, banned phrases and legal notices.
• Seasonal campaign calendar.
• People involved in content approval.

Beside each question, add one sentence explaining why you ask. Putting "to find leftover redirects after a migration" next to the site changes question raises both the quality and the speed of the answers. Unanswered questions are logged and listed openly in the weekly note, so nothing quietly disappears.

Sample Template: SEO Project Kickoff Checklist Table

The table below uses a hypothetical scenario. Imagine a small online shop at "example-shop.example" has just signed with your agency. Every status and note is an example for illustration only; it describes no real client and carries no promise about results or timing.

Keep the table in a shared document. When both sides see who waits on whom in the same place, running the project stops being inbox tracking and goes back to the actual work. Every blank cell becomes an agenda item for that week's call.

Frequently Asked Questions

What should be discussed in the first SEO meeting?

Cover scope, the client's business model, past work, the approval path and the access calendar. Replace outcome and timing promises with a clear statement of which measurements will be shared and how often. Finish by sending a written recap of decisions, owners and dates to the client.

Which accesses should be requested from the client?

Start with read-only access to Search Console and Analytics, then an editor account in the CMS. Ask for admin or server access only when a concrete change requires it and you can explain the reason. Record who granted each access, at what level and for what purpose.

Why are baseline measurements taken at the start?

Without a recorded starting point you cannot show what your work changed, and the two sides may read different numbers. Capture the baseline with one tool, one date range and one set of filters, so later monthly comparisons stay fair and easy to defend.

How do you learn about past link work?

Ask the client directly, request old agency contracts and invoices, and review the referring domain list in a link tool. Check the manual actions report in Search Console too. No single source is conclusive, but together they usually reveal patterns worth a closer look.

What should a first month report include?

Include the baseline summary, first audit findings, the risk register, a quick-win list, a record of changes made and the plan for month two. Rather than big outcome claims, state what was measured, what remains unknown and which client decisions are still pending.

What if the client does not want to give access?

Find out why, because the concern is often security. Offer alternatives such as limited read-only permission, a shared role account or screen-share data pulls. If no access is possible, write down which tasks can still be done and which cannot, and have the client confirm it.

Conclusion and Next Step

A solid start does more for a client engagement than an impressive strategy deck. Aligned expectations, staged and recorded access, a written goal, a dated baseline and a risk register together move the month-two conversation from "where are we" to "what are we doing". Adapt the table above to your own client files and keep a fillable copy ready before the first call.

If a client's first 30 day plan includes content placements on publisher sites, you can run that part through an order flow once the risk register is complete. Browse the options on the guest post packages page, choose what fits, add it to the cart and pay, then follow the seller's approval and the delivery notification, with a dispute path available if delivery does not match the order. Listing those orders as a separate line for the client also keeps the project budget transparent.