Technical & AEO · 3 min read

Four Schema Mistakes That Break WordPress Sites Silently

Structured data fails without any visible error. The four faults we find most often, and how to catch them before they cost you rich results.

The short answer

Schema fails silently, which is why so many WordPress sites carry broken structured data for months without anyone noticing. The four faults we find most often are two plugins generating conflicting blocks, duplicate FAQPage blocks that make Google ignore both, schema describing content that is not on the page, and markup broken by a theme update nobody re-validated afterwards.

Two plugins, two conflicting blocks

A site runs Rank Math and also has schema output from the theme, or from a second plugin installed for one page and never removed. Both emit structured data and the two disagree.

Check the rendered HTML rather than the plugin settings, because what the browser receives is what search engines read. Search the page source for the JSON-LD script tag and count how many appear.

Duplicate FAQPage blocks

This one is specific and costly. A page that emits two FAQPage blocks, typically one from a plugin and one from a template, gets both ignored rather than one accepted.

The correct pattern is a single block containing all the questions on the page. On this site the answer-first question leads and the page FAQs follow, all inside one block, which is handled in the template so it cannot drift.

Marking up content that is not visible

Review markup where no reviews are displayed, FAQ markup for questions the visitor cannot see, and aggregate ratings assembled from nothing are all guidelines violations, and Google does issue manual actions for them.

The rule is that structured data must describe what is actually on the page. This catches out stores that add rating markup hoping for stars in search results before they have any reviews.

Breakage after an update

Theme and plugin updates routinely alter or overwrite structured data output, and nothing alerts you. Rich results simply stop appearing and the drop looks like an algorithm change.

Validate after every theme or plugin update, and otherwise a couple of times a year. It takes minutes with the Rich Results Test and the Schema Markup Validator, and it is the only way to know.

What to check, in order

  • Count the JSON-LD blocks in the rendered page source
  • Confirm exactly one FAQPage block per page
  • Run every template through the Rich Results Test, not just one page
  • Confirm every marked-up element is visible to a visitor
  • Re-run all of the above after any theme or plugin update

Key takeaways

  • Schema fails silently, so validation has to be a routine rather than a one-off
  • One FAQPage block per page, or Google ignores both
  • Never mark up content a visitor cannot see

Reading these regularly? Make Rangblaze a preferred source on Google and our posts surface higher in your own results.

FAQ

Questions that follow this one

  • Partly. Both generate reasonable defaults and neither knows your specific service structure. Expect to supplement with custom JSON-LD, and check the plugin is not producing a conflicting second block.

  • Marking up content that is not on the page can trigger a manual action. Accurate schema describing real page content carries no risk.

Your Brand Could Be Next

Your brand could be next

Send a few details and we will reply on WhatsApp with a first read on what we would do, before any talk of fees.

No cold calls and no email sequences, so you set the pace.