An SEO request for proposal should make competing responses comparable. The outline below is an editable procurement method, not a statement of Meridian pricing or contractual terms. Adapt its inputs and acceptance criteria to your organization.
01Describe the business decision
Open with the website, audience, target market and problem the engagement should address. Provide enough context to distinguish an audit, advisory work and implementation. Keep confidential analytics or credentials out of an openly shared brief; describe how approved suppliers can receive appropriate access.
- List stakeholders and decision owner
- State scope and exclusions
- Explain constraints and existing work
02Request a scoped approach
Ask each supplier to explain the proposed workstreams, required inputs, dependencies and assumptions. Invite them to identify what they cannot conclude before access. This is more useful than asking every bidder to promise the same traffic increase before reviewing the site.
- Separate diagnosis from implementation
- Request an example task sequence
- Require assumptions to be labelled
03Define the deliverables
For an audit, an example requirement could be a URL-level issue log with evidence, priority, action and acceptance steps. For content, ask for briefs, reviewed copy, sources, metadata and publication responsibilities. Specify useful formats and review boundaries rather than judging proposals only by page or word counts.
- Name each deliverable and user
- Include an acceptance example
- State who approves publication
04Make commercial responses comparable
Ask bidders to separate included work, exclusions, optional tasks, client effort and pricing assumptions. Do not infer a package’s value from the headline fee alone. Clarify ownership of accounts, content and working files through your normal procurement and legal review.
- Compare the same scope
- Identify change-request handling
- Refer contractual questions to the responsible reviewer
05Use a documented evaluation sheet
An illustrative scorecard might compare business fit, proposed method, evidence quality, delivery clarity and collaboration requirements. Choose the criteria and weights before reviewing bids. Ask for permission-backed examples and references rather than treating unsupported logos or projected results as proof.
- Record evidence behind each assessment
- Use consistent questions across suppliers
- Keep unresolved points in the decision log
06Plan the first handoff
Before work begins, confirm the agreed scope, named owners, access process, first deliverables and review dates. Establish how recommendations become approved tasks and how completed changes are verified. The RFP becomes useful when its requirements survive into the actual working plan.
- Retain the final agreed brief
- Assign implementation and verification roles
- Document how scope changes are approved