Schema Markup for Small Businesses: The 7 Types That Actually Matter

What schema markup actually does

Schema markup is a block of structured data — usually JSON-LD in the page’s code — that describes the page in a vocabulary search engines agree on (schema.org). Instead of a crawler inferring that “Ever Fencing, Brendale, 07…” is a business with an address and phone number, you state it explicitly.

That matters more every year. Classic search engines use schema to understand entities and to power rich results. AI assistants go further: when they assemble an answer, unambiguous facts — business name, services, areas served, the people behind it — are easier to retrieve and safer to repeat. Schema is part of how you become quotable, which we cover in how to get recommended by ChatGPT.

The 7 schema types that matter for small businesses

1. Organization or LocalBusiness

This is the foundation. If customers visit your premises or you serve a defined area, use LocalBusiness (or a more specific subtype such as Electrician, Plumber or HomeAndConstructionBusiness). Otherwise use Organization. Include your legal and trading name, logo, phone, address (or areaServed for service-area businesses), and sameAs links to your Google Business Profile, LinkedIn and other official profiles.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HomeAndConstructionBusiness",
  "@id": "https://example.com.au/#business",
  "name": "Example Fencing",
  "url": "https://example.com.au/",
  "logo": "https://example.com.au/logo.png",
  "telephone": "+61 7 0000 0000",
  "areaServed": ["Brendale QLD", "Strathpine QLD", "Aspley QLD"],
  "sameAs": [
    "https://www.linkedin.com/company/example-fencing",
    "https://www.facebook.com/examplefencing"
  ]
}
</script>

2. WebSite

A small block on the homepage stating the site name and its publisher (linked to your Organization by @id). It helps search engines show the right site name and connects your entities together.

3. Service

Every service page should describe the service: name, description, provider (pointing at your Organization), areaServed and, where useful, offers. This is the markup most small business sites are missing — and it’s exactly the information an AI assistant needs to answer “who does X in Y?”.

4. Person

Expertise you can’t verify doesn’t count for much. Person markup on founder and team pages — with jobTitle, worksFor, qualifications and sameAs links to independent profiles — connects your content to real, checkable people.

5. BreadcrumbList

Simple and almost always worth it: it states the page’s place in your site hierarchy (Home › Services › Local SEO), reinforcing your structure.

6. FAQPage

Since 2023 Google shows FAQ rich results mainly for well-known government and health sites, so most businesses won’t see the expandable FAQs in Google any more. The markup is still valuable: it presents clean question-and-answer pairs that machines — including AI answer engines — can parse. Only mark up FAQs that are visible on the page.

7. Article or BlogPosting

On blog posts, state the headline, author (as a Person), publisher, and published and modified dates. Clear authorship is one of the most useful trust signals you can give.

Connect your entities with @id

The most overlooked part of schema is how the pieces connect. Each block can carry an @id — a stable identifier such as https://example.com.au/#business. Your Service blocks then say "provider": { "@id": "…#business" }, your Article blocks point their publisher at the same ID, and your founder’s Person block says "worksFor" that same business.

The result is a small knowledge graph of your business: one organisation, the people behind it, the services it offers and the content it publishes — all explicitly linked. That’s far easier for Google and AI systems to trust than a dozen disconnected snippets from different plugins.

{
  "@type": "Person",
  "@id": "https://example.com.au/#founder",
  "name": "Jane Citizen",
  "jobTitle": "Founder",
  "worksFor": { "@id": "https://example.com.au/#business" },
  "sameAs": ["https://www.linkedin.com/in/janecitizen"]
}

Mistakes that make schema worse than nothing

• Marking up content that isn’t on the page — reviews, FAQs or prices that visitors can’t see. This violates Google’s guidelines.
• Self-serving review stars — Google doesn’t show star ratings for reviews a business publishes about itself on LocalBusiness or Organization markup.
• Conflicting details — a different phone number in schema than on your Business Profile.
• Multiple disconnected Organization blocks from different plugins — use one, referenced by @id.
• Never validating — a theme update can quietly break JSON-LD for months.

How to check and validate your schema

1. Run the Rich Results Test

   Google’s Rich Results Test shows which rich-result types a page is eligible for and flags errors.

2. Run the Schema Markup Validator

   validator.schema.org checks all schema.org types, including ones Google doesn’t use for rich results (like Service).

3. Check Search Console enhancements

   Search Console’s enhancement reports surface errors across your whole site, not just one page.

4. Re-check after every theme or plugin update

   Structured data is code. Updates break it silently — add a quick check to your release routine.

About the author

Dr Andrej Miklosik

Founder of Catnapweb and Professor at the Department of Marketing and Commerce, Comenius University. Author of 170+ research publications on AI in marketing and search visibility, cited 1,705 times. Full profile →