This guide is for owners who already understand what schema markup is and have some on their site, but aren’t seeing the payoff — the star ratings, FAQ drop-downs, breadcrumbs and other “rich results” that make a listing stand out in Google. If schema is brand new to you, start with our beginner guide on what schema markup is and how to add it without code. Here we focus on the difference between having schema and having schema that actually works: the right types, error-free markup, properly connected schemas, and continuous validation.
Adding schema does not guarantee a rich result. Google shows enhanced listings only when three things are true: the schema is a type Google supports rich results for, it is valid with every required property present, and it genuinely matches the visible content of the page. Most sites fall down on at least one of these without realising, because the markup is invisible — it sits in the page’s code, so a missing field or wrong type produces no obvious symptom, just a quietly ordinary listing while a competitor’s shows stars and FAQs. The whole job at this level is closing those gaps deliberately rather than hoping a plugin got it right.
The most common and costly mistake is using the wrong schema type for the page. Schema types are specific, and rich results are tied to them. Organization (or LocalBusiness for a physical business) describes your business as a whole and belongs site-wide, typically on the home page. Product belongs on a product page and can earn price and availability and review-star results. Article belongs on blog posts and news. FAQPage belongs on pages with genuine question-and-answer content and can earn expandable FAQ results. HowTo suits step-by-step instructions. BreadcrumbList produces the breadcrumb trail under your title.
Map your important pages to the correct type before anything else. Think of it page by page: your home page carries Organization or LocalBusiness; each product page carries Product; each blog post carries Article; a contact or about page might carry WebPage plus Organization; a genuinely Q&A-led page carries FAQPage; a tutorial carries HowTo. A common error is slapping Organization on every page, marking a whole blog index as Article, or adding FAQPage to a page with no real questions — all of which either do nothing or risk a manual penalty for mismatched markup. The rule is simple: the type must describe what the page actually is, and the marked-up content must be visible to the user.
It’s also worth knowing which types currently earn a visible enhancement, because that’s where to spend effort first. Product can show price, availability and review stars. FAQPage can show expandable questions directly in the result. BreadcrumbList shows the navigation trail under your title. Review and AggregateRating add stars. Article strengthens eligibility for news and top-stories style placement. Recipe, Event, Video and HowTo each have their own enhancements. Organization and WebSite rarely show a visible badge themselves but underpin everything and feed your knowledge-panel and sitelinks search box. Decide which of these genuinely apply to your pages and prioritise them. Generate the correct type per page with the AI Schema Generator, which reads the page and picks the appropriate type for you.
Google will not show a rich result for schema that contains errors or omits required properties, and “errors” here is broader than broken code. Each rich result type has required and recommended fields: a Product needs a name and offers; a review needs an author and a rating with a defined scale; dates must be in the correct machine format; nested references between items must resolve. Miss a required field and you’re disqualified from that rich result entirely, even though the rest of the markup looks fine.
The only reliable way to know is to test. Run your pages through the Schema Debugger, which parses your existing schema and flags errors, missing required properties, and warnings in plain language. Understand the difference between the two things it reports. Errors are hard disqualifiers — a required property is absent or malformed, and Google will not show the rich result at all until it’s fixed. Warnings are recommended properties that are missing; you can still qualify without them, but adding them strengthens your eligibility and often improves how the result looks. Work through every error first, then close as many warnings as you reasonably can.
The specifics that trip most sites up are worth calling out. Dates must be in the correct machine format rather than how you’d write them for a reader. Ratings need both a value and the scale they’re out of. Prices need a currency. Images referenced in schema must actually exist and be crawlable. And nested references — where one item points to another, such as an Article’s author pointing to a Person, or a publisher pointing to your Organization — must resolve to something real, or the whole block can fail. Fix these methodically, page type by page type, and re-test until the Debugger is clean. This single step is where most owners unlock rich results they were already nearly qualified for.
Strong sites don’t rely on a single isolated block; they use several schemas that reference one another so Google receives one coherent picture. A typical setup links WebSite and Organization at the site level, a WebPage for the page itself, a BreadcrumbList for navigation, and a page-specific type such as Article, Product or FAQPage — with the page’s author and publisher pointing back to the Organization. When these connect properly (sharing consistent identifiers and references), Google can resolve who published what, where it sits in your site, and what it’s about, which makes more rich result types eligible at once and reduces ambiguity. Inconsistent or contradictory blocks — two different business names, a publisher that doesn’t match the Organization — do the opposite, so consistency across all your schemas matters as much as any single block.
In practice the way to get this right without hand-coding is to generate each block with a tool and keep your business details identical across all of them — the same business name, the same URL, the same logo — so nothing contradicts. Then validate the page as a whole, not block by block, because the value is in how they connect. A page whose schemas agree with each other and with the visible content is one Google can trust and act on; a page of disconnected, slightly inconsistent fragments is one it tends to ignore.
Beyond the basics, target the rich results that suit your business. A local service should ensure complete LocalBusiness markup with hours, area served and contact details, which underpins its map and knowledge-panel presence. A shop should add Product with offers and aggregate ratings so price and stars can show. A content site should use Article with a clear, real author and accurate published and modified dates, which supports freshness and authorship signals. And almost every site benefits from an honest FAQPage section on its key pages.
That last point is worth dwelling on, because FAQPage is the highest-leverage type for most owners. A genuine set of questions and answers does three jobs at once: it can earn an expandable FAQ rich result, it answers real customer questions on the page itself (which helps conversion), and the clear question-then-answer structure is exactly what AI search engines like ChatGPT and Perplexity extract and quote. Write the questions as the things customers actually ask, answer each directly in a sentence or two, and mark them up. The one rule across all of this: add only what genuinely reflects the visible page. Never fabricate reviews, ratings or FAQs to chase a result — Google detects markup that doesn’t match real content and penalises it, which costs you far more than the result was worth.
Schema isn’t set-and-forget. Every time you change a template, add a plugin, or redesign a page, your markup can break or change. Make validation a habit: after any change, re-run the affected pages through the Schema Debugger, and keep an eye on the enhancement reports in Google Search Console, which flag schema errors Google finds across your site and tell you when rich results start appearing. Bear in mind that even perfect, valid schema is an eligibility signal, not a guarantee — Google decides when to show a rich result — and that it can take time after fixing errors for the enhanced listing to appear as Google re-crawls.
A small shop has Product schema on every product page via its platform, but no stars or prices ever show in Google. Running the pages through the Schema Debugger reveals the offers block is missing a required field and the review markup has no defined rating scale — both hard disqualifiers. The owner regenerates correct Product markup with the generator, ensuring offers and a properly defined aggregate rating are present, and connects it to the site’s Organization schema. They re-validate until every page is error-free, then watch Search Console’s enhancement report. Over the following weeks, price and star-rating rich results begin appearing, and the product listings start standing out against competitors whose markup is still quietly broken. The content didn’t change — the markup finally became valid and complete.
The recurring ones at this level: using the wrong type for the page, or Organization everywhere. Leaving out required fields so a rich result silently never appears. Marking up content that isn’t visible on the page, which risks a penalty. Contradictory details across multiple blocks. Adding fake reviews or FAQs to chase results. And never re-validating after template or plugin changes, so markup that once worked quietly breaks. Each is detectable with the Debugger and fixable.
Usually the schema has errors or missing required fields, is the wrong type for the page, or doesn’t match the visible content. Run the Schema Debugger to find the exact problem. Note that valid schema makes you eligible but Google still decides when to display a rich result.
Match the type to the page: Organization or LocalBusiness site-wide, Product on product pages, Article on posts, FAQPage on Q&A pages, HowTo on instructions, BreadcrumbList for navigation. The type must describe what the page actually is.
Yes. Marking up content that isn’t visible, or using a type that doesn’t match the page, can trigger a manual penalty as well as failing to produce results. Only mark up genuine, visible content.
Yes. Linking WebSite, Organization, WebPage, BreadcrumbList and a page-specific type into one consistent graph gives Google a complete picture and makes more rich result types eligible at once.
After every template change, plugin update or redesign, re-validate the affected pages, and monitor the enhancement reports in Google Search Console. Markup that worked can break silently.
It varies. Once your markup is valid, Google has to re-crawl the pages and decide to show the result, which can take days to weeks. Search Console’s enhancement report shows when it picks up your fixes.