Official site — always check you are on kripicard.comVerify
SEO tools
Schema Generator
Build JSON-LD structured data for the types that matter, with the required properties filled in and warnings when a combination is invalid or no longer earns a rich result.
Rich result: Article rich result, Top stories
JSON-LD
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How card BINs actually work",
"image": [
"https://example.com/cover.png"
],
"datePublished": "2026-01-15",
"dateModified": "2026-01-15",
"author": {
"@type": "Person",
"name": "Jane Doe"
},
"publisher": {
"@type": "Organization",
"name": "Kripicard"
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/how-bins-work"
}
}
</script>Paste this anywhere in the page — JSON-LD does not have to sit in the head, and Google reads it either way. Validate the result with Google's Rich Results Test before relying on it.
Which types still earn a rich result
Schema.org defines hundreds of types. Google renders a rich result for a small fraction of them, and the list shrinks as often as it grows — How-to and FAQ were both cut back in 2023. Markup outside this list is not wrong, it just will not change anything a searcher sees.
| Type | What it shows | Status |
|---|---|---|
| Product | Price, stock, review stars | Active |
| BreadcrumbList | Breadcrumb trail replacing the URL | Active |
| Article | Headline, image, date in Top stories | Active |
| LocalBusiness | Hours, phone, address in local results | Active |
| Organization | Logo and knowledge panel details | Active |
| FAQPage | Expandable Q&A | Health & gov only |
| HowTo | Step-by-step panel | Retired 2023 |
One trap worth knowing: aggregateRating needs both ratingValue and reviewCount. Supplying one without the other is invalid, and Google drops the entire Product rich result rather than just the stars — so a half-filled rating costs you the price display too.
Related tools
- Meta Tag Generator — the tags that go alongside your structured data.
- Canonical Checker — it also reports which schema types a live page emits.
- Sitemap Generator — help Google find the pages you just marked up.
Frequently asked questions
JSON-LD, Microdata or RDFa — which should I use?
JSON-LD. Google recommends it explicitly, and it is the only one of the three that lives in a single self-contained block instead of being woven through your HTML. That means you can change your markup without breaking your structured data, and vice versa.
Does structured data improve my rankings?
Not directly. Google has been consistent that structured data is not a ranking factor. What it does is make you eligible for rich results — star ratings, prices, breadcrumbs — which change how your listing looks and can lift click-through substantially. The benefit is real, but it comes through presentation, not position.
Why does my FAQ markup no longer show an accordion?
Google restricted FAQ rich results in August 2023 to well-known health and government sites. The markup is still valid and still parsed, but for almost every site the accordion is gone. Nothing is broken — the policy changed.
Can I add schema for content that is not on the page?
No. Structured data must describe content visible to the user. Marking up reviews, prices or FAQs that do not appear on the page is a spam violation and can trigger a manual action that removes all your rich results.
Where should the JSON-LD script go?
Anywhere in the document. Head or body both work, and Google reads dynamically injected JSON-LD too, provided it exists once rendering finishes. Putting it in the head is convention, not a requirement.
Do I need to validate it?
Yes. Use Google's Rich Results Test for eligibility and the Schema.org validator for correctness — they answer different questions. This tool produces syntactically valid JSON-LD with the required properties, but only Google can tell you whether a specific page qualifies for a specific rich result.