← ClaudeAtlas

bld-optimize-seo-indexinglisted

oi: Get an app found on Google. Audit the live site, add sitemap, robots, canonical and structured data, then list the account steps only the user can do. Use for "get this on Google", "index my site", "why isn't my site showing up", "SEO this".
mnguyenht/bld-package · ★ 1 · AI & Automation · score 64
Install: claude install-skill mnguyenht/bld-package
# bld-optimize-seo-indexing — get an app found on Google Two halves that must not be confused: **the code** (Claude, one afternoon) and **the accounts** (only the user, and the slow part). This file is the conductor. The user-facing checklist lives in `references/user-steps.md` — read it only when you reach Phase 4, so it doesn't cost context on every invoke. ## Say this before doing anything The single most common confusion, and the one that wasted the most time on the first run of this skill: | | Question it answers | What fixes it | |---|---|---| | **Indexing** | Is this page in Google's database *at all*? | Crawlability + submitting the URL + **time** | | **Ranking** | *Where* does it appear for a given search? | Titles, content, backlinks | **Meta titles do not affect indexing.** YouTube SEO videos blur this constantly. If the user is anxious that a two-day-old site isn't showing up, rewriting titles will not help, and implying it will is a claim you'll have to walk back. Set the timeline expectation in Phase 5 **before** they submit anything, not after they worry. ## Phase 0 — audit the LIVE site with curl, never by reading code Reading the source tells you what *should* be served. Only a request tells you what *is*. On the first run, `SITE.url` still held the old `*.vercel.app` domain that had since started 404ing, so every canonical URL and every `og:image` on the live site pointed at a dead host. The code looked completely fine. ```bash APP=https://www.exampl