Two pages at the same position: one shows only a single line of blue title, the other carries breadcrumbs, star ratings, and a few collapsible Q&As — taking up twice the space. The difference isn’t ranking; it’s whether structured data is marked up. It’s not a direct ranking factor, but it’s the ticket to rich results, and the cost is just one more block of JSON in the page.
Structured data comes down to three things done right: pick the right schema type, fill in all required fields, and run it through the official test before launch. Do all three and rich results appear consistently; miss any one and the display either never shows or gets pulled a few weeks later with no clue why.
What the common types each get you
More types isn’t better — what you mark must match content that actually exists on the page. Hard-marking a type the page doesn’t have fails at best, and at worst gets judged as a violation that takes away your rich-result eligibility.
| Type | Pages it fits | Display it gets | Key required fields |
|---|---|---|---|
| Article | Blog, news, tutorials | Article rich card | headline, author, datePublished |
| FAQPage | Body contains real Q&A | Collapsible Q&A in search results | question, acceptedAnswer |
| BreadcrumbList | Pages with a hierarchy path | Breadcrumb navigation | itemListElement, position |
| Product | Product detail pages | Price, stock, star ratings | name, offers, price |
| HowTo | Step-by-step tutorials | Step-based display | step, name |
One page can stack multiple types — a tutorial with Q&A can mark Article, FAQPage, and BreadcrumbList at once. For specifics, check the FAQ-to-win-featured-snippets approach.
Fill fields wrong and the markup is wasted
Every type has required and recommended fields; missing a required one fails the whole block, not “show a little less”. Article missing author or datePublished means no rich card; Product missing price and availability under offers means no star ratings.
The easiest to crash is FAQPage. The questions and answers in the markup must match the text users see on the page word for word. Three common mistakes: rewriting the answer into a shorter version, stuffing marketing talk into the answer, or the Q&A doesn’t exist on the page at all but is in the markup. All three get judged as content not matching markup, and the collapsible display gets pulled.
A practical habit when writing answers
Write the Q&A in the body first, then copy it into the markup — not the other way around. Reversed order almost guarantees mismatch, especially when you edit copy later and only change the body, forgetting the markup.
How to land it on WordPress and custom sites
Most sites don’t need hand-written JSON-LD. SEO plugins like Rank Math and Yoast auto-generate schema for articles, breadcrumbs, and products, avoiding hand-writing risk. But the plugin’s default output isn’t always enough — before launch, open the source and confirm the fields actually have values.
| Implementation | Best fit | Extra things to confirm |
|---|---|---|
| SEO plugin generation | WordPress and common CMS | Whether default required fields actually have values |
| Hand-written JSON-LD | Custom sites, special-structure pages | Whether it matches body text word for word |
| Theme built-in output | Some commercial themes | Fields are often missing and need filling in |
For custom sites, inject JSON-LD into the head and keep it same-source with page rendering — the same data renders as HTML and serializes as JSON-LD, avoiding mismatch at the root. Check the schema output in passing when editing templates.
Testing and monitoring flow before and after launch
Marking isn’t the same as taking effect; there are two gates in between. The first is the official rich results test — paste in the URL or code and confirm no errors and no warnings before launching; even warnings-only shouldn’t be ignored, because warning items are often exactly what gets the display pulled weeks later.
The second is ongoing monitoring. Search Console’s “Enhancements” report lists which pages are valid and which aren’t. Treat it as a regular dashboard alongside the Search Console coverage report, scan it every two weeks, and fix invalid items the same week.
- Markup done → rich results test passes → publish.
- A week later check the enhancements report and confirm the type shows up in the “valid” list.
- Export the invalid and warning list monthly and batch-fix by page type.
How to debug rich results that suddenly disappear
When a rich display flips from “valid” to “invalid” or simply stops showing, check in the order below — most issues are located within ten minutes.
First see whether the page is still in the index. If it’s noindexed, canonicalized to another URL, or the path changed in a redesign, the page isn’t indexed at all and the rich display naturally vanishes. This case has nothing to do with the schema itself — first confirm indexing status following the canonical-tag debugging flow, then talk markup.
If the page is indexed, check the markup itself: a template change dropped a field, a plugin update changed the output structure, or an editor’s body edit made the FAQ mismatch. These three cover the vast majority — roll back or fill the field and it recovers, usually without re-marking.
There’s also a case easily misread as a bug: the markup is completely correct, but the search engine decides the query doesn’t warrant rich display. Rich results don’t necessarily appear just because you marked up — the markup only makes you eligible.
Five things to run through before landing
Pick 3 articles that already have real Q&A in the body and add FAQPage markup, copying the Q&A text straight from the body; spot-check 5 articles’ Article markup and confirm headline, author, and datePublished all have values; check the site-wide breadcrumb BreadcrumbList so the hierarchy matches the path shown on the page; add the “Enhancements” report in Search Console to the biweekly routine and fix invalid items the same week; a week later revisit the report, confirm the new FAQ appears in the valid list, then expand to more pages. Do these five and rich displays land for good.
FAQ
Is structured data a ranking factor?
Not a direct ranking factor, but it’s the ticket to rich results. Done right it gets you breadcrumbs, star ratings, and collapsible Q&A — double the footprint and higher CTR.
Why doesn’t my structured data show?
Mostly required fields missing or inconsistent with the body. Article missing author or datePublished means no rich card; FAQ answers must match the body word for word. Run it through the rich results test before launch.
What happens if FAQPage markup doesn’t match the body Q&A?
It gets judged as content not matching markup and the collapsible display is pulled. Write the Q&A in the body first, then copy into the markup — not the reverse; editing copy in the body while forgetting the markup is a top crash point.
Does WordPress need hand-written JSON-LD?
Mostly no. Rank Math and Yoast auto-generate article, breadcrumb, and product schema, but open the source before launch to confirm required fields have values; theme built-in output often misses fields and needs filling in.
