Schema Markup for Business Websites: A Practical Guide to Structured Data in 2026

Schema markup has a reputation problem. Half the advice online promises rich results, stars, and instant visibility, and the other half treats it as a magic switch for AI search. Then Google retires a feature, and thousands of sites are left carrying markup that no longer does anything visible. In 2026, FAQ rich results are the clearest example.

This guide explains what schema markup actually does, what Google's documentation says about it, which types are worth adding to a typical business website, how to implement and test it, and which mistakes put your eligibility for rich results at risk. Every claim about Google's behavior comes from Google's own documentation, which we checked while writing this.

What is schema markup, and what does it actually do?

Schema markup is structured data added to a page that describes its content in a standard, machine-readable way, using the schema.org vocabulary. According to Google's introduction to structured data, it helps Google understand a page and classify it, such as labeling the ingredients and cook time on a recipe. It can also make a page eligible for expanded search appearances.

The word to notice is eligible. Google states plainly that valid markup does not guarantee a rich result. To qualify, the markup must include all required properties for the feature and follow Google's general and feature-specific guidelines. Even then, Google's systems choose what to show based on context, and may display an ordinary text result instead. Schema markup is a clarity signal and an eligibility requirement, not a ranking switch.

Which schema format should you use?

Use JSON-LD. Google recommends JSON-LD, placed in a script tag, when your setup allows it, because it is easier to implement and maintain at scale. Microdata and RDFa are also supported, and Google treats all three formats equally if the markup is valid and correctly implemented. The practical difference is maintenance: JSON-LD sits in one block, separate from your visible HTML, so a designer can change a layout without breaking the markup.

That separation is a convenience, but it brings a risk. Because the markup is not on the screen, it is easy to let it drift away from what the page really says. We cover that mistake below, because it is the one Google's policies care about most.

Which schema types are worth adding to a business website?

Start with the types that describe who you are and how your pages fit together, then add types for the specific content on each template. The list below is a sensible baseline for most service businesses and online stores.

• Organization: your name, logo, website, contact details, and official profiles. It belongs on the homepage and gives search engines and AI tools a clear, consistent picture of the entity behind the site.

• LocalBusiness (or a more specific subtype): for businesses with a physical location or a defined service area. It carries your address, opening hours, phone number, and geographic coverage.

• WebSite and BreadcrumbList: describe the site as a whole and the path to each page. Breadcrumb markup mirrors your visible navigation trail.

• Article or BlogPosting: for blog content. It identifies the headline, author, publisher, publication date, and last-modified date.

• Product and Offer: for ecommerce product pages, including name, image, price, currency, and availability.

• Review and AggregateRating: only where genuine reviews appear on the page and the rules for that feature are met.

• Service: for service pages, to describe what you provide and where.

• Person: for author or team pages, where it ties named experts to their credentials and profiles.

Google's list of supported features changes over time, so check its current structured data documentation before building a markup plan around any single feature. The FAQ example below shows why.

Is FAQ schema still worth adding in 2026?

Not for rich results. Google's FAQ documentation states that the FAQ rich result stopped appearing in Google Search from 7 May 2026, and the page now carries a notice that the feature is no longer shown. Adding FAQPage markup will not bring back the expandable questions under your search listing.

That does not make an FAQ section pointless. A well-written FAQ still answers real questions for visitors, supports long-tail searches, and gives AI answer engines short, self-contained passages to extract. The visible content is the asset. If your developer or plugin still outputs FAQPage markup, the Google page we reviewed does not address whether it remains permitted, so treat it as optional rather than a ranking tactic, and do not prioritize it over the types above.

How do you add schema markup to a page?

1. Decide what each template needs. Map page types to schema types: homepage to Organization and WebSite, service pages to Service, blog posts to Article, product pages to Product and Offer.

2. Write or generate the JSON-LD. Include every required property for the type, and add recommended properties where you have accurate data. Use the most specific applicable schema.org type.

3. Place it on the page it describes. Add the script block to the page head or body. Duplicate pages should carry the same markup.

4. Validate before publishing. Run the page through Google's Rich Results Test to catch syntax and missing-property errors.

5. Deploy by template, not by hand. Generate markup from your CMS fields so prices, dates, and authors stay accurate when content changes.

6. Monitor after launch. Use the rich result status reports in Google Search Console, since templating or serving issues can quietly break markup. The URL Inspection tool confirms that Google has found the structured data on a given page.

