ArticleSEO, GEO and AEO

Schema Markup for Business Websites: What to Add and How to Check It

Schema markup describes your page to search engines in a structured way. Which types to add, which Google features were retired, and how to validate the code.

Published 19 min read
02 / In this article

Schema markup is code you add to a page to describe its content in a standard vocabulary, so a search engine can read facts such as the business name, the address or the price without guessing. It can make a page eligible for richer search results, but it never guarantees them. This guide covers what to add on a business website, which Google features have been retired, how to write a clean JSON-LD block and how to check it.

Key Takeaways

  • Schema markup describes, it does not promote. It must match what a visitor can see on the page, and Google says it does not guarantee a rich result.
  • Use JSON-LD. Google supports JSON-LD, Microdata and RDFa, and recommends JSON-LD when your setup allows it.
  • Start with the basics. Organization, LocalBusiness (if you serve a place), BreadcrumbList, Article on blog posts and Product on product pages cover most business sites.
  • Check the current feature list. As of October 2026, FAQ rich results no longer appear in Google Search, and several other features have been retired.
  • Test twice. Use the Rich Results Test for Google features and the Schema Markup Validator for general syntax, then watch the reports in Search Console after launch.

What is schema markup?

Schema markup is structured data written with the schema.org vocabulary, a shared set of types (such as Organization or Product) and properties (such as name or price) that search engines understand. Schema.org describes itself as shared vocabularies that webmasters use to mark up pages so major search engines can understand the content.

The page text tells a person what the page says. The markup tells a machine what kind of thing the page is about: a restaurant, a product, an article. "Structured data" is the general idea, and "schema markup" usually means structured data that uses the schema.org vocabulary.

Your phone number, opening hours and address already appear on the page. Markup states them in a form a program can read without interpreting a layout.

What does schema markup do, and what does it not do?

Schema markup helps a search engine understand a page and can make the page eligible for enhanced displays called rich results, but Google presents this as a possibility, not a promise. Its documentation says that using structured data does not guarantee a rich result, and that the algorithm decides what to show based on many factors.

That sentence has three consequences worth stating plainly.

  • It is not a ranking switch. Google's guidance on structured data describes eligibility for features and understanding of content. It does not describe markup as a way to rank higher. Treat any claim that "schema boosts rankings" as unproven.
  • It is not a manual override. You cannot force a star rating, a price or a breadcrumb trail to appear. You make the page eligible and Google decides.
  • It helps machines, and that has value beyond Google. Other systems read schema.org too, and clear facts reduce the chance of a wrong reading. We cover how that links to AI answers in our guides to answer engine optimization and generative engine optimization. No source promises that markup earns an AI citation, so do not plan around that.

If markup breaks Google's rules, a manual action can remove the page's eligibility for rich results. Google says this does not affect how the page ranks in web search.

Which format should you use?

Use JSON-LD. Google supports three formats (JSON-LD, Microdata and RDFa) and says all three work equally well if the markup is valid, but it recommends JSON-LD when your site's setup allows it.

JSON-LD sits in one script block, separate from your visible HTML, so it can be changed without touching the layout. Microdata and RDFa are woven into the page elements, so a redesign can break them unnoticed.

A minimal block looks like this. The values are placeholders, and the structure follows the format shown in Google's Organization documentation.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Studio",
  "url": "https://www.example.com",
  "logo": "https://www.example.com/images/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/example-studio"
  ]
}
</script>

@context points to the vocabulary, @type names the kind of thing and the remaining lines are its properties. A missing comma or a stray quote is the most common way to break it.

Not sure what your pages are missing?

We review your templates and tell you which markup is worth adding and which is noise.

Ask about technical SEO

What rules does Google set for structured data?

Google's rules come down to one idea: the markup must be a true description of the visible page. Its general guidelines say that markup must match what users can see, must not be misleading and must not impersonate a person or organization.

In practice, that means:

  • Do not mark up hidden content. Google warns against adding structured data about information that is not visible to the user, even if the information is accurate.
  • Put the markup on the page it describes. A product's data goes on that product's page, not on every page of the site.
  • Include the required properties. An item that lacks them is not eligible for the feature. Complete and accurate recommended properties matter more than a long list of incomplete ones.
  • Keep it current. Google says it will not show a rich result for time-sensitive content that is no longer relevant. An event that ended last year should not keep its markup.
  • Do not block the page. Pages with markup must remain accessible to Googlebot, so robots.txt, a noindex tag or a login wall will stop the markup from being used.

