Schema Markup for Small-Business Websites

Schema markup, also called structured data, is machine-readable information added to a web page to describe what the page contains. Google can use supported structured data to understand content and, in eligible cases, present a richer search result. It does not guarantee a rich result and it is not a shortcut to higher rankings.

For an ordinary small-business website, the most useful types are usually Organization, LocalBusiness, Article, BreadcrumbList and, for genuine online shops, the appropriate product and merchant-listing markup. Add only data that is accurate, visible where required and maintained when the business changes.

What structured data can and cannot do

Realistic expectations for schema markup

It can help with	It cannot guarantee
Clarifying the type and properties of content	Indexing or a ranking improvement
Making a page eligible for a supported rich result	That Google will show the rich result for every query
Providing consistent business, article, product or breadcrumb information	That incorrect or misleading business information will be trusted
Helping Google validate specific required and recommended fields	That markup will compensate for weak visible content

Google's supported search features change. A schema.org type can remain technically valid even when Google no longer uses it for a particular search appearance. Always check the current Google Search documentation rather than relying on an old plugin description or tutorial.

Organization markup

Organization markup can describe the entity responsible for the website. Depending on the business and implementation, useful properties may include the legal or public name, URL, logo, contact details, address and recognised identifiers.

Use real information. Do not add awards, accreditations, social profiles, founding dates or legal identifiers that cannot be verified. The visible website, contact page and structured data should not contradict one another.

Where it normally belongs

Organization information is usually implemented once through the site template, often on the home page, rather than copied manually into every article. The exact approach depends on the CMS and theme.

LocalBusiness markup

LocalBusiness is a more specific form of organization markup for businesses with a relevant local presence. It can describe details such as the business name, location, telephone number and opening hours.

Choose the most accurate type available rather than forcing an unrelated category. Keep opening hours, address and telephone data aligned with the visible site and the business's current public information.

Important limitations

• LocalBusiness markup does not create or verify a Google Business Profile.
• It does not guarantee visibility in local results or the map pack.
• It should not expose a private home address merely to fill a field.
• It should not describe a location that customers cannot genuinely use in the way the markup suggests.

Article markup for a blog

For editorial articles, Article or the more specific BlogPosting type can describe the headline, image, author or editorial organisation, publication date and modification date.

The visible dates and structured dates must agree. Update dateModified only when the article has been meaningfully reviewed or changed. Automatically refreshing dates without checking the content is misleading and can reduce trust.

Do not invent an expert author. If the publication uses an editorial-team byline, the structured data and visible byline should represent that arrangement honestly.

Breadcrumb markup

BreadcrumbList describes a page's position in the site's hierarchy. It is useful for a large editorial website because it reinforces relationships such as:

Home → Domains & Hosting → DNS → How to Change DNS Settings

The visible breadcrumb navigation should be useful to readers and should match the actual site structure. Do not create a misleading structured hierarchy that the user cannot navigate.

Product and merchant markup

An online shop may use product structured data to describe products, offers, prices, availability, ratings and related commerce information. Google's product documentation distinguishes between different search experiences and requirements, including product snippets and merchant listings.

The markup should be generated from the same product data used on the visible page. Manual price and availability values are likely to become inaccurate.

Common product mistakes

• The structured price differs from the visible price.
• Availability remains marked as in stock after the product sells out.
• Ratings are added without genuine visible reviews.
• The page marks up a category or service as though it were a specific purchasable product.
• Variant prices and identifiers are handled inconsistently.
• Shipping or returns information is copied into markup but not honoured by the business.

For a real catalogue, use the commerce platform's maintained product output or a carefully tested integration rather than writing JSON-LD separately for every product.

FAQ markup: do not expect an FAQ rich result

Older SEO guidance often recommended FAQPage markup to make ordinary business results expand with questions and answers. That advice is no longer suitable as a general small-business tactic.

Google restricted FAQ rich results to well-known authoritative government and health websites in 2023. Google subsequently removed FAQ from its current supported structured-data feature gallery for general implementation. A small-business website should therefore not add FAQ markup expecting a larger Google result.

You can still publish a useful visible FAQ for readers. The questions should answer real customer concerns and should not duplicate the rest of the page. The value is in the content and navigation, not an assumed search enhancement.

Review and rating markup

Review markup has detailed eligibility rules and is not a licence to add stars to every service page. Ratings must relate to a supported item, come from genuine visible review content and follow Google's guidelines.

A business should not mark up a self-created rating about itself. Do not copy a star average from an external platform into website schema unless the implementation and visible content genuinely meet the applicable rules.

Use JSON-LD where practical

Google generally recommends JSON-LD for structured data. It keeps the machine-readable block separate from the visible HTML and is normally easier to maintain than embedding microdata throughout the page.

The output should come from a reliable site-level source:

• the CMS or commerce platform;
• a single well-configured SEO or schema plugin;
• the theme or template system;
• a custom implementation maintained by the developer.

Avoid several plugins generating overlapping organization, article or breadcrumb markup. More structured data is not automatically better.

A safe implementation process

1. Identify the real page type and the Google feature, if any, that the markup is intended to support.
2. Read the current documentation for that specific type.
3. Map every property to a trustworthy source in the website or business data.
4. Generate the markup through one controlled system.
5. Test syntax and Google eligibility.
6. Inspect the rendered page source, not only the CMS settings screen.
7. Check that visible content and structured data agree.
8. Monitor Search Console enhancement reports where Google provides them.
9. Review the implementation when the business, template, platform or Google documentation changes.

Which validation tool should you use?

• Google Rich Results Test: checks eligibility and issues for rich-result types supported by Google Search.
• Schema.org validator: checks broader schema.org vocabulary and syntax, including types that Google may not use for a search feature.
• Google Search Console: reports detected items and issues for supported enhancement types after Google processes the pages.

Passing a validator means the markup is syntactically acceptable or eligible for consideration. It does not guarantee that Google will display a rich result.

What a small-business editorial blog should implement

For this type of website, a sensible baseline is:

• truthful Organization or appropriate publisher information;
• WebSite information where the implementation has a clear purpose;
• BreadcrumbList on hierarchical pages;
• Article or BlogPosting with real dates, byline and representative image;
• specific commerce markup only on genuine product pages;
• no unsupported schema added solely because a plugin offers a checkbox.

What to check before you act

Structured-data support changes. Recheck Google's current feature gallery and the documentation for the exact type before adding or revising markup. This article was fact-checked on 21 July 2026.

Sources and validation tools

• Google Search Central: structured data markup supported by Google Search (page last updated 15 June 2026; checked 21 July 2026).
• Google structured data general guidelines (checked 21 July 2026).
• Google Search Central: changes to HowTo and FAQ rich results (checked 21 July 2026).
• Google Rich Results Test.
• Schema.org validator.