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.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
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/en/rules/seo/editorial-policy
48405aa
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.