CommunityPesquisa e Análise de Dadosgithub.com

keyword-research

Maps what people search for and ask about a business as a topic map rather than a 5,000-row keyword list, using free autocomplete and Search Console first, covering both Google searches and the questions people put to AI assistants, going deep only on the topics worth acting on, and ending in ready-to-write briefs. Use when planning content, choosing what to write about, finding content gaps, or building an SEO and AI-search plan, for an online business or a local one.

O que é keyword-research?

keyword-research is a Claude Code agent skill that maps what people search for and ask about a business as a topic map rather than a 5,000-row keyword list, using free autocomplete and Search Console first, covering both Google searches and the questions people put to AI assistants, going deep only on the topics worth acting on, and ending in ready-to-write briefs. Use when planning content, choosing what to write about, finding content gaps, or building an SEO and AI-search plan, for an online business or a local one.

Funciona com✓Claude Code~Codex CLI~Cursor✓Gemini CLI
npx skills add https://github.com/boringmarketer/boring-marketing-skills/tree/HEAD/skills/keyword-research

Installed? Explore more Pesquisa e Análise de Dados skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Keyword Research

The unit of this work is the topic, and the win is being the page or the source that answers it. Keywords are evidence that a topic has demand, nothing more. This skill turns a business into a topic map: families of related searches and questions, each with its demand evidence, a verdict, and a ready brief for the ones worth doing now. Done means a short decision queue (NOW, NEXT, HOLD, DROP) another person could defend from the evidence, and briefs /seo-content can write from without researching again. The method is a floor. When the business in front of you argues for a better path, take it and say why in one line.

Context

