You Were Quoted for Schema Markup. What Are You Buying?

The line on the proposal

"Schema markup implementation, $1,800."

Google's own structured data gallery lists 33 rich result features. A plumbing company is realistically eligible for about seven of them. Nearly every schema quote is sold inside that gap, and almost none of them name which seven.

This post is not an argument about whether schema is good. It is a purchase decision. What physically arrives, how you check it without a developer, what it plausibly moves, and what a fair number looks like for a site your size.

What physically gets delivered

Strip the language off the proposal and a schema engagement produces four artifacts. Only one of them is code.

The first is an audit of what is already there. This matters more than agencies admit, because a large share of sites already have markup they never bought. JSON-LD appears on 36.6% of desktop home pages according to the HTTP Archive's 2025 Web Almanac, and most of it arrived by plugin default, not decision. If your site runs Yoast, Rank Math or Squarespace, you almost certainly have Organization and WebPage markup right now.

The second is a map: which page template gets which schema type. Home page gets Organization. Service pages get Service. Location pages get LocalBusiness. That map is the actual thinking in the engagement.

The third is the code itself. Google recommends JSON-LD over the older Microdata and RDFa formats, calling it the easiest solution to implement and maintain at scale. It is a script block in the page head. It is invisible to visitors.

The fourth is evidence that it works, which is the artifact most often missing.

That list is the right one, and we would add one item to it: ask where the code physically lives. Markup buried inside a proprietary plugin leaves with the agency. Markup in your theme or tag manager stays with you.

Verify it yourself in two minutes

You do not need a developer to find out whether you got what you paid for. You need a browser and two free tools, both of which Google names in its own documentation.

The step most people skip is the third one, and it is the one that catches overselling. The Rich Results Test only knows about features Google renders. The Schema Markup Validator knows about everything. If your agency deployed nine schema types and Google only recognizes three of them, both tools are telling the truth and only one of them is telling you what you bought.

The 33 features Google renders, and the seven you can get

Schema.org's vocabulary contains 823 types and 1,529 properties. Google renders 33 of them as rich results. A local service business qualifies for a much smaller set than either number suggests.

The review row is where quotes go wrong most often. Google's review snippet documentation, last updated 24 July 2026, states that if the entity being reviewed controls the reviews about itself, pages using LocalBusiness or any Organization structured data are ineligible for the star review feature. That kills the single most commonly sold schema deliverable in local SEO: the homepage testimonial widget marked up with AggregateRating. It is ineligible by policy, not by accident, and no amount of clean code changes that.

If a proposal promises stars in your search listing from testimonials on your own site, that is the line to strike. Genuine review visibility comes from the profiles themselves, which is a different job covered in how to get more Google reviews.

Use this graphic on your site

Free to republish with a link back to this page. Copy the embed code:

<a href="https://timpsonmarketing.com/blog/is-schema-markup-worth-it"><img src="https://timpsonmarketing.com/assets/infographics/is-schema-markup-worth-it.svg" alt="Layered stack diagram of schema markup deliverables, from crawlable page access at the base up through identity, navigation, descriptive and oversold layers" width="1200" style="max-width:100%;height:auto"></a><p>Graphic by <a href="https://timpsonmarketing.com/blog/is-schema-markup-worth-it">Timpson Marketing</a></p>

What you are not buying

The honest boundaries are all documented, and Google publishes every one of them.

Schema is not a ranking input. Google's general structured data guidelines state that using structured data enables a feature to be present and does not guarantee it will be present. The sharper evidence is in the penalty language on the same page: a structured data manual action costs a page its rich result eligibility and does not affect how the page ranks in Google web search. If schema were a ranking lever, the penalty would touch rankings. It does not touch rankings, which tells you which layer of the system it lives on.

FAQ schema is not a SERP play anymore. Google's documentation changelog records the FAQ rich result being switched off on 7 May 2026 and the documentation removed on 15 June 2026. FAQPage is still valid schema.org and keeping it causes no harm. It just produces nothing in Google Search, so it is not a deliverable worth paying for.

And it is not an AI lever. Ahrefs ran a rare controlled design here, tracking 1,885 pages that added JSON-LD against 4,000 matched control pages and finding no meaningful lift: minus 4.6 percent in AI Overviews, plus 2.4 percent in AI Mode, plus 2.2 percent in ChatGPT. Google's AI features documentation says the same thing in plainer terms, that there is no special schema.org structured data you need to add to appear in AI Overviews or AI Mode.

