SEO Review
Audit a web application's technical SEO from the codebase, based on current best practices (2026). Focuses on what is verifiable in code — not analytics data or external crawl tools.
How to Conduct the Audit
1. Explore the Codebase
Before auditing, understand the project:
- Identify the tech stack (framework, templating engine, SSR/CSR/SSG)
- Locate HTML templates, layouts, and page components
- Find routing configuration and URL generation logic
- Check for sitemap/robots.txt generation
- Identify meta tag management (global vs per-page)
- Locate structured data (JSON-LD, microdata, RDFa)
2. Load the Checklist
Read references/checklist.md in this skill's directory for the full list of practices to check.
3. Analyze Each Category
For each category in the checklist, search the codebase for relevant patterns. Use Grep, Glob, and Read tools to find:
- Missing or duplicate
<title> and <meta name="description">
- Missing canonical URLs or self-referencing canonicals
- Heading hierarchy issues (multiple H1, skipped levels)
- Missing
alt attributes on images
- Missing Open Graph and Twitter Card meta tags
- Structured data (JSON-LD) presence and completeness
- Sitemap.xml and robots.txt generation/configuration
- URL structure (clean slugs, trailing slashes consistency)
- Hreflang tags for multilingual sites
- Rendering strategy (SSR vs CSR impact on crawlability)
- Internal linking patterns and orphan pages
- Performance indicators (lazy loading, image optimization, font loading)
- Mobile responsiveness (viewport meta, responsive design)
4. Generate the Report
Produce a structured report with these sections:
## Audit SEO Technique - [Project Name]
### Score global
X / Y pratiques conformes (Z%)
### Resume
[2-3 sentences summarizing the main findings]
### Resultats par categorie
#### [Category Name]
| # | Pratique | Statut | Commentaire |
|---|----------|--------|-------------|
| 1 | ... | OK/KO/NA | ... |
### Top priorites
[List the 5-10 most impactful improvements, ordered by effort/impact ratio]
### Recommandations detaillees
[For each KO finding, explain what to fix and how]
Status values:
- OK - Practice is followed
- KO - Practice is not followed (include recommendation)
- NA - Not applicable to this project
- PARTIAL - Partially followed (explain what's missing)
5. Prioritization
When listing recommendations, prioritize by:
- Critical - Blocks indexing or causes major ranking loss (missing titles, noindex errors, broken canonicals)
- High impact - Significant ranking factors (structured data, heading hierarchy, meta descriptions)
- Quick wins - Low effort improvements (alt texts, Open Graph tags, sitemap tweaks)
- Progressive - Long-term improvements (URL restructuring, rendering strategy)
6. Export the Review Report
Once the audit is complete, save the full analysis as a Markdown document at the root of the audited codebase:
/docs/YYMMDD_seo-audit.md
Where YYMMDD is the current date (e.g., 260206 for February 6, 2026). Create the /docs/ directory if it does not exist.
The document must include:
- The complete audit report (as generated in step 4)
- An action plan section at the end, listing all tasks derived from the findings:
- Grouped by priority (Critical, High impact, Quick wins, Progressive)
- Each task broken down into sub-tasks of 2 to 4 hours (assuming AI-assisted development)
- Time estimate for each sub-task
- Total estimated time per priority level
### Plan d'action
#### Critique
- [ ] [Tache] — ~Xh (avec IA)
- [ ] [Sous-tache 1] — ~2h
- [ ] [Sous-tache 2] — ~3h
#### Impact eleve
...
#### Quick wins
...
#### Progressif
...
**Total estime : ~Xh**
Important Notes
- This is a technical code audit, not a content or backlink audit.
- Focus on what the developer can change in the codebase.
- Adapt to the tech stack: a Kirby site has different SEO patterns than a Laravel SPA.
- For Laravel: check Blade templates, route names, and packages like
spatie/laravel-sitemap or artesaos/seotools.
- For Kirby: check meta snippets, SEO plugins, routing, and content structure.
- Be specific in recommendations: point to exact files and lines.
1---2name: seo-audit3description: Analyze a web application or codebase for technical SEO best practices. Use when the user asks to audit, check, review, or analyze the SEO, search engine optimization, technical SEO, on-page SEO, or indexability of a website, web app, or codebase. Also use when the user mentions "SEO", "referencement", "referencement naturel", "meta tags", "sitemap", "schema.org", "structured data", "donnees structurees", "canonical", "indexation", "SERP", "rich snippets", or "Core Web Vitals". Works with HTML, CSS, JavaScript, TypeScript, PHP, Blade, Kirby, and common web frameworks.4---56# SEO Review78Audit a web application's technical SEO from the codebase, based on current best practices (2026). Focuses on what is verifiable in code — not analytics data or external crawl tools.910## How to Conduct the Audit1112### 1. Explore the Codebase1314Before auditing, understand the project:1516- Identify the tech stack (framework, templating engine, SSR/CSR/SSG)17- Locate HTML templates, layouts, and page components18- Find routing configuration and URL generation logic19- Check for sitemap/robots.txt generation20- Identify meta tag management (global vs per-page)21- Locate structured data (JSON-LD, microdata, RDFa)2223### 2. Load the Checklist2425Read `references/checklist.md` in this skill's directory for the full list of practices to check.2627### 3. Analyze Each Category2829For each category in the checklist, search the codebase for relevant patterns. Use Grep, Glob, and Read tools to find:3031- Missing or duplicate `<title>` and `<meta name="description">`32- Missing canonical URLs or self-referencing canonicals33- Heading hierarchy issues (multiple H1, skipped levels)34- Missing `alt` attributes on images35- Missing Open Graph and Twitter Card meta tags36- Structured data (JSON-LD) presence and completeness37- Sitemap.xml and robots.txt generation/configuration38- URL structure (clean slugs, trailing slashes consistency)39- Hreflang tags for multilingual sites40- Rendering strategy (SSR vs CSR impact on crawlability)41- Internal linking patterns and orphan pages42- Performance indicators (lazy loading, image optimization, font loading)43- Mobile responsiveness (viewport meta, responsive design)4445### 4. Generate the Report4647Produce a structured report with these sections:4849```50## Audit SEO Technique - [Project Name]5152### Score global53X / Y pratiques conformes (Z%)5455### Resume56[2-3 sentences summarizing the main findings]5758### Resultats par categorie5960#### [Category Name]61| # | Pratique | Statut | Commentaire |62|---|----------|--------|-------------|63| 1 | ... | OK/KO/NA | ... |6465### Top priorites66[List the 5-10 most impactful improvements, ordered by effort/impact ratio]6768### Recommandations detaillees69[For each KO finding, explain what to fix and how]70```7172**Status values:**7374- **OK** - Practice is followed75- **KO** - Practice is not followed (include recommendation)76- **NA** - Not applicable to this project77- **PARTIAL** - Partially followed (explain what's missing)7879### 5. Prioritization8081When listing recommendations, prioritize by:82831. **Critical** - Blocks indexing or causes major ranking loss (missing titles, noindex errors, broken canonicals)842. **High impact** - Significant ranking factors (structured data, heading hierarchy, meta descriptions)853. **Quick wins** - Low effort improvements (alt texts, Open Graph tags, sitemap tweaks)864. **Progressive** - Long-term improvements (URL restructuring, rendering strategy)8788### 6. Export the Review Report8990Once the audit is complete, save the full analysis as a Markdown document at the root of the audited codebase:9192```93/docs/YYMMDD_seo-audit.md94```9596Where `YYMMDD` is the current date (e.g., `260206` for February 6, 2026). Create the `/docs/` directory if it does not exist.9798The document must include:991001. The complete audit report (as generated in step 4)1012. An **action plan** section at the end, listing all tasks derived from the findings:102 - Grouped by priority (Critical, High impact, Quick wins, Progressive)103 - Each task broken down into sub-tasks of **2 to 4 hours** (assuming AI-assisted development)104 - Time estimate for each sub-task105 - Total estimated time per priority level106107```108### Plan d'action109110#### Critique111- [ ] [Tache] — ~Xh (avec IA)112 - [ ] [Sous-tache 1] — ~2h113 - [ ] [Sous-tache 2] — ~3h114115#### Impact eleve116...117118#### Quick wins119...120121#### Progressif122...123124**Total estime : ~Xh**125```126127## Important Notes128129- This is a **technical code audit**, not a content or backlink audit.130- Focus on what the developer can change in the codebase.131- Adapt to the tech stack: a Kirby site has different SEO patterns than a Laravel SPA.132- For Laravel: check Blade templates, route names, and packages like `spatie/laravel-sitemap` or `artesaos/seotools`.133- For Kirby: check meta snippets, SEO plugins, routing, and content structure.134- Be specific in recommendations: point to exact files and lines.
benjaminhaeberli