What this prompt does
This prompt runs a structured technical SEO audit tailored to developer-focused websites. It works through ten areas in a deliberate order: crawlability (robots.txt, sitemap, crawl budget), Core Web Vitals (LCP, INP, CLS), structured data validation and gaps, internal linking and orphan pages, mobile usability, page speed, indexing status, HTTPS and security headers, internationalization, and a prioritized action plan with estimated traffic impact. The output is a severity-rated report you can act on rather than a generic checklist.
The variables fit the audit to your site. [site_url] and [site_type] set the target and its nature — a developer blog and portfolio audits differently from a docs site. [tech_stack] (for example Laravel with Blade and Tailwind) informs stack-specific advice on rendering and caching. [content_types] tells the audit which schema types to recommend for posts, tutorials, and tools, and [languages] triggers the hreflang and internationalization checks only when multiple languages are actually supported. The audit order reflects catching crawlability and indexing regressions before they cost rankings.
When to use it
- A developer site's traffic dropped and you suspect a crawlability, indexing, or Core Web Vitals regression.
- You want a repeatable audit order rather than an ad-hoc poke at random pages.
- Structured data on your
[content_types]needs validation and gap analysis. - Orphan pages or shallow internal linking may be hurting how your content is crawled.
- You added languages (
[languages]) and need hreflang and internationalization checks. - Preparing a prioritized action plan with severity ratings and estimated traffic impact.
Example output
Expect a structured report organized by the ten audit areas, each finding carrying a severity rating and a specific fix. Core Web Vitals issues come with concrete remediation, structured data is validated with missing schema types recommended for your [content_types], indexing problems like noindex leaks and canonical issues are flagged, and the report closes with a prioritized action plan ordered by estimated traffic impact rather than a flat list of problems.
Pro tips
- Set
[site_type]and[content_types]accurately, since the schema recommendations and crawl priorities differ sharply between a portfolio, a blog, and a docs site. - Give the real
[tech_stack]; rendering and caching fixes for a Laravel and Blade site differ from a static or SPA setup, and stack-specific advice is more actionable. - Only fill
[languages]with languages you actually serve — phantom hreflang for unsupported languages creates problems rather than solving them. - Trust the audit order for a reason: crawlability and indexing issues cost rankings fastest, so fixing them before chasing Core Web Vitals usually pays off sooner.
- Treat the severity ratings and traffic-impact estimates as a prioritization aid, then verify the highest-severity findings against your own analytics before acting.
- Re-run the audit after major content or template changes, since indexing and Core Web Vitals regressions often slip in quietly with deploys.
