seo audit

Security Community

Skill notes

Arguments

/seo-audit — full audit (default) /seo-audit quick — check only critical items /seo-audit [url] — audit a specific page (e.g. /seo-audit /blog/my-post)

Phase 1: Parallel Page Audits

Launch parallel agents to audit pages. For each page, check: Meta Tags: Title tag (unique, under 60 chars, includes primary keyword) Meta description (unique, 150-160 chars, includes CTA) Meta keywords (page-specific, not generic defaults)

Phase 2: Site-Wide Checks

robots.txt: Fetch https://cc4.marketing/robots.txt Check if AI bots are allowed: GPTBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended CRITICAL: Check for Cloudflare managed block prepended before custom rules — this overrides your Allow directives Verify sitemap and llms.txt references

Phase 3: AEO-Specific Checks

FAQ schema — do any blog posts have Q&A sections that should use FAQPage? HowTo schema — do any blog posts have step-by-step instructions that should use HowTo? Featured snippets — are H2/H3 headings phrased as questions for featured snippet targeting? Entity clarity — is the Organization entity consistent across all schemas? Breadcrumb depth — do all pages have proper breadcrumb chains (Home > Section > Page)?

Phase 4: Report

Output a table: Then list fixes by priority: Critical — blocks indexing or AI discovery High — affects SERP appearance or rich results Medium — optimization opportunities

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Parallel Page Audits

Launch parallel agents to audit pages. For each page, check: Meta Tags: Title tag (unique, under 60 chars, includes primary keyword) Meta description (unique, 150-160 chars, includes CTA) Meta keywords (page-specific, not generic defaults)

02
Phase 2: Site-Wide Checks

robots.txt: Fetch https://cc4.marketing/robots.txt Check if AI bots are allowed: GPTBot, ClaudeBot, Claude-Web, PerplexityBot, Google-Extended CRITICAL: Check for Cloudflare managed block prepended before custom rules — this overrides your Allow directives Verify sitemap and llms.txt references

03
Phase 3: AEO-Specific Checks

FAQ schema — do any blog posts have Q&A sections that should use FAQPage? HowTo schema — do any blog posts have step-by-step instructions that should use HowTo? Featured snippets — are H2/H3 headings phrased as questions for featured snippet targeting? Entity clarity — is the Organization entity consistent across all schemas? Breadcrumb depth — do all pages have proper breadcrumb chains (Home > Section > Page)?

04
Phase 4: Report

Output a table: Then list fixes by priority: Critical — blocks indexing or AI discovery High — affects SERP appearance or rich results Medium — optimization opportunities

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.