Schema Markup for Small Business Websites: What to Add, What to Skip and How to Test It

What is schema markup, in plain English?

Schema markup is extra information, added to a web page's code, that explains what the page is about in a way machines can read without guessing. A human sees a page with your business name, address and opening hours. A search engine sees text. Schema markup tells it directly: this is a business, this is its name, this is its address, these are its hours.

The vocabulary comes from Schema.org, a shared set of types and properties used by Google, Bing and others. The format Google recommends is JSON-LD, a small block of data placed in the page that does not change how the page looks. Google also supports Microdata and RDFa, but JSON-LD is easier to write and maintain.

People often call schema markup an SEO trick. It is closer to a label. It does not make a weak page rank, and Google says plainly that it does not guarantee that features using structured data will show up in search results. What it does is remove ambiguity, which can make you eligible for richer displays and helps search engines and AI tools describe your business correctly.

This guide is written for small business owners and the people who maintain their websites. We build and audit structured data on our own site and for clients, so we will include a real example, what Google currently supports, what has been retired and how to test your own markup.

Does schema markup help you rank higher?

Not directly. Google's documentation describes structured data as a way to help it understand your content and, for certain types, to make your pages eligible for enhanced results called rich results, such as product details, event listings or breadcrumbs in the snippet. It does not describe markup as a ranking factor in itself.

Google's guidelines also explain what happens when markup breaks the rules. A structured data manual action means a page loses eligibility for rich results. Google states that it does not affect how the page ranks in ordinary web search. So the risk of bad markup is losing the extras, not losing your position, though a site that misleads in one place deserves to be treated with suspicion in others.

The real value for most small businesses is accuracy and clarity. When your business name, address, phone number, hours and website are marked up correctly and match your Google Business Profile and visible page, you give search engines a consistent description of who you are. That consistency matters more as AI-powered search summarises businesses from many sources. Nobody outside the search engines can say exactly how much weight they give to markup, so treat it as one good practice among several, not a shortcut.

Which structured data types matter for a small business?

Google lists dozens of supported types in its search gallery. Most small businesses need only a handful, chosen by what the site actually contains.

Organization. Describes the business behind the website: legal name, logo, address, contact details and links to official profiles. Google says it can feed knowledge panels. Every business site should have it, usually on every page.

LocalBusiness (or a more specific type such as a dentist, restaurant or electrician). Describes a business with a physical location: address, phone, opening hours, area served and price range. Google's guidance says it can help display business details in a knowledge panel with hours, ratings and directions. Use it on the pages about the business and its locations.

BreadcrumbList. Describes the trail from the home page to the current page, which Google can show in the result snippet. Easy to add and useful on any site with more than a few pages.

Article or BlogPosting. Marks up blog posts with headline, author, dates and images. Helpful for showing clear authorship and dates.

Product and Offer. For online stores: name, image, price, availability. Required for product rich results.

Event, JobPosting and VideoObject. For businesses that run events, hire through their site or publish video. Each has its own required properties.

• Every site: Organization, BreadcrumbList.
• Businesses with a location: LocalBusiness or a specific subtype.
• Blogs and guides: Article or BlogPosting.
• Online stores: Product and Offer.
• As relevant: Event, JobPosting, VideoObject.

What has Google retired, and what does that mean for FAQ markup?

Structured data features come and go, and a number of guides still recommend ones that no longer do anything. Two matter to small businesses.

FAQ rich results. For years, FAQ markup could make question-and-answer dropdowns appear under a result. In September 2023 Google limited the feature to well-known government and health websites. Its documentation now records that FAQ rich results stopped appearing in Google Search on May 7, 2026, and that the documentation for the feature was removed in June 2026. Google's page does not say whether existing FAQ markup should be deleted. Markup that stays in place is harmless, but it no longer produces a visible result in Google.

How-to rich results. Google stopped showing these in 2023, first on mobile and then on desktop.

So if a plugin or an agency has been selling you FAQ schema as a way to take up more space in search results, that benefit has ended. FAQ content itself is still valuable on the page: it answers real customer questions, helps people decide, and gives AI assistants and featured answers clear question-and-answer text to draw on. Our guide to AI search optimization explains how to write it.

We are in this position ourselves. Our site marks up the questions and answers on most pages as FAQPage data. We have kept it because it accurately describes real visible content and may be read by other tools, but we no longer count on it for a special result in Google, and neither should you.

What are Google's rules for structured data?

Google's general guidelines are short and worth following exactly. Use JSON-LD where you can. Do not mark up content that is not visible to readers of the page. Make sure your structured data is a true representation of the page content: marking up something unrelated, such as describing a broadcast as a local event, breaks the rules. Include the required properties for the type, because items missing required properties are not eligible for rich results, and add the recommended ones to improve quality.

One rule catches many local businesses. Google's review snippet guidelines say that pages using LocalBusiness or any other Organization markup are ineligible for review star features when the entity being reviewed controls the reviews about itself. In plain terms: a business that adds star ratings about itself, taken from its own testimonials, to its own site's markup will not get stars in search results for it, and fake or non-genuine reviews can trigger a manual action. Our own site follows this: we do not mark up self-published reviews, and the testimonials we show are real quotes supplied by clients.

