
Schema markup for small business
On this page
- Organization: identify the company and its official profiles
- WebSite: specify a site name without the retired search box
- LocalBusiness: describe a real location accurately
- Review snippets: eligibility depends on who reviews whom
- BreadcrumbList: desktop presentation and visible navigation
- Article and BlogPosting: describe editorial pages
- Product snippets: editorial product information and ratings
- Merchant listings: product pages where customers can buy
- VideoObject: video details and explicit key moments
- Event: public attendance at a physical place
- JobPosting: maintain real vacancies through their lifecycle
- Retired features, Dataset and Service: keep a dated record
- Rankings and AI citations: separate mechanisms from measured effects
- Validation: vocabulary, Google eligibility and indexed output
- The six-step audit decision rule
SEO
Schema markup for small business should describe your actual business and qualify suitable pages for supported search features. The familiar instruction to add FAQ markup and testimonial stars is outdated: Google stopped showing FAQ rich results on 7 May 2026, and your business's reviews about itself have been ineligible for business review stars since 16 September 2019.
FAQ eligibility had already narrowed to authoritative government and health sites on 8 August 2023. A plugin can still generate perfectly valid markup for a feature Google retired; the useful question is what each type can produce now.
| Type | What Google shows | Where | Who qualifies | Last change or verification | Verdict |
|---|---|---|---|---|---|
| Organization | Logo, entity details | Search, knowledge panel | Identifiable organizations | Checked 24 Oct 2026 | Ship |
| WebSite | Preferred site name | Desktop, mobile | Domain or subdomain | Survived removal 21 Nov 2024 | Ship |
| LocalBusiness | Business details | Search, local panel | Businesses with locations | Review guidance 2 Aug 2023 | Ship if physical business |
| Review / AggregateRating | Review stars | Search snippets | Eligible reviewed types | Incentive rule 24 Jul 2026 | Ship if eligible reviews |
| BreadcrumbList | Breadcrumb trail | Desktop | Hierarchical pages | Mobile removed 23 Jan 2025 | Ship |
| Article / BlogPosting | Better article presentation | Search | Editorial pages | Timezone guidance Oct 2023 | Ship if publishing articles |
| Product: snippet | Product information, ratings | Search snippets | Single-product pages | Checked 24 Oct 2026 | Ship if product content |
| Product: merchant listing | Purchasable product details | Search, Shopping | Single-product purchase pages | Category and sale-duration guidance 7 Jul 2026 | Ship if selling products |
| VideoObject | Video features, key moments | Search video surfaces | Pages with videos | Creator guidance 24 Sep 2026 | Ship if publishing video |
| Event | Event experience | Search | Public, physical events | Online-only removed 5 Jun 2025 | Ship if physical event |
| JobPosting | Job search experience | Google job search | Actual job openings | Checked 24 Oct 2026 | Ship if hiring |
| FAQPage | Nothing | None | No FAQ rich results | Removed 7 May 2026 | Skip |
| HowTo | Nothing | None | No HowTo rich results | Deprecated 13 Sep 2023 | Skip |
| SearchAction: search box | Nothing | None | No search-box feature | Removed from 21 Nov 2024 | Skip |
| Book Actions | A remaining feature uses it | Feature-specific | Relevant book providers | Banner removed 5 Nov 2025 | Ship if book integration |
| Course Info | Nothing | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| ClaimReview | Nothing for retired feature | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| Estimated Salary | Nothing | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| Learning Video | Nothing for retired feature | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| Special Announcement | Nothing | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| Vehicle Listing | Nothing | None | Retired feature | Tooling removed 9 Sep 2025 | Skip |
| Practice problem | Nothing | None | Retired feature | Deprecated 5 Nov 2025 | Skip |
| Dataset | Dataset discovery | Dataset Search only | Published datasets | Clarified 5 Nov 2025 | Ship if publishing datasets |
| Service | No dedicated rich result | None | No dedicated Google feature | Checked 24 Oct 2026 | Skip |
“Checked” means verified on that date, not changed then. Eligibility never guarantees display, and a retired specialized feature does not retire every related type: Learning Video and VideoObject are different cases.
Organization: identify the company and its official profiles
Wins when you give Google a consistent business identity on the home page or one about page. Organization has no required properties; Google's documentation says you do not need to repeat it on every page.
Use an accessible logo at least 112 × 112 pixels, a business name, URL and accurate contact details. sameAs connects official profiles to that identity; iso6523 and naics can help disambiguate organizations behind the scenes. Other supported identifiers include duns, leiCode, taxID and vatID, where applicable.
Loses when you treat every available identifier as compulsory or expect a guaranteed knowledge panel. Merchants can supply return-policy, address and contact information for merchant knowledge panels, but that is an input to Google's systems, not control over the finished panel.
The Organization documentation separates those uses. For the identity work behind sameAs and stable identifiers, entity SEO and entity relationships explain how references connect to one company.
Our own site, irongoo.com, serves an Organization node with five official profiles on its home page. The abridged block below shows two of its official profiles.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://irongoo.com/#organization",
"name": "Iron Goo",
"url": "https://irongoo.com",
"logo": {
"@type": "ImageObject",
"@id": "https://irongoo.com/#logo",
"url": "https://irongoo.com/logo.png",
"contentUrl": "https://irongoo.com/logo.png",
"caption": "Iron Goo"
},
"sameAs": [
"https://www.linkedin.com/company/iron-goo/",
"https://www.youtube.com/@irongoocom"
]
}
WebSite: specify a site name without the retired search box
Wins when you want to express a preferred site name for desktop and mobile results. Put WebSite structured data on the home page, with the site's name and url; Google supports one site name per domain or subdomain.
Loses when you expect separate site names for subdirectories or confuse WebSite with its former sitelinks search box use. Removing the search box did not remove site-name support.
Our own home page serves a WebSite node named Iron Goo with the identifier https://irongoo.com/#website. Keep the site identity even if you remove an obsolete search-box SearchAction.
LocalBusiness: describe a real location accurately
Wins when the page represents a business location with an accurate name and address, Google's required properties. Choose the most specific subtype, such as Plumber; if several types apply, use an @type array because Google does not support additionalType.
Recommended fields include geo, openingHoursSpecification, telephone, url and priceRange. Restaurants can add menu and servesCuisine; department describes relevant departments. Although the documentation lists review and aggregateRating, those recommendations concern sites collecting reviews about other businesses.
Loses when the markup becomes a substitute for maintaining your Business Profile. Google tells businesses to keep that profile current for its AI features; our reading is that local panel details mostly come from the profile, and LocalBusiness markup has no demonstrated local-pack ranking benefit.
The local SEO checklist for a company puts that profile work in context. Harbor Line Plumbing in the following examples is hypothetical; these blocks validated with zero errors and zero warnings in the Schema Markup Validator on 24 October 2026.
{
"@context": "https://schema.org",
"@type": "Plumber",
"@id": "https://www.example.com/#business",
"name": "Harbor Line Plumbing",
"url": "https://www.example.com/",
"logo": "https://www.example.com/images/logo-512.png",
"image": "https://www.example.com/images/van-front.jpg",
"telephone": "+1-503-555-0142",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "1420 SE Water Ave",
"addressLocality": "Portland",
"addressRegion": "OR",
"postalCode": "97214",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 45.5122,
"longitude": -122.6653
},
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "07:30",
"closes": "18:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "09:00",
"closes": "14:00"
}
],
"sameAs": [
"https://www.linkedin.com/company/example-harbor-line"
]
}
Review snippets: eligibility depends on who reviews whom
Wins when your page contains visible reviews of an eligible item. Google's supported subjects include books, course lists, events, movies, products, recipes and software apps; supported schema.org types also include CreativeWorkSeason, CreativeWorkSeries, Episode, Game, MediaObject, MusicPlaylist and MusicRecording.
LocalBusiness and Organization qualify only where the site reviews other businesses or organizations. A review needs an identifiable reviewed item, an author and reviewRating.ratingValue; an AggregateRating needs ratingValue and ratingCount or reviewCount, attached to an eligible subject.
Loses when you mark up testimonials about your own business and expect business stars. Google's self-serving review restriction explicitly includes embedded third-party review widgets.
LocalBusiness and Organization pages controlled by the reviewed business are ineligible for self-serving review stars, including stars supplied through third-party widgets. Our reading of the restriction is that product reviews on a store's own Product pages fall outside it, because the restriction names LocalBusiness and Organization.

