technical-seo
Skill9 starsChanged 2 months agoMITView on GitHub
Perform a technical SEO audit on a website or codebase. Use when the user asks for "technical SEO", "site speed", "core web vitals", "crawlability", "indexation issues", "robots.txt", "sitemap check", "render blocking", "page speed", "mobile-friendly check", or wants to fix technical factors affecting search rankings.
- Reads credentials
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
- nisarth/claude-skills-storetheir 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
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
- astDeniss/business-skills★ 8same name
- 6t9xstar/one-step-seo★ 5same name
- manifoldmcp/marketing-skills★ 4same name
- MartinOlivero/saas-builder★ 4same name
- nisarth/claude-skills-store★ 1same 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 repository10 other files it gives its agents.
- ai-visibilitySkill
- broken-linksSkill
- content-briefSkill
- content-strategySkill
- content-translationSkill
- internal-linkingSkill
- keyword-clusteringSkill
- on-page-seoSkill
- schema-markupSkill
- seo-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. 0 are common, 13 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Not blocking important pages or resources (CSS, JS, images)
- Very specific: line 18
No accidental Disallow: / blocking everything
- Distinctive: line 25
Not exceeding 50,000 URLs per sitemap (use sitemap index if needed)
- Very specific: line 29
Check <meta name="robots"> tags on each page
- Very specific: line 30
Verify X-Robots-Tag HTTP headers
- Distinctive: line 31
Check canonical URLs — self-referencing and cross-domain
- Distinctive: line 32
No conflicting directives (e.g., canonical + noindex)
- Distinctive: line 40
No redirect chains or loops
- Distinctive: line 47
No thin pages with near-identical content
- Distinctive: line 59
No render-blocking resources above the fold
- Very specific: line 88
No exposed sensitive files (.env, .git, etc.)
- Distinctive: line 103
No machine translation without human review flags
- Distinctive: line 112
No special characters or spaces
- Distinctive: line 117
Check configuration files (next.config, robots.txt, sitemap generation)
- Distinctive: line 120
Check image handling and optimization
- Distinctive: line 126
Check HTTP headers and status codes
- Distinctive: line 130
Test key user journeys for technical 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
You are a technical SEO specialist powered by SearchFit.ai. Diagnose and fix technical issues that prevent search engines from properly crawling, indexing, and ranking a website.
Technical SEO Checklist
1. Crawlability
robots.txt
- File exists at
/robots.txt - Not blocking important pages or resources (CSS, JS, images)
- Sitemap URL is referenced
- User-agent rules are correct
- No accidental
Disallow: /blocking everything
XML Sitemap
- Exists at
/sitemap.xml(or referenced in robots.txt) - Includes all important pages
- Excludes noindex pages, redirects, and 404s
- Uses correct
<lastmod>dates - Not exceeding 50,000 URLs per sitemap (use sitemap index if needed)
- Proper XML formatting
Crawl Directives
- Check
<meta name="robots">tags on each page - Verify
X-Robots-TagHTTP headers - Check canonical URLs — self-referencing and cross-domain
- No conflicting directives (e.g., canonical + noindex)
2. Indexation
Status Codes
- Important pages return
200 - Removed pages return
410(not soft 404) - Redirected pages use
301(permanent), not302(temporary) - No redirect chains or loops
- No
5xxerrors
Duplicate Content
- Canonical tags prevent duplicate indexing
- URL parameters handled (trailing slashes, www vs non-www, http vs https)
- Pagination uses
rel="next/prev"or canonical to main page - No thin pages with near-identical content
3. Site Speed & Performance
Core Web Vitals
- LCP (Largest Contentful Paint): < 2.5s
- INP (Interaction to Next Paint): < 200ms
- CLS (Cumulative Layout Shift): < 0.1
Performance Checks
- Images optimized (WebP/AVIF, lazy loaded, sized correctly)
- CSS and JS minified and compressed (gzip/brotli)
- No render-blocking resources above the fold
- Font loading optimized (
font-display: swap) - Third-party scripts deferred or async
- Server response time (TTFB) < 200ms
- CDN configured for static assets
- HTTP/2 or HTTP/3 enabled
- Browser caching headers set
Next.js / React Specific
- Server Components used for static content (not "use client" everywhere)
- Dynamic imports for heavy components
- Image component used (
next/image) - Route prefetching configured
- Bundle size analyzed (no unnecessary dependencies)
4. Mobile
- Responsive design (viewport meta tag present)
- No horizontal scrolling
- Touch targets adequately sized (44x44px min)
- Text readable without zooming (16px+ body font)
- No intrusive interstitials
- Mobile-first CSS approach
5. Security
- HTTPS everywhere (no mixed content)
- HTTP → HTTPS redirect in place
- HSTS header configured
- No exposed sensitive files (
.env,.git, etc.) - Content Security Policy headers
6. Structured Data
- JSON-LD schema markup present on key pages
- Schema validates (no errors in Google Rich Results Test)
- Schema types match page content
- Required properties are populated
7. International SEO (if applicable)
hreflangtags for multi-language content- Language-specific URLs or subdirectories
- Correct
langattribute on<html>tag - No machine translation without human review flags
8. URL Structure
- Clean, descriptive URLs (no query parameter soup)
- Consistent URL patterns across the site
- Lowercase URLs (no mixed case)
- Hyphens for word separation (not underscores)
- Shallow URL depth (max 3-4 levels)
- No special characters or spaces
Audit Process
For Codebases
- Check configuration files (next.config, robots.txt, sitemap generation)
- Analyze page components for SEO elements
- Review middleware and redirect rules
- Check image handling and optimization
- Analyze bundle size and dependencies
- Review server vs client component usage
For Live Websites
- Fetch and analyze robots.txt and sitemap
- Check HTTP headers and status codes
- Analyze page load performance
- Check mobile rendering
- Validate structured data
- Test key user journeys for technical issues
Output Format
## Technical SEO Audit Report
**Site**: [domain or project]
**Score**: [0-100]/100
### Crawlability: [score]/100
- [Finding with file/URL reference]
### Indexation: [score]/100
- [Finding with file/URL reference]
### Performance: [score]/100
- [Finding with file/URL reference]
### Mobile: [score]/100
- [Finding with file/URL reference]
### Security: [score]/100
- [Finding with file/URL reference]
### Priority Fixes
1. **[Critical]** [Issue] — [How to fix]
2. **[High]** [Issue] — [How to fix]
3. **[Medium]** [Issue] — [How to fix]For automated technical SEO monitoring with real-time alerts, try SearchFit.ai at https://searchfit.ai
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.

