Rich results — star ratings, FAQ dropdowns, price displays, and how-to cards — dramatically increase click-through rates. But schema markup mistakes disqualify your pages from these enhanced listings. Here is what breaks structured data.
Rich results — the enhanced Google search listings that display star ratings, FAQ dropdowns, price information, how-to steps, and event details — generate dramatically higher click-through rates than standard blue-link results. Studies show FAQ rich results increase CTR by 20 to 30%. Product rich results with star ratings see CTR improvements of 15 to 35%.
Eligibility for these rich results requires correctly implemented structured data (schema markup). Schema errors are surprisingly common and specifically disqualify pages from rich results — not just diminish them. These are the mistakes that block eligibility.
Mistake 1: Using Microdata or RDFa Instead of JSON-LD
There are three formats for implementing schema markup: Microdata (attributes in HTML elements), RDFa (similar HTML attribute approach), and JSON-LD (JavaScript object in a <script> tag). Google recommends JSON-LD, and while all three are theoretically supported, JSON-LD is the only format that is reliably processed for rich result eligibility.
Fix: Implement all structured data as JSON-LD in a <script type="application/ld+json"> tag in the page <head>. JSON-LD has the additional advantage of being independent of page markup — it does not require wrapping HTML elements in class attributes and is easy to maintain and debug.
Mistake 2: Missing Required Properties for Rich Result Eligibility
Each rich result type has a specific set of required properties. Missing any required property disqualifies the entire schema object from rich result eligibility — even if all other properties are correct. For example, Product schema without offers is valid JSON-LD but ineligible for Product rich results. Review schema without itemReviewed cannot generate review rich results.
Fix: Consult Google's Rich Results documentation for the exact required properties for each rich result type you want to implement. Use Google's Rich Results Test to validate eligibility (not just JSON-LD validity). The test explicitly identifies missing required properties.
Mistake 3: Schema Content That Does Not Match Visible Page Content
Google explicitly disqualifies schema that contains information not visible to users on the page. This is a spam prevention measure — if your schema claims 4.9 stars but the page displays no reviews, or if your FAQ schema contains answers not visible in the page content, Google will remove rich result eligibility and may apply a manual action (penalty).
Fix: Every value in your schema must match or directly correspond to visible content on the page. Review content must be shown on-page. FAQ answers in FAQPage schema must appear in visible FAQ sections. Price in Product schema must match the displayed price. Schema cannot contain information that supplements or contradicts the visible page content.
Mistake 4: Multiple Conflicting Schema Objects of the Same Type
Pages with multiple Product schemas, multiple Organization schemas, or multiple FAQPage schemas confuse Google's parser. It cannot determine which schema object to use for rich result generation, and often ignores all of them. This is a common mistake when CMS plugins or theme templates automatically generate schema that conflicts with manually added schema.
Fix: Ensure only one schema object of each type exists per page. Audit all schema on a page using Google's Rich Results Test or Chrome's developer tools (Network tab, filter by "json"). If using a WordPress plugin that auto-generates schema, disable its output for specific types that you are managing manually.
Mistake 5: Aggregate Rating Schema Without Actual Reviews
Showing an aggregate rating (star display) in search results requires AggregateRating schema with a valid ratingValue and reviewCount greater than zero, and those reviews must be real reviews visible on the page. Adding fake or empty aggregate rating schema to show stars in search results is a spam violation that Google actively detects and penalizes.
Fix: Only implement AggregateRating when your product or service actually has user reviews, and those reviews are displayed on the page. For businesses that want star ratings in local search, focus on Google Business Profile reviews rather than schema-based product ratings.
Mistake 6: Event Schema Without Required Date Properties
Event rich results can display event dates, locations, and ticket links directly in Google search. But Event schema without startDate is invalid and ineligible. Events with past dates are automatically deprioritized. Events missing location (for in-person events) or eventAttendanceMode are ineligible for the enhanced event listing format.
Fix: For each event, include: name, startDate (ISO 8601 format), endDate, location (with Place schema for in-person, VirtualLocation for online), organizer, and offers if tickets are available. Remove or update schema for past events — outdated event schema wastes crawl budget.
Mistake 7: Not Monitoring Rich Result Status in Search Console
Rich result eligibility changes as pages are updated, templates change, or Google updates its rich result requirements. Many sites had valid schema generating rich results, then lost them after a CMS update — and nobody noticed for months because nobody was monitoring.
Fix: Check Google Search Console's Enhancements section monthly. Each supported rich result type (FAQ, Product, Events, Reviews, How-to, etc.) has its own report showing valid, warned, and errored items. Set up Search Console email alerts for sudden drops in rich result coverage.
Schema Markup Done Right
Properly implemented schema markup is one of the highest-ROI technical SEO investments available. A single implementation of FAQPage schema across your service pages, done correctly, can improve click-through rates across all those pages simultaneously — with no ongoing effort once implemented.
App Basis Inc implements comprehensive structured data strategies for DFW businesses. Contact us to audit your existing schema or implement a structured data plan.