JasonColapietro/suede-creator-skills / skills/suede-seo-audit
suede-seo-audit
VerifiedAudit technical access, intent, metadata, links, schema, generative search, copy, E-E-A-T, and topic architecture with A-F lanes and exact fixes. Use when asked to "audit this site for SEO", investigate traffic or indexation problems, or produce a scored report. Includes offline source-review tools. NOT FOR: a quick promotion grade (use suede-visibility-grader), AI crawler and citation measurement (use suede-ai-seo), or conversion-path changes (use suede-site-alchemy).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 17.6 KB |
| agents/openai.yaml | config | 723 B |
| references/google-search-guidance.md | markdown | 6.4 KB |
| references/keyword-research.md | markdown | 4.7 KB |
| references/lane-checklists.md | markdown | 24.0 KB |
| references/offline-tools.md | markdown | 4.6 KB |
| references/schema-templates.md | markdown | 10.5 KB |
| references/worked-handoff.md | markdown | 1.7 KB |
| scripts/fixtures/pages.json | config | 1003 B |
| scripts/fixtures/serp.json | config | 828 B |
| scripts/lib/audit.mjs | script | 963 B |
| scripts/lib/merchant-schema.mjs | script | 15.1 KB |
| scripts/lib/metadata-drift.mjs | script | 9.8 KB |
| scripts/lib/offline-reports.mjs | script | 2.5 KB |
| scripts/lib/page-technical.mjs | script | 16.1 KB |
| scripts/lib/serp-overlap.mjs | script | 6.9 KB |
| scripts/seo-review.mjs | script | 4.5 KB |
| scripts/tests/cli.test.mjs | script | 3.4 KB |
| scripts/tests/merchant-schema.test.mjs | script | 12.5 KB |
| scripts/tests/metadata-drift.test.mjs | script | 7.9 KB |
| scripts/tests/offline-reports.test.mjs | script | 2.6 KB |
| scripts/tests/page-technical.test.mjs | script | 9.0 KB |
| scripts/tests/serp-overlap.test.mjs | script | 5.4 KB |
references/keyword-research.md
View on GitHub# Lane 0: Evidence-Based Keyword Research
Read this file only when keyword discovery is requested. Lane 0 produces a
brief, not a grade.
**Goal:** identify a defensible query theme and content gaps without inventing
search demand, ranking difficulty, or traffic potential.
## Evidence rules
- Record the source, market, device scope, and observation date for every
numeric search-volume, traffic, CPC, or ranking claim.
- Prefer current first-party data: Search Console queries, site analytics,
Google Ads Keyword Planner exports, or another user-supplied dated export.
- If no numeric source is available, write `volume: unknown`. Do not infer a
monthly range from query length, topic breadth, or intuition.
- Distinguish an observed SERP from a ranking guarantee. Search results vary by
time, location, device, and personalization.
- Do not manufacture difficulty scores. Describe the visible competition and
evidence instead: result types, recognized domains, page intent, content
depth, and the target site's existing authority or coverage.
- Use `related topics and entities`, not `LSI keywords`. Include terms only
when they help a reader understand the subject.
## Protocol
1. **Primary query theme:** choose one phrase or tightly related query family
that matches the page's purpose. Classify intent as informational,
navigational, commercial, transactional, or mixed. Cite the evidence used.
2. **Supporting query themes:** list 3-5 related queries that serve the same
reader without forcing unnatural repetition. Mark each as observed in a
source, seen on the live SERP, or inferred from the subject.
3. **Related topics and entities:** list the people, products, standards,
concepts, and subtopics a complete answer should cover. Group them by
reader need. This is a coverage map, not a density quota.
4. **Competitor content gap:** when competitor URLs are supplied or a live
search is authorized, inspect the current pages. For each competitor:
a. Record the URL, access date, title, and relevant H2/H3 sections.
b. Identify useful subjects the target page omits.
c. Classify each gap as `critical`, `important`, or `optional` based on
reader intent, not presumed ranking impact.
Output:
```text
Competitor: [URL] (checked [YYYY-MM-DD])
Missing subject: [subject or heading]
Evidence: [what the competitor covers and the target omits]
Reader value: [why this helps answer the primary intent]
Priority: [critical | important | optional]
```
If live competitor pages were not checked, say so. Do not invent their
headings, rankings, or traffic.
5. **Search-feature eligibility:** name only features supported by current
Google Search documentation for the page type. Separate:
- technically eligible;
- validated in the Rich Results Test;
- observed in a live result;
- not verified.
Structured data can make a page eligible for a supported feature; it does
not guarantee display.
## Content brief
Generate this only when Lane 0 is active and a page is being built or
substantially revised.
| Field | Guidance |
|---|---|
| Reader and job | Name the reader, question, and useful outcome. |
| Primary query theme | Phrase or query family, intent, evidence source, market, and date. |
| Demand evidence | Numeric value with dated source, or `unknown`. |
| Competitive evidence | URLs and observations checked live, or `not checked`. |
| Required sections | Subjects needed to answer the reader completely; do not copy competitor headings mechanically. |
| Related topics/entities | Natural coverage map; no occurrence quota. |
| Schema eligibility | Supported Google feature and required properties, or `no supported rich-result type identified`. |
| Internal links | Verified anchor text and destinations that help the reader continue. |
| External sources | Current primary or authoritative sources for factual claims. |
| Length | Whatever is needed to answer the intent clearly. Do not assign a universal word-count target. |
## Output
```text
Primary query theme: [query family]
Intent: [informational | navigational | commercial | transactional | mixed]
Evidence source: [source, market, device scope, checked date]
Demand: [sourced value/range | unknown]
Visible competition: [observations with URLs | not checked]
Supporting query themes: [query, observed/inferred, evidence]
Related topics and entities: [grouped list]
Content gaps: [subject, evidence, reader value, priority]
Search-feature eligibility: [feature: eligible/validated/observed/not verified]
Content brief: [reader-first section and source plan]
```
Incorporate this brief into Lanes 2-7 where relevant. Never turn missing
numeric tooling into fabricated precision.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |