Agent SkillsAgent Skills
vasilyu1983

marketing-seo-technical

@vasilyu1983/marketing-seo-technical
vasilyu1983
53
12 forks
Updated 4/7/2026
View on GitHub

Technical SEO auditing for traditional search engines (Google, Bing) covering Core Web Vitals, crawlability, structured data, mobile optimization, site architecture, and actionable fix recommendations.

Installation

$npx agent-skills-cli install @vasilyu1983/marketing-seo-technical
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathframeworks/shared-skills/skills/marketing-seo-technical/SKILL.md
Branchmain
Scoped Name@vasilyu1983/marketing-seo-technical

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

npx agent-skills-cli list

Skill Instructions


name: marketing-seo-technical description: Technical SEO auditing for traditional search engines (Google, Bing) covering Core Web Vitals, crawlability, structured data, mobile optimization, site architecture, and actionable fix recommendations.

TECHNICAL SEO AUDITING — OPERATIONAL SKILL

This skill contains actionable, production-ready systems for performing comprehensive technical SEO audits and delivering prioritized optimization recommendations for traditional search engines (Google, Bing).

Use this skill when the user asks for:

  • Technical SEO audits (full or targeted)
  • Core Web Vitals optimization (LCP, INP, CLS)
  • Crawlability and indexation issues
  • Structured data/Schema.org implementation
  • Mobile-first optimization
  • Site speed and performance fixes
  • Internal linking architecture
  • Duplicate content and canonical handling
  • International SEO (hreflang)
  • Security and HTTPS configuration

Quick Reference

TaskResource/TemplateLocationWhen to Use
Auditing
Full Technical Audit10-Point Checklisttemplates/audits/full-technical-audit.mdComprehensive site-wide audit
Quick AuditAbbreviated Checklisttemplates/audits/quick-audit-checklist.mdFast issue identification
Priority MatrixImpact vs Efforttemplates/priority/impact-effort-matrix.mdPrioritize audit findings
Core Web Vitals
CWV Deep DiveCWV Guideresources/core-web-vitals-guide.mdLCP, INP, CLS optimization
CWV ReportReport Templatetemplates/cwv/core-web-vitals-report.mdDocument CWV findings
Crawlability
Indexation IssuesCrawlability Guideresources/crawlability-indexing.mdRobots.txt, sitemaps, GSC issues
Performance
Site SpeedSpeed Guideresources/site-speed-optimization.mdTTFB, render-blocking, images
Technical Setup
Mobile OptimizationMobile Guideresources/mobile-seo-guide.mdResponsive, viewport, mobile-first
Structured DataSchema Guideresources/structured-data-guide.mdJSON-LD, rich snippets
Schema ReportValidation Templatetemplates/schema/schema-validation-report.mdDocument schema findings
Security/HTTPSSecurity Guideresources/security-https-guide.mdHTTPS, HSTS, headers
Architecture
Internal LinkingLink Strategyresources/internal-linking-strategy.mdLink equity, orphan pages
Duplicate ContentCanonical Guideresources/duplicate-content-handling.mdCanonicals, pagination
International SEOHreflang Guideresources/internationalization-hreflang.mdMulti-language/region sites

10-Point Audit Framework

Every technical SEO audit follows this systematic checklist:

#AreaKey MetricsWeight
1Crawlabilityrobots.txt status, sitemap coverage, crawl budgetHigh
2Core Web VitalsLCP <2.5s, INP <200ms, CLS <0.1High
3Site SpeedTTFB <800ms, FCP <1.8s, Speed IndexHigh
4MobileMobile-friendly score, viewport, touch targetsHigh
5SecurityHTTPS, mixed content, HSTS, headersMedium
6Structured DataSchema validity, rich snippet eligibilityMedium
7On-PageMeta tags, heading hierarchy, keyword signalsMedium
8ArchitectureInternal links, URL structure, canonicalsHigh
9Duplicate ContentCanonical implementation, paginationMedium
10InternationalizationHreflang (if applicable), geo-targetingLow

Scoring: Rate each area 0-10, calculate weighted average for overall Technical Health Score.


Decision Trees

