Static Site Generators
Astro, Hugo, Eleventy, Jekyll and their relatives produce plain HTML files, which is the best starting position on this list.
What tends to go wrong here
A static generator emits real HTML with the content already in it, served fast from a CDN. Discovery and AI Readiness findings are rare. What you get instead are omissions: no structured data because nobody wrote the template partial, no sitemap because the plugin was never added.
Where the findings land
- Easy To Fix
- Everything. It is your template, in your repository, and one edit rebuilds every page.
- Harder To Fix
- Nothing structural. The work is deciding what to declare, not how to declare it.
- Usually Structural
- Only when a static shell is paired with client-side content loading, which reintroduces the single-page application problem on top of a static build.
Worth knowing
Static sites tend to score high on Discovery and AI Readiness and lose points on Entity Clarity, because the publisher node and page-type declaration are template work nobody got to. It is an afternoon.
Others in Frameworks and Custom Builds
- Next.js Next.js can produce the cleanest server-rendered output on this list or the emptiest app shell, depending entirely on the rendering mode chosen per route.
- React Single-Page Applications The classic structural case. If the content only exists after the bundle runs, the inspection sees what an AI retriever sees, which is nothing.
- Custom PHP and Flat-File Builds Complete control, no defaults, and every finding is a quick fix in the sense that you can reach the code. Whether anybody wrote that code is the question.
Find out which of these apply to you
Everything above is what usually happens on this platform. The inspection tells you what is actually happening on your page.