Schema Markup Mistakes to Avoid

Mistake 1: Marking Up Content That Is Not Visible on the Page

Google’s structured data guidelines require that schema markup describe content that is actually present and visible to users on the page. Generating review stars for a page with no reviews, adding FAQ schema with questions that do not appear on the page, or including product prices that differ from the displayed price all violate this principle.

Google uses this requirement to prevent schema from being used as a vehicle for displaying misleading information in search results. If your schema describes content that a user cannot see when they visit the page, Google may issue a manual action (penalty) against your structured data, removing your rich results entirely.

The fix: audit your schema markup against the visible page content. Every property value in your schema should correspond to something a user can see, read, or interact with on the page.

Mistake 2: Self-Reviewing or Fabricating Reviews

Adding AggregateRating schema with review data that you created yourself, reviews from a different product applied to a new product, or entirely fabricated ratings violates Google’s review markup guidelines. Google has become increasingly sophisticated at detecting fake review markup and has specifically cracked down on self-serving review schema.

Only use review and rating schema when you have genuine, verifiable reviews from real customers. The reviews should be about the specific product or service described on that page, not imported from other products or platforms where they were left about something different.

Mistake 3: Using the Wrong Schema Type

Applying Product schema to a blog post, using Article schema on a product page, or using LocalBusiness schema on a page about a purely online business sends confusing signals to search engines. Each schema type carries semantic meaning, and misapplying types undermines the trust search engines place in your structured data.

A common example: using Product schema for a service that has no fixed price, SKU, or availability status. Service schema or Offer schema may be more appropriate, depending on the specifics. Choose the schema type that most accurately represents what the page content actually describes.

Mistake 4: Duplicate or Conflicting Schema on the Same Page

When a CMS theme generates Article schema automatically, a plugin generates its own Article schema, and a developer adds a third set manually, the page ends up with three conflicting versions of the same markup. Search engines must decide which one to use, and they may choose the wrong one or ignore all of them.

Before adding any schema markup, check what your existing tools already generate. Use the Rich Results Test on a live page to see all structured data currently present. Remove or consolidate duplicates before adding new markup.

Mistake 5: Incomplete Required Properties

Each schema type has required properties that must be present for the markup to be valid. Product schema requires a name. Recipe schema requires a name and image. Review schema requires a reviewRating. Missing required properties cause Google to reject the markup entirely.

Beyond required properties, many recommended properties significantly affect whether Google displays rich results. Product schema without a price or availability property is technically valid but unlikely to earn product rich results. Article schema without an image property misses potential for visual enhancements in search results.

Check Google’s structured data documentation for each schema type to see the full list of required and recommended properties. Implement as many recommended properties as you have data for.

Mistake 6: Hard-Coded Values That Become Stale

A product’s schema lists a price of $29.99, but the actual price changed to $34.99 three months ago. An event’s schema still shows last year’s date. A business’s schema lists hours that were updated during a holiday season and never changed back.

Static schema values become inaccurate as page content changes. For dynamic content (prices, availability, hours, events), schema values should be generated dynamically from the same data source as the visible page content. If the product price updates in your CMS, the schema price should update automatically.

For static schema (homepage Organization markup, for instance), include it in your content audit calendar and verify accuracy at least quarterly.

Mistake 7: Spammy FAQ Schema

FAQ schema was widely abused after Google began displaying FAQ rich results. Sites added FAQ markup to every page, regardless of whether genuine FAQ content existed. Questions were stuffed with keywords. Answers were thinly veiled sales pitches rather than helpful responses.

Google has since tightened FAQ rich result display, showing them less frequently and primarily for authoritative sources. Use FAQ schema only on pages where genuine, helpful FAQ content appears. Write questions in natural language, provide substantive answers, and avoid using FAQ sections as keyword stuffing opportunities.

Mistake 8: Ignoring Validation Errors After Deployment

Many teams implement schema markup, celebrate the initial deployment, and then never check whether it continues to work. Site redesigns can break template-based schema. CMS updates can conflict with schema plugins. Content changes can invalidate previously correct markup.

Google Search Console reports structured data errors in its Enhancements section. Check this section monthly. Errors mean your rich results are not displaying, and warnings may indicate emerging problems. Fix errors promptly, as they represent lost rich result opportunities.

Mistake 9: Applying Schema to Every Page Indiscriminately

Not every page needs every type of schema. A privacy policy page does not need Article schema. A category listing page does not need Product schema for every product in the list. Your 404 error page does not need Organization schema.

Be selective. Apply schema where it adds genuine semantic value and where there is a realistic possibility of earning a rich result. Spreading thin, low-quality schema across your entire site dilutes the signal and increases maintenance burden without proportional benefit.

Mistake 10: Forgetting About Schema When Redesigning

Site redesigns frequently break schema markup. New templates may not include the JSON-LD blocks. New page structures may invalidate the property mappings in your schema plugins. New content layouts may cause schema values to reference elements that no longer exist.

Include schema markup as a checklist item in every site redesign or migration plan. Before the new site goes live, validate schema on representative pages of every type. After launch, monitor Search Console for a spike in structured data errors. Many redesign-related schema breaks are only discovered weeks later when rich results disappear from search.

How to Fix Existing Schema Problems

Run your site through Screaming Frog or a similar crawler with structured data extraction enabled. Export all schema instances with their validation status. Prioritize fixes based on page traffic and schema type. High-traffic product pages with broken Product schema should be fixed before low-traffic blog posts with missing Article properties.

After fixing, use Google Search Console’s URL Inspection tool to request re-evaluation of specific pages. Monitor the Enhancements section to confirm that valid page counts increase and error counts decrease over the following weeks.