Before and after, the difference between a page that passes and a page that risks a manual action is often a single honest sentence:

BEFOREMismatched markupRating 4.9 in codeNo reviews on the pagePrice in code onlyHours differ from footerCopied from a templateAFTERMatching markupRating shown on pageReviews listed and realPrice visible to usersHours match the footerWritten for this page
Markup follows the page, not the other way round.

The test: check that each fact in the markup can be found on screen.

Which schema types should a business website add?

A business website should usually add Organization, a LocalBusiness type if it serves a physical area, BreadcrumbList on deeper pages, Article on blog posts and Product on pages that describe a product. Those are all features that Google documents as of October 2026, and they map to the pages most business sites already have.

Google's search gallery lists 25 features. The ones that matter for most business sites are Organization, Local business, Breadcrumb, Article, Product, Review snippet, Video and Software app. The rest (Course list, Dataset, Event, Job posting, Movie, Recipe and others) apply to specific industries or content types. A site that does not publish recipes does not need Recipe markup.

LOCAL SHOPSAASONLINE STOREHome pageLocalBusinessOrganizationOrganizationInner pagesBreadcrumbBreadcrumbBreadcrumbKey pageOpening hoursSoftware appProductBlog postsArticleArticleArticleReviewsCarefulCarefulProduct reviews
Starting markup by type of business.

Organization: who you are

Organization markup tells Google the name, logo, contact details and official profiles of your business. Google's documentation lists no required properties, and recommends properties such as name, url, logo, sameAs, address, telephone, email and description.

The logo deserves care. Google says adding the logo property can help it understand which logo you want to show, and gives guidelines: the image must be at least 112 by 112 pixels, crawlable and indexable, in a format Google Images supports, and it should look right on a plain white background. Put the Organization block on your home page, or on a single "about" page, not on every page.

LocalBusiness: where you are and when you are open

LocalBusiness markup describes a business with a physical location or a service area. It is a subtype of Organization. Google lists address and name as required, and recommends properties such as geo, openingHoursSpecification, telephone, url and priceRange.

Google also says to use the most specific subtype available, such as Restaurant, DaySpa or HealthClub. Here is a short example adapted from the structure in Google's documentation, with placeholder values:

{
  "@context": "https://schema.org",
  "@type": "Restaurant",
  "name": "Example Kitchen",
  "url": "https://www.example.com/",
  "telephone": "+1-555-0100",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1 Example Street",
    "addressLocality": "Exampleville",
    "addressRegion": "CA",
    "postalCode": "00000",
    "addressCountry": "US"
  },
  "openingHoursSpecification": [{
    "@type": "OpeningHoursSpecification",
    "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
    "opens": "11:00",
    "closes": "22:00"
  }]
}

Google's guidance on hours is worth knowing. Group days that share the same hours in one specification, use "00:00" to "23:59" for a business open all day, and use validFrom and validThrough for seasonal closures. If you have several locations, give each its own page with its own markup. If you run a business tied to a place, our page on websites for local businesses sets out the wider picture.

BreadcrumbList describes the path from a higher-level page to the current one. Google's documentation requires an itemListElement array with at least two ListItem entries, each with a position, and with a name and an item URL (the URL is optional for the last item, because Google uses the current page's URL).

Google recommends breadcrumbs that reflect how users typically reach a page, not just the URL structure. You do not need an item for the home level or for the page itself. It also notes that the old data-vocabulary.org markup is no longer eligible for rich results, which matters on older sites that were never updated.

Article: for blog posts and news

Article markup helps Google understand the title, author, images and dates of a post. Google's documentation lists no required properties, and recommends headline, image, datePublished, dateModified and author (with a name and a URL). It also states there is no markup requirement to be eligible for features like Top stories, so a blog does not break without it.

If you add it, keep it honest. The author should be the person named on the page, and dateModified should change when the content truly changes, not every time a template is touched.

