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:
data-ai
license: Apache-2.0 NOT for unrelated tasks outside this domain.
development
Use when designing caching strategies (cache-aside, write-through, write-behind), implementing distributed locks, building rate limiters, leaderboards, real-time streams (XADD/consumer groups), pub/sub, or tuning eviction policies. Triggers: thundering-herd on cache miss, dogpile on key expiry, Redlock vs SET-NX-PX choice, sliding-window rate limiter, hot-key on a single cluster slot, big-key blowup, MULTI/EXEC across slots, KEYS in production. NOT for Redis Cluster operations/admin (different domain), embedded KV (SQLite, leveldb), in-process LRU caches, or Memcached.
tools
Drawing the `'use client'` boundary correctly in React Server Components apps (Next.js App Router, RSC frameworks) — leaf-pushing, slot composition, serialization rules, and environment poisoning prevention. Grounded in react.dev and Next.js 16 docs.
development
Use when designing rate limiting for an API, choosing between token bucket / sliding window / leaky bucket / fixed window, implementing it in Redis, deciding edge (Cloudflare/Upstash) vs origin enforcement, sizing per-user vs per-IP vs per-endpoint quotas, returning the right 429 response with Retry-After, or fixing the boundary-burst bug in fixed-window limiters. Triggers: 429 too many requests, INCR + EXPIRE, ZADD + ZREMRANGEBYSCORE + ZCARD, X-RateLimit-Remaining header, Cloudflare WAF rate limiting rules, Upstash @upstash/ratelimit, leaky bucket shaping vs policing, distributed rate limiter consistency. NOT for DDoS mitigation specifically (different scale), CAPTCHA / bot management, full WAF design, or per-user quota billing.