### Audit Type Selection
Full site audit needed
  └─ Use templates/audits/full-technical-audit.md
Quick issue check
  └─ Use templates/audits/quick-audit-checklist.md
CWV-only deep dive
  └─ Use templates/cwv/core-web-vitals-report.md
Schema validation only
  └─ Use templates/schema/schema-validation-report.md

### Core Web Vitals Failing
LCP >2.5s
  └─ Preload LCP element, optimize images, add CDN
  └─ See resources/core-web-vitals-guide.md
INP >200ms
  └─ Reduce JavaScript, optimize event handlers
  └─ See resources/core-web-vitals-guide.md
CLS >0.1
  └─ Add dimensions to images/ads, avoid layout shifts
  └─ See resources/core-web-vitals-guide.md

### Indexation Issues
Pages not indexed
  └─ Check robots.txt blocking
  └─ Verify sitemap inclusion
  └─ Check canonical tags
  └─ See resources/crawlability-indexing.md
Crawl budget problems
  └─ Remove low-value pages from crawl
  └─ Fix redirect chains
  └─ Optimize pagination
  └─ See resources/crawlability-indexing.md

### Mobile Issues
Mobile-unfriendly
  └─ Check viewport meta tag
  └─ Verify responsive CSS
  └─ Test touch target sizes
  └─ See resources/mobile-seo-guide.md

### Security Issues
Mixed content warnings
  └─ Update all HTTP resources to HTTPS
  └─ See resources/security-https-guide.md
SSL/TLS issues
  └─ Run SSL Labs test
  └─ See resources/security-https-guide.md

Navigation

Core Resources

Templates

Audits

Core Web Vitals

Structured Data

Prioritization


Related Skills

Marketing & SEO

Technical Implementation

Quality & Performance


Key Differentiators

Audit Output Format:

  • Critical Issues - Fix immediately (high impact)
  • Important Optimizations - Fix soon (medium impact)
  • Recommended Enhancements - Nice to have

Each finding includes:

  • What's wrong and why it matters
  • Step-by-step fix instructions
  • Expected outcome
  • Validation method

External Resources

See data/sources.json for 46 primary sources across:

  • Google Search Central, web.dev, and Chrome developer docs (CWV, Lighthouse, CrUX)
  • Bing Webmaster Guidelines and diagnostic tooling
  • Crawl/index/render fundamentals (robots, sitemaps, canonicals, JS SEO)
  • Structured data eligibility and validation tooling
  • Optional automation references (Search Console API, CrUX API, Lighthouse CI)

Getting Started

Quick audit (15 minutes):

  1. Run PageSpeed Insights on key pages
  2. Check robots.txt and sitemap.xml accessibility
  3. Validate structured data with Rich Results Test
  4. Review GSC Coverage report for indexation issues
  5. Use templates/audits/quick-audit-checklist.md

Full audit (2-4 hours):

  1. Use templates/audits/full-technical-audit.md
  2. Work through all 10 audit areas systematically
  3. Score each area 0-10
  4. Prioritize findings with templates/priority/impact-effort-matrix.md
  5. Document fixes with validation steps

Ongoing monitoring:

  1. Set up GSC alerts for indexation issues
  2. Monitor Core Web Vitals in CrUX
  3. Schedule quarterly audits
  4. Track improvements against baseline

Core: SEO Testing & Monitoring

Testing Framework

Test TypeWhenToolsGoal
Pre-launchBefore deploymentStaging crawl, Lighthouse CICatch issues before they affect live site
SEO split testsWhen optimizingEdge routing, feature flags, server-side experimentsValidate changes before full rollout
Regression testingAfter deploymentsScreaming Frog, SitebulbEnsure no new issues introduced
CWV monitoringContinuousCrUX, PageSpeed API, WebPageTestTrack performance over time

Monitoring Checklist

SignalFrequencyToolAlert Threshold
Indexation statusDailyGSC Coverage>5% drop
CWV scoresDailyCrUX/PSIAny metric fails threshold
Crawl errorsDailyGSCAny new 4xx/5xx
Sitemap healthWeeklyGSCSubmitted ≠ Indexed
Schema validityWeeklyRich Results TestAny errors
Security issuesDailyGSC Security IssuesAny alerts

