how to write a seo proposal
How to Write an SEO Proposal Clients Accept
Learn how to write a clear SEO proposal: scope, deliverables, timeline, pricing, and proof—plus wording to reduce scope creep.
If you’ve ever sent an SEO proposal and then watched the scope “mysteriously” expand, you know the real problem isn’t the work. It’s the document. A strong SEO proposal sets expectations, protects your time, and makes it easier for clients to approve.

Start with the client’s goal, not your services
Most SEO proposals start with a list of what you do. Clients don’t buy services. They buy outcomes.
Before you write, get crisp answers to questions like:
- What are they trying to improve? (leads, sales, brand search, local visibility)
- Where are they stuck? (traffic flat, rankings drop, low conversions, technical issues)
- When do they need results? (timing matters for SEO)
Turn the call notes into a one-paragraph summary
In your proposal, lead with a short “understanding” section. This is where you show you listened.
Example wording:
Based on our discussion, your main goal is to grow qualified organic traffic and increase conversions from search. We’ll focus on technical fixes, content that matches search intent, and on-page improvements that support rankings. Because SEO takes time, the first phase will emphasize audit, prioritization, and foundations.
That paragraph does two things: it frames the work and sets realistic timing.
Include a scope you can defend (and a scope you won’t do)
SEO proposals fail when the scope is vague. “We’ll do keyword research and optimize pages” is not a scope. It’s a wish.
Use clear deliverables with boundaries. Also add a short “not included” list. This prevents the awkward “can you also…” email.
What to include in an SEO deliverables section
A solid SEO scope usually covers:
- Audit & prioritization (what you found and what you’ll fix first)
- On-page SEO (title tags, meta descriptions, headings, internal links, content improvements)
- Content plan (topics mapped to intent, briefs, or outlines)
- Technical SEO (crawl/indexing issues, site speed basics, structured data when needed)
- Reporting (what metrics you’ll track and how often)
Add “not included” wording to stop scope creep
You don’t need to be harsh. You just need to be explicit.
Example “not included” bullets:
- Link building beyond basic outreach/relationship tasks (unless you choose to offer it as a separate line item)
- Content writing or design work for pages not listed in the deliverables
- Ongoing dev support unless we agreed to an hourly/dev retainer line
- Changing client CMS settings without access and approvals
The proposal should protect both sides. Clear boundaries reduce friction and make approval easier.
Use a timeline that matches how SEO actually works
SEO moves in phases. Your proposal should reflect that.
A common structure:
- Phase 1 (Weeks 1–2): audit, keyword & competitor scan (basic set), recommendations, and plan
- Phase 2 (Weeks 3–6): implement prioritized technical/on-page changes and publish first content (if included)
- Phase 3 (Ongoing): optimization, internal linking updates, content iteration, and monthly reporting
Don’t promise rankings. Promise process and improvements.
You can’t control Google. But you can control execution.
Instead of:
- “We’ll rank #1 for X.”
Use:
- “We’ll implement on-page and technical changes based on audit findings and publish content briefs targeting identified intent clusters.”
- “We’ll track keyword visibility trends and organic traffic changes and adjust recommendations monthly.”
If you want to use “expected outcomes,” keep it framed as possibilities, not guarantees.
Write the pricing section like a menu, not a mystery
Clients want to know what they’re paying for. Make it easy to say yes.
Choose one of these pricing structures:
- One-time SEO project: audit + roadmap + initial on-page implementation + a set deliverables
- Monthly SEO retainer: ongoing optimization, content planning, reporting, and selected execution
- Hybrid: setup fee (audit + plan) + monthly retainer for implementation and iterations
Example pricing layout (copy-friendly)
Here’s a clean structure:
- SEO Proposal Setup (one-time): audit, prioritization, keyword & intent mapping, and deliverables plan
- Phase Implementation (one-time or first month): technical/on-page changes you’ll complete (list them)
- Monthly SEO Management (ongoing): reporting + additional optimizations + content briefs (if included)
If you bill by deliverable, show the package boundaries. If you bill by hours, list what hours cover and what would trigger extra work.
Add a “client responsibilities” section (this is where deals break)
A lot of SEO work depends on client inputs. Don’t skip this.
Client responsibilities might include:
- Provide access: Google Search Console, Google Analytics (or analytics alternative), CMS/admin access
- Share current goals and any brand/compliance constraints
- Approve deliverables by a set deadline
- Provide existing content (if content optimization is included)
- Confirm who will implement changes if you’re not the one updating the site
If you need developer support, state how requests are handled.
A short approval SLA reduces delays
Example:
- Client will review drafts within 3–5 business days.
- If the client misses the review window, the timeline moves accordingly.
This keeps the project from turning into “we’ll just wait forever.”
Include proof without bragging (and show you understand SEO constraints)
SEO proposals should include credibility, but not generic marketing.
Add 2–4 items max:
- A brief case study summary (what problem, what you did, what changed)
- Links to relevant work (audit sample, content samples, reporting example)
- Your process steps (audit → plan → implement → report)
Avoid over-claiming.
“Evidence” that helps close deals
You can also include small evidence pieces:
- A sample audit outline
- A sample deliverable screenshot (blur or redact if needed)
- A sample reporting layout (metrics + narrative)
Clients don’t want a mystery. They want to know what “done” looks like.
Build a proposal section for reporting and communication
Reporting is not just charts. It’s how clients stay confident.
Define:
- Frequency (monthly, biweekly for active implementation, etc.)
- Metrics you’ll show (traffic trends, impressions, clicks, rankings/visibility, conversions if tracked)
- What you’ll do with the data (recommendations, next steps)
Add a communication cadence too:
- Weekly async updates during implementation weeks
- Monthly review call (optional)
- Response time expectations (ex: 1–2 business days)
SEO proposal template you can reuse
Copy this into your proposal doc and fill in the brackets.
1) Project overview
Goal: [increase qualified organic traffic and conversions]
What we’ll do: [audit, technical/on-page fixes, content plan, implementation (as scoped)]
How we’ll measure progress: [traffic/visibility trends, conversions if available, and monthly reporting]
2) Discovery & audit (Phase 1)
Deliverables:
- SEO audit summary: [technical, on-page, content, internal linking]
- Keyword & intent mapping: [primary themes / clusters]
- Prioritized action plan: [top issues and what we’ll tackle first]
3) Implementation (Phase 2)
Deliverables (scoped):
- Technical SEO: [list specific items]
- On-page SEO: [list specific changes or page templates]
- Content plan: [brief outlines / topics / content schedule]
4) Ongoing management (Phase 3)
Monthly deliverables:
- Reporting + insights
- Optimization work: [what you’ll do each month]
- Content briefs (if included): [count or scope]
5) Timeline
- Phase 1: [dates or week count]
- Phase 2: [dates]
- Phase 3: ongoing monthly
6) Pricing
- Setup fee: [$]
- Implementation: [$] (one-time or first month)
- Monthly retainer: [$] / month
7) Client responsibilities
- Provide access and timely approvals
- Confirm who will implement changes (if not you)
- Review drafts within [X] business days
8) Out of scope / assumptions
- [Not included items]
- Assumptions: [CMS access, dev availability, tracking setup]
9) Acceptance & next steps
- If approved, we’ll start within [X] business days.
- First deliverable: [date]

