15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Proposal

Free SEO Proposal Template

An SEO proposal covers the audit and retainer scope, what gets delivered each month, who does the work, what it costs, and payment terms.

SEO Proposal template preview

Language:

en

Category:

Last updated:

October 2026

Share template

Search traffic drops, a redesign rolls out, or growth stalls, and the hard part becomes agreeing on SEO work that’s more than a tidy report. This SEO proposal spells out what gets checked first, what changes get made across crawling, templates, and tracking, and how monthly reporting ties movement back to specific work, set in process blue with print-ink green accents under Zilla Slab headings and Inter body text.

The reader starts with The short version, so the first thing they see is the outcome in plain terms and how the work gets verified. From there the proposal names the people behind the work, shows the kind of technical SEO and on-page changes that show up in real engagements, then gets specific about what “month to month” means: setup audit findings, a developer-ready ticket list, a keyword-to-page map, an on-page change log, content briefs, and a monthly SEO report that connects Search Console movement to what changed.

  • The short version Summarises the crawl, keyword-to-page mapping, and reporting approach, so the buyer knows what gets changed and how progress gets proved.
  • How we work Explains the monthly rhythm from baseline and setup through technical fixes and verification, so the work doesn’t read like guesses.
  • Setup audit findings Defines what setup produces in writing, including audit findings, a technical fix ticket list, and a keyword-to-page map that gets updated as priorities change.
  • On-page change log Details how title, heading, and internal link changes get tracked alongside content briefs and the monthly SEO report, so each month has a record of what was implemented.
  • Getting started Holds the acceptance step and the fee summary, and points to the access needed for Search Console, analytics, and templates before setup begins.

The proposal ends with What it costs and Getting started: you replace the price for the single Core retainer line item, send it, and the client signs online so the work and billing can start on agreed terms.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in an SEO proposal

PartWhat it covers

The short version

Opens with the outcomes, the evidence-first approach, and how monthly reporting ties movement back to specific site changes.

About us

Describes the team and the kind of situations clients arrive with, with an emphasis on showing exact pages changed and before-and-after results.

Who you will work with

Clarifies who stays involved from kickoff through monthly work, so the client knows who to contact when decisions are needed.

Team

Breaks down responsibilities across strategy and planning, technical SEO fixes in crawls and templates, and content SEO briefs and internal linking.

Selected work

Introduces examples of recent engagements, so the work reads like a retainer that mixes technical fixes, page work, and content planning.

Portfolio

Gives concrete examples like crawl and index cleanup, template rule rewrites, and a keyword-to-page map with publishing briefs.

How we work

Explains how each month starts from data, moves through implementable changes, and then checks what moved to shape the next plan.

Setup audit findings

Lists the setup deliverables in writing: audit and tracking issues by impact, a developer-ready fix ticket list with acceptance checks, and an updated keyword-to-page map.

On-page change log

Defines the running record of on-page work, plus the content briefs and monthly SEO report that connect results to what changed.

What it costs

Holds the priced table for the retainer, separating one-off setup from the ongoing monthly level.

Getting started

Carries the signature and fee summary, and describes the steps after acceptance, including the setup invoice split and access requests.

Payment

Sets the setup and retainer invoicing schedule, payment due window, what counts as setup, and what access and developer time the work can require.

Changes to scope

Covers how scope changes get priced, what gets measured and reported, ownership of deliverables, and the cancellation terms.

Who it is for

SEO consultants, search marketing agencies, and technical SEO specialists quoting a setup audit plus an ongoing retainer for a site that needs measurable movement.

The proposal in full

The short version

You’ll have a site Google can crawl and understand, a clear map of which pages target which searches, and month-by-month reporting that ties ranking and Search Console movement to specific changes on your site.

We’ll start by finding what is blocking crawling, indexation, and tracking, then we’ll line each key page up to a keyword that matches what it should win. You’ll see what moved, what we changed, and what we’re doing next each month.

We run the work from evidence first. We read Search Console and server logs to see what Googlebot is doing, clean up indexation and crawl paths, and then map keywords to the pages that should rank. After that we fix templates, headings, and internal links so the site supports the content you publish, not fights it.

About us

We’re a three-person SEO team, and you’ll work directly with the people doing the work. Haruka Nishida leads the strategy and the monthly plan, Kenta Moriyama handles crawl, indexation, and template fixes, and Mika Okamoto turns keyword research into content plans your team can publish without guessing.

Most clients come to us after a redesign, a platform change, or a drop they can see in Search Console. We don’t hide behind a tidy report. We show the exact pages we changed, the exact issues we fixed, and the before-and-after in Search Console and rankings, so you can tell what happened each month.

Who you will work with

You’ll see the same three names from kickoff through the monthly work, and you’ll know who to message when something needs a decision.

Team

Haruka Nishida, SEO lead. Haruka sets the keyword and page plan, keeps the work moving week to week, and writes the monthly notes so you can see what changed and why.

Kenta Moriyama, Technical SEO specialist. Kenta lives in crawls, logs, and templates. He fixes the things that stop Googlebot reaching pages, and he flags the developer work you need with clear, testable steps.

Mika Okamoto, Content SEO strategist. Mika turns research into publishable briefs. She maps topics to pages, plans internal links, and keeps the content focused on searches that can realistically win.

Selected work

Here are a few recent engagements that show the mix of technical fixes, page work, and content planning you’ll get on an SEO retainer.

Portfolio

Crawl and index cleanup. Search Console showed thousands of low-value URLs being crawled and indexed. We tightened indexation rules, fixed canonical signals, and cleaned internal links so Google spent its crawl budget on the pages that matter.

Template rewrite rollout. Key pages were sharing near-identical titles and H1s because the template was doing the work. We rewrote the rules once, rolled them across the site, and then checked the impact by page group in Search Console.

