Core principle
Schema markup is machine-readable metadata. It does not change how a page looks to human visitors, but it changes what search engines and AI systems can extract from it reliably. For SaaS websites, a small number of schema types produce most of the visibility benefit.
Why structured data matters more in 2026
Two developments have increased the importance of structured data over the past two years:
AI answer engines extract structured content preferentially. Systems like Perplexity, ChatGPT search, and Gemini retrieve candidate pages and extract specific information to construct answers. Pages with schema markup make extraction reliable — the AI system does not have to infer what the page is about or where the relevant information sits. See How AI Search Engines Choose Sources for the broader context.
Google's rich results continue to reward structured pages. The set of rich result types has evolved, but the principle has not: pages with accurate, complete schema markup receive enhanced presentation in search results, which improves click-through rate for qualifying queries.
The schema types that matter for SaaS
SoftwareApplication
The primary schema type for a SaaS product page. It signals that the page describes a software product and enables rich results showing the application name, category, price, and rating.
Minimum viable implementation:
{
"@context": "https://schema.org",
"@type": "SoftwareApplication",
"name": "Dentalytic",
"applicationCategory": "HealthApplication",
"operatingSystem": "Web",
"offers": {
"@type": "Offer",
"price": "0",
"priceCurrency": "EUR",
"description": "Free trial available"
},
"description": "AI-powered dental clinic assistant with WhatsApp integration, appointment management, and 3D treatment planning.",
"url": "https://dental.akor.net",
"publisher": {
"@type": "Organization",
"name": "AKORNET OÜ",
"url": "https://akor.net"
}
}
applicationCategory should use a recognised value from the schema.org vocabulary — HealthApplication, BusinessApplication, UtilitiesApplication, and similar. Use the most specific applicable category.
FAQPage
Add to any page that answers specific questions — product feature pages, pricing pages, support documentation, and blog posts with FAQ sections.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How does WhatsApp appointment automation work for dental clinics?",
"acceptedAnswer": {
"@type": "Answer",
"text": "The system sends automated appointment reminders via WhatsApp 48 hours and 2 hours before each appointment. Patients confirm or cancel with a single tap. Cancellations trigger an automated rebooking flow offering alternative slots."
}
}
]
}
The value is in AI extraction, not Google rich results. AI answer engines retrieve FAQPage content as discrete question-answer pairs — the format they use for direct answers. Questions should match the actual queries your target audience uses, and answers should be complete and specific rather than directing the reader to another page.
HowTo
Use on pages that describe a process — setup guides, onboarding documentation, configuration walkthroughs. HowTo schema marks up the individual steps of a process in machine-readable form.
{
"@context": "https://schema.org",
"@type": "HowTo",
"name": "How to set up a multilingual QR menu for a restaurant",
"step": [
{
"@type": "HowToStep",
"position": 1,
"name": "Build the base menu",
"text": "Create the complete menu in your primary language — all categories, items, descriptions, prices, and allergen flags — before adding any language variants."
},
{
"@type": "HowToStep",
"position": 2,
"name": "Add language variants",
"text": "From the QR Menu dashboard, add each language as a variant. Each version carries independent item names, descriptions, and currency display settings."
}
]
}
Organisation
Add Organisation schema to the homepage and any page that establishes company identity. This is the foundation for entity recognition — search engines and AI systems use it to associate content with a known, verifiable organisation.
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "AKORNET OÜ",
"url": "https://akor.net",
"logo": "https://akor.net/images/logo.png",
"contactPoint": {
"@type": "ContactPoint",
"telephone": "+90-541-865-6060",
"contactType": "customer service",
"email": "info@akor.net"
},
"address": {
"@type": "PostalAddress",
"addressLocality": "Tallinn",
"addressCountry": "EE"
},
"sameAs": [
"https://www.linkedin.com/company/akornet"
]
}
sameAs links to official profiles on other platforms — LinkedIn, Crunchbase, industry directories. These help search engines consolidate the entity across multiple sources, which strengthens authority signals.
Article
Add to all blog posts. Signals authorship, publication date, and publisher — provenance signals that both Google and AI systems use when evaluating content recency and credibility.
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Structured Data for SaaS — Which Schema Types Actually Move the Needle in 2026",
"datePublished": "2026-08-26",
"dateModified": "2026-08-26",
"author": {
"@type": "Organization",
"name": "AKORNET Growth Team"
},
"publisher": {
"@type": "Organization",
"name": "AKORNET OÜ",
"logo": {
"@type": "ImageObject",
"url": "https://akor.net/images/logo.png"
}
}
}
Implementing in Next.js 15 App Router
In Next.js 15 App Router, JSON-LD is injected as a script tag inside the page component:
export default function ProductPage() {
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'SoftwareApplication',
name: 'Dentalytic',
// ... rest of schema
}
return (
<>
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
{/* page content */}
</>
)
}
For pages with multiple schema types — a blog post that has both Article and FAQPage schema — pass an array:
const jsonLd = [
{ '@context': 'https://schema.org', '@type': 'Article', ... },
{ '@context': 'https://schema.org', '@type': 'FAQPage', ... }
]
Validate all implementations using Google's Rich Results Test before publishing.
Common implementation errors
Inaccurate data. Schema markup that contradicts the visible page content — a price in schema that differs from the displayed price, an address that no longer matches — triggers Google quality penalties. Keep schema and content in sync.
Incomplete required fields. Each schema type has required and recommended properties. Missing required properties prevent the schema from qualifying for rich results. Check the schema.org documentation for each type used.
Schema on pages where it does not apply. FAQPage schema on a page with no FAQ content, or SoftwareApplication schema on a blog post, creates quality signals that work against the site. Apply schema types accurately.
Summary
For SaaS websites in 2026, the schema types that produce measurable visibility benefit are SoftwareApplication on product pages, FAQPage on question-answering content, HowTo on process documentation, Organisation on the homepage, and Article on blog posts.
The implementation work is straightforward — JSON-LD injected as a script tag, validated before publishing. The ongoing requirement is accuracy: schema that reflects current, correct information about the product and organisation.
AKORNET implements structured data across all four of its SaaS products. See our products at akor.net →