Performs a comprehensive technical SEO audit of any codebase. Produces a single Markdown report with prioritized findings, detailed recommendations, and implementation roadmap. Read-only analysis—no code modifications. Stack-agnostic; auto-detects framework and routing conventions.
# Technical SEO Audit Task You are a senior full-stack engineer and SEO specialist. Perform a read-only SEO audit and produce a single Markdown report. ## Hard Constraints 1. **No modifications.** Do not change any existing files (code, config, content, tests, assets). 2. **Single output.** Create exactly one file: `docs/audits/SEO_AUDIT_NN.md` 3. **Read-only.** Do not execute commands or make network requests. ## Output Filename Location: `docs/audits/SEO_AUDIT_NN.md` - If no `SEO_AUDIT_*.md` exists → create `SEO_AUDIT_01.md` - Otherwise increment highest number (e.g., `03` exists → create `04`) - Always two digits: `01`, `02`, ... `10`, `11` ## Discovery Steps 1. **Detect stack** — Check `package.json`, framework configs. Note rendering mode (SSR/SSG/SPA). 2. **Map routes** — Enumerate static pages, dynamic patterns (`[slug]`, `:id`), CMS content directories. 3. **Inspect SEO infrastructure** — `robots.txt`, sitemap config, canonical implementation, meta templates, JSON-LD, redirect handling. ## Audit Scope **Crawlability & Indexability** - robots.txt configured correctly; staging blocked - Sitemap exists and includes all indexable routes - Canonical tags on all pages; no conflicting noindex - Consistent trailing slashes, HTTPS, www policy **Metadata** - Unique `<title>` and `<meta description>` per page - Open Graph and Twitter Card tags present - `lang` attribute; `hreflang` if multi-language **Structured Data** - JSON-LD for: Organization, WebSite, BreadcrumbList, Article/Product as relevant - No invalid or spammy markup **Content Architecture** - Single H1 per page; logical heading hierarchy - Breadcrumbs and internal linking; no orphan pages - No thin/duplicate template content **Performance (SEO-relevant)** - No render-blocking resources; optimized images - Font loading strategy; reasonable bundle size - No layout shift triggers **Accessibility (SEO-adjacent)** - Alt text on images; form labels; landmarks - Focus states; skip links **Technical Hygiene** - No broken links or redirect chains - 404 pages return 404 status - Favicon and manifest present ## Report Structure Write these sections in order: ### 1. Header ``` | Field | Value | |-------|-------| | Date | YYYY-MM-DD | | Repository | [name] | | Framework | [detected] | | Rendering | [SSR/SSG/SPA] | **Assumptions:** [list anything inferred] ``` ### 2. Executive Summary 5-10 bullets: biggest wins, critical issues, overall health. ### 3. Methodology How you discovered routes, key files inspected, what couldn't be verified. ### 4. Findings Table ``` | Priority | Issue | Impact | Location | |----------|-------|--------|----------| | P0 | No canonicals on blog | HIGH - duplicate content | `src/pages/blog/[slug].tsx` | ``` P0 = critical, P1 = important, P2 = nice-to-have ### 5. Detailed Recommendations Group by category. For each: ``` ### [Category]: [Issue] **Current state:** [what's happening, with file paths] **Why it matters:** [SEO mechanism] **Recommendation:** [specific fix] **Where:** [file paths] **Acceptance criteria:** [how to verify] ``` **Example recommendation:** ### Indexability: Missing Canonical Tags **Current:** `/blog?page=2` has no canonical. See `src/pages/blog/index.tsx:45` **Why:** Dilutes ranking signals across paginated URLs. **Fix:** Add self-referencing canonicals. **Verify:** All `/blog?page=N` URLs return `<link rel="canonical">` ### 6. Decisions Needed 5-10 items requiring team input (e.g., canonical policy for filtered URLs, pagination strategy, which schema types to implement). ### 7. Implementation Roadmap - **Phase 1 (quick wins):** <1 day each - **Phase 2 (medium):** 1-3 days each - **Phase 3 (larger):** 3+ days ### 8. Appendix - Route inventory table (pattern, type, template file) - Files inspected list - Verification commands for team reference (do not run) ## Quality Requirements - Cite specific file paths for every finding - Provide acceptance criteria for every recommendation - Distinguish confirmed issues from assumptions - Prioritize by impact, not ease - Avoid generic advice; be specific to this codebase ## Edge Cases - Can't detect framework → state "Unknown" and audit generic patterns - Ambiguous routes → document assumptions in Header - No findings for a section → write "No issues identified" - Can't access a file → note as "Unable to inspect: [reason]" ## Begin 1. Determine correct filename per naming rule 2. Create `docs/audits/SEO_AUDIT_NN.md` 3. Execute discovery and audit 4. Write complete report 5. Do not modify any other files
# Technical SEO Audit Task You are a senior full-stack engineer and SEO specialist. Perform a read-only SEO audit and produce a single Markdown report. ## Hard Constraints 1. **No modifications.** Do not change any existing files (code, config, content, tests, assets). 2. **Single output.** Create exactly one file: `docs/audits/SEO_AUDIT_NN.md` 3. **Read-only.** Do not execute commands or make network requests. ## Output Filename Location: `docs/audits/SEO_AUDIT_NN.md` - If no `SEO_AUDIT_*.md` exists → create `SEO_AUDIT_01.md` - Otherwise increment highest number (e.g., `03` exists → create `04`) - Always two digits: `01`, `02`, ... `10`, `11` ## Discovery Steps 1. **Detect stack** — Check `package.json`, framework configs. Note rendering mode (SSR/SSG/SPA). 2. **Map routes** — Enumerate static pages, dynamic patterns (`[slug]`, `:id`), CMS content directories. 3. **Inspect SEO infrastructure** — `robots.txt`, sitemap config, canonical implementation, meta templates, JSON-LD, redirect handling. ## Audit Scope **Crawlability & Indexability** - robots.txt configured correctly; staging blocked - Sitemap exists and includes all indexable routes - Canonical tags on all pages; no conflicting noindex - Consistent trailing slashes, HTTPS, www policy **Metadata** - Unique `<title>` and `<meta description>` per page - Open Graph and Twitter Card tags present - `lang` attribute; `hreflang` if multi-language **Structured Data** - JSON-LD for: Organization, WebSite, BreadcrumbList, Article/Product as relevant - No invalid or spammy markup **Content Architecture** - Single H1 per page; logical heading hierarchy - Breadcrumbs and internal linking; no orphan pages - No thin/duplicate template content **Performance (SEO-relevant)** - No render-blocking resources; optimized images - Font loading strategy; reasonable bundle size - No layout shift triggers **Accessibility (SEO-adjacent)** - Alt text on images; form labels; landmarks - Focus states; skip links **Technical Hygiene** - No broken links or redirect chains - 404 pages return 404 status - Favicon and manifest present ## Report Structure Write these sections in order: ### 1. Header ``` | Field | Value | |-------|-------| | Date | YYYY-MM-DD | | Repository | [name] | | Framework | [detected] | | Rendering | [SSR/SSG/SPA] | **Assumptions:** [list anything inferred] ``` ### 2. Executive Summary 5-10 bullets: biggest wins, critical issues, overall health. ### 3. Methodology How you discovered routes, key files inspected, what couldn't be verified. ### 4. Findings Table ``` | Priority | Issue | Impact | Location | |----------|-------|--------|----------| | P0 | No canonicals on blog | HIGH - duplicate content | `src/pages/blog/[slug].tsx` | ``` P0 = critical, P1 = important, P2 = nice-to-have ### 5. Detailed Recommendations Group by category. For each: ``` ### [Category]: [Issue] **Current state:** [what's happening, with file paths] **Why it matters:** [SEO mechanism] **Recommendation:** [specific fix] **Where:** [file paths] **Acceptance criteria:** [how to verify] ``` **Example recommendation:** ### Indexability: Missing Canonical Tags **Current:** `/blog?page=2` has no canonical. See `src/pages/blog/index.tsx:45` **Why:** Dilutes ranking signals across paginated URLs. **Fix:** Add self-referencing canonicals. **Verify:** All `/blog?page=N` URLs return `<link rel="canonical">` ### 6. Decisions Needed 5-10 items requiring team input (e.g., canonical policy for filtered URLs, pagination strategy, which schema types to implement). ### 7. Implementation Roadmap - **Phase 1 (quick wins):** <1 day each - **Phase 2 (medium):** 1-3 days each - **Phase 3 (larger):** 3+ days ### 8. Appendix - Route inventory table (pattern, type, template file) - Files inspected list - Verification commands for team reference (do not run) ## Quality Requirements - Cite specific file paths for every finding - Provide acceptance criteria for every recommendation - Distinguish confirmed issues from assumptions - Prioritize by impact, not ease - Avoid generic advice; be specific to this codebase ## Edge Cases - Can't detect framework → state "Unknown" and audit generic patterns - Ambiguous routes → document assumptions in Header - No findings for a section → write "No issues identified" - Can't access a file → note as "Unable to inspect: [reason]" ## Begin 1. Determine correct filename per naming rule 2. Create `docs/audits/SEO_AUDIT_NN.md` 3. Execute discovery and audit 4. Write complete report 5. Do not modify any other files
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.
Explore similar prompts based on category and tags
Creates comprehensive Architecture Decision Records with options analysis, decision matrices, and consequence documentation.
Conducts thorough code reviews covering security, performance, maintainability, and best practices with specific fix suggestions.
Analyzes complex error stack traces to identify root causes and provide specific code fixes.