← ClaudeAtlas

seo-aeo-visibility-strategylisted

Build and prioritize durable SEO and answer-engine optimization (AEO/GEO) strategies for new or established websites. Use when planning organic and AI-search visibility, choosing among content and technical tactics, designing topic or commercial page systems, adapting a plan for ecommerce, services, SaaS, publishers, or local businesses, or defining search and AI visibility measurement. Do not use as a ranking-guarantee or shortcut-hacking playbook.
apnatvar/web-development-and-online-marketing-skills · ★ 0 · Web & Frontend · score 60
Install: claude install-skill apnatvar/web-development-and-online-marketing-skills
# SEO + AEO Visibility Strategy Treat AEO/GEO as an extension of search visibility, not a replacement for SEO. Build a site that is easy to discover, index, understand, trust, retrieve, cite, and convert from. Make facts, entities, evidence, and brand identity explicit without inventing a separate set of unsupported “AI ranking factors.” ## Operating principles 1. Start with business value and user tasks, then map search and answer-engine opportunities. 2. Fix discovery, indexability, canonicalization, rendering, and content-quality failures before pursuing marginal optimizations. 3. Prefer a small, coherent corpus of useful pages over scaled, lightly differentiated content. 4. Separate citation presence, brand mention, referral traffic, and conversion; they are different outcomes. 5. Treat third-party correlation studies as directional evidence, not proof of ranking factors. 6. Never guarantee rankings, indexing, rich results, citations, mentions, traffic, or revenue. 7. Revalidate platform-specific guidance before major implementation because crawler behavior, reporting, and search features change. ## Workflow ### 1. Establish the decision context Identify: - site type, business model, audiences, markets, and conversion goals; - domain stage: new/low-authority, established, migrated, or declining; - important products, services, topics, entities, and locations; - current content inventory, page families, technical stack, feeds, and structured data; - available eviden