qte77/auditing-website-seo-geo
plugins/website-audit/skills/auditing-website-seo-geo/SKILL.md
Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-utils auditing-website-seo-geoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 14, 2026, 3:42 AM142.2s1 file scanned
SKILL.md
- name:
- auditing-website-seo-geo
- description:
- Audits a site's SEO and AI-search (GEO) readiness — meta tags, Open Graph/Twitter, JSON-LD, robots/llms conventions — and generates fixes. Use when reviewing search visibility, social previews, structured data, or LLM/AI-crawler discoverability.
- compatibility:
- Designed for Claude Code
- allowed-tools:
- Read, Write, Edit, Glob, Grep, Bash, WebSearch, WebFetch
- argument-hint:
- [url-or-file-path]
- stability:
- stable
- content-hash:
- sha256:6fc16d33ad7c663af30e578ac2b6fe93b1737781ec4df878ac84c2a52ff3515b
- last-verified-cc-version:
- 1.0.34
Website SEO & GEO Audit
Target: $ARGUMENTS
Audits a site for traditional SEO and Generative-Engine Optimization (GEO — visibility in AI search such as ChatGPT, Perplexity, Gemini, and Google AI Overviews) and generates implementable fixes. Prefer configuring the site or static-site generator so tags are emitted once (DRY) over hand-stuffing meta into every page. No over-analysis.
Audit Areas
Core meta
<title>(~30-60 chars, unique per page),<meta name="description">(~120-160 chars, entity-clear),langon<html>,charset,viewport(nomaximum-scale— it blocks zoom),robots,author,keywords,format-detection, and acanonicallink.
Open Graph & Twitter Card
og:title,og:description,og:url,og:type,og:site_name,og:image.twitter:card,twitter:title,twitter:description,twitter:image,twitter:site,twitter:creator.
Structured data (JSON-LD)
WebSite/Organization(name, url, logo, sameAs) and per-pageArticle/BlogPosting(headline, description, datePublished, author, publisher, image). Validate against the matching schema.org type.
GEO / AI-search
robots.txtAI user-agents (GPTBot, ClaudeBot, Google-Extended, CCBot, PerplexityBot, OAI-SearchBot) — the highest-leverage, best-honored lever.llms.txtat root — cheap, uncertain adoption; fine to keep.- Entity clarity, key info in the first ~160 chars, Q&A-friendly phrasing, explicit brand / product / service names.
Static-site-generator pitfalls (verify, do not assume)
- Do not double-emit. If an SSG plugin emits OG/Twitter/JSON-LD (e.g. jekyll-seo-tag, Next SEO), do NOT also hand-write those tags — duplicates result. Configure the plugin instead.
- Plugins emit conditionally. Twitter Card tags often need a configured
handle;
twitter:descriptionandog:image/twitter:imagemay not be emitted without explicit config or a per-page image. Fill only the genuine gaps in a single shared include.
Known-unwinnable conflicts (flag, do not chase)
Some checkers want mutually-exclusive lengths on a single shared tag:
og:title25-35 vstwitter:title50-70 — same tag, cannot satisfy both.og:description55-65 vs<meta name="description">120-160 — same tag.
Recommend the real-world optimum (Google limits plus GEO: a ~50-char title and a ~150-char description) and note the tradeoff rather than ping-ponging.
Reality check
- ai.txt /
/.well-known/ai.txtis not a recognized standard (competing vendor proposals, no IANA.well-knownregistration, no major adopter). Skip it; do not spend effort on/.well-known/ai.txt. - A complete
robots.txtAI-agent policy plus a full OG/JSON-LD set are what actually move GEO and social previews.
Workflow
- Identify scope from $ARGUMENTS (URL, file, or directory). For a URL,
fetch the rendered
<head>— converting tools return markdown, so fetch raw HTML when you need the tags verbatim. - Inventory the tags present versus the audit areas above; detect duplicates.
- Classify findings: HIGH (title, description, canonical, OG core), MEDIUM (Twitter, JSON-LD, keywords), LOW (format-detection, author).
- Generate fixes — prefer SSG config plus a single shared include over per-page tags.
- Verify by re-fetching the built output, not the raw templates.
Output Format
Findings
HIGH
- [Tag/issue] - Current: [value or "missing"] - Page: [url/path]
Fix: [code/config snippet]
MEDIUM / LOW
- [Tag/issue] - Current: [value or "missing"]
Fix: [code/config snippet]
Implementation Checklist
- [ ] [Fix] - Impact: [High/Medium/Low] - scope: [site-wide | per-page]
Rules
- Configure once (DRY); do not hand-stuff tags an SSG already emits.
- Flag mutually-exclusive checker targets instead of chasing impossible green.
- Optimize for real engines and GEO, not vanity checker scores.
- Every finding includes a concrete, implementable fix.
- Keep output concise: findings + fixes + checklist only.
Further Reading
- The Open Graph protocol
- schema.org Article
- Google Search Central — structured data
- llms.txt proposal
Related Skills
qte77/triaging-security-report
development
VerifiedTrustedCommunity
Verify an external or AI-generated security report against the actual codebase before acting on it. Use when handed a scanner PDF, automated teardown, audit report, or bug-bounty submission — classifies every finding CONFIRMED / OVERSTATED / FALSE-POSITIVE / FABRICATED and salvages the real work items.
2SKILL.mdUpdated Jul 18, 2026
qte77/researching-website-design
development
VerifiedTrustedCommunity
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-website-usability
development
VerifiedTrustedCommunity
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-website-accessibility
development
VerifiedTrustedCommunity
Audits website accessibility for WCAG 2.2 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
1SKILL.mdUpdated Apr 19, 2026