Turn on the schema blocks your page needs, fill in short forms, and copy one linked JSON-LD script for your SaaS site. You can also paste existing JSON-LD and check it for errors and missing properties.
One script tag. Paste it in the head or the body of the page it describes.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://northwind.example/#organization",
"name": "Northwind Reports",
"url": "https://northwind.example/",
"logo": "https://northwind.example/logo.png",
"sameAs": [
"https://www.linkedin.com/company/northwind-reports",
"https://x.com/northwindreports"
],
"contactPoint": {
"@type": "ContactPoint",
"contactType": "customer support",
"email": "[email protected]"
}
},
{
"@type": "WebSite",
"@id": "https://northwind.example/#website",
"name": "Northwind Reports",
"url": "https://northwind.example/",
"publisher": {
"@id": "https://northwind.example/#organization"
}
},
{
"@type": "SoftwareApplication",
"@id": "https://northwind.example/#software",
"name": "Northwind Reports",
"applicationCategory": "BusinessApplication",
"operatingSystem": "Web",
"url": "https://northwind.example/",
"publisher": {
"@id": "https://northwind.example/#organization"
},
"offers": [
{
"@type": "Offer",
"@id": "https://northwind.example/#offer-free",
"name": "Free",
"price": "0",
"priceCurrency": "USD",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "0",
"priceCurrency": "USD",
"billingDuration": "P1M",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": 1,
"unitCode": "MON"
}
},
"url": "https://northwind.example/pricing"
},
{
"@type": "Offer",
"@id": "https://northwind.example/#offer-team",
"name": "Team",
"price": "29",
"priceCurrency": "USD",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "29",
"priceCurrency": "USD",
"billingDuration": "P1M",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": 1,
"unitCode": "MON"
}
},
"url": "https://northwind.example/pricing"
},
{
"@type": "Offer",
"@id": "https://northwind.example/#offer-business",
"name": "Business",
"price": "290",
"priceCurrency": "USD",
"priceSpecification": {
"@type": "UnitPriceSpecification",
"price": "290",
"priceCurrency": "USD",
"billingDuration": "P1Y",
"referenceQuantity": {
"@type": "QuantitativeValue",
"value": 1,
"unitCode": "ANN"
}
},
"url": "https://northwind.example/pricing"
}
]
}
]
}
</script>SoftwareApplication: Northwind Reports: Warning.
Google requires aggregateRating or review for a software app rich result. Add one only if real reviews show on the page.
Organization: Northwind Reports: Pass.
Required and recommended properties found.
WebSite: Northwind Reports: Pass.
Required and recommended properties found.
Offer: Free: Pass.
Required and recommended properties found.
Offer: Team: Pass.
Required and recommended properties found.
Offer: Business: Pass.
Required and recommended properties found.
Schema markup is structured data, usually written in JSON-LD, that tells search engines and AI assistants what a page is about. It names the things on the page, such as a company, a software product, a price or a question, with types from the shared vocabulary at schema.org.
The markup sits in a script tag that visitors do not see. It must describe what the page shows: the same prices, the same questions, the same company name.
69.4% of the 186 SaaS homepages we scanned have JSON-LD. Organization is the most common type, on 57% of homepages, and WebSite follows on 40.3%.
Only 14% of SaaS homepages use SoftwareApplication, so only 1 in 7 marks itself up as software. FAQPage is on 3.8%, about 1 in 26. Most sites describe the company but not the product it sells.
We read the JSON-LD in each homepage's HTML before JavaScript runs, which is what most crawlers see first. A site counts once per type, however many nodes of that type it has.
| Type | Sites | Share |
|---|---|---|
| Organization | 106 | 57% |
| WebSite | 75 | 40.3% |
| ImageObject | 64 | 34.4% |
| PostalAddress | 54 | 29% |
| ContactPoint | 50 | 26.9% |
| WebPage | 49 | 26.3% |
| SearchAction | 33 | 17.7% |
| Person | 30 | 16.1% |
| ListItem | 26 | 14% |
| SoftwareApplication | 26 | 14% |
As of October 2026 · Source: BlockSnap scan of SaaS homepages (JSON-LD in the homepage HTML, before JavaScript runs), 186 sites
Homepage: Organization, WebSite and SoftwareApplication. Organization names the company and links its logo and social profiles. WebSite gives the site name. SoftwareApplication describes the product, its category and its price.
Pricing page: Product with one Offer per pricing tier, each with a price, a currency and a billing period. Blog posts and guides: Article, with the headline, the author, the date and an image.
Every page below the homepage: BreadcrumbList, so search engines see where the page sits in the site. Link the nodes with @id, so the Organization is the publisher of the app, the site and the articles.
Yes, but for different reasons than before. Rich results changed: since 2023 Google shows FAQ rich results only for some well-known health and government sites, and it removed HowTo rich results. In 2024 it also retired the sitelinks search box.
Structured data still helps search engines and AI assistants understand a page, connect it to the right company and quote its facts, such as a price or an answer. Product, software app, breadcrumb and article markup can still change how a result looks. Treat schema as a clear label for machines, not as a ranking trick.
BlockSnap builds your SaaS landing page from proven sections, with Organization, SoftwareApplication, pricing and FAQ markup ready to publish.
Get early access