Schema markup is a structured data vocabulary that lets a website state facts about itself in a form machines can parse directly: what the business is, where it operates, what it sells, and what its pages contain. Search engines and AI systems read it to confirm what your visible content claims. This page defines the types a local business actually uses, in plain language, and it exists so you can check what an agency tells you about schema against what schema actually does.
LocalBusiness
LocalBusiness markup is the machine-readable identity card of the company: name, address, phone, hours, and geographic coordinates. It is the schema version of the NAP consistency your listings need, and it must state exactly what the website and the Google Business Profile state. A LocalBusiness block that disagrees with the visible page is worse than no block, because it manufactures the identity conflict it was supposed to prevent.
Service
Service markup describes an individual offering: what it is, who provides it, and where it is available. A roofing company marks up roof repair and roof replacement as separate services rather than one generic entry, because machines match specific queries to specific services, and a business that only declares “roofing” is asking the system to guess.
areaServed
areaServed states the geography a business or a service covers, by city, county, or region. It is how a company in one city tells systems, in confirmable form, that it works across three counties. It is a statement, not a spell: declaring a county you have no presence, reviews, or content for does not create rankings there. It confirms a footprint that has to exist first.
FAQPage
FAQPage markup identifies question-and-answer pairs on a page so systems can retrieve each answer as a self-contained passage. It rewards content that was already written as direct answers, which is why every FAQ on this site opens with a statement that survives being quoted alone. Marking up evasive answers gets you accurately represented as evasive.
What schema does, and does not do
Schema markup creates eligibility, not advantage. Correct markup lets systems confirm your facts and present your content in richer formats. It does not outrank better content, substitute for consistency work, or function as a ranking lever on its own. Formatting is hygiene: failing it can disqualify you, and passing it earns you the right to compete on the things that actually decide the result. Any agency selling schema as the reason you will rank is selling the checkbox, not the outcome.
How to check your own markup
Two checks anyone can run today: paste a page into Google’s Rich Results Test to see what machines parse from it, and then compare every parsed fact against what the visible page says. Matching facts and no errors is a pass. Facts that appear in the markup but nowhere on the page are a liability, not a bonus. The source of truth for every type and property is schema.org, and the source of truth for what Google supports is Google’s own structured data documentation. If a claim about schema is not confirmable in one of those two places, treat it as marketing.