Schema markup is one of those things that sounds like it belongs to developers and therefore gets skipped by the people it would help most. It is worth twenty minutes of your attention, because it is one of the few technical jobs on a small business site that is genuinely quick, genuinely useful, and almost never done.
Schema markup is structured code added to a web page that describes what the page is about in a format machines can read reliably. It does not change how the page looks. Search engines and AI assistants use it to understand what a business is, what it sells, and where it operates, which makes the page easier to display in rich results and easier to cite in an AI answer.
What it actually is, without the jargon
A human reading your contact page understands instantly that "412-555-0100" is a phone number and "Pittsburgh, PA" is where you are.
A machine reading the same page sees a string of characters next to another string of characters. It can guess, and it is usually right, and guessing is not the same as knowing.
Schema removes the guess. It is a small block of code, invisible to visitors, that says explicitly: this is an organisation, this is its name, this is its phone number, this is the city it serves, these are the services it offers.
That is the whole concept. The rest is knowing which types to use.
Why it matters more now than it did five years ago
For a long time schema was mostly about rich results, the star ratings and FAQ dropdowns that show up under a search listing. Useful, occasionally, and not urgent.
What changed is that AI assistants now assemble answers from sources rather than sending people to links. Before an assistant will cite you, it has to be confident about who you are. That confidence comes from finding consistent, unambiguous information about your business, and schema is the least ambiguous form that information can take.
Two businesses with identical content, one with proper schema and one without, are not equally citable. The one that has spelled out what it is has removed a reason to be skipped.
The four types most small businesses need
There are hundreds of schema types. You need four.
| Type | Where it goes | What it establishes |
|---|---|---|
Organization | Every page, site-wide | Your business exists, its name, logo, and official profiles |
LocalBusiness | Home and location pages | Where you are and what area you serve |
Service | Each service page | What you sell and who provides it |
FAQPage | Anywhere you answer questions | Question and answer pairs, quotable directly |
If you add one, add Organization. If you serve a defined geographic area, add LocalBusiness second. FAQPage is the one with the most immediate upside for AI citation, because it hands an assistant a clean question and a clean answer with no interpretation required.
A worked example
Here is a complete, minimal Organization block. It goes in the <head> of every page, and you change the values to yours.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "ProfessionalService",
"name": "Your Business Name",
"url": "https://yourbusiness.com/",
"logo": "https://yourbusiness.com/logo.svg",
"description": "One clear sentence describing what you do and who for.",
"email": "hello@yourbusiness.com",
"telephone": "412-555-0100",
"address": {
"@type": "PostalAddress",
"addressLocality": "Pittsburgh",
"addressRegion": "PA",
"addressCountry": "US"
},
"areaServed": { "@type": "City", "name": "Pittsburgh" },
"sameAs": [
"https://www.linkedin.com/company/yourbusiness",
"https://www.facebook.com/yourbusiness"
]
}
</script>
That is genuinely all it takes. Paste it, change the values, done.
The field almost everyone leaves out
sameAs.
It is an array of links to every profile you control: LinkedIn, Facebook, your industry directory listing, a founder's personal site. It looks like an afterthought and it is doing something specific and important.
It tells a machine that all of these separate things are the same business. Without it, your website, your LinkedIn page, and your directory listing are three entities that happen to share a name. With it, they are one entity with three profiles, and that is a meaningfully stronger signal.
Fill it in properly. It costs one minute and it is the highest-return field in the whole block.
Four mistakes that make schema silently useless
Marking up something that is not on the page. Schema is supposed to describe visible content. Adding FAQ markup for questions that do not appear on the page is a guidelines violation and it can get rich results suppressed for the whole site. Do not do it.
Inconsistency with everything else. If your schema says one phone number and your footer says another, you have made things worse rather than better. The schema should match your website, your Google Business Profile, and every directory, exactly. This is the same NAP consistency problem that breaks local rankings, and schema is part of it.
Adding it and never validating. A single missing comma breaks the whole block, and it fails silently. Nothing on the page looks wrong. It simply stops working.
Multiple conflicting blocks. Some site builders inject their own schema. If yours does, you may now have two Organization blocks disagreeing about your business name. Check the source of a live page rather than assuming.
How to check it took
Two free tools, two minutes.
Google Rich Results Test. Paste your URL. It shows what Google can read and flags errors. If it reports nothing found, your block has a syntax error or is not on the live page.
Schema.org validator. Stricter, and better for catching structural problems the Google tool tolerates.
Run both after any change. Then run them again in a month, because site updates and plugins have a way of quietly removing things.
What to expect from it
Being straight with you: schema on its own will not move your rankings. It is not a ranking factor in the way people sometimes claim, and a page with excellent schema and thin content will still lose to a page with better content.
What it does is remove ambiguity. It makes rich results possible, it makes your business easier to resolve as an entity, and it makes your content easier for an assistant to quote with confidence. Those are real and they compound, and they cost you one afternoon.
Think of it the way you would think of labelling boxes in a warehouse. It does not make the inventory better. It makes finding the right thing dramatically more reliable.
Where to start
Add the Organization block to every page. Fill in sameAs honestly. If you serve a local area, extend it to LocalBusiness with your city and service area. Then, if you have an FAQ page, add FAQPage markup for the questions already on it.
Validate. Then leave it alone until something changes.
If your site is built on something that makes editing the head awkward, this is a reasonable thing to hand to whoever maintains it. It is a thirty minute job for someone who has done it before, and it is part of what the content and SEO service sets up.
Eric Howard
Founder of SteelAIQ and a chief marketing officer with more than twenty years running marketing organizations across enterprise software, manufacturing, and consumer brands. Based in Pittsburgh.
