skills/seo-visibility-expert/SKILL.md
Comprehensive SEO, discoverability, and AI crawler optimization for web projects. Use for technical SEO audits, llms.txt/robots.txt setup, schema markup, social launch strategies (Product Hunt, HN, Reddit), and Answer Engine Optimization (AEO). Activate on 'SEO', 'discoverability', 'llms.txt', 'robots.txt', 'Product Hunt', 'launch strategy', 'get traffic', 'be found', 'search ranking'. NOT for paid advertising, PPC campaigns, or social media content creation (use marketing skills).
npx skillsauth add curiositech/windags-skills seo-visibility-expertInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Traffic stalled/low? → Check in this order:
├── 1. Technical health
│ ├── Core Web Vitals score <90? → Fix performance first
│ ├── robots.txt blocking? → Check user-agents
│ └── Schema markup missing? → Add JSON-LD
├── 2. Content discoverability
│ ├── No llms.txt? → AI can't reference your content
│ ├── Missing Open Graph? → Poor social shares
│ └── No sitemap? → Crawlers missing pages
└── 3. Distribution channels
├── New project? → Need social launch strategy
├── Existing project? → Expand content marketing
└── B2B tool? → Focus on community presence
Ready to launch?
├── Product Hunt
│ ├── Tuesday-Thursday? → Proceed
│ ├── Holiday week? → Wait
│ └── Major tech news? → Reschedule
├── Hacker News
│ ├── 6-8am PST, Tue-Thu? → Post
│ ├── Weekend? → Wait for weekday
│ └── Technical audience? → Use "Show HN"
└── Reddit
├── Participated 90% vs promoted 10%? → Safe to promote
├── New account? → Build karma first
└── Wrong subreddit rules? → Find better fit
Want AI to find your content?
├── Training data inclusion
│ ├── Want citations? → Allow GPTBot, Claude-Web
│ └── Privacy concerns? → Block Google-Extended only
├── Content optimization
│ ├── Technical docs? → Detailed llms.txt with examples
│ ├── Marketing site? → Brief llms.txt with features
│ └── Blog? → Post summaries in llms.txt
Detection: Product posted, gets <50 total votes/comments across all platforms Symptoms: No pre-launch network, posted at wrong times, generic messaging Fix: Build relationships 4 weeks before launch, time posts strategically, craft platform-specific messaging
Detection: Zero mentions when searching your product in ChatGPT/Claude/Perplexity Symptoms: Missing llms.txt, AI crawlers blocked in robots.txt, no structured data Fix: Create llms.txt immediately, allow AI user-agents, add schema markup
Detection: Core Web Vitals score <50, bounce rate >70% Symptoms: Slow loading, layout shifts, heavy JavaScript Fix: Optimize images first (biggest impact), minimize JS bundles, set explicit image dimensions
Detection: Shared links show default browser title, no image preview Symptoms: Missing Open Graph tags, no og:image, generic descriptions Fix: Add complete Open Graph meta tags, create 1200×630 og:image, test with social debuggers
Detection: Rankings dropped after content update, unnatural reading flow Symptoms: Same keyword repeated 10+ times unnaturally, robotic prose Fix: Rewrite for humans first, use synonyms and related terms, maintain 1-2% keyword density max
Situation: DevSync (code collaboration tool) launched 3 months ago, getting only 50 visitors/day
Diagnostic Process:
Actions Taken:
Expert vs Novice:
Results: 2,500 visitors on launch day, #3 Product of the Day, 450% increase in trial signups
Situation: Open source library docs getting 90% traffic to homepage, other pages invisible
Diagnostic Process:
Actions Taken:
Results: Individual doc pages now rank for long-tail queries, 300% increase in organic traffic to deep pages
SEO audit is complete when ALL of these are true:
Do NOT use this skill for:
paid-marketing-specialist insteadcontent-creator insteademail-marketing-expert insteadconversion-optimization insteadbrand-strategist insteadDelegate when:
Gray areas requiring judgment:
tools
Building resilient distributed systems with circuit breakers, retries with full-jitter exponential backoff, retry budgets (per-request 3-attempt + per-client 10% ratio per Google SRE), deadline propagation, and the cascading-failure math (4 layers × 3 retries = 64x amplification). Grounded in Resilience4j, Microsoft Cloud Patterns, AWS Architecture Blog (Marc Brooker), and Google SRE Book.
testing
Designing HTTP cache headers that work correctly across browsers, CDNs, and shared proxies — `Cache-Control` directives per RFC 9111, `stale-while-revalidate` and `stale-if-error` per RFC 5861, the Vary header for varying responses, and surrogate keys for tag-based purging. Grounded in IETF RFCs and Cloudflare/Fastly docs.
development
Use when designing or fixing a Content Security Policy on a real site, choosing between nonce-based and hash-based CSP, adding strict-dynamic, debugging "Refused to execute inline script" errors, deploying CSP in report-only mode first, configuring report-to / report-uri, or auditing an existing policy for unsafe-inline / unsafe-eval / wildcards. Triggers: "CSP blocks legitimate inline script", strict-dynamic, nonce-{RANDOM}, sha256-{HASH}, object-src none, base-uri none, frame-ancestors, Trusted Types, X-Content-Security-Policy obsolete, report-only vs enforced. NOT for general HTTP security headers (HSTS, COOP/COEP), Trusted Types deep dive, CORS configuration, or building a WAF.
tools
Choosing and operating an HTTP API versioning strategy that doesn't break clients — Stripe's date-based pinned versions, the Deprecation/Sunset header pair (RFC 9745 + RFC 8594), URI vs header vs media-type approaches, and the version-transformer pattern. Grounded in Stripe's published architecture and IETF RFCs.