no-bluff-seo-skill
Validate SEO Claims With Evidence
SEO copy often includes claims that are hard to verify. This skill guides Claude, Codex, and Claude Code to source claims, score confidence, and separate facts from forecasts.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "no-bluff-seo-skill" from https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill.md and its manifest at https://skillstore.io/api/skills/cleanexpo-no-bluff-seo-skill/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "no-bluff-seo-skill". A landing page says the company is the top-rated provider in its market.
Expected outcome:
The claim should be rejected unless current review data supports it. Replace it with a dated rating, review count, source, and confidence label.
Using "no-bluff-seo-skill". A keyword report includes traffic estimates from multiple tools.
Expected outcome:
The report should identify each source, mark direct measurements as high confidence, and label calculated estimates as medium confidence.
Using "no-bluff-seo-skill". A product page needs search metadata and FAQ schema.
Expected outcome:
The page can include product and FAQ structured data when each answer is present on the page and review claims use real reviews.
Security Audit
SafeThe static analyzer flagged six uses of inline Markdown backticks as Ruby or shell execution. Review of SKILL.md shows these are formatting markers around field names and confidence labels, with no executable commands or command interpolation present.
Risk Factors
⚙️ External commands (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cleanexpo-no-bluff-seo-skill/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/cleanexpo-no-bluff-seo-skill.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
CleanExpo. (2026). no-bluff-seo-skill security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill/audits/8BibTeX citation
@techreport{cleanexpo-cleanexpo-no-bluff-seo-skill-2026,
author = {CleanExpo},
title = {no-bluff-seo-skill security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "no-bluff-seo-skill security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CleanExpo"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/cleanexpo-no-bluff-seo-skill/audits/8"
identifiers:
- type: other
value: "skillstore:cleanexpo-no-bluff-seo-skill:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Landing Page Claim Review
Check marketing copy for measurable SEO claims, add sources, and remove unsupported ranking statements.
Client SEO Audit Preparation
Create audit notes that show what data was checked, what changed, and how confident each insight is.
Structured Data Cleanup
Review product, local business, article, FAQ, and review schema requirements before updating page metadata.
Try These Prompts
Review this landing page copy with the No-Bluff SEO protocol. List unsupported claims, required sources, and safer wording.
Assess these SEO insights. Add source, metric type, confidence score, and a short reason for each confidence level.
Review this page type and content. Recommend the appropriate structured data fields and flag any values that need evidence.
Audit this client SEO report for factual claims, forecasts, opinions, vanity metrics, missing sources, and required audit trail notes.
Best Practices
- Provide the source data or tool output before asking for claim validation.
- Keep dates with statistics so readers know when the evidence was current.
- Log checked sources, findings, content changes, and responsible reviewers.
Avoid
- Do not publish rankings or superlatives without a cited source.
- Do not mix facts, forecasts, and opinions in the same unsupported statement.
- Do not add review schema unless the reviews are real and visible to users.