How to Write an RFP for SEO Services

An SEO RFP (request for proposal) is the document an organization sends to prospective SEO agencies and consultants so they can propose how they would improve its organic search performance, what it would cost and how long it would take. A good one does more than collect prices. It forces the buyer to decide what it actually wants, gives every bidder the same information, and produces responses that can be compared side by side instead of as a stack of incompatible sales decks.

This guide is for marketing leads, procurement teams, founders and in-house SEO managers who need to hire outside help and want to do it properly. It walks through each section of an SEO RFP in the order it usually appears, with what to include, example wording you can adapt, and the mistakes that most often produce vague or misleading proposals. It finishes with how to evaluate the responses and run a shortlist that ends in a confident decision.

One point runs through all of it: SEO is a slow, dependent discipline. Results depend on your site's condition, your competition, your content and, above all, whether your developers can ship the recommendations. An RFP that hides those realities gets proposals that hide them too.

What a good SEO RFP achieves, and when it is worth the effort

A well-written RFP does four jobs. It clarifies your own goals, because you cannot write the scope section without deciding what success means. It levels the field, because every bidder answers the same questions with the same information. It exposes approach, because a structured response shows how a supplier thinks, not just what it charges. And it creates a record, so that six months later you can check the work against what was promised.

When a formal RFP is worth it

• The engagement is large or long. A multi-month retainer, a program spanning several markets or languages, or work across several sites justifies the effort of a structured process.
• Your organization requires it. Public bodies, regulated businesses and many larger companies have procurement rules that require competitive proposals above a spending threshold.
• Several stakeholders must agree. When marketing, product, engineering and finance all have a say, a written RFP gets their requirements onto one page before suppliers are involved.
• You are replacing a supplier. A structured process makes it easier to compare a new supplier against what the incumbent actually delivered.

When it is not

For a single, well-defined piece of work, such as a one-off technical audit on a modest site, a full RFP can cost more time than it saves. A short brief sent to two or three suppliers, followed by a call with each, is often enough. The same applies when you are choosing between a freelancer and an agency and have not yet decided which model suits you; settle that first, using a guide like freelance SEO consultant vs SEO agency, and then write the RFP for the model you chose.

Keep the whole document proportionate. Suppliers invest real time in a good response, and the best ones decline RFPs that ask for a free strategy, a hundred pages of boilerplate or a response within a few days. A focused RFP of a handful of pages, with clear questions, tends to attract better responses than an exhaustive one.

Background and goals

This section tells bidders who you are and what you need search to do for the business. It is the section most often written as marketing copy, and the one that most needs to be written as a business problem.

What to include

• A short description of the organization, its customers and how it makes money from the website: leads, online sales, bookings, subscriptions or support deflection.
• The business goal behind the search goal. "More organic traffic" is not a goal; "more qualified demo requests from mid-market companies" is.
• Why you are going to market now: a relaunch, a traffic decline, a new product line, expansion into new markets, or dissatisfaction with a current supplier.
• Any constraints that shape the work, such as regulated claims, brand rules or a planned platform migration.

Example wording (illustrative)

We sell scheduling software to independent clinics in the United States. Around half of our new trials start on the website, and we want organic search to become a more reliable source of trials from clinic owners researching software, rather than from people searching our brand name. We are going to market because our organic trial signups have been flat for a year while paid acquisition costs have risen.

Common mistakes

• Listing target keywords instead of business outcomes. It invites suppliers to promise rankings rather than propose strategy.
• Leaving out the reason for going to market. A supplier who knows you are replacing an incumbent over poor reporting will address reporting.
• Hiding known problems. If a migration last year lost traffic, say so; bidders will find it anyway, and your honesty improves their proposals.

Current state and access

Bidders cannot propose sensible work on a site they know nothing about. This section gives them enough context to estimate effort without asking them to perform a free audit.

What to include

• The domain or domains in scope, the approximate number of indexable URLs, and the content management system or framework.
• Recent history: migrations, redesigns, domain changes, known penalties or significant traffic changes, with rough dates.
• Your current team: who writes content, who owns the site technically, how often developers can release changes.
• What data you can share and when: read-only analytics and search console access for shortlisted bidders, or a summary export for everyone.
• Previous audits or strategy documents, if you are willing to share them.

