seo-auditlisted

# SEO + AEO Audit Produce an audit a developer can act on the same day: concrete findings, each with evidence (the actual tag, the actual HTTP response) and a fix, ranked by impact. Do **not** hand back a generic "add alt text and use keywords" listicle — those are worthless. The value is in checking *this* site and reporting what is actually broken. SEO (ranking in search results) and AEO (getting quoted by AI answer engines) share the same foundation: a crawler must be able to fetch your URL and read real content and metadata in the **raw HTML response**, without running your JavaScript. Most of the highest-impact findings come from that one fact, so establish it first. ## Step 0 — Establish what you're auditing Before checking anything, figure out three things. Guessing here wastes the whole audit. 1. **Is there a live URL?** If yes, you audit what crawlers actually receive (best signal). If not, audit the build output / source and say so — some checks (real HTTP status, redirects) can't be verified without a deployment. 2. **What renders the HTML?** Static file, server-rendered (SSR), statically generated (SSG), or client-rendered (CSR/SPA)? Look at the framework: a plain Vite/CRA React or Vue SPA is CSR by default; Next/Nuxt/Astro/SvelteKit are usually SSR/SSG; a `.html` file is static. This single fact drives the most important check below. 3. **What are the routes/pages?** Home, product/landing pages, blog posts, legal pages. You'll sample across