Seo strategist

Skill hamza-ali-shahjahan/hamzaish/_archive/v0/agents/launch/seo-strategist

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

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

8 stars8 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.

SKILL.md

3.2 KB, 800 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

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.

Sources

knowledge-base/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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most marketing audience skills give in 800 tokens

Counted across 690 of the 894 authors here whose files we hold, read 2026-08-07

Apply Poppins font to headingsin 41 of 690, across 6 files
Apply Lora font to body textin 41 of 690, across 6 files
Use Arial fallback for headingsin 39 of 690, across 4 files
Use Georgia fallback for body textin 39 of 690, across 4 files
Maintain text hierarchy and formattingin 39 of 690, across 4 files
Use accent colors for non-text shapesin 38 of 690, across 3 files
Use RGB values for precise color matchingin 38 of 690, across 3 files
Use brand colors for primary text and backgroundsin 36 of 690, across 1 file
Read product marketing context file before asking questions, starting, or auditingin 35 of 690, across 23 files
Use active voice instead of passive voicein 26 of 690, across 10 files
Implement or generate appropriate JSON-LD structured datain 24 of 690, across 17 files
Prioritize clarity over clevernessin 22 of 690, across 8 files

Said here and by no other author read

save strategy to seo-strategy.md
read product prd brand and metrics files
determine if seo is the right lever
define hubs and spokes for each pillar
lock down technical baseline as checklist
suggest three specific link-building moves

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.