mcpField
T
technical-seo-triage

technical-seo-triage

github.com/lvtd-llcMarketing & growth161 installsUpdated 7w ago
Repository

About technical-seo-triage

A technical SEO skill for diagnosing issues across discovery, crawling, indexing, ranking, and user outcomes. It guides marketers and site teams from symptoms to evidence, prioritized fixes, and validation.

Key features

  1. 01Search-stage issue diagnosis
  2. 02Workflow for common SEO problems
  3. 03Google Search Console-led evidence
  4. 04Prioritized fixes and validation

Use cases

  1. 01Investigating organic traffic drops
  2. 02Diagnosing indexing or canonical issues
  3. 03Assessing migration or crawl risks

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/lvtd-llc/skills --skill technical-seo-triage

After installing, type/technical-seo-triagein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

guidelines.md
agents/
openai.yaml
references/core/
examples.md
knowledge.md
rules.md
workflows/
triage-seo-issue.md

Details

From the project README

Technical SEO Triage

Use this skill to diagnose technical SEO problems by moving from symptoms to search-system stages: discovery, crawling, indexing, ranking, and user outcomes.

This skill is derived from Eli Schwartz's Product-Led SEO and uses transformed guidance with durable book-topic references. Do not copy book prose into user outputs.

Quick Start

  1. Load guidelines.md to choose relevant references.
  2. Use workflows/triage-seo-issue.md for traffic drops, indexing issues, canonical issues, migration risk, or crawl problems.
  3. Prefer Google Search Console as the primary search visibility source.
  4. Segment by URL, query, device, country, brand/non-brand, and date before proposing fixes.
  5. Separate technical blockers from content, UX, and business-fit issues.

Default Output

When asked to triage an issue, return:

  1. Symptom summary - what changed and where.
  2. Likely search stage - discovery, crawl, index, rank, click, or conversion.
  3. Evidence to inspect - GSC reports, logs, crawl data, redirects, canonicals, robots, schema, templates.
  4. Priority fixes - ordered by risk and likely impact.
  5. Validation plan - how to verify recovery or improvement.
  6. Cautions - migration, redirect, duplicate, or crawl-budget risks.

Contents

NeedStart Here
Understand technical SEO systemsreferences/core/knowledge.md
Apply triage rulesreferences/core/rules.md
See diagnosis examplesreferences/core/examples.md
Triage a problemworkflows/triage-seo-issue.md
Route by taskguidelines.md

Comments

Markdown supported