An SEO price means little without its scope and responsibilities. This guide helps buyers compare proposals and identify excluded work. The example numbers are invented for arithmetic only; they are not Meridian prices, market averages or a performance forecast.
01Describe the purchase before requesting a rate
State whether you need a diagnostic audit, implementation support, content delivery or ongoing consulting. Include the website size, known constraints and who can deploy changes. A quote for recommendations cannot be compared fairly with a quote that includes development, writing and production verification unless those differences are visible.
- Name the intended deliverables
- List access and platform constraints
- Identify your implementation capacity
02Normalize the proposal units
Ask what a page, audit or monthly task actually includes. Ten metadata rows and ten fully researched pages are different deliverables. Clarify the review rounds, sample size, source requirements and handoff format. Record optional work separately so an attractive headline fee does not hide the effort needed to make the recommendations usable.
- Specify acceptance criteria
- Check quantities and exclusions
- Distinguish recurring work from one-time setup
03Calculate the full illustrative budget
Suppose an invented proposal costs $1,000 for an audit and $500 for implementation support. If your own developer needs eight hours at a hypothetical $100 per hour, the direct planned total is $2,300 before other costs. This example shows why external fees and internal effort belong in the same comparison; it does not estimate your project.
- Label every assumption
- Include internal review and development
- Keep taxes and optional expenses explicit
04Ask who owns release and verification
A proposal should explain who edits the CMS, approves copy, deploys code and checks the result. If the provider only supplies advice, budget for an implementer and a verification pass. Keep customer dependencies separate from supplier deadlines so a delayed release is not automatically described as missing SEO research or writing.
- Assign implementation ownership
- Define production acceptance checks
- Document access and approval dependencies
05Examine evidence and promises
Request relevant work samples and ask how progress will be reported. Google advises buyers to be cautious about guaranteed first-place rankings. A credible proposal can define deliverables, communication and the basis for an estimate without guaranteeing a search outcome. Evaluate the quality of the proposed work rather than treating a low price or large page count as value by itself.
- Ask about measurement permissions
- Review methods and exclusions
- Keep forecasts separate from commitments
06Agree a decision point
Choose a bounded first package and a review date tied to actual delivery. Record what has to be completed before expanding the engagement. Later ROI analysis should use observed revenue, costs and attribution assumptions, not the proposal fee alone. Bring your current scope and implementation constraints to a consultation if you need help structuring the comparison.
- Save the agreed scope
- Track actual costs against assumptions
- Use the inquiry form for project-specific discussion