Use when applies especially to e-commerce checkouts, contact/lead forms, pricing pages, and YMYL (Your Money or Your Life) content. Use when auditing E-E-A-T or conversion optimization.
46
48%
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
Fix and improve this skill with Tessl
tessl review fix ./skills/trust-signals/SKILL.mdGoogle's Quality Rater Guidelines explicitly evaluate trustworthiness as a core page quality signal; pages lacking visible trust evidence score lower in manual quality assessments that influence ranking systems.
On key conversion pages (checkout, contact, pricing, landing pages), check for: security/SSL badges near forms, third-party review platform ratings (Google, Trustpilot), industry certifications, client/partner logos, testimonials with names and photos, money-back guarantee language. Verify all badges are genuine (not just images).
Add appropriate trust signals to each key page: embed real review widgets from Google/Trustpilot, display relevant certifications with verifiable links, add named testimonials with photos, include security badges near form submission areas. Ensure all trust elements are current and accurate.
Explain how trust signals affect both user conversion rates and Google's quality assessments, what E-E-A-T means for content quality, and why YMYL pages face higher trust scrutiny from Google's Quality Rater Guidelines.
Review metadata generation, rendered HTML, structured data, and response headers related to Show trust signals on key pages. 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/en/rules/seo/trust-signals
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.