ワンクリックでManusで任意のスキルを実行

seo-strategist

スター5

フォーク0

更新日2026年7月2日 17:22

Build the SEO strategy — content hubs, target keywords, internal linking, schema, technical baseline — for a product that needs organic growth.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

hamza-ali-shahjahan

hamza-ali-shahjahan/hamzaish

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

SEO Strategist

When you activate

User asks: "what's the SEO play for X?", "build a content strategy", "rank for Y", "audit the SEO on Z"

What you produce

Saved to products/<name>/launch/seo-strategy.md:

## SEO Strategy — <product>

### Goal & timeline
- Target: <N organic visits/mo by month 6>
- Why this matters: <reasoning — is SEO the primary GTM lever or a supporting one?>

### Core content pillars (3–5)
| Pillar | Search intent | Target queries | Page type |
|---|---|---|---|
| <pillar> | informational | <list> | guide / blog |
| ... | commercial | ... | comparison / tool |

### Hub-and-spoke map
- **Hub** (pillar page): <topic>
  - Spoke 1: <long-tail topic>
  - Spoke 2: ...
  - Spoke 3: ...
- Internal linking: every spoke → hub; hubs cross-link by relevance

### Striking-distance keywords (from GSC if data exists)
Keywords currently ranking positions 5–15 with > 100 impressions/mo — these are the cheapest wins. Run `/keyword-research` first.

### Technical baseline (must-haves)
- [ ] Sitemap.xml auto-generated and submitted to GSC
- [ ] Robots.txt allows crawl, no accidental disallows
- [ ] JSON-LD schema on: Article, Product, FAQPage, BreadcrumbList, Organization
- [ ] Open Graph + Twitter Card meta on every page
- [ ] Canonical URLs set
- [ ] Lighthouse: SEO ≥ 95, Performance ≥ 90 (mobile)
- [ ] H1 unique per page; H2/H3 logical hierarchy
- [ ] Internal links use descriptive anchor (no "click here")
- [ ] No orphan pages (every page reachable in ≤3 clicks from homepage)

### Off-page (link building)
- 3 unlock-able link sources for indie products: directories, IndieHackers, niche newsletters
- Avoid: paid link schemes, PBNs, link exchanges

### Content cadence
- <N> posts/month — start conservative (1/wk), scale only after the first 4 published rank
- Each post: 1500–2500 words, schema'd, internally linked, has a clear CTA

### Measurement
- Weekly: GSC impressions, top 10 queries, position changes for tracked keywords
- Monthly: organic sessions (Plausible/GA4), conversion rate from organic

Protocol

Read the product's prd.md, brand.md, and metrics.md.
Decide if SEO is the right lever. SEO works for: high-intent commercial keywords, evergreen problems, content-heavy verticals. SEO is wrong for: brand-new categories no one searches for, very technical B2B niches with tiny search volume.
Identify the 3–5 content pillars based on the product's value props.
For each pillar, define hub + spokes.
Invoke keyword-researcher if real keyword data is needed.
Lock down the technical baseline as a checklist.
Suggest 3 specific link-building moves.

Contract (handoff)

Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:

Preconditions (from keyword-researcher): for the keyword-driven sections (pillars, striking-distance), a keyword brief with sourced volume/difficulty data — or explicit user-pasted data.
On precondition gap: build the strategy skeleton (pillars from value props, technical baseline, cadence) but mark keyword sections BLOCKED — needs /keyword-research; never fill them with invented volumes.
Produces: products/<name>/launch/seo-strategy.md in the format above.
Shape: guaranteed sections — Goal & timeline / Content pillars / Hub-and-spoke map / Technical baseline checklist / Off-page / Cadence / Measurement.
Postconditions: an explicit go/no-go call on SEO as a lever is stated up front — and on no-go, the strategy names the better channel instead (see first-100-customers.md channel table) rather than delivering a reluctant SEO plan.

Sources

factory/playbooks/launch-stage/seo-content-strategy.md
stack/analytics-stack.md (for the SEO data stack)

What you don't do

Don't write "we'll rank #1 for X" — you can't promise SERP positions.
Don't recommend SEO for products where it's structurally wrong (e.g., a B2B tool for 200 people in the world).
Don't put schema in scope if the dev team won't actually ship it.

このリポジトリの他の Skills

同じリポジトリ

feature-slicing

hamza-ali-shahjahan/hamzaish

Slice a goal into the smallest feature slices that can each be PROVEN — every slice ships with a named eval and an end-to-end test, and a slice you can't evaluate or test doesn't get selected. Use after the goal is set and before the spec, so only provable features make the build.

2026-07-215

go-live

hamza-ali-shahjahan/hamzaish

Guided, stateful provisioning of a product's production stack — deep-links, key-format validation, a secrets backend (fnox recommended, or user-touched .env.local), a resumable ledger, CLI automation after signup, and a blocking A1–A10 live gate. Hands off to /security-check → /ship. The walked version of SETUP.md.

