Skip to content
AskVault Docs
Try Free →

Schema.org for SaaS docs

Written by , Founder, AskVault · Reviewed by Aashiq
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.
  • Sitelinks search box populates correctly.

About 30 to 50% lift in AI Overview citation rate for properly-tagged pages.

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": "Aashiq",
    "jobTitle": "Founder, AskVault"
  },
  "datePublished": "2026-05-15",
  "dateModified": "2026-05-15"
}

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 shows HowTo as rich card in search.

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": "4999",
    "priceCurrency": "INR"
  }
}

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:

  • Google Rich Results Test. validator.schema.org.
  • Schema Markup Validator. schema.org/docs/validator.html.
  • 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

  • Schema size. Practical cap around 50 KB per page.
  • Nesting depth. Up to 5 levels.
  • Validation time. Under 30 seconds in Google's Rich Results Test.
  • Common schema types. 6 fit most SaaS docs.
  • AI citation lift. About 30 to 50% for tagged pages.
  • 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?