CSS Gradient Generator
Build linear, radial and conic gradients and copy the CSS.
Design & SEO
Build valid JSON-LD for FAQ, HowTo, Article, Product, Local Business and more.
Google has narrowed this considerably since 2023, and a lot of advice online is now out of date.
| Type | Rich result | Status in 2026 |
|---|---|---|
| FAQPage | Expandable Q&A | Restricted to government and health sites since Aug 2023 |
| HowTo | Step-by-step panel | Retired from desktop and mobile results |
| Product | Price, availability, rating | Active and valuable |
| Review / AggregateRating | Star rating | Active — must reflect real ratings |
| LocalBusiness | Map pack, hours, contact | Active and high value |
| Event | Date, venue, tickets | Active |
| Recipe | Image, time, rating | Active |
| BreadcrumbList | Path instead of URL | Active, near-universal |
| Article / NewsArticle | Top stories, headline | Active |
| VideoObject | Video thumbnail, key moments | Active |
| Organization | Knowledge panel signals | Indirect but worth having |
FAQ and HowTo losing their rich results does not make them pointless. They still describe the page to AI answer engines, which is where an increasing share of discovery happens, and Google still parses them. But do not build a content strategy around a SERP feature that no longer appears.
This is the rule that causes manual actions, and it is absolute.
Structured data must describe content visible on the page. FAQ schema for questions that are not on the page, a review rating with no reviews, a price different from the displayed price, an event that is not listed — each is a spam policy violation, and the penalty is loss of all rich results across the site, not just that page.
Invented aggregate ratings are the most common version. A star rating with no genuine review mechanism behind it is fabricated data, and it is trivially detectable because there is nothing on the page to support it. Either collect real ratings or omit the field.
The safe construction: generate the schema from the same source that renders the visible content, so the two cannot drift apart. That is exactly how the pages on this site are built.
JSON-LD. Google has recommended it explicitly for years and it is what every current guide assumes.
The reason is separation. JSON-LD sits in a single script block in the head, independent of the markup. Microdata and RDFa interleave attributes into the HTML, which means a template change can silently break the structured data, and a designer has to understand schema to edit a page safely.
JSON-LD is also far easier to generate programmatically and to validate, because it is just an object. If you are working with existing microdata there is no urgency to migrate — Google reads all three — but write anything new in JSON-LD.
Two tools, and they answer different questions.
Google’s Rich Results Test tells you whether the page is eligible for a specific rich result. This is the one that matters for search.
The Schema.org validator tells you whether the markup is technically valid against the vocabulary. It will pass things Google does not support, and flag things Google tolerates.
After shipping, the Enhancements section of Search Console reports errors across the whole site as Google recrawls, which catches the case where a template change broke the markup on a thousand pages at once. Check it after any template change — that is the failure mode that actually happens.
Only for well-known government and health sites since August 2023. It is still worth including for AI answer engines and general page understanding, but it will not produce the expandable Q&A for most sites.
In a script tag with type="application/ld+json", normally in the head. Body placement also works — Google parses both.
Yes, and it is normal. A tool page might carry SoftwareApplication, HowTo, FAQPage and BreadcrumbList together.
Not directly. It affects how your result is displayed, which affects click-through rate, which affects performance. Google has been consistent that it is not a ranking factor in itself.
It violates the structured data spam policies and risks a manual action that removes rich results across the whole site. Fabricated ratings are the most common and most detectable version.
No. Once, on the homepage or an about page, is enough. Repeating it everywhere adds nothing.
No. The JSON is assembled in this page.