How Agencies Should Price Schema Markup Services

Schema markup is one of the most underpriced services in agency portfolios. The work is significant: auditing, reviewing, deploying, monitoring, and governing structured data across a live website is not a two-hour task. But agencies routinely charge for it as if it were a two-hour task because they have not productised the process.

The fix is not to charge more for the same thing. It is to package the right thing — a machine visibility service with a defined audit, implementation, and monitoring layer — and price each layer at the margin it actually generates.

Why underpricing happens — the four patterns

Pattern 1: Schema is bundled into SEO retainers at zero incremental price

The client is paying for 'SEO' and the agency includes schema setup as part of that. Nobody has defined what schema setup means, how long it takes, or what the ongoing maintenance looks like. When the work expands, there is no mechanism to bill for it.

Pattern 2: Schema is treated as a one-time code task

A developer writes JSON-LD for the homepage and a few service pages. The work is billed as development hours. Nobody budgets for monitoring, drift detection, or future updates. When the site changes and schema drifts, the agency does the fix for free because there was never a maintenance agreement.

Pattern 3: The client only sees code, not risk reduction

When the agency explains schema as 'adding structured data to your website', the client mentally prices it as a small technical task. When the agency explains it as 'ensuring your business information is machine-readable so you remain eligible for rich results and AI recommendations', the client prices it as a strategic service.

Pattern 4: No productised delivery process

Without a defined process, the agency cannot estimate reliably, cannot scope consistently, and cannot explain the value clearly. Unpredictable scope creates margin risk and client uncertainty.

The three-layer pricing model

The agencies that price schema work sustainably use a three-layer model that separates audit, implementation, and monitoring into distinct billable engagements.

Layer 1: Schema Audit and Roadmap

Scope: a structured audit of the client's current schema coverage, accuracy, and drift. Output: a scored report by page type with prioritised remediation recommendations.

• Typical scope: 20–100 page service business website
• Typical time investment: 4–8 hours with tooling support
• Positioning: discovery engagement that creates a clear baseline and roadmap
• Entry price point: €800–€2,000 depending on site size and client segment
• Value proposition: the client sees exactly where machine understanding is weak, in a format they can present internally

Layer 2: Schema Implementation

Scope: review, approve, deploy, and QA schema for all prioritised pages from the audit roadmap. Deployment via script tag with version control.

• Typical scope: 5–20 pages per implementation sprint
• Typical time investment: 6–16 hours depending on site complexity
• Positioning: controlled deployment with human review at every field — not a plugin drop
• Entry price point: €1,500–€4,000 per sprint
• Value proposition: schema that is accurate, content-backed, and verifiable — not generic plugin output

Layer 3: Schema Monitoring and Governance

Scope: recurring scans, drift detection alerts, and monthly health score reporting. Schema updates triggered by content changes.

• Typical scope: monthly monitoring for priority pages
• Typical time investment: 2–4 hours per month with tooling support
• Positioning: the maintenance layer that protects the implementation investment
• Entry price point: €400–€800 per month
• Value proposition: ensures schema does not silently decay after content updates, protecting rich result eligibility and AI discoverability

In conversations with agencies using Loopful, the monitoring retainer is consistently the easiest layer to sell after a successful implementation. Clients who have seen the audit report understand that drift is a real risk — and they want someone to watch it.

How to scope and estimate reliably

Reliable scoping requires a site assessment before quoting. The variables that affect time are:

• Number of distinct page types requiring different schema types
• Existing schema state — starting from nothing is easier than cleaning up bad plugin output
• CMS complexity — how difficult is deployment, and does the client need a script-tag approach?
• Content change velocity — high-velocity sites need tighter monitoring loops
• Number of locations if local schema is in scope

A 30-minute pre-engagement schema scan with Loopful produces a coverage and accuracy report that makes scoping precise. This removes the guesswork from estimates and demonstrates expertise before the proposal is submitted.

Positioning the pitch to win the engagement

The client meeting framing that works: 'Right now, machines that are evaluating whether to include your business in search results and AI recommendations are seeing incomplete or outdated information. We are going to audit exactly what they see, fix the gaps, and set up monitoring so the problem does not come back.'

What does not work: 'We are going to add schema markup to your website.' That is a task description, not a value proposition.

For the client-facing ROI narrative, see How To Explain Schema ROI to Non-Technical Stakeholders. For the operational delivery workflow that supports these three layers, see Agency Playbook: Deliver Schema at Portfolio Scale. Loopful is built specifically for the agency delivery model described here.