Claude Skill

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 a

LLM Mart · 0 points · 16 views 0 listing impressions 0 install-command copies
Virus-scanned Reviewed automatically before listing.

Full trust report

Download cbrock84-headcount-plugins_demand-generation_skills_seo-strategy-98d1c17.zip · 3 KB
Part of cbrock84/headcount — 160 skills

Install

skills CLI npx skills add https://github.com/cbrock84/headcount/tree/main/plugins/demand-generation/skills/seo-strategy
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install cbrock84-headcount@llmmart
Git git clone https://github.com/cbrock84/headcount.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole cbrock84/headcount collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

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.

Files (headcount)
  • references
    • sources.md 2.6 KB
      # Sources — `demand-generation:seo-strategy`
      
      <!-- Generated by scripts/build-sources.py from sources/*.toml. Do not edit. -->
      
      Check these before answering on anything they cover, and cite what you used. The use note on each one is binding: most of what a professional cites is free to read and not free to reproduce.
      
      ## Google crawlers and user-triggered fetchers
      
      Google · global · CC BY — quote with attribution
      
      <https://developers.google.com/search/docs/crawling-indexing/overview-google-crawlers>
      
      Machine-readable: <https://developers.google.com/search/docs/crawling-indexing/robots/intro>
      
      **Authoritative for:** Which user agents Google operates and what each one is for, including the separate control over training and AI surfaces — the question behind every robots.txt argument about blocking AI.
      
      ## RFC 9309: Robots Exclusion Protocol
      
      IETF · global · **read and cite only — copyrighted, do not reproduce**
      
      <https://www.rfc-editor.org/rfc/rfc9309.html>
      
      **Authoritative for:** The formal parsing rules for robots.txt — precedence, wildcards, size limits, and what a crawler is obliged to do. Settles at the protocol level whether disallow prevents indexing, which it does not.
      
      ## Schema.org vocabulary
      
      Schema.org community group · global · CC BY-SA — quote with attribution; share-alike, so do not fold into this repository
      
      <https://schema.org/>
      
      Machine-readable: <https://schema.org/version/latest/schemaorg-current-https.jsonld>
      
      **Authoritative for:** The canonical property names and expected types for structured markup. Share-alike, so cite and link rather than folding definitions into your own documentation.
      
      ## Spam policies for Google web search
      
      Google · global · CC BY — quote with attribution
      
      <https://developers.google.com/search/docs/essentials/spam-policies>
      
      **Authoritative for:** Whether a tactic is sanctionable — scaled content abuse, site reputation abuse, expired-domain abuse, cloaking, doorway pages. The only authoritative answer to whether a programmatic build will be penalized.
      
      ## Structured data markup that Google Search supports
      
      Google · global · CC BY — quote with attribution
      
      <https://developers.google.com/search/docs/appearance/structured-data/search-gallery>
      
      **Authoritative for:** Which structured data types Google actually acts on, as opposed to which exist in the vocabulary. Pair it with schema.org: one defines the vocabulary, the other says what is honored.
      
      ---
      
      Sources are maintained in `sources/` upstream, not here. If one is wrong, out of date, or missing, fix it there — this file is regenerated and an edit to it is lost.
      
  • SKILL.md 5.2 KB
    ---
    name: seo-strategy
    description: 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.
    ---
    
    # 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.
    
    ## Sources
    
    `references/sources.md` in this skill lists the outside authorities that settle the questions
    here — what each one is authoritative for, and what you may do with it. Check them before
    answering on anything they cover, and cite what you used. Most are free to read and not free
    to reproduce; the use note on each is binding.
    
    ## 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.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.

Related