Does every Astro site publish its version?

Only those whose layout includes the generator meta tag. The documentation's examples include it, so it is common, and removing it is a one-line change.

Why is an Astro site without islands sometimes not recognised?

Without the generator tag and without islands, the HTML contains nothing specific to Astro. Reporting it anyway would be a guess.

Is Astro good for SEO audits?

It removes one common problem: content is in the served HTML rather than rendered by script. Titles, descriptions, links and images still need checking like on any site.

Technologies

Astro

An Astro site is recognisable from a `<meta name="generator">` tag naming Astro, which Astro's tutorial and documentation examples include, and from the `astro-island` elements that wrap interactive components. The generator value names the Astro version in the form `Astro v5.x.x`, so a site that keeps the tag publishes its version. Astro renders pages to HTML and sends no JavaScript by default, which makes content-level checks straightforward and moves attention to the islands that do ship scripts.

How the engine recognises it

A generator meta tag naming Astro — weight 90.

`astro-island` elements or `data-astro-` attributes in the markup — weight 70. Islands are how Astro marks the components that hydrate in the browser.

Either signal alone is reported; together they report with high confidence.

A site that removed the generator tag and has no islands is not recognised, which is the honest outcome: nothing else in its HTML is specific to Astro.

The generator tag and the version

Astro exposes a `generator` value described as the current version of Astro, in the format `Astro v5.x.x`, intended for a `<meta name="generator">` tag.

The tag is opt-in in principle, but the tutorial and the documentation's own layout examples include it, so many sites publish it without deciding to.

The full generator string is recorded as evidence. The engine's version field is filled only when it parses a number after a space, so Astro's `v`-prefixed form is shown as observed text rather than as a parsed version.

Removing the tag from the layout is a one-line change if publishing the version is unwanted.

What mostly-static output changes

Astro's own documentation lists zero JavaScript by default as a design goal: pages are delivered as HTML, and only islands add scripts.

Content and metadata are therefore in the served HTML, and indexing does not depend on a crawler executing JavaScript.

The performance findings that remain concentrate on the islands — which components hydrate, and whether they load immediately, when idle or when visible.

Images and fonts are the usual remaining weight on a site with little script.

What recognition does and does not prove

It proves the page was produced by Astro.

It does not say whether the site is fully prerendered or partly server-rendered, which Astro supports through adapters.

It does not identify the host or the UI framework used inside islands.

It is an inventory fact; a detected Astro version is not treated as a vulnerability.

Which checks apply

`technology.inventory` lists Astro with its evidence, including the generator string.

`technology.versions` lists versions only where one is parsed from a published string, and never guesses one.

`performance.javascript` and `performance.heavy_javascript` measure the script the islands actually ship.

`performance.page_weight` and `images.inventory` cover the weight a mostly-static page still carries.

Islands and their loading directives

A component becomes an island only when it carries a `client:*` directive; without one, Astro renders it to HTML and sends none of its JavaScript.

`client:load` hydrates the component as soon as the page loads, `client:idle` when the browser becomes idle, and `client:visible` only once it enters the viewport, according to Astro's islands documentation.

The choice of directive is therefore a performance decision made component by component, and it is visible in the markup of the island wrapper.

A page whose islands all use `client:load` behaves much like a conventional script-heavy page, however static the rest of it is.

An audit measures the script that each page really downloads, which is what those choices add up to.

Frequently asked questions

Does every Astro site publish its version?: Only those whose layout includes the generator meta tag. The documentation's examples include it, so it is common, and removing it is a one-line change.
Why is an Astro site without islands sometimes not recognised?: Without the generator tag and without islands, the HTML contains nothing specific to Astro. Reporting it anyway would be a guess.
Is Astro good for SEO audits?: It removes one common problem: content is in the served HTML rather than rendered by script. Titles, descriptions, links and images still need checking like on any site.

Sources

VeriFixScan crawls a site and applies its checks to every page it reaches, keeping the evidence behind each finding. Scanning one website is free.

Scan a website