Keyword map and content plan. The site had content, but pages were competing with each other and missing obvious searches. We built a keyword-to-page map, set priorities, and shipped briefs the team could publish without rewriting the strategy each time.

“We finally knew what changed each month, and rankings followed.”

Marketing manager, a growing services company

How we work

We keep the work simple to follow. Each month starts with what the data says, then we make a short list of changes that can be implemented and verified, and we finish by checking what moved so next month isn’t a repeat of the same guesses.

1. Setup and baseline Week 1 We confirm Search Console access, analytics tracking, and how you want conversions counted. Then we pull a baseline of rankings, indexed pages, and top queries so you can see movement against a starting point, not against a feeling. 2. Technical fixes Weeks 1-2 Kenta reviews logs and crawl data to spot blocked paths, indexation leaks, and template issues that spread across hundreds of pages. You’ll get a short list of fixes, the exact URLs or templates affected, and a check we can run to confirm each fix landed. 3. Page and intent work Weeks 2-3 Haruka and Mika map priority queries to the pages that should rank, then we adjust titles, headings, internal links, and on-page structure to match search intent. If two pages are competing, we pick a winner and change the site so Google can tell which one it is. 4. Monthly cycle Monthly We start the month by reviewing what moved in Search Console and rankings. Then we implement the next batch of fixes and on-page updates, and we finish with a monthly update that lists what changed, where it changed, and what we’re doing next.

Setup audit findings

A written list of technical and tracking issues, grouped by impact, with the exact pages or templates affected. Delivered after setup so you can see what we’re fixing first.

TECHNICAL FIX TICKET LIST

A developer-ready list of fixes with steps and acceptance checks. Updated as we work through the backlog, so you can track what’s done and what is waiting on dev time.

KEYWORD-TO-PAGE MAP

A map of priority queries to the pages that should rank, including notes on intent and conflicts. Updated when priorities change or new sections are added.

On-page change log

A running log of title, heading, and internal link changes, with the page URLs. Updated throughout the month so you can point to exactly what was implemented.

CONTENT BRIEFS

Briefs your team can write from, including target query, headings, internal links to add, and what the page is competing against. Delivered each month based on the plan we agree.

MONTHLY SEO REPORT

A monthly summary that leads with ranking and Search Console movement, then lists the work completed and the next month’s plan. Delivered at the end of each month.

What it costs

The setup is a one-off cost for Week 1 through Week 3. After that, you pick the monthly level that matches how much we can implement and how much developer time you can give us. Prices are per month.

Priced items

Getting started

If you want us to start the SEO retainer, the fastest path is signing and getting us the access we need for setup week.

1. Sign this proposal to confirm the scope and start date. 2. We’ll send the setup invoice for 40% and request access. 3. We book the kickoff call and start the baseline and audit.

Signature

Fee summary

Payment

Setup is invoiced 40% to start and 60% when we hand it over. The SEO retainer is invoiced at the start of each month. Every invoice is payable within 7 days.

What counts as setup. Setup covers Week 1 through Week 3: baseline and audit findings, the initial technical fix ticket list, the first keyword-to-page map, and the first on-page change log. We hand these over in writing.

Access we need. Before we start, you’ll give us access to Google Search Console and analytics, plus CMS access or a staging link where we can review templates. If we can’t see data or pages, we can’t diagnose or verify fixes.

Developer time. Some fixes need developer time on your side. We’ll label each ticket as template, content, or configuration, and we’ll tell you the level of effort we expect. If developer time is limited, we’ll queue work by impact.

Changes to scope

If the site changes during the month, we’ll update the fix list and the plan. If the change adds work beyond the SEO retainer capacity, we’ll price the extra work in writing before we start it.

What we measure. We report on Search Console and rankings, then list what we implemented, where we implemented it, and what we’re doing next. SEO results move with indexing and competition, so we can’t promise a fixed ranking by a date.

Ownership. Once setup is paid in full, you own the setup audit findings, fix ticket list, keyword-to-page map, on-page change log, content briefs, and monthly reports we produce for your site. Your logins and data stay yours.

Cancellation. You can stop the SEO retainer with written notice before the next invoice date. If a month is already invoiced, we’ll deliver that month’s planned work up to the capacity of the retainer and close out with a report.

Questions about this proposal template

What should an SEO proposal include?

An SEO proposal usually covers the scope of setup and ongoing work, what gets delivered each month, who does the work, what it costs, and the payment terms. This one also describes the specific artifacts clients can expect, like a fix ticket list, a keyword-to-page map, an on-page change log, and a monthly report tied to Search Console movement.

What will get changed first on a site?

Early work focuses on finding what blocks crawling, indexation, and tracking, then turning that into a prioritised list. This proposal describes setup audit findings plus a developer-ready technical fix ticket list with affected templates or pages and acceptance checks.

How do you show what work got done month to month?

Clear reporting connects outcomes to actions, not just charts. This proposal includes an on-page change log with URLs and a monthly SEO report that leads with ranking and Search Console movement, then lists completed work and the next plan.

How long does SEO take to show results, and what gets measured?

SEO movement depends on indexing and competition, so a proposal usually avoids promising a fixed ranking by a date. This one says reporting comes from Search Console and rankings and ties movement back to what was implemented and where.

Do SEO fixes need developer time?

Technical fixes can require developer time when issues live in templates, crawling paths, or site rules. This proposal calls that out and describes tickets with clear steps and acceptance checks, so developer work stays testable and trackable.

Will you write the content or only provide recommendations?

Some engagements need writing and some need briefs a team can publish from. This proposal includes content briefs with target queries, headings, internal links to add, and what each page competes against, which supports in-house writing without guessing.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away