Schema Markup for FAQ is code you add to your website that tells search engines exactly what your content means. Not what it says. What it means. A price is a price, a review is a review, a question is a question. Google reads it, sometimes likes it, and sometimes rewards you with a rich result.
Rich results are the fancy bits you see on a search results page. Star ratings under a product link. A dropdown of questions and answers under a blog post. Stock status and price sitting right there before anyone clicks through. That extra real estate is free marketing, if you set it up correctly.
Where This Structured Data Language Comes From
All of this runs on a shared vocabulary called Schema.org. It’s a reference site, not a search engine, and not owned by Google alone. According to the Wikipedia entry on Schema.org, it publishes documentation and guidelines for marking up web pages using formats like microdata, RDFa, or JSON-LD, and its whole point is to standardize the tags webmasters use so that search engines can build rich, visual results from ordinary HTML.
Schema.org sits inside a bigger idea called the semantic web. The goal there is simple: make web content readable by machines, not just humans, without making it messy for the humans either. FAQ schema and Product schema are just two small, practical corners of that much bigger project.
FAQ Schema: Still Alive, Just Smaller
FAQ schema used to be a favorite trick. Add a few question-and-answer pairs in JSON-LD, and Google would show them as an expandable list right in the search results, sometimes taking up half the screen. That changed.
According to Google’s own Search Central documentation, Google now limits FAQ rich results mostly to well-known, authoritative sites, and for most other sites the FAQ snippet feature has been scaled back significantly. If you’re a small business marking up FAQs, don’t expect the old dramatic dropdown. You might still get it. You might not. Google’s documentation is upfront that this changed, so don’t build a strategy that depends entirely on it.
Here’s the part people miss: adding FAQ schema is still worth doing even without the guaranteed rich result. It helps Google understand the structure of your page. It can feed into featured snippets. And if your site does qualify, you get the bonus for free. Low cost, occasional high reward.
Product Schema: Where the Real Money Is
Product schema is a different story. This is the markup that shows price, availability, and star ratings directly on a search result for an ecommerce product page. For anyone selling online, this is not decoration. This is the difference between a plain blue link and a listing that looks like it belongs on a shelf.
To get this right, you need to mark up the basics accurately: product name, image, price, currency, and availability status. If you claim something is “in stock” in your schema but your site actually shows “out of stock,” Google’s Search Central guidelines are clear that this counts as a mismatch, and mismatches get pages excluded from rich results or flagged for spam review. Accuracy matters more than completeness here.
Review and rating markup is where most Sri Lankan ecommerce sites fall down. You cannot invent a 4.8-star rating and slap it on a page with zero real reviews. Google checks for this. If you don’t have real customer reviews yet, don’t fake the schema. Wait until you do.
JSON-LD Is the Format to Use
Schema.org supports three formats: microdata, RDFa, and JSON-LD. In practice, JSON-LD has become the default recommendation, including from Google itself, because it’s a clean block of code separate from your visible HTML. It doesn’t tangle with your page design. It doesn’t break your CSS. You can drop it in the page head and move on.
Most WordPress SEO plugins generate this automatically now, but automatic doesn’t mean correct. Always test with Google’s Rich Results Test tool before assuming it’s working. A lot of sites carry broken schema for months without noticing, because nothing crashes. It just quietly fails to earn the rich result.
If your site has deeper structural problems, schema won’t fix those. Bad site speed, broken navigation, and outdated plugins tend to sit underneath the more visible SEO issues. We’ve covered some of the common ones in Top 5 Big Website Mistakes Sri Lankan Businesses Make, and schema markup only helps once those basics are sorted.
The Honest Limits Here
Schema markup does not guarantee a rich result. It’s an eligibility ticket, not a confirmed booking. Google decides case by case, page by page, and sometimes changes the rules for entire categories overnight, like it did with FAQ snippets. Anyone promising guaranteed rich results is overselling.
It’s also uncertain exactly how much ranking weight Google gives to schema itself versus the content it describes. Google has said publicly, in various Search Central posts over the years, that structured data is mainly about enabling features, not a direct ranking factor. Treat any claim otherwise with suspicion.
Still, for FAQ pages and product listings, correctly implemented schema is one of the cheapest wins available in SEO. It costs a developer an afternoon. It costs nothing in ad spend. And when it works, it makes your listing look more trustworthy before anyone even clicks.
