SEO Proposal

An SEO proposal is not a brochure. It is a sales document and a work blueprint rolled into one. I have seen agencies send a generic PDF with 'we do on-page optimisation, link building, and technical SEO' and wonder why the prospect never signs. The problem is that the proposal did not answer the one question every business owner is asking: What will this do for my revenue? A good proposal starts with a brief executive summary that frames the client's current situation — maybe their organic traffic has flatlined or they are losing visibility to a competitor. Then it presents findings from a mini audit: technical issues like missing meta descriptions or slow page speed, plus competitive gaps that show why [SEO Strategy](/seo-strategy/) matters for them specifically, and why [Organic SEO](/organic-seo/) is the right channel for their market. The scope of work lists deliverables by month — content briefs, technical fixes, reporting — and explicitly states what is excluded. Pricing is transparent: retainer, setup fee, or project-based. Most importantly, the proposal ties every task to a business outcome: 'We expect to increase qualified leads by 30% over six months based on current conversion rates and search volume.' That is what converts a prospect into a client. If your proposal does not include a specific number that the client can hold you to, go back and add one. I learned this the hard way after losing a £5,000 project because my proposal promised 'improved rankings' and the client said, 'So what?'

The proposal matters most when the prospect has been burned before. I have had clients tell me they paid an agency £2,000 a month and got nothing but a PDF report full of green arrows. For that audience, the proposal must prove that you understand their business, not just their keywords. A second scenario is when the engagement involves multiple stakeholders — a marketing director who needs to justify the spend to a CFO, for example. The proposal becomes the document they use internally to get approval. That is why including a timeline with milestones matters. If you show that month one will be a technical audit and month two will be content optimisation based on findings, the CFO sees a plan, not a promise. A third scenario is competitive bidding. When the prospect is comparing three agencies, the proposal that includes a mini audit — real data about their site's crawl errors, top pages, and backlink profile — instantly wins trust. I always include a table comparing the client's domain rating to top competitors, sourced from [SEO Best Practices](/seo-best-practices/) tools, and I structure the proposal as a [SEO Service](/seo-service/) contract that makes the scope clear. The key is customisation. I once saw a proposal that had the wrong company name in the header. That is a death sentence. The proposal is not a template; it is a proof of work. If you cannot spend two hours analysing the site before writing the proposal, you are not ready to work with that client. The proposal should act as a [SEO Checklist](/seo-checklist/) for both you and the client, so you both know exactly what will happen each week. When I started treating the proposal as a contract preface rather than a sales pitch, my close rate went from 30% to 60%.

My first mistake was treating the SEO proposal as a one-off task. I would write it, send it, and forget about it. Then when the client asked three months later why we were not doing something I had not mentioned, I had no document to point back to. Now I see the proposal as the roadmap for the entire engagement. I reference it in every monthly check-in. Second, I used to copy a template from an online guide and swap the client name. That was lazy. Every proposal needs a unique selling proposition tailored to the client's specific situation — maybe they are losing traffic from a Google core update, or their e-commerce category pages are not indexing. Generic advice like 'improve site speed' does not differentiate you. Third, I focused on vanity metrics: keyword rankings and traffic volume. Those matter, but they are proxies. The client cares about leads and revenue. I once wrote a proposal that promised 'first page rankings for 20 keywords'. The client signed, but when we got to page one for those keywords and saw no increase in phone calls, they were disappointed. I should have tied the keywords to search intent and conversion rate. Now I always include a section on measurement: how we track calls, form submissions, and e-commerce transactions using [Google Search](/google-search/) Console and Analytics. Finally, I underestimated the importance of exclusions. I did not list what was out of scope, so the client kept asking for extra content, extra link outreach, extra reports. Now I write: 'This proposal covers technical fixes and content optimisation only. Link building is not included unless added as a separate retainer.' That has eliminated scope creep entirely. The proposal is not a wish list; it is a contract for your [SEO Business](/seo-business/).