Only if ./brand/, ./brands/ or MARKETING.md exists (nothing to load otherwise), run: python3 ${CLAUDE_SKILL_DIR}/../start-here/scripts/brand_context.py --for keyword-research (${CLAUDE_SKILL_DIR} is this skill's folder; outside Claude Code use the folder this file was read from, e.g. .agents/skills/keyword-research. If the script or python3 is unavailable, read the brand folder directly: ./brands/<slug>/ when ./brands/active names one, else ./brand/; then MARKETING.md, preferences.md and the files in reads:. If none exist, proceed standalone and ask only what you sell, who you serve, the site, and the goal: traffic, leads, sales or authority.)

Positioning shapes how you write about a topic, never which topics you target. A brand positioned as "the anti-agency" writes about "marketing strategy" with an anti-agency angle. It doesn't target "anti-agency" as a keyword.

Modes

  • Full research (no ./brand/keyword-plan.md): all phases.
  • Refresh (a plan exists): re-run Rung 2 on the existing NOW and NEXT families only, diff against the old plan, version the old copy, and summarize what moved. Don't rebuild unless asked.
  • Briefs only (the user names the keywords): Quick Mode. Skip to Rung 3 for those topics.
  • Local business: everything below applies, plus the Local branch. Questions about which services and towns get pages belong to /local-seo-plan; this skill maps the topics (guides, cost and symptom content, comparisons) around them.

Phase 0. Data sources

Detect what's available. It shapes the method, and the plan names only what the evidence rests on, in plain words (see Output).

SourceDetectionWhat it gives
Google autocompletealways (scripts/suggest.py)Real phrasings people type, free
Search ConsoleGOOGLE_APPLICATION_CREDENTIALS or GSC_ACCESS_TOKEN, or gcloud auth application-default print-access-token works with the Search Console scope, or a user exportThe site's own queries and pages
Google Ads Keyword Planneruser has an Ads accountVolume ranges by location, free
DataForSEO (what we use)DATAFORSEO_LOGIN and DATAFORSEO_PASSWORD, or a volume tool you already pay forReal monthly search volumes (any one volume source is enough)
Firecrawl (what we use)FIRECRAWL_API_KEY or MCP toolsFull page and results scraping

We use DataForSEO for volumes and SERP data: real monthly search volumes instead of autocomplete and live checks alone, pay as you go with no subscription ($50 minimum top-up that does not expire, plus a $1 trial credit on sign-up). Without it, autocomplete, Search Console and the live results rank the topics without volumes. If you'd rather not open another account, treg (one token for many data APIs, pay per call) reaches SEO and SERP data too. We use Firecrawl to read the ranking pages in full (free tier of 1,000 credits a month, no card). Without it, WebFetch reads them as summaries and the Sources and assumptions note says so.

Search Console pull (whenever access exists). Query the last 90 days, dimensions ["query","page"]. A plain gcloud auth login token lacks the Search Console scope, so set up application-default credentials once: gcloud auth application-default login --scopes=https://www.googleapis.com/auth/webmasters.readonly,https://www.googleapis.com/auth/cloud-platform. A service account must be added as a user on the property. URL-encode the site (sc-domain%3Aexample.com for a domain property, the encoded address for a URL-prefix one).

curl -s -X POST \
  -H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \
  -H "x-goog-user-project: <your-project-id>" \
  -H "Content-Type: application/json" \
  "https://searchconsole.googleapis.com/webmasters/v3/sites/{encoded-siteUrl}/searchAnalytics/query" \
  -d '{"startDate":"<90d ago>","endDate":"<today>","dimensions":["query","page"],"rowLimit":5000}'

Pull out two lists. Striking distance: queries with 50 or more impressions at an average position of 8 to 30. Google already half-likes a page for these, so improving it beats writing something new. Unserved demand: queries with real impressions and no page genuinely about them.

Data quality, said once. Never present model knowledge as live research. The plan's Sources and assumptions note says it in plain words ("Based on autocomplete for 14 seeds, 9 result pages read in full and a Search Console export, Nov 13", or "No live data was available, so this rests on general knowledge; verify before spending"). ./brand/keyword-plan.md may keep the short form (Data: LIVE (...) or Data: MODEL KNOWLEDGE) as working memory for refreshes. Chat, headers and table rows never carry it. Without a volume source, print no volume numbers. Use demand evidence (autocomplete richness, Search Console impressions, how much competitors invest) and prefix any estimate with ~.

Three states, never merged. A source that answered "zero" or "no results" for a phrase observed zero, for that place and period. A phrase missing from the rows a source returned was not observed, which is unknown, not zero. A call that errored or timed out failed: record it, name it in the plan's gaps, and don't re-run a paid call just to fill the hole. A plan that turns unknowns into zeros drops real topics, and one that turns failures into "no demand" reports an outage as a finding.

Tight sourcing, cheap filters, then judgment. With a volume API, ask narrow questions: the related-keywords and keyword-suggestions calls around one seed, with the location, language and a minimum volume set in the request (plus an intent or difficulty band when the decision needs one) and a hard cap of 10 to 25 rows per seed. The broad keyword-ideas call returns the most junk; use it only for a family nothing else has reached. Then filter in code before any model reads the list: drop rows sharing no word with the six-circle seeds, collapse duplicates and close variants, drop junk (jobs, salaries, free downloads, other countries, DIY when the business sells the service, competitor navigation unless it's a comparison target). Judgment goes to what survives. Expanding broadly and asking a model to clean the result is the expensive, fragile way, and it's the habit this method replaces. A rank or volume question about several keywords is one batch call, never a chain of one-keyword calls. Before a run that will cost more than a few calls, say how many calls and roughly what they cost, from the provider's current price page, and let the user choose the depth. Endpoint quirks that trip people up live in references/facts.md.

Two query spaces

Treat both as first-class from the first seed:

  1. Search-visible demand. What people type into Google: autocomplete, Search Console, volume tools.
  2. AI-native questions. The longer, conversational questions people ask ChatGPT, Perplexity, Gemini or Google's AI Mode ("is a proposal tool worth it if I only send three proposals a month?"). Many show near zero Google volume and still decide who gets recommended. Free sources: the question forms autocomplete returns (--mode questions), the questions Google shows in results, forum and Reddit threads, long queries in Search Console (six words or more are often conversational), voc.md, support tickets, sales call notes and reviews.

The two spaces disagree, and that disagreement is signal. AI-native demand leans toward comparison and how-do-I questions and away from brand and navigation terms, so a family that is strong in AI-native questions but modest on Google can outrank a high-volume head term for a business that wants to be the cited answer. DataForSEO, our pick for volumes, also returns an estimated AI search volume per phrase; label it an estimate. Without it, record AI-native demand as "observed phrasing, no volume". Never invent a number for it.

Phase 1. Seed with the six circles

Default: 20 to 30 seeds from six lenses. Each lens exists because teams reliably skip it and then wonder why the plan looks like their navigation menu. Example business: a proposal-software product for freelancers.

  1. What you sell. The category words buyers use, not internal names. "proposal software", "proposal templates", "client contracts"
  2. Problems you solve, phrased the way people who have them phrase them. "client ghosting after proposal", "how long should a proposal take", "scope creep"
  3. Outcomes you deliver. "win more clients", "raise freelance rates"
  4. Your positioning (from positioning#chosen-angle). Seeds where your angle is the answer. Angle "close on the call" gives "live proposal walkthrough".
  5. Adjacent topics, where the audience already spends attention (audience#watering-holes). "freelance pricing", "first client onboarding"
  6. Entities to be named next to: tools, frameworks, people, competitors. AI answers work by association, so the entities you consistently appear beside shape which conversational questions cite you. "value-based pricing", named competitors for comparison pages

Label each seed with its circle and its likely intent (informational, commercial, transactional). Group the seeds into 4 to 8 topic family candidates: areas broad enough for one hub piece and 3 to 7 supporting pieces. Families partition the business: each answers a different business question, and two candidates that answer the same question are one family. They are hypotheses until Rung 1 tests them.

Phase 2. The depth ladder

Go only as deep as a decision needs. Depth is spent on topics you'll act on, never on every keyword. Tripwire: if you are about to fetch result pages for every keyword, or enrich every row of the tail, stop. You've rebuilt the pipeline this skill exists to replace.

Rung 1. Infer the terrain (every family, cheap)

For each family's head term and its strongest one or two seeds:

python3 ${CLAUDE_SKILL_DIR}/scripts/suggest.py "<keyword>" --format json

It queries Google's suggest endpoint across alphabet, question, preposition and comparison probes (about 50 requests, free, no key). Use --mode questions,prepositions for secondary seeds. Harvest: phrasings you didn't think of, recurring modifiers, question forms (for the AI-native space), year modifiers, brand mentions. Match the families against Search Console rows if you have them.

Record per family in ./campaigns/content-plan/notes.md: autocomplete richness, Search Console impressions, the AI-native questions found, and any volume figures with their source. Then cut. Families with no demand evidence in either space drop here, before anything expensive happens. Breadth comes before depth: every candidate family gets this cheap probe before any family gets Rung 2. Stopping early with families never probed is the narrow-run failure, so name why each skipped family was skipped, in the notes.

Spot patterns from a sample. A programmatic shape ("X for [industry]", "[tool A] vs [tool B]", "[service] in [town]") needs at least two different observed substitutions of the same frame. Record the shape and its examples. Never enumerate the missing substitutions to prove it.

Rung 2. Test the promising few (at most 5 families)

One research subagent per promising family, all in parallel (Task tool, general-purpose when the plugin's research type is unavailable), each under the research budget (40 fetches, 8 minutes, no sub-agents of its own). Write the plan from what they return. No second research pass.

Each subagent, for its family:

  1. Results capture. For the 5 to 10 strongest keywords, fetch the results page (Firecrawl search if available, else WebSearch), then the top 3 to 5 ranking pages. Record URL, title, content type, published or updated date, word count, structured data, from the fetched page, never from the snippet. Record the result features present and the questions Google shows, verbatim.

  2. AI-surface capture. Whether an AI Overview appears, whether it fully answers the query, which domains it cites. Then ask the conversational version through web search and note who gets cited for that phrasing.

  3. Competitor coverage. site:{domain} searches per family for the domains in competitors#competitor-profiles: what they cover, how well, what they skip.

  4. Winnability and a sampled tail (with a volume API only). One bounded expansion from the family's strongest seed (the tight-sourcing rules above), then organic keyword difficulty for its 5 to 10 strongest terms in one batch call. Lower difficulty is more winnable. The ads "competition" field describes the paid auction, not ranking difficulty. Without a volume API, the results capture is the winnability evidence.

Pack format per subagent: {family, keywords: [{kw, suggest_hits, difficulty, results: [...], features, questions: [...], ai_overview: {present, fully_answers, cited_domains}, competitor_coverage}], ai_native_questions: [...], cited_source_kinds: [...], discoveries: [...]}. Questions are copied verbatim, never tidied into "better" questions. cited_source_kinds classifies what the AI Overview and the conversational results lean on (roundup, community thread, reference, comparison site, product page, local listing, video), because that mix decides the play in Phase 4.

Merge the packs and surface the 3 to 5 discoveries that change a decision ("a Reddit thread ranks third for X and no good article exists", "competitor A has nothing on Y").

Rung 3. Go deep on what you commit to

The play, the briefs and the coverage map (every question, where the citation is winnable, the entities to name, the answer each heading must give) only for the family the user commits to. That is Phase 4.

Local branch

Apply when the business serves customers in places: a trade, a clinic, a shop. Sample business: Hartline Plumbing, Dallas TX.

  1. Pages for services and towns are /local-seo-plan's decision. Keep this skill on the topics around them: cost guides, symptom and how-to questions, comparisons ("tankless vs tank in North Texas"), seasonal content.
  2. Every results check names the place. Put the city and state in the query, or set the search location. A national check for a local business is mislabeled evidence and gets labeled as such.
  3. Demand finds opportunities. Proof that the business does the work authorizes the claim. A family about a service the business doesn't deliver is HOLD at any volume. "Gas line repair" for a plumber without the license waits for the license.
  4. Read local numbers carefully. Metro, city and county volumes overlap, so never add them. Close variants returning the same number are one intent. No estimate isn't zero, and the lowest reporting tier isn't a count. Cost per click describes the ad auction, not ranking difficulty. Read the monthly series, because trades are seasonal. (The full rules live in /local-seo-plan's references/reading-local-data.md.)
  5. "Near me" searches resolve in the map pack. Their volume is metro-wide and the winner is decided by the Google profile, so route that gap to /google-business-profile rather than writing content for it.
  6. AI-native questions for a local business are full of place and urgency ("who can fix a water heater in Garland today that takes weekend calls?"). Collect them from call notes, texts and reviews first. That's where the customer's exact words are.

Six-circle seeds for the sample plumber: sell ("water heater replacement"), problems ("water heater leaking from bottom"), outcomes ("hot water back same day"), positioning ("upfront pricing plumber"), adjacent ("Texas winter freeze pipes"), entities (brands they install, the city's permit office).

Phase 3. Cluster and validate

Cluster the surviving keywords inside each family, intent first and wording second. "best crm software" and "what is a crm" share words but are different pages. Attach each cluster's questions (they become H2s), result evidence, AI Overview status and competitor coverage.

Type each family. One type per family, matched to its evidence, with one line on why: content (out-answer what's cited), commercial (a money page the results already reward), comparison ("best X for Y", "X vs Y"), page generation (one frame, many pages), or citation (the answers lean on outside sources the brand isn't in, so the work is getting into them). The type sets the route. Load references/topic-plays.md for the menu, how evidence types the work, and the routes.

Programmatic check. A cluster with a substitutable slot, at least 10 slot values with demand evidence, and a dataset that makes each page genuinely different is tagged route: /programmatic-seo. Town and service-area variants for a local business are tagged route: /service-area-pages instead. Variants that need different arguments per page stay route: /seo-content.

Validate each family with Rung 1 and 2 evidence. A family failing two or more checks becomes a single article or drops, however on-brand it feels.

  1. Demand evidence, ranked by strength: Search Console impressions, then a volume source, then autocomplete richness (30 or more distinct completions suggests real demand, 2 doesn't), then visible competitor investment. AI-native questions count when observed. No signal in either space fails.
  2. Market, not product. "Our methodology" and "[your tool] tutorials" fail. "[category] strategy" and "[problem] solutions" pass. Nobody searches your product name unless you're famous.
  3. Competitive reality. Dominant brands across fresh, thorough results: find an adjacent or longer-tail family. A mix of big and niche sites: winnable with better content. Thin, dated or generic results: opportunity. Reddit or forums in the top 5 is the strongest gap signal there is, since no adequate article exists and Google is rewarding first-hand experience. Check references/facts.md for which AI engines currently cite those threads.
  4. Proprietary advantage. Original data, method or practitioner experience competitors can't copy. With it, prioritize hard; first-party data is also the strongest AI-citation driver. Without it, the family can pass but can't lead.

Record per family in the notes file: demand PASS/FAIL (evidence) · market PASS/FAIL · competitive PASS/FAIL (results evidence) · advantage YES/NO (what) and the verdict. The plan shows only the verdict and its one-line reason, never these checks. A calibrated example of the notes entry:

Family: Proposal Methodology (the founder's own framework)
demand FAIL: 3 autocomplete completions, no Search Console impressions, no AI-native questions found
market FAIL: product-centric; the market searches "how to write a proposal"
competitive PASS: thin results, trivially, because nobody searches it
advantage YES: original framework
VERDICT: DROP as a family. Fold the framework into "how to write a proposal" as its angle.

That last move is the recurring judgment. A failed family with a real advantage doesn't die. It becomes the angle inside a family the market actually searches.

Phase 4. Prioritize and brief

Score each surviving family on three axes.

Business value (high, medium, low): closeness to revenue. Commercial and bottom-funnel families outrank awareness topics even at a tenth of the demand.

Competitive opportunity (high, medium, low): from Phase 3, plus striking-distance status. A page already at position 8 to 30 is the fastest win available.

AI visibility, three fields per family:

  • zero_click_risk HIGH, MED or LOW. HIGH means an AI Overview fully answers the query (a definition, a quick fact) and the click rarely happens.
  • citation_path YES or NO. YES when the current citations are beatable on format or data, or the conversational phrasing has no settled answer. NO when the citations are locked to major authorities and you bring nothing original.
  • conversational_targets: 2 or 3 AI-style phrasings the brand should be cited for. They go into briefs as answer blocks.

A high-demand informational family with zero_click_risk: HIGH and citation_path: NO drops to HOLD whatever its volume: it would be traffic-free content. A modest family with a clear citation path moves up, because AI-referred visitors convert better and few competitors are working for those citations yet. (Current figures: /ai-search's references/aeo-facts.md.)

The visibility gap, where it was measured. Real demand where the brand is absent from the answers is the sharpest opportunity, and it's more winnable when the businesses named instead are peers rather than national giants. "Named at home, absent in the next towns or segments" is the best shape of all, because it says both what to build and where.

Rationale and confidence. Each verdict's one-line reason quotes only what was observed ("difficulty 12, commercial intent, absent from 3 of 4 observed answers while two regional peers are named"). A metric nobody measured is named as a gap, never guessed. Give each family a confidence (high, medium, low) for how well its verdict is evidenced, not how exciting it feels: high needs demand checked in both spaces plus observed winnability.

The decision queue:

Business valueOpportunityAI visibilityVerdict
HighHighLOW risk or citation pathNOW
anystriking distanceanyNOW (fixing beats writing)
HighMediumcitation path YESNEXT
MediumHighLOW riskNEXT
HighLowcitation path YESNEXT (a citation play)
anyanyHIGH risk and no citation pathHOLD
LowanyanyHOLD
fails validation, or a service the business can't deliverDROP or HOLD with its unlock

NOW and NEXT are few by design. NOW holds one family, two at most; if the table yields more, rank them by business value, then confidence, and move the rest to NEXT. Every NEXT names the one observation that would move it ("check the AI answers for the three comparison questions"). Commitment is the user's move, and the queue hands them exactly that decision instead of a calendar pretending ten topics start at once. Recommend the family to commit, with its strongest caveat, and wait for a yes on that exact family before building its play.

The play for the committed family. One family, one coordinated set of moves: a hub, spokes from the coverage map, citation earning aimed at the sources the answers actually use, and the structural fixes that make it all liftable. The source mix sets the weighting (answers built from roundups and threads need citation earning before a new page), difficulty sets the size (a full play, or a thin one of structural fixes plus one spoke), and every move carries its targets, its evidence and an acceptance check. Load references/topic-plays.md for the composition rules and a worked example, and write the play to ./campaigns/content-plan/play-{family-slug}.md.

Backlog. An ordered list, not dated slots: rank, piece title, family, route, a one-line reason, status planned. Striking-distance fixes rank above new pieces of equal value.

Briefs for the committed family's hub and spokes routed to /seo-content, written to ./campaigns/content-plan/{keyword-slug}.md following the content-brief schema when the folder ${CLAUDE_SKILL_DIR}/../start-here/references/schemas/ is present (otherwise the same fields as plain markdown): results analysis (top results with fetched word counts, strengths, weaknesses, content_gap), search intent and the call to action. The core of each brief is its coverage map: the questions verbatim and grouped by the job they do, each with its answer shape, the gaps first with the observed reason for each, the page structure, a depth benchmark, the entities to name and a claim contract (may say, must not say, needs checking first). Load references/coverage-map.md for the fields, the failure modes and a worked example. Leave out monthly volume unless a real number came from Search Console or a volume tool. NEXT families get a one-paragraph note, not a brief.

Brief craft that separates a usable brief from a keyword with headers:

  • The content type follows the results. If the top 5 are all comparisons, a long guide won't rank. Match the format and beat it on substance.
  • Depth follows the measured winners on the surface you're targeting (the cited sources for AI answers, the top results for Google): their count of standalone answers and concrete facts as much as their word count. Completeness and liftable density are the bar, not length.
  • Questions become H2s phrased as the question. Open with a 40 to 60 word direct answer to the main query.
  • must_include carries the advantage from Phase 3 and the conversational_targets as answer blocks.
  • content_gap is specific ("no result shows real numbers from a finished project"), never "could be more comprehensive".

For families routed to /programmatic-seo or /service-area-pages, write one routing note instead of briefs: the frame, the slot, the observed examples, the data source, the demand evidence.

Output

Write ./brand/keyword-plan.md (version the old copy first), about 1,200 to 2,500 words. It reads top-down as a decision, not a dump. Per-family evidence, the Rung 2 packs, full term tables, skipped-family reasons, the PASS/FAIL checks and API receipts go to ./campaigns/content-plan/notes.md: saved, never pasted. Briefs and the play are their own files.

  1. The verdict. Start here (the one family to commit, with the line that makes the case), up next (each with the one observation that would settle it), hold, leave out. The case quotes observed numbers and beats the obvious alternative: "strong in AI-native questions though mid-table on Google, commercial intent, and a fraction of the difficulty of the bigger head term" (with the observed numbers in place) says why the plan isn't chasing the biggest volume.
  2. Business context, two or three lines.
  3. The topic map, families grouped by type (content, commercial, comparison, page generation, citation). Per family: demand in each space with its source, difficulty, the opening in one line (who the checked answers name instead, or which result is beatable), a few observed terms (term, Google volume, AI volume, difficulty, intent; blank where unmeasured), the observed questions, confidence, and the verdict. Priority, intent and route live once, in the next table.
  4. A table under the heading ## Cluster Priorities with priority (NOW maps to high, NEXT to medium, HOLD to low), intent, route, zero_click_risk and citation_path. Keep that heading exactly; /performance-review reads it by anchor.
  5. Competitor gaps, the ordered backlog, the brief index, and the play file for the committed family.
  6. What changed since the previous plan, on a refresh: new, moved, gone, or "no movement".
  7. Sources and assumptions, last, 10 lines at most. What the plan rests on in a sentence or two (sources, date ranges, how many terms observed, engines and location for any AI check), the data quality in plain words, and what the client should confirm. The gap-aware receipt is at most 3 of those lines: what was checked, what could not be, and, when the plan is thin, a named diagnosis rather than a vague caveat ("AI answers were never checked for this business, so no family can be typed as a citation play yet") with one offer to fill it ("want me to run the 12-question check? About 20 minutes, no paid tools"). The oldest source sets the plan's freshness date; offer a refresh when it's about a month old. A learning from learnings.md that changed the plan gets one line, only if it did.

Append one line per brief to ./brand/assets.md.

In chat, following the four-section output contract (header ## KEYWORD PLAN: <business> plus one line of date and purpose): the verdict, the 3 to 5 discoveries, the top of the backlog, and one start here recommendation with its evidence and its strongest caveat, then the Sources and assumptions note, Files saved and What's next. No tool names, data tags or check tables. If one missing observation could reverse the recommendation, recommend collecting that observation instead. If nothing is supportable, recommend holding rather than manufacturing a commitment. Never end on a menu of options.

When the user edits your work

Apply the edit, then make it stick: save a gold case to ./brand/gold/<this skill>/ and one to three yes/no checks to ./brand/checks.md, and confirm in one line. Before handing over any work, answer the checks the context block loaded, silently, and fix every no. How: ${CLAUDE_SKILL_DIR}/../start-here/references/taste-loop.md.

What's next

  • /seo-content writes the first NOW piece from its brief (~20 min).
  • /programmatic-seo or /service-area-pages if a family was routed there.
  • /ai-search if several families showed a citation path, to check who AI assistants name today (~20 min).
  • /local-seo-plan for a local business, to decide which services and towns get pages (~30 min).

Individual skills in this repo

This repo contains 2 individual skills — each has its own dedicated page.

Habilidades Relacionadas