kostja94/marketing-skills

seo-audit

When the user wants to run an SEO audit, technical SEO audit, or site health check.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/kostja94/marketing-skills --skill seo-audit

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

Strategies: SEO Audit

Guides end-to-end SEO audit: technical foundation, on-page, content, and off-page. Execute in order—technical blockers prevent indexing; on-page limits rankings; content and off-page build authority. Use when auditing an existing site or planning fixes.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Audit Order

PhaseFocusSkills
1. TechnicalCrawl, index, sitemaprobots-txt, xml-sitemap, canonical-tag, indexing, site-crawlability
2. On-PageMetadata, structure, schematitle-tag, meta-description, page-metadata, schema-markup, internal-links, heading-structure
3. ContentGaps, intent, optimizationkeyword-research, content-strategy, content-optimization
4. Off-PageBacklinks, authoritylink-building, backlink-analysis

Principle: Fix foundation before optimizing pages. See seo-strategy for workflow and prioritization.

Technical Checklist

ItemCheckSkill
robots.txtSyntax; not blocking important pagesrobots-txt
SitemapSubmitted to GSC; indexable pages only; ≤50K URLs per sitemapxml-sitemap
HTTPSSitewide; valid certificatecanonical-tag
404/5xxProper status codes; fix or redirectsite-crawlability
noindexNo accidental noindex on key pagesindexing
CanonicalCorrect; no conflictscanonical-tag
Core Web VitalsLCP ≤2.5s, INP ≤200ms, CLS <0.1core-web-vitals
MobileMobile-first; content parity; no intrusive interstitialsmobile-friendly
CrawlabilityRedirect chains, broken links, orphan pagessite-crawlability

On-Page Checklist

ItemCheckSkill
TitleUnique; 50–60 chars; keyword in first 10 wordstitle-tag
Meta description150–160 chars; CTAmeta-description
HeadingsOne H1; H1→H2→H3 hierarchyheading-structure
ImagesAlt text; no decorative alt for decorative imagesimage-optimization
SchemaValid; Rich Results Testschema-markup
Internal linksFrom strong pages; descriptive anchorsinternal-links
Duplicate contentCanonical; consolidate or differentiatecanonical-tag

Content & Off-Page

PhaseFocusSkill
Content gapMissing topics vs competitorscontent-strategy, competitor-research
Intent matchContent matches search intentcontent-optimization
BacklinksToxic links; link gap vs competitorsbacklink-analysis, link-building

Frequency

CadenceUse
Full auditQuarterly
Check-insMonthly (GSC, indexing, Core Web Vitals)

Output Format

  • Phase 1–4 findings (technical → on-page → content → off-page)
  • Priority list (P0 blocker → P1 core → P2 important)
  • Skill mapping (which skill for each fix)
  • Timeline (immediate vs short-term vs ongoing)

Related Skills

  • seo-strategy: Workflow order, prioritization, when to invest in SEO
  • google-search-console: Performance, indexing, Core Web Vitals data
  • site-crawlability: Redirect chains, broken links, crawl budget
  • indexing: Indexing issues, noindex, Search Console
  • core-web-vitals: LCP, INP, CLS optimization

Correlati per attività

dallo stesso repository

Altri Skills

Tutti gli Skills
kostja94
Community

google-search-console

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (

installazioni
1
GitHub Stars
1,1K
Aggiornato
6 ott
kostja94
Community

indie-hacker-strategy

When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.

installazioni
1
GitHub Stars
1,1K
Aggiornato
6 ott
kostja94
Community

google-ads

When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube ads." For paid mix, use paid-ads-strategy.

installazioni
3
GitHub Stars
1,1K
Aggiornato
6 ott
kostja94
Community

growth-funnel

When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.

installazioni
3
GitHub Stars
1,1K
Aggiornato
6 ott