Agent skill

FAQPage Schema Markup

by thedaviddias in thedaviddias/Front-End-Checklist

Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

MITAuto-check passedMarketing & SEO

Install FAQPage Schema Markup

skills CLI
$ npx skills add thedaviddias/Front-End-Checklist --skill faq -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install thedaviddias/Front-End-Checklist faq --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/faq .claude/skills/faq && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
faq
GitHub stars
74k
Token cost
~774 tokens
SKILL.md length
319 words
Files
2 (incl. references)
Skills in repo
390
Repo updated
First seen
Licence
MIT

At a glance

Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.

  • Works in 4 steps: Identify pages with FAQ-style content (a… → Add a JSON-LD script to the page or → Validate the markup using Google's Rich… → …
  • Adding an FAQ section to a landing page or blog post
  • SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
  • Reaches schema.org

What it does

The skill covers FAQPage structured data: a JSON-LD script with a mainEntity array of Question objects, each holding the question text as name and an acceptedAnswer of type Answer with a text property. It applies only to pages whose question-and-answer content is visible to visitors.

It works in several modes. Check inspects each FAQ page for the script block, the array and the answer fields. Fix finds the FAQ sections, writes the JSON-LD into the head or body and runs it through Google's Rich Results Test. Explain describes why mismatched markup is ignored and may draw a manual action, and Code Review parses every ld+json block and compares each marked-up question with one visible on the page. Longer implementation notes sit in references/rule.md.

When your agent uses it

  • Adding an FAQ section to a landing page or blog post
  • Generating FAQPage JSON-LD from Q&A content already on a page
  • Validating structured data on pages with FAQ sections
  • Reviewing templates for markup that does not match visible content

Example prompts

  • “Generate FAQPage JSON-LD for the questions at the bottom of our pricing page.”
  • “Check whether the FAQ schema on the seo-basics blog post matches the questions shown on the page.”
  • “Review this template for FAQPage markup that lists questions readers cannot see.”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify pages with FAQ-style content (a section of questions and answers visible to users).
  2. Add a JSON-LD script to the page or
  3. Validate the markup using Google's Rich Results Test at https://search.google.com/test/rich-results.
  4. Ensure every question in the schema has a corresponding visible answer on the page.

What it can do on your machine

Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • schema.org

    Also links to:

    • search.google.com
    • frontendchecklist.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

FAQPage Schema Markup loads about 774 tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~774
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 319 words, ~774 tokens.

Download SKILL.mdSave it as .claude/skills/faq/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
faq
description
Use when adding FAQ sections to landing pages or blog posts, generating FAQPage JSON-LD from existing Q&A content, or validating that structured data on pages with FAQ sections is syntactically and semantically correct.
metadata.category
seo
metadata.priority
medium
metadata.difficulty
intermediate
metadata.estimatedTime
10
metadata.source
frontendchecklist.io
metadata.url
https://frontendchecklist.io/rules/seo/faq

Add FAQPage schema markup

Valid FAQPage structured data can generate rich results in Google Search, displaying expandable question-and-answer pairs directly in the SERP. This increases click-through rate and SERP real estate without requiring a higher ranking position.

Quick Reference

  • Add FAQPage JSON-LD with mainEntity question/answer pairs to pages that contain FAQ sections
  • Each Question must include acceptedAnswer with an Answer type containing the text property
  • Only use FAQPage schema when the page actually contains FAQ-style question-and-answer content visible to users

Check

Check pages that contain FAQ or Q&A sections. For each: (1) Is there a <script type="application/ld+json"> block with "@type": "FAQPage"? (2) Does it include a mainEntity array of Question objects? (3) Does each Question have a name (the question text) and an acceptedAnswer with "@type": "Answer" and a text property? (4) Does the schema content match what is visible on the page?

Fix

  1. Identify pages with FAQ-style content (a section of questions and answers visible to users).
  2. Add a JSON-LD script to the page <head> or <body>:
json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "How do I reset my password?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Click 'Forgot password' on the login page and enter your email address. You will receive a reset link within 5 minutes."
      }
    }
  ]
}
  1. Validate the markup using Google's Rich Results Test at https://search.google.com/test/rich-results.
  2. Ensure every question in the schema has a corresponding visible answer on the page.

Explain

FAQPage structured data enables Google to display expandable Q&A pairs directly in search results as a rich result. This increases the page's visible footprint in the SERP and can improve click-through rate. Invalid or mismatched schema (questions in markup not visible on page) will cause Google to ignore it and may trigger a manual action.

Code Review

Parse all <script type="application/ld+json"> blocks. Find any with "@type": "FAQPage". Validate that mainEntity is an array, each item has "@type": "Question", name is a non-empty string, and acceptedAnswer is an object with "@type": "Answer" and a non-empty text. Cross-reference each question in the schema against visible question elements on the page.


For full implementation details, code examples, and framework-specific guidance, see references/rule.md.

Rule page: https://frontendchecklist.io/rules/seo/faq

© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/faq of thedaviddias/Front-End-Checklist.

  • SKILL.md
  • references/rule.md

Open the folder on GitHubat commit e8d14d0

Compare with similar skills

FAQPage Schema Markup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

