SEO Costs Explained: A Guide to Audits, Implementation and Content Scope
Published:
Last Updated:
Authors: Shusaku Yosa
SEO proposals are difficult to compare when one includes an audit and another includes the work to publish changes. A monthly fee or an article price tells you little until you know what will be examined, what will change and who will implement the recommendations.
This guide helps website owners and marketing teams define an SEO brief before requesting a quote. Rather than presenting a universal market price, it explains the work that changes the cost and how to compare proposals on the same basis.
Separate four kinds of SEO work
Work | Deliverables to discuss | Scope question |
|---|---|---|
Audit and priorities | Evidence, affected URLs and recommended actions | Will the review cover all pages or a sample? |
Implementation | Agreed changes and a record of verification | Does it involve CMS editing or development? |
Content | Briefs, drafts, revisions and optional publishing | Who provides expertise, interviews and source material? |
Ongoing support | Analysis, priorities and an agreed cycle of improvements | Are production and implementation included? |
A lack of traffic does not automatically mean that a site needs more articles. Existing pages may be difficult to discover, overlap in purpose or fail to answer important customer questions. An initial review can help distinguish those situations before you commit to a production volume.
What changes the cost?
Site coverage and complexity
List the sites, languages and page types in scope. A corporate site, a product site and a publication may have different owners and systems. Page count matters, but so do templates, publication workflows and whether access requires authentication. A sample-based review should state how the sample is chosen and what it cannot establish.
Who can make the changes
Your team may be able to edit copy but need a developer for templates, redirects or tracking. Specify which tasks are available internally and which require outside help. A useful proposal identifies the owner of approval, testing and production release. Recommendations without an implementation owner can remain unfinished even when the audit is sound.
Content inputs and review
An article based on supplied product documentation has a different workflow from one requiring interviews or specialist review. Provide accurate product details, customer questions and material that can be published. Decide whether the quote includes an outline, drafting, factual review, images, CMS entry and publication checks. See the content cost and scope guide when production is the main requirement.
Small edits versus development
Changing a title in an existing CMS is different from migrating a site or rebuilding a template. Ask for the boundary between routine edits and separately assessed development. Confirm the test environment, release approval and how changes can be reversed. The label “technical SEO” does not by itself define those responsibilities.
The ongoing decision process
For recurring support, specify what happens after reporting. Who selects the next action, prepares the material and publishes the change? Agree on the pages and business questions to review, rather than treating a report as the entire service. Search visibility and business outcomes should have separate definitions.
Two hypothetical briefs
Brief A: an internally maintained corporate site. The company wants an audit and a prioritized list of changes. Its team will edit pages and release updates. The requested deliverable should connect each issue to affected URLs, supporting evidence and a way to check the change. New articles can be considered after the initial review.
Brief B: a service site that has not been maintained. The company needs help with planning and agreed changes to existing pages. It supplies product expertise and approves claims. If new articles are required, writing, CMS entry and release responsibilities should be named separately. A major system change should not be hidden within a routine-edit allowance.
These are examples for defining work, not fixed Ficilcom packages or quoted prices. Use the closer scenario as a starting point, then document your own inclusions and exclusions.
What to prepare before requesting a quote
- Website URLs, languages, business purpose and target customers.
- The pages or topics causing concern, including when the issue became noticeable.
- Available Search Console and GA4 access, with known measurement limitations.
- The editing and development work your team can handle.
- Source material, content requirements and specialist approval needs.
- Expected deliverables, deadlines and the process for approving extra work.
Share only the access needed for the assessment. Agree on permission levels and a secure sharing method rather than sending broad credentials in an initial inquiry.
How to compare the proposals you receive
Compare coverage, deliverables, content, implementation and recurring work line by line. Ask whether tools, meetings, revisions and handover are included. Confirm contract duration, cancellation and ownership of the resulting material. A lower fee may reflect a smaller scope rather than better value for the work you need.
Make reporting useful by agreeing on a baseline and on what can be verified. A search position, an organic landing session, an inquiry and a customer are different units. A tracking event is not automatically a successful sale, and an unmeasured outcome should remain unknown.
Frequently asked questions
Can I request improvements without adding articles?
Yes, existing-site improvements and new content are separate decisions. Ficilcom's SEO estimator allows the additional article count to be zero. If research later suggests a content gap, assess its purpose and production requirements before adding it to the brief.
Can an SEO provider guarantee a ranking or a completion date for results?
A delivery date for agreed work is different from a promise about search results. Google's guidance on hiring an SEO warns against ranking guarantees. Define the work that will be delivered and the indicators you will observe separately.
Does an English estimate page mean that English content has the same production terms?
No. The current SEO estimator describes its article unit as 3,000–5,000 Japanese characters using supplied material. Translation, English production requirements and the applicable service conditions need separate confirmation. Do not treat the displayed article unit as an English word-count allowance.
Check an estimate using your support scope
Ficilcom's estimator asks for the request scope and number of sites, with conditions for page coverage, additional articles, minor edits and technical work. Read the current standard scope and exclusions before interpreting the result. It is a preliminary estimate, not a ranking forecast or a binding quotation.
Check an SEO estimate by support scope
To discuss a result, copy the conditions and breakdown into the inquiry form and add any unresolved requirements. Displaying an estimate does not automatically send an inquiry. The final scope and price are confirmed after reviewing the request.
