← ClaudeAtlas

seo-playbooklisted

Architect a website's page surface for search and AI visibility, audit an existing site's SEO, or judge whether a site should do programmatic SEO at all. Use WHENEVER the user mentions SEO, GEO, AEO, search rankings, "why isn't this page indexed", "why isn't my site ranking", "we get no organic traffic", meta descriptions, title tags, canonical tags, robots.txt, sitemaps, schema markup / JSON-LD / structured data, internal linking, crawl budget, Core Web Vitals, programmatic or templated pages, landing-page generation at scale, keyword targeting, AI search visibility (ChatGPT / Perplexity / AI Overviews), llms.txt, blocking AI or SEO-crawler bots. ALSO use for: backlinks, link building, domain authority / domain rating, how a new site earns the right to rank, and how long ranking takes; faceted navigation, filters, e-commerce category and pagination indexing; and whenever the user is planning a new site or product site and asks how to structure it, how many pages it should have, or what URLs it should expose.
yash-banka/seo-playbook · ★ 2 · AI & Automation · score 66
Install: claude install-skill yash-banka/seo-playbook
# SEO/GEO Playbook ## The premise this playbook is built on Most people treat SEO as something applied to a site after it exists. That is backwards and it caps your ceiling. **The page surface of a site *is* its SEO strategy**, and it is an architecture decision made before the first line of code. The reference implementation behind this playbook is a browser-based media conversion tool. Functionally it is *one* engine — a single JS bundle, a single stylesheet, a router that maps a URL slug to a preset. Product necessity would justify roughly three pages. It ships **several hundred**. Nearly all of those URLs are not product. They are deliberately manufactured **search surface**. Each one is the same tool wrapped in an explanation written for one specific query. That single decision is why it competes in a brutally commoditised category. So the first question for any new site is never "how do I optimise these pages". It is: **"what is the full space of things people search for that this product can answer, and how much of that space deserves a URL?"** --- ## Routing: which mode are you in? **First: does this playbook even apply?** It is written for sites that must *manufacture* demand capture. Personal sites, portfolios and studios generally should not — they rank on brand, singular content and earned links, and a generated surface would actively harm them. Read the "When this playbook does not apply" section of `reference/00-surface-design.md` before proceeding if t