What Is Schema Markup and Does Your Website Actually Need It?
A new website goes live, and everything visible on it looks right: the service list, the phone number, the areas covered. Weeks later, someone on a marketing call asks whether the schema markup was added, and the room goes quiet, because nobody on it has ever seen schema markup, knows where it would sit, or knows what it would change if it were there.
That silence is fair. Schema markup never appears on the page a customer reads. It sits in the source code, in a block written for software, and it labels the facts a page already states in ordinary sentences. Nothing about it changes how your site looks, which is exactly why it goes missing at launch and then stays missing for years.
What Schema Markup Is, in Plain Terms
Structured data is a standardized format for providing information about a page and classifying its content —for example, on a recipe page, the ingredients, the cooking time and temperature, and the calories. Two words in that description carry the load. Standardized means the labels come from a shared vocabulary that search engines already recognize, so nobody has to invent their own. Classifying means the page ceases to be a block of prose and becomes a set of labeled facts.
For a home-service business, the labeled facts are ordinary ones: the business name, the type of business, the service area, the hours, the phone number, the individual services offered, and the page each belongs to. None of it is new information. Every item is printed somewhere on the site. The visitor already sees all of it. The markup restates it in a format software can parse without guessing which number on the page is a phone number and which is a job number.
Three Formats Exist, and Google Names One
There is more than one way to write it. There are three accepted formats, and JSON-LD is the one recommended for ease of implementation and upkeep. All three are treated as equally valid, provided the markup itself is valid and properly implemented. The reason JSON-LD is favored is maintenance, not raw power, and the format you can maintain will outlast the format you cannot.
The difference lies in where the code sits. JSON-LD is a self-contained block in the page source, separate from the visible HTML, so it can be corrected on its own instead of reworking the page around it. Microdata and RDFa are woven into the visible tags themselves, so editing the markup edits the visible page itself. For a business that changes services and hours more often than it changes layout, that separation is the practical argument for JSON-LD.
Choosing the Sub-Type That Matches Your Trade
The most specific applicable business sub-type should be used, for example Restaurant, DaySpa, or HealthClub rather than a generic label. For a trade business, that means the difference between labeling a page as a business in general and labeling it as the trade you actually run. Labeling a page as a business in general adds nothing a search engine cannot infer. The shared vocabulary includes named subtypes for most trades, and a specific label gives a system something narrower to match against a particular question.
Trades rarely fit one label. Multiple types can be specified together as an array, listing sub-types such as Electrician, Plumber and Locksmith side by side for a business that offers several services. Nothing in the shared vocabulary forces a single label. A contractor who does drain work, water heaters, and repiping is describing one business with several sub-types, and the markup has room for every one of them.
The Rule That Trips Up Most Contractor Sites
The most common defect in contractor markup is not a missing label. It is a label for something the page never shows. The rule is simple: markup should never describe information that is not visibly present on the page, even when that information is accurate elsewhere. Read that against a real service page. If the markup lists twelve services and the page names four, the extra eight services will not get you found for them. Markup is a label on visible content, and content that is not on the page cannot be labeled.
Correct, valid markup still does not buy a placement in a result. Even fully valid structured data is not guaranteed to produce any visible feature in search results. Eligibility and appearance are two separate things, and the second is never promised.
There is also a failure mode worth naming. When markup violates the guidelines, a page can receive a structured data manual action; when that happens, the structured data on that page is ignored, although the page can still appear in search results.
Who Owns the Markup After the Site Goes Live?
Markup is generated by the site itself, not typed onto a page. In most builds, it lives in a template or a plugin setting, which means one person edits the words a customer reads while a different person, or a different tool, controls the block that labels them. That split is the point where markup goes stale. A service gets added to the visible page and never to the type array. Someone changes the hours in one place, and the page keeps declaring the old ones. Nothing on the screen looks wrong, so nothing in the business prompts a fix.
So the question of who owns it has a staffing answer before it has any other kind. Somebody has to be named to update the markup when the business changes, and the changes that matter are changes to the facts the markup labels: a new service line, a new coverage area, new hours, a new phone number. Ask whoever maintains the site which of those changes flows into the markup automatically and which needs a hand edit. If you cannot get a clear answer to that, you have found the gap.
Checking the Markup Before and After It Ships
Two checks matter, and they happen at different times: run the Rich Results Test during development, and check the Rich Results status reports after deployment, since pages can break after launch due to templating or serving issues.
The split matters because markup that validated at launch can break later, when a template changes and nobody looks at the source again. Open the page source, find the markup block, and read what it claims about the business it describes.
Frequently Asked Questions
No. They are separate systems. Markup lives in your website's code and describes the page it sits on; the profile is a record held by Google in its own dashboard. Correcting one leaves the other alone, and they can drift apart without you noticing.
Not in any way you or a visitor would notice. A JSON-LD block is plain text in the page source, and browsers do not render it. What can slow your site is a plugin that rebuilds markup, and that is a hosting question, not a markup one.
Markup describes the page it sits on, so a homepage block only describes your homepage. Sites usually carry a business-level block sitewide plus page-level markup on the pages that earn it, which for a contractor usually means your service pages and any page you built around a specific customer question.
They fight, quietly. A theme and a plugin can each output their own business block, leaving a single page with two entries that disagree about the same business. Before you add a second source of markup, check what your current site already outputs, because the fix is usually to switch one off, not add another.
Partly. Search Console's rich result status reports cover pages Google has processed, and its URL Inspection tool renders a single page of your site and lists the structured data found on it. Neither confirms that a rich result will appear for a page of yours. Both stop short of that, at what the crawler actually found.
This is the property contractors most often get wrong. The aggregate rating property is meant for sites that collect reviews about other local businesses, a directory model, not a business's own site. Your own site publishing your own star rating is not that case, and marking your rating up anyway falls outside recommended use.
Get a schema check — see what your pages actually declare. Green Thumb Local helps home-service businesses get found, get chosen, and get more calls with local SEO, Google Business Profile optimization, and content. Call (480) 360-0101.
