Check this page with an assistantOpens a chat asking it to summarise this article and name the evidence behind each claim.
Claude opens with the prompt on your clipboard: Anthropic does not support prefilled prompts on the web, and we would rather copy it than ship a button that drops it.
Schema Is a Label, Not a Bag of Keywords
Structured data gives machines explicit facts about the page: which organization it describes, where the page sits in a hierarchy, who published an article, or which price belongs to an offer. Google may use supported markup for richer search appearances, but correct markup does not guarantee a feature or a ranking increase.
The confusion starts because schema.org and Google Search are not the same catalog. Schema.org defines a broad vocabulary that many systems can use. Google maintains a smaller gallery of structured-data features with its own eligibility rules, required properties, and content policies. A type can exist at schema.org without producing a Google rich result.
For a small business, the goal is not maximum markup coverage. It is a small, accurate layer that reflects the visible site and survives ordinary changes to the name, address, logo, author, price, or navigation. Google’s guidance explicitly favors fewer complete and accurate properties over a larger set of incomplete ones.
The Six Types Most Small Businesses Should Evaluate
| Type | Where it belongs | What it can clarify |
|---|---|---|
| Organization | Home page or a single organization/about page | Name, logo, address, contact details, identifiers, profiles |
| WebSite | Home page | Preferred site name and alternate name |
| BreadcrumbList | Pages with a meaningful hierarchy | The page’s position and navigable parent path |
| LocalBusiness | Pages describing a real local business or location | Business type, location, hours, contact and actions |
| Article | News, blog, or article pages | Headline, dates, author, publisher, and representative image |
| Product | Supported product and variant pages | Product identity, offer, price, availability, ratings, policies |
This is a decision set, not a required bundle. A consultant with no public office may use Organization without LocalBusiness. A five-page brochure site may not need breadcrumbs. A service company should not add Product markup to a service just because “product” sounds commercial. Choose the most specific truthful type that has a maintained page and a documented use.
Organization and WebSite: Establish Identity Once
Google recommends Organization markup on the home page or one page that describes the organization; it does not need to be repeated across every URL. Include the legal or public name that matches the site, the canonical URL, a crawlable representative logo, relevant contact or address information, and sameAs references to authoritative profiles when they truly belong to the organization.
Use the most specific relevant Organization subtype. Google’s current documentation gives OnlineStore as an example for an ecommerce operation. Do not choose a subtype because it sounds more prestigious, and do not publish every social profile the company has ever opened. Identity markup should reduce ambiguity.
WebSite markup on the home page is Google’s documented path for expressing a preferred site name and optional alternate name. It does not replace the visible brand, title, logo, or consistent naming elsewhere. Markup is corroborating data, not a hidden rebrand.
LocalBusiness: Reflect the Real-World Operation
LocalBusiness is a subtype of Organization designed for business details such as hours, location, contact information, and supported actions. Use the most specific local subtype that accurately describes the business. Populate hours, address, phone, URL, and other facts from the same maintained source that feeds the visible location page and Google Business Profile.
Do not create a markup-only location that customers cannot visit or that the business does not actually operate. Do not hide a different name or address in JSON-LD. Google’s general structured-data policy requires markup to represent visible page content and warns that misleading data can lose rich-result eligibility or trigger a manual action.
For a multi-location business, each useful location page can describe that specific operation while the organization page describes the parent entity. The visible page still needs the customer information; schema does not rescue thin city pages. See the local SEO checklist for the profile, review, and citation controls surrounding the markup.
Markup That Usually Does Not Deserve the First Sprint
| Temptation | Why to pause | Better decision |
|---|---|---|
| Every plugin type enabled | More stale or contradictory data to maintain | Implement supported types with a page owner |
| FAQ markup on every page | General FAQ rich-result visibility is highly restricted and absent from the current feature gallery | Keep genuinely useful questions visible without promising a feature |
| Review stars for your own business | Self-serving LocalBusiness and Organization review markup is ineligible for review features | Display honest proof; follow the documented review type rules |
| Service markup sold as a rich result | A schema.org type does not automatically create a Google feature | Use Organization/LocalBusiness and strong visible service content |
| Hidden keywords in JSON-LD | Markup must describe visible content and is not a keyword field | Improve the actual page and label only true facts |
The Safe Build, Test, and Release Sequence
- Choose a documented feature and page set. Link the exact Google feature guide in the implementation ticket and list the qualifying templates.
- Map every property to a maintained source. Decide where the logo, author, price, hours, and identifiers originate and who updates them.
- Compare markup with the visible page. The same entity, offer, dates, and claims should be inspectable by a visitor.
- Validate representative rendered URLs. Use the Rich Results Test for supported features and inspect the final DOM, not only a local JSON formatter.
- Release a sample before scaling. Confirm Google can crawl the page, inspect it in Search Console, and watch enhancement reports for template errors.
- Monitor values, not just syntax. A perfectly valid old price or wrong author is a data-quality failure. Re-test after CMS, theme, catalog, or routing changes.
Keep a rollback path. Duplicate markup from a theme, app, and custom component can describe the same entity differently. The right fix is usually one owned generator, not another override.
Questions About Schema Markup
- Does schema markup improve Google rankings?
Google documents structured data as a way to understand page content and enable supported search appearances. It does not promise a ranking increase, and valid markup does not guarantee a rich result. Judge implementation by accuracy, eligibility, presentation, and qualified search outcomes, not a universal rank boost.
- Which schema should a small business use?
Most businesses should begin with accurate Organization information on the home or about page and BreadcrumbList on hierarchical pages. Add LocalBusiness, Article, Product, or another supported type only where the visible page genuinely satisfies that feature’s documentation. Fewer complete types are better than a sitewide bundle of speculative markup.
- Should schema markup be placed on every page?
Only markup that describes a page belongs on that page. Google recommends Organization markup on the home page or a single organization page, not necessarily everywhere. Breadcrumb and Article markup can be template-level when each instance is populated accurately. Product markup belongs on supported product experiences, not generic category pages.
- Is JSON-LD better than microdata?
Google supports JSON-LD, Microdata, and RDFa and generally recommends using the format that is easiest to implement and maintain; in most cases that is JSON-LD. The important controls are truthful values, supported types, complete required properties, visible agreement, crawlability, and testing after rendering.
Primary Sources Reviewed
- Google Search Central: Supported structured-data features
- Google Search Central: How structured data works
- Google Search Central: General structured-data guidelines
- Google Search Central: Organization structured data
- Google Search Central: LocalBusiness structured data
- Google Search Central: Breadcrumb structured data
Reviewed July 28, 2026. Google changes supported search features and property requirements; check the current gallery and type-specific guide before every implementation.
