Skip to main content
ClaudeWave
ES, Spanish
Skill2.1k estrellas del repoactualizado 10d ago

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/cbrock84/headcount /tmp/seo-strategy && cp -r /tmp/seo-strategy/plugins/demand-generation/skills/seo-strategy ~/.claude/skills/seo-strategy
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# SEO strategy

## Diagnose in this order

Skipping to content when the problem is technical wastes months. Work down; stop when you find the
break.

1. **Can it be crawled?** Robots directives, noindex left on after a launch, blocked resources,
   crawl budget wasted on parameter and filter URLs.
2. **Can it be indexed?** Check what is actually in the index versus what should be. Canonicals
   pointing at the wrong page and unintended duplicates are the two usual causes.
3. **Does the page deserve to rank?** Search intent match first. A page can be technically perfect
   and still lose because it answers a different question than the query asks.
4. **Does the site have the authority to rank for it?** Some terms are out of reach for now.
   Targeting them is a decision to spend without return.

## Architecture

Structure follows how people look for things, not how the company is organized.

- Anything important reachable within three clicks of the home page.
- Group related pages so internal linking is natural, not retrofitted.
- One URL per thing. Parameters, trailing-slash variants, and case differences that all resolve are
  duplicate content in the crawler's eyes.
- URLs readable and stable. Changing them costs equity even done correctly.

Internal linking is the most underused lever available: it is fully within your control, and it
directs authority to the pages you actually care about. Link with descriptive anchor text from your
strongest pages to the ones that need help.

## Performance and mobile

Speed and mobile usability are ranking inputs and, more importantly, conversion inputs. Audit them
as part of every SEO review rather than treating them as an engineering concern.

Measure on **field data** from real users where available, not only lab tools. Lab scores on a fast
connection routinely miss what mobile users experience.

The three that matter:

- **Loading** — how long until the largest visible element renders. Usually fixed by image sizing
  and format, render-blocking resources, and slow server response.
- **Interaction responsiveness** — how long the page takes to react to a tap or click. Usually
  fixed by reducing main-thread JavaScript work.
- **Layout stability** — how much content shifts while loading. Almost always fixed by reserving
  space for images, ads, and embeds before they load.

Mobile is the version that gets indexed. Check that mobile serves the same content as desktop —
content hidden or dropped on mobile is content that does not exist for ranking — and that tap
targets, font sizes, and viewport configuration do not make the page unusable.

Prioritize performance work by pages with traffic, not by worst score. A terrible score on a page
nobody visits is not a finding.

## Structured data

Mark up what genuinely exists on the page — the entity, its attributes, the relationships. It
clarifies meaning to the crawler and can earn richer results.

Use JSON-LD in the page head rather than inline microdata — it is easier to maintain and validate,
and it does not entangle markup with content.

The types worth implementing, in rough order of return: organization and site identity, breadcrumbs,
articles, products with offers and availability, frequently asked questions, events, local business
details, and job postings. Implement the properties each type actually requires plus the recommended
ones you can populate honestly; partial markup with missing required fields is usually ignored
entirely.

Validate after every template change. Structured data breaks silently when a template is edited, and
nothing tells you.

Never mark up content that is not visible on the page, and never mark up ratings, prices, or events
that are not real. Both are policy violations with penalties attached.

## Prioritizing

Rank fixes by traffic at risk against effort. In practice the order is almost always: indexation
problems, then intent mismatch on high-value pages, then internal linking, then structured data,
then everything else.

## Never

- Chase rankings for a term the page cannot satisfy. The click arrives, bounces, and teaches the engine the page was wrong.
- Restructure a site without a redirect map. Lost link equity does not come back on its own.
- Judge a change in the first fortnight. Search feedback is slow enough that early movement is usually noise.

## Return contract

Findings by severity with the evidence for each, the sequenced fix list, expected impact and when it
should be visible, and what you are choosing not to fix.
account-based-marketingSkill

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

agent-hierarchySkill

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

ai-ml-governanceSkill

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

ai-research-analystSkill

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

ai-search-optimizationSkill

Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.

app-store-optimizationSkill

Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.

backup-and-recoverySkill

Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.

budgeting-and-forecastingSkill

Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.