AveriResources
TemplateSEO & GEO

Schema Markup Templates for Content

Copy-paste schema markup templates for content pages. Includes Article, FAQ, HowTo, Breadcrumb, and Organization schemas with step-by-step implementation guides.

Schema Markup Templates for Content: Article, FAQ, HowTo, and Breadcrumb

Schema markup is structured data that tells search engines — and increasingly, AI search systems — exactly what your content is about. It's the difference between Google guessing what your page contains and Google knowing. And when Google knows, it shows rich results: star ratings, FAQ dropdowns, step-by-step instructions, and breadcrumb trails that increase both click-through rates and search visibility.

Despite being a well-established best practice, the majority of websites don't implement schema correctly — or at all. This guide gives you ready-to-deploy code for the four schema types that matter most for content marketing, plus guidance on implementation and validation.

Why Schema Markup Matters for Content Teams

Schema isn't just technical SEO — it's content discoverability infrastructure. When you publish a well-written FAQ, schema markup transforms it from text in a blog post into an interactive dropdown that can appear directly in search results (an "FAQ rich result"). When you publish a how-to guide, HowTo schema can generate a step-by-step result with estimated time and materials listed in Google.

The business case, in numbers:

  • FAQ rich results have been shown to increase SERP real estate by up to 300%
  • Rich results consistently show higher click-through rates than standard results for comparable positions
  • In 2024, AI Overviews began heavily citing structured data sources, meaning schema is now a factor in AI-assisted search visibility

The four types covered here are the highest-value for B2B content teams:

  1. Article schema — For blog posts, research pieces, and editorial content
  2. FAQ schema — For pages with question-and-answer sections
  3. HowTo schema — For step-by-step instructional content
  4. Breadcrumb schema — For site navigation hierarchy

Implementation Method: JSON-LD

Always use JSON-LD (JavaScript Object Notation for Linked Data) for schema. It's Google's recommended format because it lives in a <script> tag rather than being tangled into your HTML. It's easier to maintain, easier to debug, and doesn't affect page rendering.

Place the JSON-LD block in the <head> or at the end of the <body> of each page.

Averi automates this entire workflow

From strategy to drafting to publishing — stop doing it manually.

Start Free →

Template 1: Article Schema

Use this for any editorial content: blog posts, thought leadership, research pieces, guides.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title Here",
  "description": "A 1–2 sentence summary of the article. This may appear in search results.",
  "image": "https://yourdomain.com/images/article-featured-image.jpg",
  "datePublished": "2025-01-15",
  "dateModified": "2025-03-01",
  "author": {
    "@type": "Person",
    "name": "Author Full Name",
    "url": "https://yourdomain.com/author/author-slug",
    "sameAs": [
      "https://linkedin.com/in/author-profile",
      "https://twitter.com/authorhandle"
    ]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Company Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yourdomain.com/logo.png",
      "width": 200,
      "height": 60
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://yourdomain.com/blog/article-slug"
  },
  "articleSection": "Content Marketing",
  "keywords": "content marketing, B2B SaaS, content strategy",
  "wordCount": 1500,
  "inLanguage": "en-US"
}
</script>

Key Fields Explained

  • headline: Must match the <h1> on the page exactly (or nearly). Max 110 characters.
  • description: Distinct from meta description but can be similar. Aim for 150–200 characters.
  • image: Required for Google Discover eligibility. Must be at least 1200×630px, accessible without login.
  • datePublished / dateModified: ISO 8601 format. Always update dateModified when you refresh content.
  • author: Use Person for individual authors, Organization if content is institutional. sameAs links help Google understand the author's identity.
  • publisher: Required. Logo should be on a white or transparent background.

For Multiple Authors

"author": [
  {
    "@type": "Person",
    "name": "Author One",
    "url": "https://yourdomain.com/author/author-one"
  },
  {
    "@type": "Person",
    "name": "Author Two",
    "url": "https://yourdomain.com/author/author-two"
  }
]

Template 2: FAQ Schema

FAQ schema generates expandable question-and-answer dropdowns directly in Google search results. This is the highest-value schema type for most content teams because it massively increases SERP real estate.

