How to mark up breadcrumbs and articles on a SaaS content site
Written by Olayinka Olayokun·Published ·Updated ·Verified
BreadcrumbList schema declares a page's position in the site hierarchy; Article schema declares the page is a piece of editorial content with author, dates, and publisher. Together they form the standard structured-data kit for SaaS blog posts and playbook chapters.
Summary and key takeaways
Two schemas every blog post and playbook chapter should have: BreadcrumbList (so SERP shows the URL path, not just the domain — boosts CTR ~5%) and Article (so Google and AI engines know it's editorial content with an author, dates, and a publisher). Both validate cleanly in 5 minutes and pay back for the life of the page.
- •BreadcrumbList increases SERP CTR by ~3–7% by replacing raw URLs with clickable paths.
- •Article schema with author and dateModified is the single biggest factor in AI Overview citation eligibility.
- •Use Article, not BlogPosting or NewsArticle, unless the content is genuinely a news or blog post format.
- •Author should be a Person schema with sameAs links to verifiable profiles (LinkedIn, GitHub, X).
- •Both schemas are template-level changes that propagate across the whole content site in one edit.
In plain English ·BreadcrumbList schema replaces the raw URL with a clickable path in SERPs, boosting CTR. Article schema declares editorial provenance (author, dates, publisher) that AI engines use for citation. Together they're the minimum schema kit for SaaS blog posts and playbook chapters.
- Author + dateModified
- Two Article fields most correlated with AI Overview citation eligibility SERPNAUT playbook
How this compares
| Schema | Field | Required | Purpose |
|---|---|---|---|
| BreadcrumbList | itemListElement | Yes | Define each step in the hierarchy |
| Article | headline | Yes | The article title (max 110 chars) |
| Article | author | Recommended | E-E-A-T signal + AIO citation |
| Article | datePublished | Yes | Original publish date |
| Article | dateModified | Recommended | Last meaningful update |
| Article | publisher | Recommended | Organization that publishes the content |
Part of the Schema Markup for SaaS: JSON-LD That Actually Validates guide
BreadcrumbList schema declares a page's position in the site hierarchy; Article schema declares the page is a piece of editorial content with author, dates, and publisher. Together they form the standard structured-data kit for SaaS blog posts and playbook chapters.
Most SaaS blogs ship without breadcrumbs or article schema, leaving CTR on the table and missing AI Overview citation eligibility on every published article. Both are template-level fixes — one engineer hour adds them across the whole content site and the benefit compounds with every new URL published. The ROI is the highest of any single schema move.
What this chapter covers: template-applied, verified-author, honest-dates, validation-clean.
Article: the AI Overview citation enabler
Article schema declares the page is editorial content authored by a person, published on a date, by an organisation. AI engines use these signals to decide who to cite when answering related queries.
Article schema declares the page is editorial content authored by a person, published on a date, by an organisation. AI engines use these signals to decide who to cite when answering related queries.
Author is the most important Article field for AI citation. Use a Person schema with name, url (to author bio), and sameAs (array of links to LinkedIn, GitHub, X, conference profiles). Anonymous or generic 'Editorial Team' authors get cited less.
datePublished is required. dateModified is optional but strongly recommended — AI engines prefer recently-modified content for time-sensitive queries.
Picking the right Article subtype
Article (the generic type) is the right default for playbook chapters, in-depth guides, and most editorial SaaS content.
Article (the generic type) is the right default for playbook chapters, in-depth guides, and most editorial SaaS content.
BlogPosting suits casual, time-stamped blog content. Use only if the content is genuinely a blog post — quick takes, opinion pieces, news commentary.
NewsArticle is reserved for news publications. Don't use on a SaaS marketing site; misuse can trigger manual action.
TechArticle is fine for technical documentation but rarely earns more visibility than generic Article in Google's parsing.
Implementation: one template edit, sitewide impact
In the blog/playbook template (e. g. src/routes/playbook_. $slug. tsx), render both schemas in a single <script type='application/ld+json'> block in the head.
In the blog/playbook template (e.g. src/routes/playbook_.$slug.tsx), render both schemas in a single <script type='application/ld+json'> block in the head.
BreadcrumbList: build the array from the current route's hierarchy. Each item is a ListItem with position, name, and item (full URL).
Article: pull from the page's frontmatter or content metadata — headline, author Person object, datePublished, dateModified, publisher Organization, image (the og:image).
Validate one URL from each template type with Rich Results Test. Fix any errors. Ship template-level and propagate to every page on next deploy.
The checklist for this chapter
- ✓Add BreadcrumbList schema to every content template
- ✓Add Article schema to every blog post and playbook chapter template
- ✓Include author as Person with sameAs links
- ✓Include datePublished (required) and dateModified (recommended)
- ✓Include publisher as Organization linking to the brand
- ✓Validate one representative URL from each template with Rich Results Test
Where this chapter sits in the guide
AI Overview citation eligibility — Article schema with author and date signals is what AI engines parse to decide who to cite.
a consistent URL hierarchy — BreadcrumbList only adds value when the hierarchy itself is meaningful.
SoftwareApplication schema (which applies to product pages) — Article and BreadcrumbList apply to content pages. Read the softwareapplication schema for saas chapter →
Google's Rich Results Test against a representative URL from each template type (blog post, playbook chapter, guide).
Quick answers about breadcrumb and article schema for the saas blog and playbook
- What's the right Article subtype for a SaaS playbook chapter?
- Article. Don't use NewsArticle (reserved for news), don't use BlogPosting unless the content is genuinely a casual blog post. Article is the safe, broad default that works for playbook chapters, guides, and tutorials.#
- Should I include dateModified even if I haven't updated the page?
- datePublished is required; dateModified is optional but strongly recommended. Set dateModified to a real edit date when the content was meaningfully updated. Don't fake modification dates to chase 'freshness' — Google detects unchanged content with modified dates and discounts the signal.#
Questions about breadcrumb and article schema for the saas blog and playbook
- No — landing pages are not articles. Use SoftwareApplication for product/landing pages. Reserve Article for genuinely editorial content.
- BreadcrumbList schema enables breadcrumb display in Google SERPs. Google Search Central — breadcrumbs
- Article schema declares editorial provenance for content pages. Google Search Central — Article
This chapter is one node in the founder-led playbook. To see which nodes your specific URLs are bleeding traffic from, get a founder-grade SEO audit of your URLs. Same six disciplines, applied to the pages you actually own.
Olayinka Olayokun
Founder, SERPNAUT and Invoicemonk
Written by Olayinka Olayokun. I run SERPNAUT, a founder-led SEO service for B2B SaaS, and Invoicemonk, the SaaS I grew from zero to 300+ organic visits and a paying customer in 28 days using the same playbook. Everything below is what worked on my own URLs and on the audits I've shipped since.
More chapters in this guide
Breadcrumb and Article schema are the schema work that pays back across the entire content site at template-level cost. Combined with SoftwareApplication on product pages and Organization on the brand, they form a minimum-viable schema kit that covers every page type a SaaS site publishes — and earns visibility in both classical SERP and emerging AI Overview surfaces.
See the full guide at schema markup for saas: json-ld that actually validates. The commercial bridge above is the canonical path from this chapter to your URLs.