Schema Markup in Plain English (No Code Required)
Schema markup explained for business owners: what structured data actually does, the five types a small Australian site needs, and what it will never do.
Search for an emergency electrician in your city and look at the results, not the pages. One listing shows a breadcrumb trail instead of a raw URL, the business name rendered properly, opening hours attached. The next is a blue link, a grey URL and a description Google chopped mid-sentence. Same industry, same suburb, same size operation.
That difference usually isn't budget, authority or backlinks. One site bothered to label its facts in a format machines read without guessing. That label is schema markup — simultaneously the cheapest technical job on a website and the most oversold line item in Australian SEO proposals.
The position, unpopular with anyone selling structured data as a service: schema buys eligibility, not ranking. It does not move a page from position 40 to position 4. It qualifies a page to be displayed differently once it already ranks. Worth having, just not the lever owners are told it is — and a chunk of what still gets quoted as schema work was switched off by Google years ago.
The label on the tin
A web page is written for humans. Everything a machine knows about it is inferred: it reads "Open 7am–5pm Mon–Fri" near a phone number and guesses these are trading hours. Usually it guesses right. On a page with three locations, two phone numbers and a careers section, it guesses wrong.
Schema markup removes the guessing. It's a shared vocabulary — published at schema.org, founded in 2011 by Google, Microsoft and Yahoo with Yandex joining soon after, mostly so the search engines stopped inventing incompatible versions of the same idea — letting a page state its own facts explicitly in a small block of code, in a format called JSON-LD. Stripped back, it reads like this:
{
"@type": "LocalBusiness",
"name": "Northside Electrical",
"telephone": "+61 3 9000 0000",
"address": "142 Sydney Road, Brunswick VIC 3056",
"openingHours": "Mo-Fr 07:00-17:00"
}
That's the whole mystery: a form the page fills out about itself. You're not adding information the page didn't have, you're restating what a human can already see in a way that can't be misread. Hence the one rule governing everything below — if it isn't visible on the page, it doesn't belong in the markup. Break it and you've moved from labelling to lying, and Google has a penalty for that.
What it actually changes for a visitor
What a searcher sees before clicking is the whole point, and where the exaggeration happens.
That last row is the honesty test. Ask an agency what FAQ schema will get you; if the answer involves dropdowns in the search results, they're selling a 2021 brochure.
The five types a small business actually needs
The vocabulary has hundreds of types. A normal Australian business needs five, two of them conditional.
Organization or LocalBusiness, once, sitewide. LocalBusiness if customers come to a premises or you serve a defined area, Organization if you're national or online-only. Running both hands Google two competing descriptions of the same company.
BreadcrumbList, on every page that isn't the homepage. Automatic in any decently built template.
Article or BlogPosting, on posts and guides, populated from real publish and update fields rather than typed by hand.
Product, only if you sell things, and only with prices and stock matching the page.
FAQPage, where you genuinely have questions and answers on the page — not as a dropdown play, but because it makes the structure legible to anything parsing it.
The rest is situational: Event for venues, JobPosting for recruiters, Course for training providers. Service markup gets sold hard and delivers almost nothing visible. Google's structured data documentation lists which types tie to a real search feature — a shorter list than the sales pitch.
What schema will not do
It will not rank you. Google's guidance is consistent: structured data makes a page eligible for search features, it isn't a signal you accumulate. A slow page with thin copy and nothing linking to it is a slow page with thin copy, marked up. If the fundamentals aren't in place, markup is decoration on a problem.
It will not always increase traffic either. A rich result that answers the question in full gives the searcher a reason not to click — the mechanism behind rankings holding steady while traffic falls. Markup showing your opening hours saves a visit you didn't need; markup showing your whole answer saves one you wanted. Label the facts that qualify a visitor, keep the reasoning that earns the enquiry behind the click.
The AI claim, specifically
Structured data is being resold hard as the way to get recommended by AI assistants. Be sceptical of the strong version: large language models don't consume schema through Google's rich-results pipeline, and no published mechanism turns a JSON-LD block into a mention in a ChatGPT answer.
The defensible version is narrower and still useful. Assistants ground answers in pages they can parse, and unambiguous facts reduce the chance a model confuses you with a similarly named business in another state. State your name, address, service area and phone number identically across your markup, your Google Business Profile and the directories listing you, and there's less room to get it wrong.
That's entity consistency, not ranking. The fuller picture is in our piece on showing up in AI answers. Anyone charging a retainer to "optimise your schema for AI" should be made to name the mechanism.
The review stars trap
Star ratings are the rich result owners ask for by name, and the one most likely to get a site punished.
Google's review snippet guidelines exclude self-serving reviews — ratings about a business, collected by that business, marked up on its own site. The testimonials on your homepage, gathered through your own feedback form, aren't eligible for stars no matter how genuine they are. Stars generally come from third-party review platforms carrying their own markup.
Plugins don't always respect that. A common pattern is a schema plugin injecting an AggregateRating invented at install time, or averaged from reviews appearing nowhere on the page. Two things follow. Google has a manual action named for spammy structured markup, applied where markup misrepresents page content. And there's a second regulator in the room: the ACCC treats fake reviews as misleading conduct under Australian Consumer Law.
Publishing a rating you made up, in machine-readable format, on your own domain, is the only kind of SEO cheating that arrives pre-formatted for the regulator.
Check yours, then specify the fix
A fifteen-minute audit of what you already have
You can audit your own markup this afternoon without touching code.
- Run the Rich Results Test on three URLs: homepage, best service page, a blog post. It shows what Google can parse and which features each qualifies for. Empty on all three means you have none. For the wider vocabulary rather than Google's feature list, validator.schema.org is the second opinion.
- Read the Enhancements reports in Search Console. The same check across the whole site, errors flagged on live URLs. If those reports are unfamiliar, our plain-English guide to Search Console errors covers what's urgent and what's noise.
- View the page source and search for
application/ld+json. Count the blocks. Two Organization blocks with different phone numbers is the most common finding on WordPress sites where a theme and an SEO plugin both emit markup.
The rest of the front end is worth a look in the same sitting — our free site audit covers speed and the technical surface markup sits on, which decides whether a page ranks well enough for a rich result to matter.
What to ask your developer for
Specified properly, this is a small job. Ask for JSON-LD generated from your CMS or data layer rather than pasted in by hand — hand-pasted markup goes stale the first time you change your phone number. One Organization or LocalBusiness block sitewide, duplicates removed. Breadcrumbs on every non-homepage. Article markup from real post fields. No AggregateRating unless the ratings are real, visible and eligible. And validation built into the deploy, so markup is checked every release rather than once at launch.
On a well-built site that's a half-day inside the template layer, not a four-figure deliverable. It should arrive as part of a properly built small business website — our custom builds start at $8,000 AUD, and structured data is part of that, not an upsell against it.
If a proposal prices "schema markup implementation" as a headline item, ask which types and what feature each is eligible for. A specific answer means they know the field. A vague one means they're installing a plugin and charging you for the afternoon.
FAQ
What is schema markup in simple terms?
It's a standard set of labels that let a web page state its own facts in a format machines read without interpreting. Rather than hoping Google works out that a line of text is your trading hours, the page declares it in a hidden block of code. It adds nothing for human visitors; it restates what's already there so software can't misread it.
Does schema markup improve Google rankings?
No, not directly. Google's position is that structured data makes pages eligible for search features — breadcrumbs, product prices, review stars — rather than acting as a ranking signal. The indirect benefit is real but limited: a result that displays more usefully can earn more clicks at the same position. That's presentation, and it won't rescue a page that isn't ranking already.
Do I need a plugin for schema markup?
On WordPress or a similar CMS a plugin is the usual route and it's fine, provided you check what it emits. The recurring problem is duplication — a theme and a plugin both publishing business details with different phone numbers, leaving Google to choose between two versions of you. On a custom-built site the markup is generated from the site's own data in the template layer, so there's only one source.
How do I check if my website has schema markup?
Paste the URL into Google's Rich Results Test. It reports what markup exists and which search features the page qualifies for. For a whole-site view, the Enhancements section of Search Console lists valid items and errors across every indexed page. The manual method works too: view the page source and search for application/ld+json.
Can schema markup get my business penalised?
Yes, if it misrepresents the page. Google has a manual action for spammy structured markup, applied where markup describes content that isn't there — invented ratings, prices that don't match, events that don't exist. There's a second exposure in Australia: fabricated review data is a false claim about your business whatever format it's published in, and the ACCC treats fake reviews as misleading conduct.
Where this sits on your list
Schema markup is hygiene, not strategy. The order that matters: does the page load quickly, does it say something worth ranking, is anything linking to it — and then, once all three are true, is it labelled so machines can't misread it. Businesses obsessing over markup while skipping the first three steps are polishing the label on an empty tin.
Do this much today. Run the Rich Results Test on three pages. If you find duplicate business blocks or a star rating nobody can trace to a real review, fix those first — they're liabilities, not gaps. If you find nothing, put an Organization block and breadcrumbs on the next sprint and stop there. Then spend the attention you saved on whatever is actually holding the page back. It's almost never the markup.