FAQPage
Use it only when the FAQ is visible on the same page and the questions match the JSON-LD exactly.
Schema guide
Schema helps when it describes visible content. On finance pages, the goal is fit, not decoration. The wrong schema can create confusion fast, especially when the page already deals with trust-sensitive claims.
Schema types
Use it only when the FAQ is visible on the same page and the questions match the JSON-LD exactly.
Use it for article-style pages with a clear editorial structure, not for thin service pages or promos.
Use it when the page visibly shows breadcrumbs that reflect the real page hierarchy.
Use it to describe the brand or site. Keep it grounded in real site details and logos.
Use it for the GPT or other tool pages when the page is actually describing a software-like product.
Do not use it unless the page has real sequential instructions that are visible to the reader.
Validation checklist
Common mistakes
| Mistake | Why it is a problem | Better move |
|---|---|---|
| FAQPage without a visible FAQ | Schema and page content no longer match. | Add the FAQ visibly or remove the schema. |
| HowTo on a broad guide | It implies step-by-step instructions that do not exist. | Use a normal article structure instead. |
| Article on a service page | It can misrepresent the page type. | Use Article only on actual editorial pages. |
| Organization with made-up details | Unsupported schema is worse than no schema. | Keep the brand data real and minimal. |
Next step