Product: for pages where you describe something you sell

Product snippets need a name plus at least one of review, aggregateRating or offers. Google separates product snippets (for product review pages and aggregators) from merchant listings, which apply when shoppers can buy the product from you. If you run a shop, check which feature your page fits before you copy a template.

Reviews and prices must be visible on the page, in line with the general rule.

Can you mark up your own reviews?

Not for stars on your own business. Google's review snippet guidelines say that pages using LocalBusiness or Organization markup are ineligible for the star review feature when the entity controls the reviews about itself, including reviews embedded from a third-party widget. Ratings must come directly from users, and Google does not want editors creating or compiling ratings for local businesses.

This catches many sites. A plumber who copies the average rating from a review platform into the site's LocalBusiness markup is doing exactly what the guideline discourages. If you want to show customer feedback, show it on the page as content and leave out the rating markup.

Which structured data features has Google retired?

Google has retired several structured data features, so check the current documentation before you build anything. The most recent change affects FAQ markup: Google's documentation records that the FAQ rich result "will no longer appear in Google Search starting May 7, 2026," and on June 15, 2026 the FAQ documentation was removed because the feature is no longer shown.

Google's own update log lists other removals. Here are the ones recorded there, with the dates Google gives.

  • HowTo. The documentation was removed on September 14, 2023, because the rich result no longer appeared on desktop or mobile.
  • Special announcement. A deprecation notice appeared on April 23, 2025, and the documentation was removed on September 9, 2025.
  • Course info, estimated salary, learning video and vehicle listing. Notices were added on June 12, 2025, and the documentation was removed on September 9, 2025, because these types are no longer shown in Google Search results.
  • Practice problem. Documentation was removed on January 6, 2026. In November 2025, Google also clarified that Dataset markup is used only by Dataset Search.
  • FAQ. Retired as above in 2026. Before that, in September 2023, Google had already limited it to well-known government and health sites.

A retired feature does not make a visible FAQ section worthless: the questions still help readers. What goes away is the special display in Google. If you already have FAQ markup, leaving it does no harm as long as it matches the visible content. Do not spend new effort on it for Google's sake.

Want your site template checked for markup?

We look at what your pages already declare and flag errors, mismatches and retired features.

Talk to us about web design

How do you add schema markup to a website?

You add markup in the page template, so every page of the same type gets the right block with its own values. The method depends on how the site is built.

  1. Your CMS or theme. Many platforms output Organization, Article or Product markup by default or through a plugin. Check what is already there before you add more, because two sources can produce duplicate or conflicting blocks.
  2. A custom template. In a coded site, a template function builds the JSON-LD from the same data that renders the page, which keeps the two in sync. This is the most reliable approach.
  3. Google Tag Manager. Google's documentation says you can add JSON-LD with a Custom HTML tag. It warns that hardcoding values risks a mismatch with the page, and recommends variables that read from the page.
  4. JavaScript. Google can process structured data that is in the DOM after rendering, but verify it. For Product markup, Google warns that dynamically generated markup can make Shopping crawls less frequent and less reliable.

Generating the markup on the server from the same content fields as the visible page is the most dependable option, but any of the four works if the result is valid and matches the page. If you are planning a rebuild, put markup on the requirements list from the start, as we describe in our guide to AI and website redesign, and see our web design service for small business sites.

How do you test and validate schema markup?

Test in two tools, then monitor in a third. Each answers a different question.

01WriteJSON-LDin thetemplate02ValidateSchemaMarkupValidator03RichResultsGooglefeatures04DeployCheckthe liveURL05MonitorSearchConsolereports
The check route from code to Search Console.
  • Schema Markup Validator (validator.schema.org). It checks syntax and conformance to the schema.org vocabulary, including types that Google does not support. It is the successor to Google's Structured Data Testing Tool and it does not check Google rich result eligibility.
  • Rich Results Test. Google calls it an easy and useful tool for validating your structured data. It shows which Google features the page is eligible for and lists errors and warnings per item. Google notes that code input has limits for JavaScript pages, so test the live URL when you can.
  • Search Console rich result reports. After launch, these sort items into valid and invalid, with non-critical issues in a separate "Improve item appearance" table. Google's documentation says fixes must be made in your site's source code, since Search Console cannot apply them.

