Seo Growth logo

Seo Growth

OrganizationPopular
AI-Builder-Club
seo-growth

Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why an SEO effort stalled despite consistent output. NOT for writing an article, keyword expansion mechanics, or auditing a single tactic for penalty risk.

Overview

PublisherAI-Builder-Club
Repositoryskills
Skill nameseo-growth
Stars
1.3K
Forks
159
Bundled files
7
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by AI-Builder-Club on GitHub. Read the source before you install it.

Installation

Install the Seo Growth AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AI-Builder-Club/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/skills/seo-growth .claude/skills/seo-growth
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Seo Growth in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Seo Growth on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Seo Growth is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/seo-growth — first-party SEO growth method

Core principle: the right move depends on whether you have data yet, and most bad SEO advice is given to the wrong one of those two situations. A site with no rankings and a site with a breadwinner page need opposite behavior. Advice that ignores which you are in is how efforts stall despite consistent output.

Distilled from two content properties run in production and the Search Console reads that produced each rule. This is a first-party method: narrower than a general playbook, and more trustworthy for it. Every rule traces to the failure or result behind it in references/why-these-rules.md. Absolute traffic figures are withheld; the ratios and thresholds are as observed.

The two playbooks

You are here if…PlaybookRead
No rankings, no authority, <100 clicks/mo, possibly no contentA — Cold startreferences/cold-start.md
GSC has real rows: something ranks, something earns clicksB — With datareferences/with-data.md

Diagnose per cluster, not per site. A mature site opening a new territory is in Playbook A for that territory and Playbook B everywhere else — and that combination is the strongest position in the method.

Playbook A in one line: you cannot win an established term from zero authority, so hunt an emerging one, ship ONE page, and let day-7 / day-21 decide whether it was real.

Playbook B in one line: your own GSC already knows which page shapes win for you — find the breadwinner, extract the shape, diagnose whether it is position-limited or snippet-limited, compound it, and protect it while you do.

Read alongside either playbook

  • references/emerging-terms.md — the hunt. The wedge in both playbooks, and the only thing that works in Playbook A. Where to look, in what order, and the seven gates a candidate must pass.
  • references/measurement.md — which metric scores which situation, the four query families that never click, and the GSC traps that produce confident wrong conclusions.
  • references/why-these-rules.md — the failure or result behind each rule.
  • references/operationalize.md — turning either playbook into scheduled loops.

Before advising anything: get three numbers

Pull a 28-day GSC window ending 3 days back (GSC lags 2–3 days):

  1. Total clicks — the scale, and which playbook you are in.
  2. Breadwinner share — what % of clicks the single best page earns.
  3. Best non-brand position — where you rank on something you don't own by name.

If these aren't available, say so and instrument first. Advising without them is guessing, and it is the most common failure mode in this whole area.

The five laws

  1. A low-authority domain can only win a term while competition is thin. So a cold start doesn't "do SEO" — it hunts emerging terms. Validated on two separate terms, months apart.
  2. Score an emerging term on position, a mature one on clicks. Backwards, and the metric tells you to quit the land-grab exactly as the ground becomes valuable — or leaves a page at 0.53% CTR untouched for a month because its rank looked fine.
  3. Impressions are not progress. The trap is a page drawing a very large impression base relative to the rest of the site at 0.2% CTR. It feels like traction and converts nothing. Rank work by click opportunity from human queries.
  4. Concentration is the goal, not the problem. One page earning ~45% of clicks is healthy. Compound the winner before adding breadth.
  5. What you double down on is derived, not chosen. Read your own GSC for which shapes win, then repeat the shape — not just the page.

Quick reference

QuestionShort answerDetail
Cold start, what now?Instrument, then land ONE emerging term. Not a cluster.cold-start
Cluster or one page?One page until the term proves itself. Cluster after.cold-start
How do I find emerging terms?Your own saved stream → repo/release feeds → social listening → diff vs your pagesemerging-terms
Is this term worth it?Seven gates; failing one drops it, and dropping is normalemerging-terms
What do we double down on?The page at ≥30% of clicks — and the archetype it belongs towith-data
Ranks well, no clicks?Screen the query mix first. Most such pages are not broken.with-data, measurement
Traffic plateaued despite publishingThe cluster saturated. Open a new front, don't add pages to it.with-data §7
When do I stop land-grabbing?Three computable numbers, never a vibemeasurement
How do I stop doing this by hand?Four loop roles, never one loopoperationalize

Common mistakes

  • Advising before diagnosing. Get the three numbers first.
  • Treating every low-CTR page as broken. Four query families score ~zero clicks by design; one verified family ranked position 4.7–5.8 for exactly 0 clicks and was working perfectly.
  • Publishing on a cadence instead of on evidence.
  • Diversifying away from a winner because concentration feels risky.
  • Grounding research on your own pages and your own GSC. A closed loop. It produces internal reshuffles that cannot move a term you don't yet own — one property lost its head term to page 2 this way while the answer sat unread in the owner's own bookmarks.
  • Counting a ship as an outcome. A shipped page is a hypothesis until traffic verifies it.

Scope honesty

Derived from B2B content SEO on low-to-mid authority domains. The two-playbook split, the measurement discipline, and the emerging-term method transfer broadly. The specific archetypes in with-data.md do not — they are one property's, and yours must be extracted from your own data. Local, e-commerce, and YMYL were never tested here; say so rather than extrapolating.

What this skill deliberately does not cover

  • Penalty risk / what Google punishes. Read current third-party research before shipping at any scale — Lily Ray on algorithmic collapses, Kevin Indig on how AI systems select sources, Rand Fishkin and Amanda Natividad on zero-click. This skill is about where to aim, not about which tactics are dangerous, and the two are different questions.
  • Writing the page. Use whatever content skill or process you already have. The bar this method assumes: genuine first-party substance, 15+ concrete specifics, and an answer a competitor cannot regenerate from the same prompt tomorrow.
  • Keyword expansion mechanics. Once you know the territory, any keyword tool will widen it.

Companion skills in this plugin

  • new-loop — build the scheduled loop that runs either playbook on a cadence. See references/operationalize.md and assets/seo-loop-template.md.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Seo Growth AI skill do?

Use when deciding WHERE to point SEO effort, not how to write a page. Triggers: a new site or brand with no rankings and no authority ("cold start", "starting from zero", "nobody knows us"), deciding what to double down on, a page or cluster that ranks but earns nothing, hunting emerging or newly-coined keywords before competitors arrive, "should we build a cluster or one page", "what do we write next", "we get impressions but no clicks", "our traffic plateaued despite publishing", whether to chase a head term at all, or turning any of it into recurring automation. Also use when asked why a...

Why use Seo Growth on TypingMind?

Because you install it once and use it with any model. Seo Growth is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Seo Growth in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AI-Builder-Club/skills/tree/main/skills/seo-growth. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Seo Growth?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Seo Growth?

As many as you like. As long as a model supports skills, you can use Seo Growth with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Seo Growth AI skill free?

It is published on GitHub by AI-Builder-Club. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