The business controls the page displaying reviews about itself, even when a widget supplies them. A separate site reviewing other businesses has a different eligibility position.
Do not aggregate ratings from other websites, and keep the reviews visible to readers. Google's guideline added on 24 July 2026 prohibits fake and undisclosed incentivized reviews. Separately, Google added the recommendation to accept only ratings accompanied by a review comment and the author's name on 15 January 2025. The requirement that author.name stay under 100 characters dates from October 2021.
BreadcrumbList: desktop presentation and visible navigation
Wins when your pages have a meaningful hierarchy that visitors can follow. Supply at least two ListItems, with position and name, and an item URL for each intermediate destination; the final item can omit its URL.
You do not have to include the home page or mirror the URL path mechanically. The following trail represents a plausible customer route to the current page.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Services",
"item": "https://www.example.com/services/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Water heaters",
"item": "https://www.example.com/services/water-heaters/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Tankless installation"
}
]
}
Loses when you expect breadcrumb trails in mobile Google results. Google removed those on 23 January 2025, across languages and regions; desktop support and the Search Console report remain.
Visible mobile breadcrumbs can still help users. In SearchPilot's travel-site test, server-side breadcrumb schema alone was inconclusive, while visible mobile breadcrumbs plus server-side schema produced a statistically significant 5% organic traffic uplift. That result does not isolate a schema-only benefit.
Article and BlogPosting: describe editorial pages
Wins when you publish actual articles and provide accurate headline, image, author and date information. Google has no required Article properties; Article, NewsArticle and BlogPosting can help it show better title text, images and dates.
Use timezone information in datePublished and dateModified, such as an explicit UTC offset. If publisher or author points to another node through @id, make the referenced entity resolvable; our own guide pages print the publisher Organization node and author Person node on the page.
Loses when you expect Article markup to be a requirement for Top stories or a ranking boost. Google does not require Article markup for Top stories, and filling optional fields with guesses makes the description less reliable.
Product snippets: editorial product information and ratings
Wins when a page focuses on one product, including a review or editorial page where visitors cannot buy it. Product snippet eligibility requires name plus at least one of review, aggregateRating or offers, with the selected object's own required fields.
Product is an eligible review subject. Our reading of Google's self-serving restriction is that reviews on a store's own product pages fall outside that restriction, which specifically names LocalBusiness and Organization.
Loses when a business labels an ordinary service page Product solely to obtain stars. Schema.org Service has no dedicated Google review-snippet eligibility; describe the actual subject and satisfy the applicable product requirements.
A purchasable product page can also qualify for product snippets. Merchant listings add a separate set of shopping requirements, so the two labels describe overlapping opportunities rather than interchangeable validation checklists.
Merchant listings: product pages where customers can buy
Wins when the page sells a single product or its variants and exposes accurate purchase details. Google's merchant-listing requirements require Product name, image and offers; the Offer needs price or priceSpecification.price, plus priceCurrency.
The example price is an assumed $3,890, not a market quotation. Its shipping and return terms are also hypothetical and must match the page before anyone deploys it.
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Condensing tankless gas water heater, supplied and installed",
"image": [
"https://www.example.com/images/re199in-1x1.jpg",
"https://www.example.com/images/re199in-4x3.jpg",
"https://www.example.com/images/re199in-16x9.jpg"
],
"description": "Indoor condensing tankless gas water heater, supplied and installed, including removal of the old tank.",
"sku": "HL-RE199IN-INST",
"offers": {
"@type": "Offer",
"url": "https://www.example.com/shop/re199in-installed/",
"price": 3890.0,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"itemCondition": "https://schema.org/NewCondition",
"shippingDetails": {
"@type": "OfferShippingDetails",
"shippingRate": {
"@type": "MonetaryAmount",
"value": 0,
"currency": "USD"
},
"shippingDestination": {
"@type": "DefinedRegion",
"addressCountry": "US",
"addressRegion": "OR"
},
"deliveryTime": {
"@type": "ShippingDeliveryTime",
"handlingTime": {
"@type": "QuantitativeValue",
"minValue": 1,
"maxValue": 3,
"unitCode": "DAY"
},
"transitTime": {
"@type": "QuantitativeValue",
"minValue": 0,
"maxValue": 1,
"unitCode": "DAY"
}
}
},
"hasMerchantReturnPolicy": {
"@type": "MerchantReturnPolicy",
"applicableCountry": "US",
"returnPolicyCountry": "US",
"returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
"merchantReturnDays": 30,
"returnMethod": "https://schema.org/ReturnByMail",
"returnFees": "https://schema.org/FreeReturn"
}
}
}
Loses when prices and availability depend on fragile client-side injection. Google can process rendered structured data, but warns that dynamically generated markup can make Shopping crawls less frequent and less reliable.
For shipping and return policies, Merchant Center and Search Console settings take precedence over markup; do not extend that precedence rule to every product field. On 7 July 2026, Google added category and clarified sale-duration use of the existing validFrom, validThrough and priceValidUntil properties.
VideoObject: video details and explicit key moments
Wins when a page contains a video you can describe accurately. Required properties are name, thumbnailUrl and uploadDate; useful recommended fields include contentUrl, embedUrl, description and duration.
For explicit key moments, each Clip requires name, startOffset and url; endOffset is recommended. Offsets are in seconds, and the destination URL must take the viewer to the corresponding point.
Loses when chapter URLs do not actually seek or the markup describes a video the visitor cannot access on the page. SeekToAction is another key-moment mechanism, while BroadcastEvent serves the LIVE badge; neither is a reason to add imaginary playback capabilities.
Google added creator/author guidance on 24 September 2026. If you need to opt out of key moments, Google's documented control is nosnippet, which deserves consideration beyond the video feature because it affects snippets.
Event: public attendance at a physical place
Wins when a page describes one event that the general public can book at a physical location. Required properties are name, startDate, location and location.address; provide the UTC offset in the start time.
The free workshop example satisfies those structural conditions. Free admission does not remove the need for a genuine event page and accurate attendance details.
{
"@context": "https://schema.org",
"@type": "Event",
"name": "Homeowner workshop: winterizing your plumbing",
"startDate": "2026-11-14T10:00:00-08:00",
"endDate": "2026-11-14T12:00:00-08:00",
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
"location": {
"@type": "Place",
"name": "Harbor Line Plumbing showroom",
"address": {
"@type": "PostalAddress",
"streetAddress": "1420 SE Water Ave",
"addressLocality": "Portland",
"addressRegion": "OR",
"postalCode": "97214",
"addressCountry": "US"
}
},
"image": "https://www.example.com/images/workshop-16x9.jpg",
"description": "A two-hour hands-on session on shutting off, draining and insulating home water lines before the first freeze.",
"offers": {
"@type": "Offer",
"url": "https://www.example.com/events/winterizing-workshop/",
"price": 0,
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"validFrom": "2026-10-20T09:00:00-07:00"
},
"organizer": {
"@type": "Organization",
"name": "Harbor Line Plumbing",
"url": "https://www.example.com/"
}
}
Loses when the event is an online-only webinar, invitation-only meeting or members-only gathering. Since 5 June 2025, Google's documentation requires a physical component and public bookability; business hours, coupons and sales are also ineligible substitutes for events.
JobPosting: maintain real vacancies through their lifecycle
Wins when you publish actual openings and can keep each vacancy page accurate. JobPosting remains supported, and Google recommends its Indexing API for job-posting URLs.
Loses when recruitment markup is installed without anyone owning vacancy updates. Check the current JobPosting required-property checklist for the actual job arrangement before deployment; a generic company careers introduction is not an individual opening.
For a company hiring occasionally, this is conditional work with an operational owner. The person closing the vacancy should also trigger the page and indexing update.
Retired features, Dataset and Service: keep a dated record
Wins when a non-Google consumer actually needs the vocabulary you retain. Dataset still serves Dataset Search, Book Actions still has a remaining use, and Service can describe services for other consumers without producing a dedicated Google rich result.
Loses when valid schema.org output is counted as evidence that a Google feature exists. The Google Search documentation changelog records the following restrictions and retirements.
- 16 September 2019Self-serving business stars restricted
LocalBusiness and Organization review stars stopped appearing when the reviewed entity controls the reviews. Embedded third-party widgets are included.
- 8 August 2023FAQ eligibility narrowed
FAQ rich results became limited to authoritative government and health sites. Google also said unused structured data causes no Search problems and has no visible effects.
- 13 September 2023HowTo fully deprecated
HowTo stopped appearing on desktop after its earlier mobile removal. The feature was fully deprecated.
- 21 November 2024Sitelinks search box removal began
The search box was removed. WebSite support for site names survived.
- 23 January 2025Mobile breadcrumbs removed
Breadcrumb trails disappeared from mobile results. Desktop support remained.
- 5 June 2025Online-only events unsupported
Event guidance required public bookability and a physical location. Virtual experiences with no real-world component became unsupported.
- 12 June 2025Seven types entered the phaseout
Google named seven types for removal. Search Console reporting and Rich Results Test support disappeared for six on 9 September 2025, excluding Book Actions.
- 5 November 2025Practice problems retired and exceptions clarified
Practice problem was deprecated, with documentation removed on 6 January 2026; Dataset was clarified as Dataset Search only. Google removed the Book Actions deprecation banner because a feature still used its markup.
- 7 May 2026FAQ rich results ended
FAQ rich results stopped appearing entirely. Google removed their documentation on 15 June 2026.
| June phaseout type | Subsequent status |
|---|---|
| Book Actions | Deprecation banner removed 5 November 2025 |
| Course Info | Tooling removed 9 September 2025 |
| Claim Review | Tooling removed 9 September 2025 |
| Estimated Salary | Tooling removed 9 September 2025 |
| Learning Video | Tooling removed 9 September 2025 |
| Special Announcement | Deprecated 31 July 2025; tooling removed 9 September 2025 |
| Vehicle Listing | Tooling removed 9 September 2025 |
Leaving old FAQ or HowTo markup is harmless for Google Search, although it earns no corresponding feature. Remove it when that simplifies template maintenance; an emergency cleanup because it supposedly damages rankings has no supporting basis here.
Rankings and AI citations: separate mechanisms from measured effects
Schema markup is not a documented ranking boost. Google says a structured-data manual action removes rich-result eligibility without affecting web-search rankings, and its June retirements likewise did not affect rankings.
SearchPilot reported no detectable impact from switching microdata to JSON-LD in a controlled SEO test. JSON-LD is convenient and Google's recommended format, but changing the serialization is not a traffic strategy.
Google's AI optimization guidance says structured data is not required for generative AI search and there is no special schema.org markup to add. Microsoft's AI-answer optimization advice says schema helps search engines and AI systems understand content; that is a vendor explanation of a mechanism, not a measured citation lift.
The Ahrefs controlled study compared pages adding JSON-LD against about 4,000 matched control pages, using a 30-day before-and-after window. Its matched difference-in-differences results were:
Those pages already had 100 or more AI Overview citations. The result does not tell us about pages that are not cited yet; other limitations include pooled schema types, static JSON-LD only, coincident page changes and the short observation window.
Search Atlas also reported no consistent upward relationship between schema coverage and AI visibility. Treat that as vendor correlational research: its page states no sample size, and correlation cannot isolate schema's effect.
Delivery is a separate constraint. Vercel reported on 17 December 2024 that major AI crawlers including GPTBot, ClaudeBot and PerplexityBot did not render JavaScript; a crawler fetching HTML without rendering cannot see JSON-LD injected afterward.
That observation is dated, not a permanent claim about every crawler. The technical SEO and crawl-cost explanation helps distinguish initial HTML from rendered content when you investigate whether a consumer can receive your markup at all.
Validation: vocabulary, Google eligibility and indexed output
The Schema Markup Validator and Rich Results Test answer different questions. Passing either also leaves Google's display decisions unresolved.
Checks schema.org syntax and vocabulary across types, including types with no Google feature. It does not determine Google rich-result eligibility.
Checks Google-supported rich-result types from a URL or code, using smartphone by default. Shareable results are retained for about 90 days.