One caution: automated tools catch most technical errors, but Google says structured data can be incorrect in ways the Rich Results Test cannot catch. A passing test says the code is well formed. It does not say the markup is true.

To measure impact, Google suggests a before-and-after comparison on a set of pages using the Performance report in Search Console. Keep expectations modest: many types change appearance, not position.

What are the most common schema markup mistakes?

The most common mistakes are markup that does not match the page, missing required properties, and copying a template without editing it. These are easy to avoid once you know them.

  1. Mismatch with the page. The price, rating, hours or address in the code differ from what the visitor sees. Fix the source so both come from one data field.
  2. Hidden or invented content. Reviews that no visitor can read, or ratings made up by an editor. This is the case Google's guidelines warn about, and it can lead to a manual action.
  3. Self-serving review stars. Marking up your own business's rating on LocalBusiness or Organization, as covered above.
  4. Missing required properties. A LocalBusiness block with no address, or a BreadcrumbList with fewer than two items. The item is then not eligible.
  5. Duplicate blocks. A plugin and a theme both output Organization markup with different logos or names. Pick one source.
  6. Copied placeholders. Example values left in place, such as "Example Corporation" or a stock logo URL. Search your templates for them.
  7. Syntax errors. A trailing comma, a missing quote or curly quotes pasted from a document. The Schema Markup Validator catches these fast.
  8. Chasing retired features. Building FAQ or HowTo markup for a Google display that no longer exists.

A useful habit: add the markup check to your release routine. When a template changes, test one page of each type. Our website audit checklist puts structured data next to crawling, speed and content checks.

How does schema markup fit into your wider SEO work?

Schema markup is one small layer on top of good content, clear structure and a site that search engines can crawl. It does not replace any of them. If a page is thin, slow or hard to find, markup will not fix it.

A sensible order is to fix crawling and indexing, write clear pages, then add Organization, LocalBusiness, BreadcrumbList, Article and Product markup where they fit, and finally validate and monitor. The wider approach is described in our guide to SEO for small business and in the AI SEO guide. Markup comes late because it describes what already exists.

Frequently Asked Questions

Is schema markup a ranking factor?

Google's documentation presents structured data as a way to help it understand a page and make the page eligible for rich results. It does not describe markup as a ranking signal, and rich results are not guaranteed. Add it for clarity and eligibility, not for position.

Do I need schema markup on every page?

No. Add markup where it describes the page's main subject: Organization on the home page, BreadcrumbList on inner pages, Article on posts, Product on product pages. Markup on a page that does not match the content only adds risk.

Is JSON-LD better than Microdata?

Google supports both and says they work equally well when valid, but it recommends JSON-LD if your setup allows it. JSON-LD lives in one block, which makes it easier to generate, test and update without editing the visible layout.

Does schema markup help with AI search answers?

Markup gives machines clear facts, which can reduce misreadings, but no primary source promises that it earns a citation in an AI answer. Treat it as clean description and focus on clear, answer-first content. The content side matters far more.

Should I still add FAQ schema?

Not for Google. FAQ rich results stopped appearing in Google Search from May 7, 2026, and the documentation was removed in June 2026. A visible FAQ section is still good content. Markup for it is optional and has no Google display to aim at.

How long does it take for markup to show in Search Console?

Google must recrawl the page first, so timing varies and no fixed number is published. Use the URL Inspection tool to check the live page and request indexing, then watch the rich result reports over the following weeks.

Can I add schema markup myself?

Yes, if you can edit your templates or use a plugin. Start with an Organization block, validate it in both tools and check the result on the live page. For larger sites, or when the markup must come from product and location data, a developer should generate it from the source fields.

Next steps

Start with an inventory: list your page types, note which markup each already has, and compare it against the visible page. Fix mismatches first, then add Organization, LocalBusiness and BreadcrumbList where they are missing, and validate in both tools. If you want help with the technical side, see our technical SEO service and the wider SEO, GEO and AEO service, or get in touch with your site address and what you sell.

Sources

Newsletter

One short email when we publish

Notes on AI, image, video and brand work, from the people who do it. No spam.

Author