agentsclimarketplace

Seo strategist

Skill hamza-ali-shahjahan/hamzaish/factory/agents/launch/seo-strategist

Your Claude Code setup that builds, launches, and learns — across the whole product lifecycle. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.

Install
npx -y skills add hamza-ali-shahjahan/hamzaish --skill seo-strategist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

4.2 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

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

  1. Read the product's prd.md, brand.md, and metrics.md.
  2. 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.
  3. Identify the 3–5 content pillars based on the product's value props.
  4. For each pillar, define hub + spokes.
  5. Invoke keyword-researcher if real keyword data is needed.
  6. Lock down the technical baseline as a checklist.
  7. 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.

Gives 0 of the 12 instructions most seo skills give in ~1.0k tokens

Counted across 454 of the 460 authors here whose files we hold, read 2026-08-06

  • implement structured data using JSON-LDin 30 of 454, across 26 files
  • write unique meta descriptions under 160 charactersin 27 of 454, across 20 files
  • verify one H1 exists per pagein 24 of 454, across 15 files
  • maintain a single h1 per pagein 24 of 454, across 15 files
  • use JSON-LD format for all schema markupin 23 of 454, across 15 files
  • use descriptive anchor text for internal linksin 21 of 454, across 16 files
  • add descriptive alt text to imagesin 19 of 454, across 15 files
  • read product marketing context before auditingin 19 of 454, across 10 files
  • write unique title tags under 60 charactersin 19 of 454, across 14 files
  • add unique title and meta description per pagein 19 of 454, across 17 files
  • Reference the sitemap in robots.txtin 19 of 454, across 18 files
  • verify core web vitals meet thresholdsin 17 of 454, across 9 files

Said here and by no other author read

  • identify three to five content pillars
  • lock down technical baseline as checklist
  • suggest three specific link-building moves
  • read the relevant product context files
  • state whether seo is a viable growth lever
  • define hub pages and spoke pages

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.