An FAQPage block can pass vocabulary validation with zero errors and warnings. That clean result cannot restore a retired Google feature.
Our example blocks returned zero errors and zero warnings in the Schema Markup Validator on 24 October 2026. An FAQPage block did too, while a negative-control Plumber block with ratingValue directly on it produced one unknown-field warning.
These examples were not run through the Rich Results Test. Run that test on your live URL, where serving behavior and the surrounding page can affect the result.
The old Google Structured Data Testing Tool is not the current Google eligibility checker. The Rich Results Test left beta on 7 July 2020; Google announced the old tool's move toward schema.org on 15 December 2020, the Schema Markup Validator was announced on 11 May 2021, and the old Google tool redirected from 9 August 2021.
For first-party evidence, our own crawl-budget guide on irongoo.com returned a PASS rich-results verdict through the URL Inspection API on 24 October 2026. Its detected items listed only Breadcrumbs, despite Article and Organization blocks also being present.
Our reading is that URL Inspection lists report-backed rich-result types, so absence from that list does not establish that Google ignored another node. Article, Organization and WebSite lack corresponding rich-result reports; do not use that observation as Google documentation of the inspector's internal behavior.
Run this command against your own page, replacing https://www.example.com/ with your page's URL. It extracts JSON-LD from initial HTML, so JavaScript-injected markup will not appear.
curl -s https://www.example.com/ | grep -o '<script type="application/ld+json">[^<]*' | sed 's/<script type="application\/ld+json">//' | python3 -m json.tool --json-lines
The pattern assumes the exact script opening tag shown, without extra attributes. --json-lines handles multiple JSON objects; plain json.tool can fail with Extra data.
If a theme or plugin controls stale FAQ blocks, injected JSON-LD or self-serving rating templates, website foundation work can move those decisions into maintained page templates. Fixing the emitter makes the correction repeatable across pages.
The six-step audit decision rule
- Inventory emitted types. Open the source of each distinct page template and search for
application/ld+json; record every@type. Check rendered output separately if the initial HTML contains none. - Identify an actual consumer. Match each type to Google's gallery and the dated restrictions, treating WebSite site names separately and Dataset as Dataset Search only. If no supported Google feature applies, retain it only for an identified consumer such as Bing, internal search or a maintained knowledge graph.
- Check completeness and visibility. Open the relevant Google requirements and tick off every required property. Match marked-up content to what visitors can actually read, see or use on the page.
- Remove self-serving business rating markup. Delete
reviewandaggregateRatingfrom LocalBusiness or Organization nodes when the reviews concern your own business. Check embedded widgets and shared templates as well as hand-authored blocks. - Verify the live and indexed page. Run the Rich Results Test on the live URL with its default smartphone agent, then inspect the indexed URL in Search Console. Watch the applicable rich-result reports for template or serving regressions.
- Validate remaining vocabulary separately. Use the Schema Markup Validator for syntax and schema.org vocabulary, including types Google does not consume. Record a clean vocabulary result separately from Google eligibility so an error-free FAQPage never becomes evidence of a working FAQ feature.
Put your next steps in order
Build on what you have just read with a free ebook on semantic SEO and AI visibility. Get worked examples, decision rules, checklists and a do-this-week action in every chapter, plus a six-week plan for your site.