FAQPage Schema Markup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
FAQPage Schema Markup this skillthedaviddias/Front-End-Checklist74k—~774Automated safety check: PassMIT
HTML Metadata Fixeribelick/ui-skills9.6k2 repos~1.1kAutomated safety check: PassMIT
Roier SEOdavila7/claude-code-templates33k—~2.7kAutomated safety check: PassMIT
SEO Validatesoftspark/ai-toolkit179—~3.9kAutomated safety check: NotesApache-2.0
Site ArchitectureAvdLee/RocketSimApp80511 repos~3.3kAutomated safety check: PassCustom licence
SEO Optimizerailabs-393/ai-labs-claude-skills4551 repos~3.2kAutomated safety check: PassMIT

Similar skills

  • HTML Metadata Fixer

    ibelick/ui-skills

    Audits and fixes page titles, meta descriptions, canonical URLs, Open Graph and Twitter cards, favicons, JSON-LD and robots directives.

    9.6k GitHub starsUsed in 2 repos~1.1k tokens
    Marketing & SEOAuto-check passed
  • Roier SEO

    davila7/claude-code-templates

    Technical SEO auditor and fixer. An agent skill from davila7/claude-code-templates.

    33k GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed
  • SEO Validate

    softspark/ai-toolkit

    SEO validator: meta/OG, Schema.org, hreflang, Core Web Vitals, crawlability.

    179 GitHub stars~3.9k tokensUpdated 2 days ago
    Marketing & SEOAuto-check: notes
  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    805 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • SEO Optimizer

    ailabs-393/ai-labs-claude-skills

    This skill should be used when analyzing HTML/CSS websites for SEO optimization, fixing SEO issues, generating SEO reports, or implementing SEO best practices.

    455 GitHub starsUsed in 1 repo~3.2k tokens
    Marketing & SEOAuto-check passed
  • SEO

    ever-works/ever-works

    Optimize for search engine visibility and ranking. An agent skill from ever-works/ever-works.

    162 GitHub starsUsed in 10 repos~2.9k tokens
    Marketing & SEOAuto-check passed

More from thedaviddias/Front-End-Checklist

All 390 skills in this repo
  • Content Dates Audit

    thedaviddias/Front-End-Checklist

    Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.

    74k GitHub stars~691 tokensUpdated 4 days ago
    Auto-check passed
  • Favicon Audit and Setup

    thedaviddias/Front-End-Checklist

    Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.

    74k GitHub stars~731 tokensUpdated 4 days ago
    Auto-check passed
  • Content Freshness Signals

    thedaviddias/Front-End-Checklist

    Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.

    74k GitHub stars~741 tokensUpdated 4 days ago
    Auto-check passed
  • Geo Meta Tags Audit

    thedaviddias/Front-End-Checklist

    Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).

    74k GitHub stars~763 tokensUpdated 4 days ago
    Auto-check passed
  • Improve a Front-End Checklist Rule

    thedaviddias/Front-End-Checklist

    Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.

    74k GitHub stars~1.3k tokensUpdated 4 days ago
    Auto-check passed
  • Front-End Checklist npm Package Finder

    thedaviddias/Front-End-Checklist

    Finds two or three well-maintained npm packages for a Front-End Checklist rule, checks download and release thresholds, and adds them to the rule's frontmatter.

    74k GitHub stars~989 tokensUpdated 4 days ago
    Auto-check passed

Questions about FAQPage Schema Markup

What does FAQPage Schema Markup do?

Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results. The skill covers FAQPage structured data: a JSON-LD script with a mainEntity array of Question objects, each holding the question text as name and an acceptedAnswer of type Answer with a text property. It applies only to pages whose question-and-answer content is visible to visitors.

When should I use FAQPage Schema Markup?

FAQPage Schema Markup fits situations like: adding an FAQ section to a landing page or blog post; generating FAQPage JSON-LD from Q&A content already on a page; validating structured data on pages with FAQ sections; reviewing templates for markup that does not match visible content.

How do I install FAQPage Schema Markup in Claude Code?

Run `npx skills add thedaviddias/Front-End-Checklist --skill faq -a claude-code`. Or copy the skill folder (skills/faq in thedaviddias/Front-End-Checklist) into .claude/skills/faq in your project. Claude Code loads it when a task matches its description.

How do I install FAQPage Schema Markup in Codex?

Run `npx skills add thedaviddias/Front-End-Checklist --skill faq -a codex`. Or copy the skill folder (skills/faq in thedaviddias/Front-End-Checklist) into .agents/skills/faq in your project. Codex loads it when a task matches its description.

Can I use FAQPage Schema Markup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill faq -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/faq, .gemini/skills/faq, .github/skills/faq and .opencode/skills/faq in your project.

What does FAQPage Schema Markup need to run?

SKILL.md names no scripts, command-line tools or credentials: FAQPage Schema Markup is instructions for the agent only.

Does FAQPage Schema Markup access the network?

SKILL.md names 3 domains. In commands or code: schema.org; the agent is likely to contact it when it follows the instructions. As links in the text: search.google.com and frontendchecklist.io. This is read from the text; nothing was executed.

Is FAQPage Schema Markup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does FAQPage Schema Markup use?

FAQPage Schema Markup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does FAQPage Schema Markup use?

About 774 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to FAQPage Schema Markup?

Skills that share tags, products or a category with FAQPage Schema Markup: HTML Metadata Fixer (ibelick/ui-skills, 9.6k stars), Roier SEO (davila7/claude-code-templates, 33k stars), SEO Validate (softspark/ai-toolkit, 179 stars) and Site Architecture (AvdLee/RocketSimApp, 805 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains FAQPage Schema Markup?

thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,421 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.

Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.