When to use: Any page with a "Frequently Asked Questions" section containing 3+ questions and clear answers.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is [Topic]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Your complete answer here. Write in full sentences. HTML is allowed and will be rendered in the rich result. Keep answers under 300 words for best display. <br><br>You can include formatting like <strong>bold text</strong> or lists: <ul><li>Item 1</li><li>Item 2</li></ul>"
      }
    },
    {
      "@type": "Question",
      "name": "How do you [achieve common goal related to topic]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Answer to the second question. Be specific and actionable. Answers should be self-contained — assume the reader sees only this answer, not the surrounding article."
      }
    },
    {
      "@type": "Question",
      "name": "What is the difference between [X] and [Y]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Clear comparative answer. Use concrete distinctions."
      }
    },
    {
      "@type": "Question",
      "name": "How long does [process] take?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Specific time estimate with context. Avoid vague answers like 'it depends' without qualification."
      }
    },
    {
      "@type": "Question",
      "name": "Is [Your Product/Approach] right for [use case]?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Honest, specific answer. If it's not always the right fit, say so — this increases trust."
      }
    }
  ]
}
</script>

FAQ Schema Rules and Gotchas

Do:

  • Include the same questions in both the schema and the visible page content (they must match)
  • Use full, complete sentences in answers
  • Mark up only genuine FAQ content — not promotional questions

Don't:

  • Use FAQ schema for content that's primarily promotional ("Why should I buy Product X?")
  • Include the same FAQ schema on multiple pages (Google may discount duplicate FAQ markup)
  • Add more than 5–7 questions — rich results typically show 3–4, so front-load your best ones

Template 3: HowTo Schema

HowTo schema is ideal for instructional content: tutorials, setup guides, recipe-style walkthroughs. When triggered in search results, it can display step titles, images, and estimated time directly on the SERP.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to [Do Specific Thing]",
  "description": "A complete guide to [doing the thing], including [key steps or outcomes].",
  "image": {
    "@type": "ImageObject",
    "url": "https://yourdomain.com/images/howto-featured.jpg",
    "height": 630,
    "width": 1200
  },
  "totalTime": "PT30M",
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "0"
  },
  "supply": [
    {
      "@type": "HowToSupply",
      "name": "Tool or resource needed (e.g., Google Analytics account)"
    },
    {
      "@type": "HowToSupply",
      "name": "Second resource"
    }
  ],
  "tool": [
    {
      "@type": "HowToTool",
      "name": "Software or tool name"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "position": 1,
      "name": "Step 1: [Short step name]",
      "text": "Detailed instructions for this step. Be specific and actionable. Explain both what to do and why.",
      "image": {
        "@type": "ImageObject",
        "url": "https://yourdomain.com/images/step-1-screenshot.jpg",
        "height": 630,
        "width": 1200
      },
      "url": "https://yourdomain.com/guide/article-slug#step-1"
    },
    {
      "@type": "HowToStep",
      "position": 2,
      "name": "Step 2: [Short step name]",
      "text": "Instructions for step 2. Each step should be independently understandable.",
      "image": {
        "@type": "ImageObject",
        "url": "https://yourdomain.com/images/step-2-screenshot.jpg",
        "height": 630,
        "width": 1200
      },
      "url": "https://yourdomain.com/guide/article-slug#step-2"
    },
    {
      "@type": "HowToStep",
      "position": 3,
      "name": "Step 3: [Short step name]",
      "text": "Instructions for step 3.",
      "url": "https://yourdomain.com/guide/article-slug#step-3"
    }
  ]
}
</script>

HowTo Schema Notes

  • totalTime: Use ISO 8601 duration format: PT30M = 30 minutes, PT2H = 2 hours, PT1H30M = 1.5 hours
  • estimatedCost: Include if relevant (free tools, paid subscriptions required). Set to "0" for free guides.
  • supply vs. tool: supply is consumed (account credits, materials); tool is used but not consumed (software, equipment)
  • step images: Optional but strongly recommended — significantly increases display real estate in rich results
  • step URLs: Link to specific anchors on the page (#step-1, #step-2) for better user navigation

Build your content engine with Averi

AI-powered strategy, drafting, and publishing in one workflow.

Start Free →

Template 4: Breadcrumb Schema

Breadcrumb schema tells Google the hierarchy of your page within the site structure. This affects how your URL appears in search results (replacing the raw URL path with a readable breadcrumb trail) and reinforces your site architecture for SEO.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://yourdomain.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Resources",
      "item": "https://yourdomain.com/resources"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Templates",
      "item": "https://yourdomain.com/resources/templates"
    },
    {
      "@type": "ListItem",
      "position": 4,
      "name": "Blog Post Template for B2B SaaS",
      "item": "https://yourdomain.com/resources/templates/blog-post-template"
    }
  ]
}
</script>