Site size and condition drive cost more than almost anything else. Auditing two hundred URLs is not auditing two hundred thousand, and a site with years of accumulated redirect chains takes longer than a clean one. Development capacity matters just as much: recommendations only count when they ship, and an engagement with no engineering time behind it produces documents, not results. State your release cadence honestly.

Common mistakes

• Giving everyone full data access before a shortlist. It is unnecessary and creates confidentiality risk.
• Omitting development capacity. Without it, bidders cannot tell whether to propose a technical program or a content-led one.
• Understating the size of the site. A proposal priced for a small site will be revised upward the moment the crawl finishes.

Scope of work

The scope section tells bidders what you are buying. It should be specific enough that two proposals can be compared, and open enough that bidders can suggest what you might have missed.

What to include

• The workstreams you expect: technical SEO, content strategy and production, internal linking, site architecture, local SEO, international SEO, digital PR, or a subset.
• What is explicitly out of scope, such as paid search, web development, or content your in-house team will write.
• The division of labor: who writes, who publishes, who implements technical fixes, who approves.
• Markets and languages. Each locale is its own research, its own content and its own technical setup, so list them.
• Whether you want a one-off project, an ongoing retainer, or a project followed by a retainer.

If you are unsure what a retainer should cover, what a monthly SEO retainer should include sets out the usual components. If several sites are involved, say how they relate, who owns each and whether one supplier should cover all of them.

Example wording (illustrative)

In scope: a technical audit of the main domain, followed by a twelve-month retainer covering technical fixes, content briefs, internal linking and monthly reporting. Our in-house writer will produce roughly half of new content from the supplier's briefs; please propose how you would produce the rest. Out of scope: paid search, the help center subdomain, and front-end development, which our engineering team will handle from your specifications.

Common mistakes

• Writing "full-service SEO" and leaving bidders to define it. Every response will define it differently.
• Ignoring content volume. Content is usually the largest line in an SEO budget, and it is the line most often underestimated.
• Forgetting implementation. If nobody on your side can ship technical changes, either put implementation in scope or accept that technical recommendations will wait.

Deliverables and reporting

Deliverables turn scope into things you will receive. This section is where you prevent the familiar outcome of paying a retainer for months and being unable to say what was produced.

What to include

• Named outputs you expect: an audit document, a prioritized fix list, a keyword and topic map, content briefs, published articles, internal linking recommendations, reports.
• The format for each, for example a prioritized backlog your developers can import into their ticketing system rather than a slide deck.
• Reporting cadence and content. Monthly reporting and quarterly strategy reviews are a common rhythm.
• Who attends reviews on both sides, and what decisions each review should produce.

A technical audit is most useful when findings are ranked by expected impact against effort and written for the developers who will act on them. Prioritizing technical SEO fixes explains that ranking in detail, and it is worth asking bidders to describe their own method.

Common mistakes

• Accepting "monthly report" without asking what is in it. Reports full of ranking screenshots and no record of work shipped are common.
• Asking for deliverables your team cannot use, such as a strategy deck with no actionable backlog.
• Not requiring the supplier to report blockers. Work that is stuck waiting for your developers should be visible, not buried.

Measurement and success criteria

This is the section that separates a useful SEO RFP from a wish list. It defines how you will know whether the work is succeeding, and it sets realistic expectations about when you will know.

What to include

• The primary business metric: organic leads, organic revenue, qualified signups or another conversion you can track.
• Supporting search metrics: non-brand organic clicks, impressions and visibility for priority topics, indexation of key pages, and technical health measures.
• The baseline period and how it will be established. An audit and baseline phase typically takes 2–4 weeks.
• How you will separate SEO effects from other changes, such as seasonality, brand campaigns or site redesigns.
• The time horizon for judging results.

Be honest about timing in the RFP itself. Technical fixes can ship from week 3 onward, but first measurable movement typically takes 3–6 months, and anyone promising faster is guessing. Content usually needs 6–12 months before a library starts pulling its weight. Writing this into the RFP signals that you understand the discipline and discourages bidders from overpromising. For a longer treatment, see how long SEO takes to work and setting SEO expectations.

