Schema Markup Guide: FAQPage, LocalBusiness and Product Structured Data Explained

Schema markup (structured data using the schema.org vocabulary, typically implemented as JSON-LD) tells search engines and AI systems explicitly what a piece of content actually is — a product with a specific price, a local business with specific hours, a question with a specific answer — rather than leaving them to infer it from unstructured page text. Three types matter most for a typical small business site: FAQPage, LocalBusiness, and Product.

FAQPage Schema: Turning Real Q&A Into Rich Results

FAQPage schema marks up genuine question-and-answer content on a page in a machine-readable format, which can make that Q&A eligible for expandable rich results directly in Google's search listing — visibly taking up more space in search results than a standard listing, which itself tends to improve click-through rate. The specific requirement worth noting: the questions and answers must genuinely appear as visible content on the page itself, not be schema-only content invisible to actual visitors — Google has explicitly tightened enforcement of this, and schema not matching visible page content risks the rich result being denied or, in more serious cases, being treated as a manipulation attempt.

LocalBusiness Schema: Structured Business Information

LocalBusiness schema (or its more specific subtypes — Restaurant, ProfessionalService, and others depending on the actual business type) structures a business's name, address, phone number, hours, and often price range and accepted payment types in a format search engines can parse reliably, reinforcing the same NAP consistency signals that matter for local SEO more broadly. This schema type is particularly valuable for businesses with a physical location relying on local search visibility, since it directly reinforces the information Google's local ranking systems already weigh heavily.

Product Schema: Direct E-commerce Search Visibility

Product schema marks up price, availability, and review/rating data for individual products, which can make listings eligible for rich product results in search — showing price and star rating directly in the search listing before a user even clicks through. For an e-commerce site, this is one of the highest-leverage schema types available, since price and rating visible directly in search results measurably affects click-through rate compared to a standard text-only listing.

Implementation: JSON-LD Is the Recommended Format

Google explicitly recommends JSON-LD format (a self-contained script block, typically placed in the page head) over the older microdata or RDFa approaches, since it's easier to implement correctly and doesn't require interweaving markup directly into visible HTML content, reducing the chance of implementation errors that break the visible page layout.

A Common Mistake: Schema That Contradicts the Page

Schema marking a product as "in stock" when the actual page shows it as sold out, or FAQ schema listing questions that don't actually appear as visible content, both violate Google's structured data guidelines and risk manual action, not just a missed rich-result opportunity. Schema should describe what's genuinely, visibly on the page — never used to make a claim the actual page content doesn't support.

How to Verify Implementation

Google's Rich Results Test tool directly validates whether a page's schema is correctly formatted and genuinely eligible for the intended rich result type — running every page with schema markup through this tool after implementation (and periodically afterward, since a template change can silently break schema across many pages at once) catches errors before they cost real search visibility.

Monitoring Schema Health Over Time

Schema markup implemented once at launch can silently break later — a template update, a CMS plugin change, or a content restructuring can invalidate previously working schema without any obvious visible symptom on the page itself, since broken schema doesn't usually affect how a page looks to a visitor, only how search engines interpret it. Periodically re-running key pages through Google's Rich Results Test (quarterly is a reasonable cadence for most sites) catches this kind of silent breakage before it costs meaningful search visibility.