We are not relitigating that here. The full evidence review lives in is AI SEO worth paying for and the mechanics of how the engines actually choose sources are in where AI chatbots get their data. For a purchase decision, one sentence is enough: do not pay a premium for the AI line on a schema quote.

There is a legitimate long game, and it is worth stating fairly rather than dismissing.

That is a real position from someone who has built this for a living, stated in 2024 and still the strongest case for descriptive markup. It is also an argument about future optionality, not about leads this quarter. Price it accordingly.

What a fair price actually looks like

Schema pricing is not mysterious once you convert it into hours, because that is all it is.

Two independent surveys give you the rate. Ahrefs polled 439 SEO professionals and found agencies averaging $98.90 an hour at the top of their quoted tiers, with $75 to $100 the most common band. Backlinko surveyed more than 300 professionals and put typical monthly SEO cost at $1,000 to $2,500. Both are practitioner polls rather than random market samples, and both are directionally consistent with the technical specialist range published elsewhere.

Now the hours. This estimate is ours, built on those published rates, and you should treat it as a benchmark to argue with rather than a quote.

A typical local service site has about five page templates: home, service, location, about, and blog post. JSON-LD is generated by the template, so 60 location pages built from one template are one unit of work, not sixty. Audit runs one to two hours. Template mapping, one to two. Writing and deploying across five templates, three to six. Validation and Search Console setup, one to two. Call it six to twelve focused hours, which at $80 to $150 lands roughly between $500 and $1,800.

So the $1,800 line item is not automatically wrong. It is at the top of a defensible band, and it is only worth it if the audit, the map, the validation evidence and the documentation all arrive with it. Paid as pure code delivery it is roughly double the market.

Watch the two ends. At the bottom, plugin installs sold around $99 are real and are sometimes the correct purchase for a five page site. At the top, enterprise platforms like Schema App do not publish a price at all, requiring a custom quote, a one time setup fee and a 12 month minimum term. That is a legitimate product for a 10,000 page catalog. A 40 page HVAC site does not need a knowledge graph platform, and quoting one is a scoping failure.

If your quote is priced per page, ask why. If the answer is that each page is hand coded, you are paying for a method nobody should be using in 2026. Wider context on where this fits in a real budget is in how much local SEO costs.

Five questions that separate an engagement from a line item

Ask these before you sign. The answers take a competent provider ninety seconds and expose an incompetent one immediately.

Question five is the one that saves the most money. Schema is largely a one time build with occasional maintenance when your services or locations change. A recurring fee is defensible when it covers monitoring, new page types and fixing what your page builder breaks on update. It is not defensible as rent on code that was written once.

Question four matters more than it looks. We have inherited sites where every schema block vanished the day a plugin license lapsed, and the owner had paid four figures for markup he never owned.

And if a proposal guarantees rankings or guaranteed rich results, that is the end of the conversation. Google's own guidance for hiring an SEO says plainly that nobody can guarantee a number one ranking. The same logic applies to rich results, which Google explicitly declines to guarantee even with correct markup.

When schema is genuinely worth paying for

Here is the ranking we would actually give an owner.

Buy it when your business has real structure to describe: multiple locations, multiple services, staff with credentials, events, jobs, or video. Markup earns its keep by removing ambiguity, and a business with genuine complexity has more ambiguity to remove. Multi-location businesses get the most out of it, which connects directly to building location pages properly.

Buy it as part of technical cleanup, not as a standalone product. Correct Organization and LocalBusiness markup belongs in the same work order as your titles, canonicals and internal links. Sold alone at a premium it is usually margin.

Do not buy it expecting a ranking change. If Google Maps visibility is the goal, the Whitespark survey of 47 local search experts put primary Google Business Profile category at the top of the local pack factors, and schema is not near it. That work is covered in ranking higher on Google Maps.

The honest summary: schema markup is worth it as cheap, durable search hygiene that makes your pages eligible for better listings and easier for machines to parse correctly. It is not worth a premium, it is not a ranking lever, and it is not the thing standing between you and the phone ringing. Judge the invoice by the artifacts, not by the adjectives, and use the two minute check on whatever you already paid for before you buy any more. If you want to know whether the rest of your retainer is producing anything, how to tell if your SEO agency is working applies the same test to everything else.