agentleFS
vindreshsinghvindreshsingh/engineering-skills/skills/marketing/seo-growth/SKILL.md

seo-growth

Skill0 starsChanged 5 months agoMITView on GitHub

Improves organic search visibility — keyword research, on-page SEO, landing pages, technical basics, and content gaps. Use when you need more search traffic, better page rankings, or SEO-optimized pages for a developer product.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After launch — monthly SEO review

    line 22
  2. Distinctive:

    Check competitor pages ranking for those terms

    line 54
  3. Distinctive:

    Document in a keyword map:

    line 59
  4. Distinctive:

    No analytics or Search Console installed

    line 147

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SEO Growth

Organic search is the highest-ROI channel for developer tools — intent is built in. Someone searching "developer networking platform" is closer to signing up than someone scrolling X. This skill turns search demand into ranked pages that convert, without black-hat tricks that get you penalized.

Chains from [[growth-strategy]] (ICP, keywords, goals) and [[content-marketing]] (articles to optimize). Complements [[social-distribution]] (social drives links and brand searches).

When to Use

  • New product/site with no organic traffic
  • Rankings stuck on page 2–3 for target keywords
  • Launching a landing page or docs site
  • Auditing existing pages for SEO fixes
  • Planning a content cluster around a topic
  • After launch — monthly SEO review

Skip when traffic goal is purely viral/social and SEO is explicitly deferred (document why).

Process

1. Baseline audit

Gather current state:

  • Site URL and key pages (home, sign-up, pricing, blog)
  • Analytics — sessions, top pages, bounce rate, conversions (or "none yet")
  • Search Console — impressions, clicks, average position (or setup needed)
  • Competitors — 3–5 similar products ranking for your terms
  • Technical — HTTPS, mobile-friendly, page speed (Core Web Vitals rough check)

List quick wins vs long-term fixes.

2. Keyword research

For developer products, cluster keywords by intent:

IntentExample keywordsPage type
Informational"how to find a coding mentor", "developer networking tips"Blog / guide
Commercial"best developer networking app", "linkedin alternative for developers"Comparison / landing
Transactional"developer connection platform", "join dev community"Home / sign-up
Branded"[product name]", "[product] review"Home, about

Process:

  1. Brainstorm 20–30 seed terms from ICP ([[growth-strategy]])
  2. Check competitor pages ranking for those terms
  3. Prioritize by: search volume (rough), difficulty (low/med/high), business fit
  4. Pick 5 primary keywords and 10 long-tail for first 60 days
  5. Map one primary keyword per page — no cannibalization

Document in a keyword map:

Page URL | Primary keyword | Secondary keywords | Search intent | Status

3. On-page optimization

For each target page:

Title tag (50–60 chars): Primary keyword near front + benefit
Meta description (150–160 chars): Keyword + CTA verb
H1: One per page; matches intent, not identical to title
H2/H3: Related keywords naturally; answer sub-questions
URL: Short, readable, keyword if sensible (/developer-networking not /page?id=3)
Body: Answer the query in first 200 words; 800+ words for blog targets
Internal links: 2–3 links to related pages with descriptive anchor text
Images: Alt text describing image + keyword where natural
CTA: Above fold and end of page — sign up, try demo, join waitlist

Developer-specific:

  • Code examples and CLI commands in content (increases dwell time)
  • FAQ schema for common questions (rich snippets)
  • Fast load — devs bounce on slow pages

4. Landing page essentials

Home / sign-up page must have:

  • Clear value prop in H1 (what + for whom)
  • Social proof — user count, testimonials, logos (real or [PLACEHOLDER])
  • Feature bullets tied to benefits, not jargon
  • FAQ section — targets long-tail "is X good for Y" queries
  • Open Graph / Twitter cards — title, description, image for social shares
  • Structured data — SoftwareApplication or WebApplication JSON-LD where appropriate

5. Content cluster plan

Build topical authority with a hub + spokes:

Hub: "Developer Networking Guide" (pillar page)
  → Spoke: How to find a mentor
  → Spoke: Building your dev brand on LinkedIn vs niche platforms
  → Spoke: First 30 days as a new developer — who to connect with
  → Spoke: [Product] vs LinkedIn for developers

Each spoke links to hub and to sign-up. Hub links to all spokes. Hand spoke drafts to [[content-marketing]].

6. Technical SEO checklist

Minimum bar:

  • robots.txt allows crawling of public pages
  • XML sitemap submitted to Search Console
  • Canonical tags on duplicate/thin pages
  • No broken links (404 audit)
  • Mobile responsive
  • LCP < 2.5s on key pages (rough — fix biggest issues)
  • HTTPS everywhere
  • hreflang if multi-language

7. Measure and iterate (monthly)

MetricSourceAction if flat
ImpressionsSearch ConsoleExpand keywords, fix titles
CTRSearch ConsoleRewrite meta descriptions
Average positionSearch ConsoleImprove content depth, backlinks
Organic sessionsAnalyticsMap which pages convert
Sign-ups from organicAnalytics + UTMOptimize high-traffic low-convert pages

Feed learnings to [[growth-strategy]] weekly review.

Common Rationalizations

  • "SEO takes too long — skip it" — It compounds. Start month 1 or month 6 is lost traffic forever.
  • "Keyword stuffing helps rankings" — Google penalizes it. Write for humans.
  • "We need backlinks before content" — Good content earns links; publish first.
  • "Our SPA doesn't need SSR" — If Google can't render it, you don't rank. Fix rendering.

Red Flags

  • Multiple pages targeting the same primary keyword
  • Title tags missing or duplicate across pages
  • Thin pages (<300 words) targeting competitive terms
  • No analytics or Search Console installed
  • Blocking /blog or /docs in robots.txt
  • Fake testimonials or review schema

Verification

SEO work is done when:

  • Baseline audit documented with quick wins listed
  • Keyword map with 5 primary + 10 long-tail terms and page mapping
  • On-page checklist applied to each target page (title, meta, H1, CTA)
  • Landing page has value prop, proof, FAQ, OG tags
  • Content cluster plan (hub + 3+ spokes) handed to content-marketer
  • Technical checklist passed or gaps logged with owners
  • Monthly metrics template set up

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.