2026-07-215

spec-driven-development

hamza-ali-shahjahan/hamzaish

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

2026-07-215

factory-launch

hamza-ali-shahjahan/hamzaish

Launch the factory's control plane — scaffold and fill FACTORY-ORDERS (weekly mandate + hard budget), STANDING-ORDERS (autonomous-program authority), HEARTBEAT (weekly pulse), and write lifecycle gates for every registered product. A deliberate one-time ritual (re-run to audit); invoke as /factory-launch, not auto-triggered.

2026-07-185

scaffold

hamza-ali-shahjahan/hamzaish

One-shot a new product — folders, Next.js starter, product.config.json, CLAUDE.md, scope.md, PRD skeleton, SETUP.md checklist. The Lovable-like ignition.

2026-07-145

planning-and-task-breakdown

hamza-ali-shahjahan/hamzaish

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

2026-07-025

SEO Strategist

When you activate

User asks: "what's the SEO play for X?", "build a content strategy", "rank for Y", "audit the SEO on Z"

What you produce

Saved to products/<name>/launch/seo-strategy.md:

## SEO Strategy — <product> ### Goal & timeline - Target: <N organic visits/mo by month 6> - Why this matters: <reasoning — is SEO the primary GTM lever or a supporting one?> ### Core content pillars (3–5) | Pillar | Search intent | Target queries | Page type | |---|---|---|---| | <pillar> | informational | <list> | guide / blog | | ... | commercial | ... | comparison / tool | ### Hub-and-spoke map - **Hub** (pillar page): <topic> - Spoke 1: <long-tail topic> - Spoke 2: ... - Spoke 3: ... - Internal linking: every spoke → hub; hubs cross-link by relevance ### Striking-distance keywords (from GSC if data exists) Keywords currently ranking positions 5–15 with > 100 impressions/mo — these are the cheapest wins. Run `/keyword-research` first. ### Technical baseline (must-haves) - [ ] Sitemap.xml auto-generated and submitted to GSC - [ ] Robots.txt allows crawl, no accidental disallows - [ ] JSON-LD schema on: Article, Product, FAQPage, BreadcrumbList, Organization - [ ] Open Graph + Twitter Card meta on every page - [ ] Canonical URLs set - [ ] Lighthouse: SEO ≥ 95, Performance ≥ 90 (mobile) - [ ] H1 unique per page; H2/H3 logical hierarchy - [ ] Internal links use descriptive anchor (no "click here") - [ ] No orphan pages (every page reachable in ≤3 clicks from homepage) ### Off-page (link building) - 3 unlock-able link sources for indie products: directories, IndieHackers, niche newsletters - Avoid: paid link schemes, PBNs, link exchanges ### Content cadence - <N> posts/month — start conservative (1/wk), scale only after the first 4 published rank - Each post: 1500–2500 words, schema'd, internally linked, has a clear CTA ### Measurement - Weekly: GSC impressions, top 10 queries, position changes for tracked keywords - Monthly: organic sessions (Plausible/GA4), conversion rate from organic

Protocol

Read the product's prd.md, brand.md, and metrics.md.

Decide if SEO is the right lever. SEO works for: high-intent commercial keywords, evergreen problems, content-heavy verticals. SEO is wrong for: brand-new categories no one searches for, very technical B2B niches with tiny search volume.

Identify the 3–5 content pillars based on the product's value props.

For each pillar, define hub + spokes.

Invoke keyword-researcher if real keyword data is needed.

Lock down the technical baseline as a checklist.

Suggest 3 specific link-building moves.

Contract (handoff)

Per factory/playbooks/mvp-stage/agent-handoff-contracts.md:

Preconditions (from keyword-researcher): for the keyword-driven sections (pillars, striking-distance), a keyword brief with sourced volume/difficulty data — or explicit user-pasted data.

On precondition gap: build the strategy skeleton (pillars from value props, technical baseline, cadence) but mark keyword sections BLOCKED — needs /keyword-research; never fill them with invented volumes.

Produces: products/<name>/launch/seo-strategy.md in the format above.

Shape: guaranteed sections — Goal & timeline / Content pillars / Hub-and-spoke map / Technical baseline checklist / Off-page / Cadence / Measurement.

Postconditions: an explicit go/no-go call on SEO as a lever is stated up front — and on no-go, the strategy names the better channel instead (see first-100-customers.md channel table) rather than delivering a reluctant SEO plan.

Sources

factory/playbooks/launch-stage/seo-content-strategy.md

stack/analytics-stack.md (for the SEO data stack)

What you don't do

Don't write "we'll rank #1 for X" — you can't promise SERP positions.

Don't recommend SEO for products where it's structurally wrong (e.g., a B2B tool for 200 people in the world).

Don't put schema in scope if the dev team won't actually ship it.

name	seo-strategist
description	Build the SEO strategy — content hubs, target keywords, internal linking, schema, technical baseline — for a product that needs organic growth.
model_tier	sonnet