Example wording (illustrative)

Our primary measure is qualified trial signups from non-brand organic search. Supporting measures are non-brand organic clicks to product and comparison pages, and the share of priority pages that are indexed and free of critical technical issues. We will judge early progress on work shipped and technical health, and business results over twelve months. Please describe how you would establish a baseline and how you would report results that are affected by factors outside your control.

Common mistakes

• Setting ranking positions for specific keywords as the success measure. Rankings fluctuate and do not pay bills; conversions do.
• Expecting business results inside the first quarter and judging the supplier on them.
• Including brand search in the headline metric, which rises and falls with advertising and PR rather than SEO.

Budget and timeline

Many buyers leave the budget out, hoping to discover the lowest price. The usual result is a set of proposals that cannot be compared, because each supplier has guessed a different budget and scoped to it. Give a range.

What to include

• A budget range for the engagement, or for each phase, and whether it includes content production.
• The pricing structure you prefer: fixed project fee, monthly retainer, per-word content rates, or a mix.
• Engagement length and key dates: RFP issue, questions deadline, submission deadline, shortlist presentations, decision and start.
• Any internal deadlines that matter, such as a product launch or site migration.

Reference ranges

The table below shows typical US market ranges alongside our own published starting rates, so you can sanity-check a budget before you write it. Our rates are starting prices, not totals; the final number depends on the factors listed after the table. How much SEO costs explains the pricing models, and what a technical SEO audit costs goes deeper on audits.

What moves a budget within those ranges: site size and condition; competition, since some terms are contested by organizations with large teams and long histories, which makes them slow and expensive rather than unwinnable; how much content is needed; development capacity; the number of markets and languages; and the starting position, since a site with existing authority moves faster than a domain registered last month. Content priced well below the market range usually means you are buying volume, not writing.

A worked budget example

This example is illustrative, using our published starting rates, to show how to build a budget range for the RFP. Suppose you want a technical audit, a twelve-month retainer, and supplementary content of 15,000 words over the year (for example, ten articles of 1,500 words each).

• Technical audit: from $3,800.
• Retainer: from $3,200 per month × 12 months = from $38,400.
• Content: 15,000 words × $0.45 per word = from $6,750.
• Total at starting rates: $3,800 + $38,400 + $6,750 = from $48,950 for the year.

That figure is a floor, not a quote; a larger or more troubled site, more markets or a heavier content plan would raise it. Other suppliers will price differently within the market ranges above. The value of the exercise is that it lets you write a realistic range into the RFP instead of a number pulled from last year's budget.

Common mistakes

• Omitting the budget, which produces proposals scoped to guesses.
• Setting a submission deadline of a few days. Good suppliers need time to read, ask questions and think.
• Expecting a start date immediately after the decision, without allowing for contracts, access and onboarding.

Evaluation criteria and weighting

Publishing your evaluation criteria tells bidders what matters to you and makes your own scoring more consistent. Weight the criteria before responses arrive, so a polished presentation cannot quietly rewrite your priorities.

What to include

• The criteria you will score, each with a short description of what a strong answer looks like.
• The weighting, expressed as multipliers or points, so bidders understand relative importance.
• Whether price is scored, and how. Scoring price as one criterion among several avoids automatically choosing the cheapest.
• Who will score, and whether scoring is done independently before discussion.

The scorecard below is an illustrative template. The weights are an example for a business whose main constraint is engineering capacity; adjust them to your own situation. Each criterion is scored from 1 to 5 and multiplied by its weight.

With these weights, the maximum possible score is 75: the weights add up to 15, and 15 × 5 = 75. A bidder scoring 4 on every criterion would reach 60 (15 × 4).

Common mistakes

• Weighting price so heavily that the cheapest bid wins regardless of approach.
• Scoring as a group from the start, so the most confident voice sets everyone's scores.
• Scoring "experience" on logos rather than on work comparable to yours.

Submission requirements

Submission requirements make responses comparable and make your job of reading them manageable.

What to include

