| name | seo-launch-resonance |
| description | Use when launching a site/section and you want fast ORGANIC search growth, or diagnosing why a launch got no traffic. Triggers — RU "алгоритм успеха seo-запуска", "почему нет трафика после запуска", "быстрый органический рост", "запуск лендингов сразу в индекс", "резонанс канала и спроса"; EN "seo launch playbook", "fast organic growth", "why no traffic after launch", "channel content demand resonance". Produces an ordered launch checklist + attribution/retention follow-up. |
SEO Launch Resonance
Goal
Get explosive organic search growth on launch by firing three multipliers at the same time — search channel (indexing), content (landing pages + freshness), and demand (a real search-interest peak). Miss any one and you get a slow warm-up instead of a spike. This skill turns that into an ordered, verifiable checklist.
Core principle
Explosive growth = Channel (indexing) × Content (landings + freshness) × Demand (interest peak)
Any multiplier at zero → no spike. Channel without content = empty results. Content without channel = nobody sees it. Both without demand = slow organic warm-up.
When NOT to invoke
- Paid-traffic / ads launch (this is organic-search specific)
- Brand-new domain with zero content strategy — build the content plan first
- Pure technical SEO audit of an existing ranked site (use a dedicated audit skill)
Requirements
- Agent: Claude Code (primary) | Codex CLI | Gemini CLI
- Tools: site codebase access, ability to deploy,
git
- Accounts: Yandex Webmaster + Metrica (RU audience), Google Search Console; analytics (e.g. Vercel Analytics)
- OS: macOS / Linux
Process
1. Open the channel FIRST — search-engine verification
- Connect Yandex Webmaster + Metrica (for RU audience Yandex is usually the dominant source — often the majority of organic traffic).
- Connect Google Search Console.
- Verify the verification file actually returns 200 (a routing 404 on the verification file silently blocks indexing).
- Ship a valid
sitemap.xml (prefer age-decay priority favouring fresh URLs) and correct robots.txt.
- This is the trigger, not a "later" task. Nothing below indexes without it.
2. Ship content in one wave — a set of targeted landing pages
- One page per query cluster (don't cram clusters onto one page).
- Per-page technicals: H1 with the target key, breadcrumbs, internal linking (a hub + navigation between the landings).
- Resolve cannibalization up front: one key = one page. Redirect / repurpose duplicate competitors (e.g. turn an overlapping page into a different intent and hand its key to the canonical one). Keep a topic registry.
3. Add freshness — auto-generated dated content
- A
/news-style section or dated archive, regenerated regularly.
- Freshness is a strong ranking signal, especially in event-driven niches.
4. Sync the launch with a demand peak
- For event-driven niches (news, releases, seasonal), ship the landing wave on the rising edge of real interest, so pages land in the index by the time queries peak.
- The site doesn't create demand — it catches an existing wave. Timing is the multiplier.
5. Close the loop (after launch)
- Attribution: in Yandex Webmaster split traffic by query and page → learn which landings actually fired → pour the next wave there.
- Retention / bounce: internal-link from the landing deeper (core product, adjacent pages) — high bounce means you under-convert the traffic you already earned.
Quick checklist
Anti-patterns
- ❌ Building landings before verifying the search channel — pages sit unindexed
- ❌ Two pages competing for one key (cannibalization) — split intent or redirect
- ❌ Static content in an event-driven niche — no freshness signal
- ❌ Launching off-peak and expecting a spike — demand is a multiplier, not optional
- ❌ Celebrating the spike and never measuring per-page attribution — you can't repeat what you can't attribute