Common SEO proposal mistakes (and what to write instead)
Here are the errors that most often slow approvals or cause scope fights.
-
Mistake: “Keyword research + SEO optimization” with no specifics.
- Fix: Name deliverables and list the types of changes you will make.
-
Mistake: Promising rankings by a date.
- Fix: Promise actions and reporting. Frame outcomes as trends, not guarantees.
-
Mistake: No “not included” section.
- Fix: Add a short out-of-scope list so surprises don’t become unpaid work.
-
Mistake: Reporting is vague (“we’ll track results”).
- Fix: Define frequency and the metrics you’ll include.
-
Mistake: No mention of client approvals or access.
- Fix: Add a simple review timeline and list access requirements.
If you want a quick self-audit of how you’re running the business side (process, billing, and follow-through), use the Freelance Business Check to spot common blind spots before they cost you deals.
Make it easy for the client to approve
A proposal shouldn’t make people work to say yes.
End with a clear call to action:
- “Confirm you approve the scope above by replying ‘Approved.’”
- “Once invoice is paid, we’ll deliver Phase 1 within [X] days.”
- “If you want changes, list them and we’ll adjust the scope and timeline.”
Also include a “change control” sentence:
- Any new requests outside the scope will be quoted separately.
That line alone can save you from months of unpaid extra work.

Related reading: How to Get SEO Clients: A Simple, Repeatable System · How to Write a Copywriting Proposal That Wins
Conclusion: your SEO proposal is your project plan
When you write a good SEO proposal, you’re not just selling. You’re documenting the plan your client is hiring you to execute. Clear scope. Real timeline. Defined responsibilities. Honest reporting.
If you want to keep proposals, contracts, invoices, and client messages all in one place, tools like Jolix can help you run the workflow more systematically, so follow-ups and approvals don’t slip.