Do (Testing)

  • Set up automated Lighthouse CI in your deployment pipeline
  • Use GSC API to monitor indexation programmatically
  • Test staging environments with noindex before launch
  • Track CWV in CrUX (field data) not just lab data
  • Create baseline measurements before optimization

Avoid (Testing)

  • Testing only on fast dev machines (test on throttled mobile)
  • Ignoring field data (CrUX) in favor of lab data (Lighthouse)
  • Making multiple changes simultaneously (can't isolate impact)
  • Deploying without crawling staging first

Success Criteria

A successful technical SEO audit delivers a prioritized list of issues with clear fix instructions and validation methods that measurably improve search visibility and Core Web Vitals scores.


Optional: AI / Automation

Note: Core technical SEO fundamentals above work without AI tools. This section covers optional automation capabilities.

Automated Auditing Tools

ToolAutomation LevelBest For
Screaming FrogCrawl + exportComprehensive site audits
SitebulbCrawl + prioritized insightsVisual issue prioritization
Semrush Site AuditAutomated crawls + alertsContinuous monitoring
Ahrefs Site AuditAutomated crawlsTechnical + backlink combined
ContentKingReal-time monitoringEnterprise with frequent changes
Lumar (DeepCrawl)Enterprise crawlingLarge sites, JavaScript-heavy

Log Analysis Automation

ToolUse Case
Screaming Frog Log AnalyzerGooglebot crawl patterns
OnCrawlLog + crawl correlation
JetOctopusLarge-scale log analysis
BigQuery + GSC APICustom analysis pipelines

AI-Assisted Analysis

Use CaseApproachConsideration
Issue prioritizationML models rank by impactValidate with domain knowledge
Anomaly detectionAutomated traffic/ranking dropsSet appropriate thresholds
Content gap analysisNLP-based competitor analysisCombine with manual review
Schema generationLLM-generated JSON-LDAlways validate output

Do (AI/Automation)

  • Automate crawling on a schedule (weekly minimum)
  • Use alerts for critical issues (500 errors, robots.txt changes)
  • Combine automated findings with manual analysis
  • Version control robots.txt and critical SEO files

Avoid (AI/Automation)

  • Trusting automated recommendations without validation
  • Over-relying on tools without understanding fundamentals
  • Auto-implementing schema without testing
  • Ignoring false positives (tools over-report)

Collaboration Notes

With Product

  • Site redesigns: SEO requirements in early planning, not post-launch
  • URL changes: Redirect mapping before launch
  • New features: Consider indexability and crawlability impact
  • Page deprecation: Proper 301/410 handling

With Engineering

  • Deployment pipeline: Add Lighthouse CI, crawl staging pre-launch
  • Performance budgets: Set CWV thresholds in CI
  • Server config: robots.txt, redirects, canonical implementation
  • JavaScript: SSR/SSG for critical content, hydration impact
  • CDN setup: Cache headers, edge optimization

With Design

  • Image optimization: WebP/AVIF formats, responsive images
  • Layout stability: Reserve space for dynamic elements (CLS)
  • Above-the-fold: Prioritize LCP element rendering
  • Fonts: Font loading strategy (font-display: swap)

Anti-Patterns

Anti-PatternWhy It FailsInstead
Audit without actionFindings sit in a spreadsheetAssign owners, set deadlines, track progress
Fix everything at onceCan't measure what workedBatch by priority, deploy incrementally
Ignore mobile60%+ of traffic is mobile, mobile-first indexingTest and optimize mobile-first
Over-optimize CWVDiminishing returns past "good" thresholdFocus on user experience, not perfect scores
Block crawlers "for protection"Invisible to searchAllow crawlers, rate limit if needed
Dynamic rendering as first choiceComplexity, maintenance costPrefer SSR/SSG; dynamic rendering as last resort
Trust lab data onlyDoesn't reflect real user experienceUse CrUX (field data) as source of truth
One-time auditSEO degrades over timeContinuous monitoring, quarterly deep audits