SEO Proposal for Client Sample

An SEO proposal is the document you hand a prospective client before they commit. It is not a price list; it is a plan. The best ones start with where the client is now — their traffic, their conversion rate, their biggest technical gaps — and then show where they could be in six months. For example, I recently pitched a local roofing company. Their site had 40 visits a day, a bounce rate above 70%, and no organic leads. I mapped each recommendation to a predicted outcome: fixing core web vitals could lift rankings for "roof repair [city]" by three positions, adding content for service pages could bring in an extra 30 visits a month, and building three local citations could push their Google Maps listing into the top three. Each line item had a number. That is what separates a proposal from a brochure. I also make sure the proposal answers one question the client is afraid to ask: "What happens if it does not work?" I handle it by showing a traffic baseline and realistic timelines — typically 3–4 months before measurable growth. No SEO proposal should promise page one results in two weeks. Google Search does not work that way, and the client will lose trust the moment that promise breaks. Keep the language plain. Instead of "we will conduct semantic keyword clustering," say "we will group related search terms so each page targets a clear topic." The proposal is the first test of your communication. [SEO](/seo/) is a long game, and the proposal must reflect that.

You need a written proposal when the project is large enough to require approval from someone who was not on the discovery call. A one-page email quote works for a £500 technical audit. For a £2,000 monthly retainer, you need a proposal that a CFO can read and say yes to. It also matters when you are up against competitors. In a pitch situation, the proposal is your chance to show you listened. I once competed for an ecommerce site and learned that the other agencies sent generic slide decks. I sent a four-page document that listed their three biggest technical issues — uncovered from a free Ahrefs crawl — and how I would fix each one. I won the account because the specifics proved I had done the work before the sale. The counter-argument is that a proposal takes time to write, and some freelancers prefer a call and a verbal agreement. That works for repeat clients, but for a new lead a proposal sets boundaries. It defines what is in scope and, more importantly, what is out. Without it you get scope creep. I also use the proposal to set the expectation that [SEO strategy](/seo-strategy/) is a marathon, not a sprint. I include a section on algorithm volatility so the client knows that a [Google ranking](/google-ranking/) dip after an update is normal, not a sign of failure. That upfront honesty reduces churn later. Where it matters most is when the client has been burned by a previous provider. That proposal must acknowledge their pain without trashing the competitor. A strong [SEO plan](/seo-plan/) includes a thorough [SEO checklist](/seo-checklist/) and follows [SEO best practices](/seo-best-practices/).

My first SEO proposals were templates from a Google Doc I found online. I changed the client name and sent them off. Every one of them failed. The clients could tell I had not studied their business. One even replied saying "this looks like it was written for a different company." That stung. The lesson was brutal: a generic proposal is worse than no proposal. I also used to list services without deliverables. I wrote "keyword research" as a line item but did not say how many keywords, which tools, or when the list would be delivered. Clients would ask "what exactly am I paying for?" and I would scramble to clarify on email. That eroded confidence. Another mistake was quoting a flat project fee without explaining what happens after the project ends. A client paid me £3,000 for a one-time optimisation, then expected three months of ongoing management for free. That was my fault for not defining the boundary. I also fell into the trap of promising traffic numbers. I once projected "50% increase in [organic SEO](/organic-seo/) traffic in three months" based on a competitor analysis, but the client's site had thin content and no authority. The growth was more like 10%, and they were disappointed. Now I frame everything as "estimated increase based on current baseline" and I never guarantee a specific percentage. The proposal is a contract of expectations, and vague promises become liabilities. My SEO service offering improved once I started treating the proposal as the first deliverable.