Review disclaimers on health, finance, legal, and safety pages, plus affiliate disclosures. The skill checks wording, visibility, and placement, then suggests context-specific copy and disclosure placement before the first affiliate link.
Use when auditing YMYL content pages for trust signals, generating disclaimer copy for medical or financial content, or reviewing affiliate disclosure requirements under FTC or ASA guidelines.
Run score Not tested
See how to installReviews disclaimers on medical, financial, legal, and safety pages, along with advertising disclosures in affiliate articles. It uses the YMYL perspective, which covers information affecting areas such as health and personal finances. It checks whether the text states that the content is not professional advice, is specific to the article, and appears where readers can find it. It covers wording for different subject areas, visual presentation, and role attributes that help assistive technologies identify the disclaimer.
Use it before publishing health information or investment articles, or when reviewing pages containing legal information. It also helps check whether an advertising disclosure appears before affiliate links and whether a disclaimer is buried in a footer or after a long article.
The advertising disclosure guidance covers the US FTC and the UK ASA. The material emphasizes accurate disclaimers tailored to the article's subject and context, so check that any example wording fits the content where it will appear.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Google's Search Quality Rater Guidelines classify health, finance, and legal topics as 'Your Money or Your Life' (YMYL) pages that are held to the highest trust standards. Pages lacking appropriate disclaimers score low on Trustworthiness within the E-E-A-T framework, suppressing their rankings.
Identify pages covering medical, legal, financial, safety, or affiliate content. For each, check: (1) Is there a visible disclaimer stating the content does not constitute professional advice? (2) For affiliate content, is there an FTC-compliant disclosure before the first affiliate link? (3) Is the disclaimer placed prominently — not hidden in footers or after lengthy content?
Google evaluates YMYL pages under its E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) framework. Missing disclaimers on sensitive topics reduce the Trustworthiness score, which quality raters assign and which influences how Google ranks those pages. Disclaimers also reduce legal risk and meet regulatory requirements (FTC in the US, ASA in the UK for affiliates).
Scan page content for YMYL topic keywords (medical symptoms, drug names, investment advice, legal rights, etc.). If found, check for a disclaimer element near the top of <main> or <article>. Verify affiliate pages include FTC-compliant disclosure text before the first <a> with a referral parameter or affiliate domain.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/disclaimers
No reviews yet. Tell others what you thought.
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.
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.
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.
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 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.
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.
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.