If you would rather have the implementation checked by a specialist, schema is a standard part of our technical SEO services, where it is reviewed alongside crawling, indexing, and site structure.

What are the rules Google sets for structured data?

Google's general structured data guidelines split into technical and content rules. The technical rules ask for a supported format, valid syntax, and pages that Googlebot can access, meaning you should not block them with robots.txt or noindex. The content rules matter more in practice:

• Mark up only what users can see. Markup must describe content that is visible on the page. Google's introduction adds that you should not mark up information users cannot see, even if it is accurate.

• Do not mislead. No fake reviews, no content unrelated to the page, and no markup that impersonates a person or organization or misstates ownership or affiliation.

• Be complete and current. Include all required properties and keep information up to date.

• Follow feature-specific rules. Each feature has its own requirements on top of the general ones.

• Follow the spam policies. Markup used to deceive is treated as a violation.

The consequence for a violation is worth knowing. A structured data issue can trigger a manual action, which, according to Google, removes the page's eligibility for rich results but does not affect its ranking in web search. You can check for one in the Manual Actions report in Search Console. That is a limited penalty, but losing rich result eligibility on your best product pages still costs clicks.

What are the most common schema markup mistakes?

• Marking up content that is not on the page. Prices, ratings, or FAQs that exist only in the JSON-LD break Google's visible-content rule.

• Copying markup between unrelated pages. A block written for the homepage does not describe a blog post.

• Leaving out required properties. The page then passes a syntax check but is not eligible for the feature.

• Inventing reviews or ratings. Self-written reviews are the clearest example of misleading markup, and they put your eligibility at risk.

• Letting markup go stale. A product that sells out, a price that changes, or an author who leaves should all be reflected in the markup the day it happens.

• Treating validation as the finish line. A pass in the Rich Results Test proves the syntax is valid, not that Google will show a rich result.

• Stacking plugins. Two SEO plugins or a theme and a plugin can output conflicting or duplicate blocks. Audit what your site actually emits.

How does schema markup work on WordPress, Webflow, and online stores?

WordPress

Most SEO plugins add Organization, WebSite, breadcrumb, and Article markup automatically. The risks are duplication and stale defaults: a theme and a plugin may both output the same type, and default author or logo values are often wrong. Check the rendered source of a few templates, rather than trusting the plugin settings screen. Our WordPress website development work includes this kind of template review.

Webflow

Webflow does not generate schema for you, so you add JSON-LD through custom code in the page or site settings, and use CMS fields to populate it for collection pages. That works well for blog posts and service pages, provided the field mapping is tested. See our Webflow development services for how we structure it.

Online stores

Product and Offer markup is the highest-value schema on most stores, because price and availability change often and should always match the visible page. Generate it from the product database rather than writing it by hand. Our ecommerce SEO services and ecommerce website development teams build and monitor this together.

Does schema markup help with AI search and answer engines?

It can help machines interpret your pages, but treat claims about guaranteed AI visibility with caution. The documentation we reviewed describes structured data as a way to help Google understand and classify page content, and says nothing that promises citation in AI-generated answers. What is reasonable to say is practical: clear entity information, accurate authorship, and well-structured, self-contained answers on the page make your content easier for any system to interpret.

That is why Invisio Solutions treats schema as one layer of a wider approach. The visible page does most of the work: direct answers under clear headings, consistent naming of your business, and sources you can verify. Markup then confirms those signals in a format machines can parse. For a broader view of how this fits a search program, see our SEO services.

What does a realistic schema rollout look like?

7. Week 1: Audit. Crawl the site, list the markup each template currently outputs, and note duplicates, errors, and missing types.

8. Week 2: Plan and build. Define the target schema per template, write the JSON-LD, and map CMS fields to properties.

9. Week 3: Test and deploy. Validate in the Rich Results Test, deploy on a few templates first, and confirm with the URL Inspection tool.

10. Week 4: Monitor. Check the Search Console rich result reports and the Manual Actions report, fix errors, and roll out to the remaining templates.

11. Ongoing: re-check markup after every redesign, plugin update, or CMS change, since these are the usual causes of silent breakage.

Because the work depends on templates, a redesign or rebuild is the cheapest moment to do it properly. Our website redesign services include structured data in the technical brief.

Get your structured data checked

Schema markup pays off when it is accurate, template-driven, and monitored. Invisio Solutions can audit the markup on your site, remove what is outdated or duplicated, and add the types that fit your pages.

Contact Invisio Solutions for a free written technical audit within 48 hours, or read about our web development approach.