technical-seo
Skill1 starsChanged 7 months agoMITView on GitHub
Run a technical SEO audit covering site speed, crawlability, indexation, structured data, and Core Web Vitals. Use when diagnosing crawl issues, preparing for a site migration, fixing indexation problems, or optimizing page performance. Trigger with "technical SEO audit", "check crawlability", "Core Web Vitals", or "indexation issues".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- 6t9xstar/one-step-seotheir own version, first seen Nov 8, 2026
- uprinter/ai-agents-teamtheir own version, first seen Nov 8, 2026
- astDeniss/business-skillstheir own version, first seen Nov 1, 2026
- manifoldmcp/marketing-skillstheir own version, first seen Oct 17, 2026
- MartinOlivero/saas-buildertheir own version, first seen Oct 13, 2026
- teachskillofskills-ai/DigitalMarketingPro-techshutheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- indranilbanerjee/digital-marketing-pro★ 934same name
- agencia-conversion/agentic-seo-skills★ 51same name
- searchfit/searchfit-seo★ 9same name
- astDeniss/business-skills★ 8same name
- 6t9xstar/one-step-seo★ 5same name
- manifoldmcp/marketing-skills★ 4same name
- MartinOlivero/saas-builder★ 4same name
- novatic-cu/nova-skills★ 1same name
- uprinter/ai-agents-team★ 1same name
- teachskillofskills-ai/DigitalMarketingPro-techshu★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 15 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
15
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
XML sitemap validation: Check for errors, outdated URLs, missing pages, sitemap index structure.
- Distinctive: line 38
URL parameters: Check for duplicate content caused by tracking parameters or session IDs.
- Distinctive: line 43
Check what search engines are actually indexing:
- Distinctive: line 46
Noindex directives: Verify that noindex tags are only on pages that should be excluded.
- Distinctive: line 57
INP (Interaction to Next Paint): Check JavaScript execution time, long tasks, event handler efficiency.
- Distinctive: line 61
Compression: Check for gzip or Brotli compression on text resources.
- Distinctive: line 62
Caching: Verify cache headers and expiration policies for static assets.
- Distinctive: line 69
Validation errors: Run structured data through schema.org validation.
- Distinctive: line 70
Rich result eligibility: Check which pages qualify for rich results and whether markup supports them.
- Distinctive: line 72
JSON-LD best practices: Verify placement, nesting, and required properties.
- Distinctive: line 76
Check foundational technical requirements:
- Very specific: line 137
Action: Run PageSpeed analysis, identify LCP/INP/CLS offenders, trace root causes, provide specific optimization steps.
- Distinctive: line 140
Action: Verify robots.txt, check for noindex tags, validate sitemap inclusion, inspect canonical tags, check internal linking to new posts.
- Distinctive: line 144
Test representative pages from each template, not just the homepage.
- Distinctive: line 145
Always check both mobile and desktop.
- Distinctive: line 149
Check Google Search Console coverage report for Google's own view of indexation issues.
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical SEO Audit
Perform a technical SEO audit focused on site speed, crawlability, indexation, structured data validation, and Core Web Vitals. Produce prioritized findings with fix instructions.
Workflow
Step 1: Crawlability Assessment
Evaluate how effectively search engines can discover and crawl the site:
- Robots.txt analysis: Identify directives blocking important content or allowing access to low-value pages.
- XML sitemap validation: Check for errors, outdated URLs, missing pages, sitemap index structure.
- Crawl depth: Map how many clicks it takes to reach key pages from the homepage.
- Internal link structure: Find orphan pages, broken internal links, excessive link depth.
- Redirect audit: Identify redirect chains (3+ hops), redirect loops, and unnecessary redirects.
- URL parameters: Check for duplicate content caused by tracking parameters or session IDs.
- Crawl budget signals: Large sites should check for low-value pages consuming crawl budget.
Step 2: Indexation Analysis
Check what search engines are actually indexing:
- Index coverage: Compare indexed pages (via site: operator or GSC) to total pages.
- Noindex directives: Verify that noindex tags are only on pages that should be excluded.
- Canonical conflicts: Find pages where the canonical tag contradicts the expected URL.
- Duplicate content: Detect pages with substantially similar content that may compete.
- Thin content: Identify pages with insufficient content to warrant indexation.
- Soft 404s: Pages that return a 200 status but display error-like content.
Step 3: Site Speed and Core Web Vitals
Measure and diagnose performance issues:
- LCP (Largest Contentful Paint): Identify the LCP element, check image optimization, server response time, render-blocking resources.
- INP (Interaction to Next Paint): Check JavaScript execution time, long tasks, event handler efficiency.
- CLS (Cumulative Layout Shift): Find elements causing layout shifts -- images without dimensions, dynamically injected content, web fonts.
- TTFB (Time to First Byte): Server response time, CDN configuration, caching headers.
- Resource loading: Unused JavaScript, render-blocking CSS, third-party script impact.
- Compression: Check for gzip or Brotli compression on text resources.
- Caching: Verify cache headers and expiration policies for static assets.
Step 4: Structured Data Validation
Audit schema markup implementation:
- Schema types: Identify all structured data types present on the site.
- Validation errors: Run structured data through schema.org validation.
- Rich result eligibility: Check which pages qualify for rich results and whether markup supports them.
- Missing opportunities: Identify pages where structured data could be added (FAQ, HowTo, Product, Article, BreadcrumbList).
- JSON-LD best practices: Verify placement, nesting, and required properties.
Step 5: Security and Mobile
Check foundational technical requirements:
- HTTPS: Certificate validity, mixed content, HSTS headers.
- Mobile-friendliness: Viewport configuration, responsive design, tap target sizing.
- International SEO: Hreflang correctness, language targeting, regional URL structure.
- HTTP headers: Security headers (CSP, X-Frame-Options), server configuration.
Output Format
## Technical SEO Audit: <domain>
**Audit Date**: <date>
**Focus**: <full / speed / crawl / indexation / structured-data>
**Overall Technical Health**: <score>/100
### Critical Issues
| # | Issue | Impact | Pages Affected | Fix |
|---|-------|--------|---------------|-----|
| 1 | <issue> | <impact on SEO> | <count or URLs> | <specific fix steps> |
### Core Web Vitals
| Metric | Mobile | Desktop | Target | Status |
|--------|--------|---------|--------|--------|
| LCP | <time> | <time> | < 2.5s | Pass/Fail |
| INP | <time> | <time> | < 200ms | Pass/Fail |
| CLS | <score> | <score> | < 0.1 | Pass/Fail |
| TTFB | <time> | <time> | < 800ms | Pass/Fail |
### Crawlability
- Robots.txt: <status>
- Sitemap: <status>
- Redirect chains: <count found>
- Orphan pages: <count found>
- Crawl depth issues: <count pages > 3 clicks>
### Indexation
- Pages submitted: <count>
- Pages indexed: <count>
- Noindex pages: <count>
- Canonical issues: <count>
- Duplicate content: <count groups>
### Structured Data
| Type | Pages | Errors | Warnings |
|------|-------|--------|----------|
| <schema type> | <count> | <count> | <count> |
### Prioritized Fix Plan
| Priority | Issue | Effort | Impact | Owner |
|----------|-------|--------|--------|-------|
| 1 | <issue> | <hours/days> | <impact> | <dev/content/ops> |
| 2 | <issue> | <hours/days> | <impact> | <dev/content/ops> |Examples
User: "Technical SEO audit of our site before the redesign launch" Action: Full crawl audit, check redirect plan, validate structured data, baseline Core Web Vitals, produce a pre-launch checklist.
User: "Our Core Web Vitals are failing -- diagnose and fix" Action: Run PageSpeed analysis, identify LCP/INP/CLS offenders, trace root causes, provide specific optimization steps.
User: "Check why Google isn't indexing our new blog posts" Action: Verify robots.txt, check for noindex tags, validate sitemap inclusion, inspect canonical tags, check internal linking to new posts.
Best Practices
- Test representative pages from each template, not just the homepage.
- Always check both mobile and desktop. Google uses mobile-first indexing, but desktop issues matter too.
- Prioritize by impact on indexation and rankings, not by issue count.
- Provide specific fix instructions with code examples where applicable.
- Baseline current performance before making changes so improvements can be measured.
- Check Google Search Console coverage report for Google's own view of indexation issues.
- For large sites, focus crawl budget analysis on ensuring high-value pages are crawled frequently.
- Validate structured data changes in Google's Rich Results Test before deploying to production.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

