The Shelf / Growth / Product SEO Site Builder
Product SEO Site Builder
A guide page per long-tail keyword, SERP-gated. Organic traffic your product owns.
The job: build your product the website Google can actually rank — a home page plus a guide page per long-tail keyword plus an FAQ wired into the guides — so people searching the problem find the product that solves it.
Most products have a listing and maybe a one-page landing. Neither ranks in web search. Meanwhile the queries your buyers actually type — "how to
What it makes your agent do
- Gate every keyword on the live SERP. Before any page is written, the agent searches the exact phrase. Page 1 all major publishers and official docs? Dropped, and logged so you never re-research it. Page 1 has forum threads or nothing on-intent? That keyword earns a guide. Fewer real pages beat padded doorway pages — the skill enforces that trade.
- Write guides Google can trust. Fixed anatomy: H1 is the query, the direct answer lands in the first 150 words, a genuine step-by-step solution helps even people who'll never buy, and the product bridge is capped at roughly 20% of the page with one real screenshot.
- Wire the structure that trains rankings. Unique titles and descriptions, canonicals, OG tags, JSON-LD (SoftwareApplication, FAQPage, Article, HowTo, breadcrumbs — all templated in the package), and an internal-link scheme from home to guides to siblings.
- Cut over cleanly. 301s from any old page, one canonical host, Search Console domain property, sitemap submission, and the IndexNow recipe — plus the calibration that saves you a panic: indexing takes weeks, and "Couldn't fetch" right after sitemap submission is normal.
- Refuse the shortcuts that get sites penalized. No invented metrics or review counts anywhere, no fabricated aggregateRating markup, no keyword pages with duplicate intent, no two hosts serving the same content.
Who it's for
App and SaaS builders whose product is invisible in web search. Indie makers who want traffic that compounds instead of installs they rent. Agencies delivering guide sites for clients.
Why it beats a free directory download
Free "SEO content" prompts generate pages; they don't know which pages deserve to exist. The SERP gate, the guide anatomy, the schema set, and the cutover checklist here come from shipping real guide sites for real products — including the mistakes (redirect loops, cert races, doorway-page temptations) already paid for. Maintained as Google's systems move. The field report shows a real keyword-plan verdict before you pay.
FIELD REPORT real output, not a promise
A worked slice from the skill's own documented example — a voice-logging feature of a budgeting app going through Step 2 (keyword plan + SERP gate) and the guide anatomy that follows. No rankings claimed; indexing verdicts belong to Search Console weeks later.
Keyword plan entry (the Step-2 deliverable format, filled)
| # | Keyword (exact) | Intent | Guide must answer | SERP winnability |
|---|---|---|---|---|
| 1 | log expenses by voice | wants hands-free logging | how voice logging works, platform options, assistant vs app | page 1 has 2 forum threads + thin listicle — OPEN |
The verdict column is the gate: two forum threads and a thin listicle on page 1 means a genuinely helpful page from a real site can compete. Had page 1 been official support docs and major-publisher roundups, the keyword would land in the ## Dropped log with the reason — and never get a page.
What that keyword's guide must look like (anatomy enforced by the skill)
- H1, humanized: "How to Log Expenses by Voice (Hands-Free, in Seconds)" — the query, not a clever headline.
- Direct answer in the first 150 words. Zero throat-clearing; this is the text AI Overviews and featured snippets pull. "In today's fast-paced world" is banned on sight.
- Generic step-by-step solution that honestly serves someone who will never install the app — the section that earns Google's trust.
- The product bridge, capped: one H2 ("The one-tap way"), 2-4 sentences in the app's voice, ONE real screenshot of the app doing exactly this. Never more than ~20% of the page.
- Mini-FAQ, related guides with keyword anchor text, CTA band.
800-1500 words, written for a human first.
The schema that ships with it
Article JSON-LD on the guide; FAQPage markup only for questions visible verbatim on the page; aggregateRating only if pulled from a real ratings source with a meaningful count — the skill treats fabricated ratings markup as a manual-action magnet, not a growth hack.
The honest expectation set at handoff
Submit the sitemap, then leave it alone: days-to-weeks to index, check Search Console at ~2 weeks. The deliverable is a site where every page targets a query it can plausibly win — the rankings themselves are Google's call, and the skill never claims otherwise.
SERVICE RECORD living gear — updated as the factory learns
v1.0.0 — 2026-07-17
First issue. Ported from the factory's internal skill: sanitized for general use, methodology intact, field report captured from a real run.
Every update ships free to owners — your locker always serves the latest version.
QUESTIONS
Is this just 'generate 50 AI blog posts'?›
The opposite. Every keyword must pass a live SERP check before it earns a page, guides must genuinely answer the query for someone who will never buy your product, and the skill ships fewer pages rather than padded doorway pages. Thin scaled content is exactly what Google penalizes.
Does it work for products other than iOS apps?›
Yes. The method was refined on app sites but the workflow is product-agnostic — apps, SaaS, tools, services. Store lookups are one seed source among several; the SERP gate and guide anatomy are the same everywhere.
What stack does it build with?›
Any static stack. The skill recommends a static generator (Astro is a proven fit) and gives host-agnostic deploy requirements — Netlify, Vercel, Cloudflare Pages, or your own server all work.
How fast will I rank?›
No promises — anyone who promises is selling you something else. Indexing takes days to weeks; the skill's own guidance is to check Search Console after ~2 weeks and not panic-diagnose before then. What it controls is that every page targets a query you can actually win.