Skip to content
AskVault Docs
Try Free →

Schema.org for SaaS docs

Written by Joseph Russo, Principal Architect, Networks and Tech, AskVault · Reviewed by Allison Chan
Last updated: · 4 min read

Why schema.org matters

Without schema.org, search engines guess what your page is about. With:

  • Google rich snippets in search results.
  • AI Overview citations more accurate.
  • Voice assistants can read structured answers.

Structured data helps engines understand a page; no public study we trust puts a reliable number on the citation lift.

Common types for SaaS docs

Six types cover most pages:

  • Article. Concept and overview pages.
  • HowTo. Step-by-step guides.
  • FAQPage. FAQ pages with Q&A.
  • Product. Product pages with pricing.
  • SoftwareApplication. App-specific.
  • TechArticle. Technical reference.

Sample Article schema

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Migrate from Chatbase to AskVault",
  "author": {
    "@type": "Person",
    "name": "Hajera Affrin",
    "jobTitle": "Founder, AskVault"
  },
  "datePublished": "2026-05-15",
  "dateModified": "2026-06-18"
}

Place inside <script type="application/ld+json"> in <head>.

Sample HowTo schema

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "Embed AskVault widget on WordPress",
  "totalTime": "PT5M",
  "step": [
    {"@type": "HowToStep", "text": "Install AskVault plugin"},
    {"@type": "HowToStep", "text": "Paste workspace token"},
    {"@type": "HowToStep", "text": "Save and reload"}
  ]
}

Google stopped showing HowTo rich results in 2023, so the markup no longer earns a rich card there. It still describes your steps clearly to other parsers and AI engines.

Sample FAQPage schema

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your refund policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "14-day refund window..."
      }
    }
  ]
}

AI engines often quote acceptedAnswer verbatim.

Sample Product schema

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "AskVault Growth",
  "offers": {
    "@type": "Offer",
    "price": "99",
    "priceCurrency": "USD"
  }
}

Implementation in Astro / Next.js

Place schema in frontmatter or page head:

---
head:
  - tag: script
    attrs: { type: application/ld+json }
    content: |
      {"@context":"https://schema.org","@type":"Article","headline":"..."}
---

Static-rendered into final HTML. No JS required.

Validation

Three tools:

  • Schema Markup Validator. validator.schema.org checks that your JSON-LD is valid schema.org.
  • Google Rich Results Test. A separate Google tool that shows which Google rich results your page can qualify for.
  • Manual in browser DevTools.

All errors must clear before submitting sitemap.

Best practices

  • One primary type per page. Don't double-up.
  • Required fields populated. Missing required fields rejects.
  • Match content. Schema must reflect actual page content; mismatch penalized.
  • Update dateModified on edits.

Limits

  • Common schema types. 6 fit most SaaS docs.
  • AI citation lift. Plausible but unmeasured; treat any precise figure with suspicion.
  • Implementation time. 5 to 10 minutes per page.

Common pitfalls

Invalid JSON. Trailing commas, unescaped quotes. Validate.

Mismatched type. A how-to page with Article schema is suboptimal.

Outdated dates. dateModified stale signals stale content; AI engines downweight.

Spammy schema. Adding schema unrelated to content can trigger penalty.

FAQ

Does AI engines cite based on schema?

Some. Perplexity and Bing's index heavily use it.

Will Google penalize wrong schema?

Yes for clearly-spammy. Honest mistakes are OK.

Can I have multiple schemas on one page?

Yes if they're complementary (Article plus Author).

Was this page helpful?