Audit or draft an editorial policy for a blog, news site, or sensitive-topic publication. Cover author qualifications, research, fact-checking, corrections, and funding disclosures, and check that readers can find the policy from relevant pages.
Use when auditing a blog, news site, or YMYL content site for trust signals, drafting editorial policy page content, or evaluating whether a site meets Google's quality rater trustworthiness criteria.
Review a blog or news site's editorial policy and organize the information needed to draft it. The review covers the publication's topics and purpose, author expertise, research and fact-checking methods, article updates and corrections, and relationships with advertising, affiliate programs, and funders. It also checks whether the About page, site footer, and article bylines direct readers to the policy.
This skill helps site operators explain how their articles are researched, written, and checked. It is useful for sites covering subjects that can substantially affect readers' lives, such as health and money. You can also use it to revise an existing policy that consists of only a short, generic statement.
A site review also checks whether the policy is publicly available and returns HTTP status 200, indicating a successful response. Drafting requires information about actual author qualifications, review practices, and funding relationships. The content should describe how the publication operates, with specific details rather than formal statements alone.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
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.
Review the instructions the agent will receive before you install.
Google's E-E-A-T framework rates sites on Expertise, Authoritativeness, and Trustworthiness. Quality raters look for editorial standards pages as evidence of a trustworthy publication. Sites without visible editorial policies — especially YMYL sites — receive lower trust ratings, which suppresses search rankings.
Check if the site has a publicly accessible editorial policy page (commonly at /editorial-policy, /about/editorial-standards, or linked from the About page). Verify it covers: (1) how topics are chosen, (2) author qualifications, (3) fact-checking or review process, (4) how corrections are handled, and (5) conflicts of interest or funding disclosures.
Google's Search Quality Rater Guidelines specifically look for editorial standards as part of evaluating a site's Trustworthiness. For YMYL topics especially, the absence of an editorial policy is a clear signal to quality raters that the site cannot be trusted to publish accurate, expert-reviewed content, leading to lower quality ratings and reduced search visibility.
Check the site's footer links, About page, and individual article templates for a link to an editorial policy page. Verify the editorial policy URL returns a 200 status code and that the page contains substantive content — not just a boilerplate paragraph — covering research methodology, author qualifications, and correction policies.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/editorial-policy
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.