Check whether pages clearly explain affiliate or sponsorship relationships before promotional links appear. Review the rendered HTML and HTTP responses, identify affected pages or templates, and suggest disclosure wording and placement that readers can easily understand.
Use when auditing metadata, crawlability, structured data, or indexability related to Provide clear affiliate disclosures. Verify the rendered HTML and HTTP response rather than relying only on source files.
Run score Not tested
See how to installaffiliate-disclosure checks whether affiliate links and sponsored content have a clear notice explaining the financial relationship. It reviews whether the notice appears prominently before the links and whether the wording is unambiguous. It suggests standard disclosure text for the beginning of an article or near the links. The review covers generated HTML and HTTP responses, rather than relying only on source files.
Use it before publishing product recommendation articles or sponsored pages. It also helps when you want consistent disclosures across several articles, or when reviewing existing pages for reader communication and SEO. It identifies the specific pages or templates with problems and sets out how to verify the result after changes.
The source discusses guidance such as FTC guidelines and explains the legal and ethical importance of disclosures. Implementation details and code examples are provided through the accompanying references/rule.md.
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.
Clear disclosures are required by law (e.g., FTC guidelines) and are essential for maintaining user trust and preventing search engine penalties for hidden advertisements.
Verify that all pages containing affiliate links or sponsored content have a clear, visible disclosure before the links appear.
Add a standardized disclosure statement at the beginning of your content or near affiliate links to inform users of the partnership.
Explain the legal and ethical importance of affiliate disclosures and how they impact user trust and SEO.
Review metadata generation, rendered HTML, structured data, and response headers related to Provide clear affiliate disclosures. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/affiliate-disclosure
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.