Breadcrumb Schema Best Practices

  • Always implement on content pages nested more than one level deep
  • Match the breadcrumb names to what appears visually on the page
  • The last item in the list should be the current page
  • The item URL for the last breadcrumb must match the canonical URL of the page

Combining Multiple Schema Types

You can and should combine multiple schema types on the same page. A blog post might have Article + FAQ + Breadcrumb schema. Use separate <script> blocks for each:

<!-- Article Schema -->
<script type="application/ld+json">
{ "@type": "Article", ... }
</script>

<!-- FAQ Schema -->
<script type="application/ld+json">
{ "@type": "FAQPage", ... }
</script>

<!-- Breadcrumb Schema -->
<script type="application/ld+json">
{ "@type": "BreadcrumbList", ... }
</script>

Or use a single @graph structure:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Article",
      "headline": "...",
      ...
    },
    {
      "@type": "FAQPage",
      "mainEntity": [...]
    },
    {
      "@type": "BreadcrumbList",
      "itemListElement": [...]
    }
  ]
}
</script>

Validating Your Schema

Always validate before deploying. Use these tools:

Google Rich Results Test: search.google.com/test/rich-results Tells you exactly which rich result types your schema qualifies for and flags any errors.

Schema.org Validator: validator.schema.org Validates technical correctness against the schema.org specification.

Google Search Console > Enhancements: After deployment, monitor this section for structured data errors and impressions from rich results.

Ready to put this into practice?

Averi turns these strategies into an automated content workflow.

Start Free →

Further Reading

Frequently Asked Questions

Does schema markup directly improve rankings? Schema markup doesn't directly boost rankings as a ranking factor, but it improves how your content appears in search results (rich results), which increases click-through rates. Higher CTR sends positive engagement signals to Google and can indirectly improve ranking performance. For AI-assisted search (Perplexity, Bing AI, Google AI Overviews), structured data is increasingly used to identify and cite authoritative sources.

What happens if my schema has errors? Minor errors (like a missing optional field) typically result in the rich result not being displayed — Google falls back to the standard result. Critical errors (malformed JSON, required fields missing) may be flagged in Google Search Console. The page continues to rank normally regardless; schema errors only affect rich result eligibility.

Should every page have schema? Prioritize pages that would benefit most from rich results: FAQ-heavy resource pages (FAQ schema), step-by-step guides (HowTo), and all blog posts (Article + Breadcrumb). Product pages warrant additional types like Product and Offer. Don't add schema just to add it — every schema block should serve a specific display or discoverability purpose.

How do I implement schema on WordPress? Plugins like Yoast SEO, RankMath, and Schema Pro can generate Article, FAQ, and Breadcrumb schema automatically from page content. For FAQ schema, you'll need to use Yoast's structured data blocks or RankMath's FAQ block. For fully custom schema, use a custom plugin or the "Additional Schema Markup" field in advanced SEO plugins.

How often should I update my schema? Always update dateModified when you refresh a piece of content — this is one signal Google uses to determine content freshness. For evergreen content that you republish with updates, keeping this field current can maintain search ranking. Review your schema whenever you significantly change page structure or add new FAQ sections.

Averi helps content teams build well-structured, SEO-ready content — including the metadata and structured data infrastructure that AI and search engines need. Try Averi free.

Start Your AI Content Engine

Ready to put this into practice? Averi automates the hard parts of content marketing — so you can focus on strategy.

Get Started FreeGenerate FAQ Schema

Related Resources

GEO Optimization Checklist for AI Search
SEO & GEOTemplate

GEO Optimization Checklist for AI Search

Optimize your content for Generative Engine Optimization. This checklist covers entity definitions, structured data, FAQ markup, citation-worthy formatting, and llms.txt.

On-Page SEO Checklist
SEO & GEOTemplate

On-Page SEO Checklist

Hit every on-page SEO element with this checklist. Covers title tags, meta descriptions, headings, internal links, schema markup, image optimization, and Core Web Vitals.

llms.txt File Template & Generator
SEO & GEOTemplate

llms.txt File Template & Generator

Create an llms.txt file that helps AI search engines like ChatGPT, Perplexity, and Claude understand and cite your content. Includes format spec and examples.