Rich Results

What are rich results?

Google's structured-data introduction describes rich results as enhanced Search displays that structured data can enable. The markup provides explicit clues about page meaning. It is useful to distinguish that implementation from the actual display a searcher sees.

Before commissioning a fix, name the feature you expect and the page that should qualify. “Add schema for more visibility” is too vague to verify. A developer needs the applicable feature requirements, while a business owner needs a record of what changed and what was observed afterward.

Eligibility is not a display guarantee

Google's general structured-data guidelines explicitly say that correct markup, even according to the Rich Results Test, does not guarantee a Search display. Google lists factors including search history, location and device type, and says a text result may be more appropriate.

The same guidelines require relevant, visible, up-to-date content, compliance with general and feature-specific policies, and all required properties. They warn that quality guidelines are not easily checked by an automated tool. A syntax pass therefore cannot certify that a review is genuine or that the markup represents the page accurately.

Some familiar examples are retired

A copied template may describe a feature Google no longer displays. The entries below document specific retirements, not a complete list of currently supported types. Retiring a Search display does not by itself mean the vocabulary type has disappeared or that every block using it should be deleted.

The old government-and-health restriction for FAQ results is historical guidance, not the current status described by the later removal notice. Check the destination of an old documentation link rather than assuming its title still describes a supported feature.

Diagnose the missing display in order

The following is a recommended investigation workflow. It is not a claim that any particular website has passed Google's checks.

1. Confirm that the intended feature is still supported and that its requirements apply to the page.
2. Inspect the rendered markup and compare its facts with visible page content.
3. Run the relevant technical checks and resolve detected errors without inventing missing facts.
4. Review content quality and feature-specific policies, including any applicable review requirements.
5. Record Search observations separately from implementation results. A missing display alone does not establish its cause.

Google's guidelines recommend the Rich Results Test and URL Inspection for technical checks. They say a structured-data issue can result in a manual action that removes rich-result eligibility, but that such a structured-data manual action does not affect how the page ranks in Google web search. Check the actual Manual Actions report before asserting that an action exists.

Review requirements differ by feature and page context. Use the relevant policy instead of a blanket instruction that all ratings must come from third-party platforms. Never invent reviews or imply that a validator verified who wrote them.

Illustrative diagnosis

Hypothetical example, not a customer result: an agency promises FAQ dropdowns for a client's service page because an old tutorial recommends FAQPage. The editor checks Google's current notice and finds the display has retired. The useful correction is to revise the promise and keep the on-page answers useful, not add more markup to chase that display.

If a different supported feature is appropriate, evaluate it on its own requirements. This example reports no validation run, Search appearance, click increase or recovered ranking.

Measure outcomes without a fixed CTR promise

Google's structured-data introduction recommends performance comparisons when evaluating changes and notes that page views vary for multiple reasons. Its suggested approach considers seasonal and topical changes. A before-and-after increase is therefore something to investigate, not proof that markup alone caused it.

Keep implementation dates, observed Search appearances and business metrics in separate fields. Compare similar conditions and note other site changes. The sources used here do not establish a universal click-through lift, a best-performing type for every business or a guaranteed CTR-to-ranking effect.

Where theStacc fits

theStacc's first-party feature catalogue describes research, article drafting and CMS publishing with manual, approval-first and automatic modes. Those are content-workflow capabilities, not a certification of rich-result eligibility or a promised Search display.

Explore the AI Blog Writer and publishing controls, or book a demo to inspect the workflow. Assign an editor or developer to verify the rendered content and markup for your setup.

Frequently asked questions

Does correct structured data guarantee rich results?

No. Google says a page may not receive a rich-result display even when the Rich Results Test finds correct markup. Review feature requirements, content quality and actual Search observations separately. Eligibility and display are different questions.

Can FAQPage markup still produce Google FAQ dropdowns?

Google's June 2026 documentation update says FAQ rich results are no longer shown in Search. Do not use older eligibility guidance to promise that display. Useful questions and answers on the page can remain useful without it.

Does a structured-data manual action reduce web rankings?

Google's general guidelines say a structured-data manual action removes eligibility for rich-result appearance but does not affect how the page ranks in Google web search. This statement concerns that specific action, not every possible Search policy issue. Check the actual report rather than assuming an action.

Which rich result guarantees the highest click-through rate?

The inspected sources do not establish a universal winner or guaranteed lift. Choose a supported feature that accurately fits the page, then measure the observed display and performance under comparable conditions. Do not replace missing evidence with a generic percentage.

Related terms

Read Structured Data for markup checks, JSON-LD for the format, Knowledge Graph for the entity system and AI citation for attribution and measurement.

Sources and scope

The linked Google introduction, general guidelines and retirement notices were reviewed September 14, 2026. Product statements use theStacc's first-party catalogue. The workflow and example are editorial guidance, not original testing. No live Rich Results Test, Search Console inspection, product test or business-outcome experiment was performed for this guide.