Whatever you mark up should also match the rest of the internet. A business address and phone number in markup that differ from your Google Business Profile or your footer create exactly the kind of inconsistency you are trying to avoid.

• JSON-LD is Google's recommended format.
• Mark up only what visitors can see on the page.
• Include every required property for the type.
• Never add self-published reviews or ratings for yourself.
• Keep name, address and phone identical to your Business Profile.

What does good LocalBusiness markup look like?

Google's local business documentation lists two required properties, the business name and its address, and several recommended ones: geographic coordinates, opening hours, telephone, a URL for the location and a price range. It notes that coordinates should be given to at least five decimal places.

Below is an illustrative example for a fictional plumbing company that works at customers' homes. The company and its details are invented, so replace them with your own. A business that travels to customers lists the areas it serves, and should not publish a home address it does not want shown.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "@id": "https://www.example-plumbing.com/#business",
  "name": "Example Plumbing Co.",
  "url": "https://www.example-plumbing.com/",
  "telephone": "+1-555-010-0100",
  "image": "https://www.example-plumbing.com/images/van.jpg",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "100 Main Street",
    "addressLocality": "Springfield",
    "addressRegion": "IL",
    "postalCode": "62701",
    "addressCountry": "US"
  },
  "areaServed": [
    { "@type": "City", "name": "Springfield" },
    { "@type": "City", "name": "Chatham" }
  ],
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "17:00"
    }
  ],
  "sameAs": [
    "https://www.facebook.com/exampleplumbing",
    "https://www.linkedin.com/company/example-plumbing"
  ]
}
</script>

What should you notice in that example?

Three details are worth noticing. The type is the specific Plumber rather than a generic business, which is more precise. The address and phone number are exactly what appears on the page and in the Business Profile. And there are no review stars, because the reviews live on Google and other independent sites, not in the markup.

If your business serves customers only at their homes, check Google's current guidance on how to show addresses for service-area businesses, and keep the Business Profile and markup consistent. Our guide to Google Business Profile for service area businesses covers the profile side.

A real example: what we found auditing our own website

We audited our own site while writing this guide, and it is a useful, honest case study. Our pages carry Organization markup on every page, with our legal name, logo, address, two contact points, links to our official profiles, and the services we offer. Our home, contact and Pune pages carry LocalBusiness markup, using the ProfessionalService type. Nearly every page carries BreadcrumbList markup that matches its URL path, blog posts carry BlogPosting markup with authors and dates, and case studies carry Article markup.

We also found things to fix. Our LocalBusiness markup gives the office coordinates to three and four decimal places, and Google's documentation asks for at least five. We will correct that after confirming the exact pin against our Google Business Profile, rather than guessing. And as noted above, the FAQ markup on most pages no longer produces a visible result in Google, so we treat it as harmless but no longer a reason to write FAQs. We mention these because small gaps like these are normal, and an audit like this takes an afternoon.

Our build process also validates every page for valid JSON-LD, one H1, a canonical tag and matching breadcrumbs before anything is published. For a small business site, you can get most of the same safety with a monthly check in Search Console and the Rich Results Test.

How do you add schema markup to your site?

There are three common routes. On WordPress, SEO plugins such as Yoast and Rank Math add Organization, breadcrumb and article markup automatically, and let you fill in local business details in settings. On Shopify, themes and apps add Product and Offer markup, and most good themes handle breadcrumbs. On custom sites, a developer adds JSON-LD blocks generated from the same data as the page, so the two cannot drift apart.

Whichever route you take, resist adding markup by pasting snippets from a generator without checking them. Generated code often includes properties that do not match your page, such as ratings you do not display, or types that are not supported. Every property should map to something visible on the page or to a fact you can prove.

If your site is being rebuilt, include structured data in the plan from the start. Our website redesign SEO checklist lists what to preserve, and our web design for US businesses and technical SEO pages describe how we build it in.

How do you test and monitor your markup?

Test before you publish and monitor after. Google's Rich Results Test checks whether a URL or a piece of code is eligible for Google's rich result features and flags missing required properties. The Schema Markup Validator, run by Schema.org, checks general syntax and vocabulary for any type, including those Google does not display.

After publishing, use Search Console. Its enhancement and rich result reports show which pages have valid markup, which have errors and warnings, and how many items are affected. Check them monthly, and after any redesign, plugin update or theme change, since updates often change markup without warning.

Remember what a passing test means. It means your markup is valid, not that Google will show anything special. Google states that it does not guarantee that features using structured data will appear in search results. Judge the effort by whether your pages are accurate and clear, not by whether a rich result appears.

If you would like us to review your site's structured data, send your address through the contact page and we will reply in writing with what to fix first. Our SEO services for US businesses page describes how we work, remotely from Pune, India, with calls in US business hours.