Skip to content
cccskills
FreePublished on GitHubEnglish overview

faq

Add FAQ sections to landing pages or blog posts and generate FAQPage structured data, a format search engines can read. Check required question and answer fields, valid syntax, and consistency with content visitors can see.

OriginalShow the original 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.

AI rating100/ 100See how to install

Good for

  • Adding FAQ sections to landing pages or blog posts
  • Generating structured data from existing questions and answers
  • Checking FAQ markup against visible page content

Overview

What it does

Helps add FAQ sections to landing pages and blog posts, and creates FAQPage structured data from published questions and answers. Structured data provides information that search engines can read. It reviews the JSON-LD syntax and checks fields including mainEntity, which lists questions, name for question text, and acceptedAnswer and text for answers.

When it helps

Use it when adding frequently asked questions to a page or describing existing Q&A content in a format for search engines. It is also useful when you need to check both the syntax and whether the questions and answers in the data match what visitors actually see on the page.

Example requests

  • “Create FAQPage JSON-LD from the questions and answers in this article.”
  • “Check the required FAQ fields and confirm that they match the questions and answers displayed on the page.”

Notes

This applies to pages with questions and answers visible to visitors. Do not add questions or answers only to the structured data. The validation steps include Google’s Rich Results Test. Display in search results is not guaranteed.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt covers adding FAQs, generating JSON-LD from existing Q&A, and validating syntax and consistency with visible content.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt provides a JSON-LD example, required properties, Rich Results Test validation, and steps to compare markup with visible content.
SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt limits additions to visible Q&A and requires validation and comparison with page content.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt provides the Rich Results Test URL and requires no additional API key or paid service.

The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (2)

  • SKILL.md3.0 KB
  • references/rule.md4.5 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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>:
{
  "@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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

404-page

FreeSummaryAI rating 100

Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

about-page

FreeSummaryAI rating 90

Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessibility-testing

FreeSummaryAI rating 80

Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.

  • Review accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-authentication

FreeSummaryAI rating 90

Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-notifications

FreeSummaryAI rating 100

Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-tables

FreeSummaryAI rating 100

Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

See all skills by thedaviddias

Report a problem with this skill