Which rich results can we win?

This is an on-page SERP-features question — the kind that usually shows up from sEO specialist, content. It rarely has a one-line answer, because the honest version of “Which rich results can we win” is a shortlist of rival explanations, not a single cause. The job is to work through that shortlist with evidence and stop as soon as one of them is confirmed — not to write a report that mentions all of them.

The rival explanations

Direct answer: A rich-result decision needs to check five separate things — whether the page type is actually eligible for the feature, whether CMS edits are silently breaking JSON-LD, whether a title/snippet fix would beat new markup, whether the feature you remember (like FAQ) still exists on live SERPs, and which of product/review/article/video markup is genuinely available — before any engineering time gets spent.

Treat these as competitors, not a checklist. The point of naming five up front is to stop the first plausible-sounding one from becoming the story before the others have been checked.

• Markup is valid but the page type is ineligible for the feature we want.
• Authors break JSON-LD when they edit the CMS.
• We already rank; a title/snippet change would lift CTR more than new schema.
• FAQ/HowTo markup no longer earns the feature we remember from old SERPs.
• Product / review / article / video is the actually available surface.

What the evidence has to show

Direct answer: A SERP-feature inventory for the money query set, Rich Results Test plus GSC Enhancement reports by template, a crawl-based audit of JSON-LD types against template intent, a review of who in the CMS can publish without breaking markup, and a CTR comparison between URLs that already show rich results and siblings that don't are what confirm eligibility and payoff.

None of the five above survives on a hunch. Here is what actually needs pulling before any of them can be ruled in or out:

• SERP-feature inventory for the money query set (who owns what today).
• Rich Results Test + GSC Enhancement reports by template.
• Crawl extract of JSON-LD types vs template intent.
• Editorial process: who can publish without breaking markup.
• CTR for URLs that already show rich results vs siblings that do not.

The decision rule

Direct answer: Implement schema only where (a) the page genuinely matches the type and (b) the live SERP still grants a feature worth the engineering. Validate in GSC for 28 days before rolling a template globally. Do not chase retired rich results.

What to tell the people around you

Direct answer: Engineering needs a schema matrix by template and CMS guardrails against broken JSON-LD — not a blanket 'add schema everywhere' request with no eligibility check behind it.

The analysis is not finished until it produces something a non-specialist can act on. That means naming the situation, the cost of getting the first move wrong, and a specific ask — not a summary of the investigation.

• Situation — Structured data is eligibility, not a ranking hack. Appearance is earned after eligibility.
• So what — Engineering time on ineligible or retired features is a dead ticket. CTR work on titles may beat new markup.
• The ask — A schema matrix by template. CMS guardrails so authors cannot publish broken JSON-LD.

Technical SEO + CMS owner.

How to act on this

1. Inventory which SERP features are currently live on the money query set and who owns each one today.
2. Run the Rich Results Test and pull GSC Enhancement reports by template to confirm current markup validity.
3. Crawl the site to extract actual JSON-LD types and compare them against each template's real intent — mismatches are common after CMS changes.
4. Check whether URLs that already show a rich result get a meaningfully better CTR than siblings without one, before investing engineering time elsewhere.
5. Build a schema matrix by template, add CMS guardrails so authors can't publish broken JSON-LD, and validate any new rollout in GSC for 28 days before going global.

Frequently asked questions

Does adding schema markup improve rankings directly?

No — structured data affects eligibility for a rich result and how a page appears in search, not the underlying ranking. That's exactly why the decision rule treats it as an appearance investment, not a ranking hack.

Why would valid markup stop showing a rich result?

Google periodically changes which page types and markup earn a given feature — a rich result that worked on old SERPs can be retired or restricted, which is why current live-SERP eligibility is checked, not just markup validity.

How often does CMS-introduced markup breakage happen?

Often enough that it's checked as its own failure mode — author edits, template changes, or plugin updates can silently break JSON-LD without any visible symptom until someone runs the Rich Results Test.

Should every eligible page get schema markup rolled out immediately?

No — validate on a template in GSC for 28 days first. A global rollout that turns out to have a markup error is much more expensive to fix than a scoped validation period.

What if our page type doesn't match any current rich-result category?

Then the answer is genuinely 'we can't win this feature right now' — pursuing markup for an ineligible page type produces a dead ticket, and the decision rule is explicit about not chasing retired or unavailable features.

Can invalid schema on one template affect other templates?

Not directly, but a shared component (like a global header or footer script) with broken JSON-LD can silently affect every template that includes it — which is why the CMS-wide audit checks types against template intent, not just one page.

Do rich results ever appear inconsistently for the same query and page?

Yes — SERP feature eligibility can fluctuate even with valid markup, since Google decides case by case whether to display a feature, which is part of why the decision rule treats appearance as earned, not guaranteed.

Sources

1. See how your structured data looks in Google Search — Search Gallery
2. QAPage structured data — Search Central
3. Structured data — Wikipedia
4. Schema.org — Wikipedia

Where nqzai fits

nqzai runs this same rival-hypothesis framework against your own connected Search Console, Analytics, and audit history, and returns a keep / change / stop decision with the evidence named — including which of the explanations above it could not test, and what to connect to close that gap. No extra cost for the analysis itself; it reads measurements already on file.

Ask nqzai: “Which rich results can we win?”