• The response structure you want, ideally mirroring your RFP sections so you can compare answers directly.
• A length limit. A cap forces bidders to prioritize and saves you from reading boilerplate.
• Pricing in a set format, separating one-off and recurring costs and listing any assumptions.
• The names, roles and time allocation of the people who will work on the account.
• Two or three references from comparable engagements.
• The deadline, the submission method, a single point of contact, and a questions process in which all questions and answers are shared with every bidder.

It also helps to ask the questions you would ask in an interview directly in the RFP. Questions to ask before hiring an SEO agency is a good source, and asking them in writing gives you comparable answers.

Common mistakes

• Asking for a detailed strategy or free audit in the response. It attracts suppliers who give away shallow work and deters those who charge for proper analysis.
• Answering bidders' questions privately, which gives some bidders information others lack.
• Not asking who will actually do the work. Senior people often present; junior people often deliver.

Legal and contract terms

Stating your key contract terms in the RFP avoids surprises at the end of the process, when the preferred supplier turns out to require terms your legal team will not accept. This is a practical outline, not legal advice; have your own counsel review the contract.

What to include

• Confidentiality. Whether bidders must sign an NDA before receiving data, and whether the RFP itself is confidential.
• Ownership. That you own the deliverables, content, data and any accounts created on your behalf, including analytics and tool configurations.
• Term and termination. Minimum term, notice period, and what happens to work in progress on termination.
• Access and security. How access to your systems is granted and removed, and your requirements for handling any personal data.
• Methods. A requirement that the supplier follows search engine guidelines and does not use tactics that could put the site at risk, such as buying links.
• Subcontracting. Whether the supplier may subcontract work, particularly content writing, and whether it must disclose this.

Common mistakes

• Allowing the supplier to own accounts or tool setups you depend on, which makes leaving painful.
• Signing long minimum terms before any work has been seen. A defined first phase, such as the audit, with a review point is a safer start.
• Leaving content ownership unclear, especially for content written by subcontractors.

If you already have documented SEO standards for your site, attach them and require compliance. If you have not, the first phase of the engagement is a sensible time to write them together.

How to evaluate SEO RFP responses

When responses arrive, resist reading them in order of arrival and forming a favorite. A disciplined evaluation takes a little longer and produces a decision you can defend.

Reading between the lines

The strongest responses usually show that the supplier looked at your site and market, even briefly, and said something specific about it. They explain how they would prioritize, not just what they would do. They name the people involved. They are honest about timing and about what depends on your team. The weakest responses are interchangeable: remove your company name and they could be for anyone.

A worked scoring example

The following is illustrative. Two shortlisted bidders are scored with the weights from the scorecard above (maximum 75).

Bidder B is cheaper and has more impressive experience, but Bidder A shows a better grasp of this particular site and a clearer way of prioritizing work around limited engineering time. Under the weights the team agreed in advance, Bidder A leads. The gap is close enough that the shortlist conversation should test Bidder A's pricing assumptions and Bidder B's approach before a final decision.

Running the shortlist and making the decision

The shortlist stage is where you test what the written responses claimed. Keep it structured, so each shortlisted supplier faces the same questions.

Shortlist presentations

• Ask the people who will do the work to present, not only the business development lead.
• Give shortlisted bidders read-only data access under NDA, and ask them to walk through two or three things they would prioritize first and why.
• Ask each bidder to explain one engagement that did not go as planned and what they changed. How they answer tells you more than a success story.
• Include someone from engineering, who can judge whether the technical recommendations are realistic to ship.

References

Call references and ask specific questions: what was shipped in the first three months, how the supplier handled blockers, whether the reports were useful, and whether the named people stayed on the account. General praise is less useful than a clear answer to any of these.

Deciding and starting well

Re-score after presentations, using the same criteria. Then agree a first phase with a clear review point, for example an audit and baseline over 2–4 weeks, followed by a decision on the retainer. That structure gives both sides a chance to confirm fit before a long commitment. Once the engagement starts, hold to the rhythm of monthly reporting and quarterly strategy reviews, and compare the work against what the RFP asked for.

If you would like to see how we would answer an RFP like this one, our SEO services page describes how we scope, price and report on the work, and the SEO Services articles cover the individual disciplines in more depth.