AI visibility and GEO

Astro SEO: what Astro does on its own for Google and AI, and what to add

Gabriel Gervais
Gabriel Gervais

Partner · Strategy, advertising and measurement

November 18, 202614 min readLire en français →

ShareLinkedInFacebookEmail

Gabriel Gervais

Insights · AI visibility and GEO

Write to Gabriel Gervais

A question about this article or about your situation? Your message goes straight to Gabriel.

A company address, preferably.
Reply within 1 business day

An Astro site starts with a head start for SEO and for visibility in AI answers: every page reaches the crawler as complete HTML, without waiting for JavaScript to run. That matters because the crawlers behind ChatGPT and Claude did not execute JavaScript in the largest study published on the subject (Vercel and MERJ, December 2024). Astro does not do everything, though. Title tags, structured data, robots.txt, hreflang tags, 301 redirects and a good part of the sitemap are still yours to write. A fast Astro site that lacks them can rank below a slower site that is well maintained.

Key takeaways
  • Astro produces HTML on the server or when the site is built: text, links and metadata are in the response, readable by a crawler that does not execute JavaScript.
  • In December 2024, the Vercel and MERJ study saw none of the major AI crawlers execute JavaScript, except those of Google (Gemini) and Apple.
  • Google says its ranking systems use Core Web Vitals, without guaranteeing a position to a page that passes them.
  • Astro writes neither your title tags, nor your structured data, nor your hreflang tags, nor your robots.txt. The sitemap needs an integration and a declared site address.
  • On a fully static site, a redirect declared in Astro's configuration becomes an auto-refreshing page, not a true 301 redirect: it is set up with your host.
On this page
Definition

Pre-rendering

Pre-rendering means producing a page's complete HTML before a visitor or a crawler requests it, when the site is built or on the server. The page arrives ready to read: text, links and metadata are in the response. It is the opposite of client-side rendering, where the browser receives an almost empty page and fills it by running JavaScript. Google still recommends server-side rendering or pre-rendering. Astro pre-renders by default.

0crawlers from OpenAI, Anthropic, Meta, ByteDance or Perplexity that executed JavaScript in the Vercel and MERJ studyVercel and MERJ, December 2024
71%of Astro sites pass Core Web Vitals on mobile, compared with 48% of WordPress sitesHTTP Archive, September 2026

Why HTML served ahead of time matters for AI

A crawler visiting a page first receives an HTML file. On a site built as a JavaScript application, that file often holds very little: an empty frame and scripts that will fill the page in the browser. A human visitor does not notice the difference. A crawler that does not run those scripts leaves with an almost empty page.

Google does run JavaScript, but in stages. Its documentation describes three phases (crawling, rendering, indexing) and says a page can sit in the rendering queue for a few seconds or longer. Google still recommends server-side rendering or pre-rendering. It adds that not all bots can run JavaScript.

AI crawlers are the best example. In December 2024, Vercel (the company behind Next.js) and the technical SEO agency MERJ analyzed a month of crawler traffic on Vercel's network. Their conclusion: none of the major AI crawlers executed JavaScript. OpenAI's crawlers (GPTBot, OAI-SearchBot, ChatGPT-User), Anthropic's ClaudeBot, Meta-ExternalAgent, Bytespider and PerplexityBot were among them. ChatGPT downloaded JavaScript files in 11.5% of its requests and Claude in 23.84%, without ever running them. Only two crawlers rendered pages like a browser: Apple's, and Gemini, which relies on Googlebot's infrastructure.

OpenAI's and Anthropic's documentation, read on October 31, 2026, describes the role of each crawler without saying whether it executes JavaScript. The study dates from December 2024 and the crawlers may have changed since. The cautious approach stays the same: everything that matters (main text, headings, links, prices, structured data) should be in the HTML of the response. Our AI crawler log analysis recipe shows how to see which of your pages these crawlers come to read.

Watch out

Google reads JSON-LD structured data added by JavaScript, as its documentation states. An AI crawler that does not execute JavaScript will not see it. A JSON-LD block injected by Tag Manager or by a third-party script can therefore be read by Google and ignored by ChatGPT.

What Astro does for your SEO

Astro describes itself as the web framework for building content-driven websites. Its documentation sums up its approach in two principles: it favours server-side rendering, and it ships no JavaScript to the browser by default. For SEO, three things follow.

01

The content is in the response

Each page is produced when the site is built (a pre-built site) or on the server. Googlebot, GPTBot and ClaudeBot receive the same text as your visitor, without depending on a rendering step.

02

JavaScript stays in the islands

The parts that must respond (a form, a carousel, a calculator) load their own code. Their HTML is still produced on the server, except with the client:only directive, which skips that step: important content placed in such an island disappears from the HTML and becomes invisible to an AI crawler.

03

The page is lighter

Less JavaScript to download and run means faster display and faster response, especially on an average phone. That is what Core Web Vitals measure.

Astro did not invent HTML served ahead of time: a well-built WordPress site serves it too, since PHP produces the page on the server. Astro's advantage lies elsewhere. JavaScript only arrives if you ask for it, whereas it often piles up with a theme and plugins.

Core Web Vitals: what the data says

Core Web Vitals measure three aspects of real visitors' experience. Google sets a threshold for each.

MetricWhat it measuresGood result according to Google
LCP (Largest Contentful Paint)How long the largest visible element takes to display2.5 seconds or less
INP (Interaction to Next Paint)How quickly the page responds to a click or a key pressUnder 200 milliseconds
CLS (Cumulative Layout Shift)Unexpected movement of content while the page loadsUnder 0.1

Google writes that Core Web Vitals are used by its ranking systems. It also states that good results do not guarantee that your pages will appear at the top of Google Search results. Relevant content comes first. Speed separates comparable pages, and it matters to the visitor who is waiting.

HTTP Archive's technology report compares the share of sites that pass Core Web Vitals, based on real visits measured by Chrome. In September 2026, on mobile: Astro 71%, WordPress 48%, Gatsby 44%, Next.js 36% and Nuxt 29%. Hosted platforms do as well or better: Webflow and Squarespace 71%, Wix 81%. The figure comes with one caveat. It compares very different kinds of sites: a simple blog passes more easily than a store loaded with advertising scripts. A light, well-hosted WordPress site can pass too. The figure shows a trend: with Astro, the default setup points in the right direction.

The default setup is not always enough. A heavy video at the top of the page, a badly loaded font or a Tag Manager container full of tags can make an Astro site fail. Core Web Vitals are measured on the live site, with your real visitors' data in Search Console, not only in a lab test.

What you still need to add to an Astro site

A new Astro project produces fast, readable pages. It does not produce a site that is ready for Google and AI. The following pieces are built into the project, usually once and for all in a shared layout.

01

Title tags, meta descriptions and the canonical address

Astro writes none of these tags for you. They go in each page's head, usually through a layout that receives the page's title and description. That layout also writes the canonical tag, the Open Graph tags for sharing on LinkedIn and the robots tag. A forgotten page ships without a description, and Google builds one from whatever it finds.

02

JSON-LD structured data

Google recommends the JSON-LD format. On an Astro site, the block is written in the layout and ships in the page's HTML, so every crawler can read it. The data must match the visible text: Google asks for this explicitly for its AI features. Our article on title tags and structured data covers the types that are useful to a business.

03

The sitemap

The official @astrojs/sitemap integration generates it on every build, provided the site's address is declared in the configuration. It cannot guess a page's modification date (lastmod): without extra setup, the sitemap carries none. Pages to keep out of the index (thank-you pages, internal search) are excluded one by one.

04

Hreflang tags for French and English

Astro's internationalization routing creates the /en/ addresses, but it does not write hreflang tags into the pages. Google asks that each version name itself and every other version. In Canada, the fr-CA and en-CA codes are added with an x-default value for other visitors. The sitemap integration can also carry these language links. The details are in our article on hreflang for a French and English site.

05

The robots.txt file

Astro does not create it. It goes in the public/ folder or is generated by a robots.txt.ts page. That is where access for each AI crawler is decided: search crawlers (which can get you cited) and model-training crawlers. Our article on which AI crawlers to allow or block helps you decide.

06

The llms.txt file

An Astro site can generate it on every build, from the same data as the pages. It remains optional. Google writes that no AI-specific file is needed to appear in its generative answers. Our article on the llms.txt file explains why its value lies mostly in the page sorting it requires.

07

301 redirects during a migration

This is the least known trap. On a fully static site, a redirect declared in Astro's configuration ships as an HTML page that refreshes automatically (a meta refresh tag). Google treats an instant refresh of this kind as a permanent redirect, but it recommends a server-side redirect first, as the most reliable option. Redirects are therefore declared with your host (the _redirects file on Cloudflare Pages or Netlify, for example) or through an adapter that writes that file for you. Our article on website migration without losing SEO describes the URL mapping table to prepare.

08

Images

The <Image /> component from astro:assets resizes images and infers their width and height so the page does not jump while it loads. It requires an alt attribute. It leaves images stored in the public/ folder untouched: those ship as they are, without optimization. Alt text itself still has to be written for every image that carries information.

What this means for you

What Astro does for you, what you need to do

ItemWhat Astro does for youWhat you need to do
Content readable without JavaScriptIt produces each page's HTML before the visitor arrivesKeep important content out of client:only islands
Page weightIt ships no JavaScript by defaultWatch added scripts: videos, live chat, Tag Manager tags
Title tags, descriptions, canonicalNothingWrite them in a shared layout and fill them in page by page
Structured dataNothingWrite it as JSON-LD in the HTML, faithful to the visible text
SitemapThe official integration generates itDeclare the site address, exclude non-indexed pages, add modification dates
HreflangIt creates addresses per languageWrite the tags into every page, with x-default
robots.txt and llms.txtNothingCreate them, then decide on AI crawler access
301 redirectsAn auto-refreshing page on a static siteDeclare them with your host or through an adapter
ImagesIt optimizes them with <Image />Write alt text, avoid the public/ folder for large images

Astro gives you a fast, readable page. The rest of SEO is built into the project once, then checked on every release.

Checking what an AI crawler sees

Three checks take a few minutes and apply to any site, Astro or not.

  • The page source. In Chrome, Ctrl+U (Cmd+Option+U on a Mac) shows the HTML received from the server. Look for a sentence from your main text, your price and the application/ld+json block. Whatever is missing there may not exist for an AI crawler.
  • The page without JavaScript. Turn off JavaScript for the site in your browser settings, then reload the page. What you see is close to what a crawler that does not run it reads.
  • A crawler's request. In Terminal, the command curl -A "GPTBot" https://yoursite.com/your-page/ requests the page while identifying as OpenAI's crawler. A 403 code or a verification page may mean a firewall is blocking that crawler.

On an Astro site, the first test almost always passes. Failures most often come from a component added with client:only, from content loaded from an outside service after display, or from an overzealous firewall.

What we do on falia.co

Falia's site is built with Astro 7.2.4 and Claude Code (Anthropic's coding tool), and has been hosted on Cloudflare Pages since September 22, 2026. On October 31, 2026, it had 843 pages in French and English. Here is how each item in the list above is handled.

ItemOn falia.co
Head tagsA single layout writes the title tag, description, canonical, robots tag, Open Graph tags and hreflang tags (fr-CA, en-CA and x-default, which points to French) for every page.
Structured dataA JSON-LD graph ships in the HTML of every page, built from the same data as the visible text.
Sitemap@astrojs/sitemap generates it. A step added after the build writes in the date of the last substantive change and the language links, read from each built page. A page without a date gets none.
robots.txtIt is generated by a robots.txt.ts page, in named groups: search engines and AI search crawlers, then training crawlers, which we have allowed since a decision on September 21, 2026.
llms.txtIt is regenerated on every build from the pages. A check verifies its format and that every page it lists still exists.
RedirectsThe former WordPress site's addresses are declared in Cloudflare's _redirects file. Those of former articles go through a small function placed in front of the site.
ImagesThey are prepared ahead of time as WebP, with their dimensions declared. Decorative images still receive alt text after the build.
How we work

A well-made layout is easy to forget: that is the risk. On falia.co, 30 automatic checks run on every release. Several cover SEO: valid structured data, title tags and descriptions within their limits and without duplicates, internal links that lead to a real page, and a redirects file that stays under the size the host reads. A single error blocks publication. That is what lets us change the site often, with AI, without damaging what makes it readable.

What Astro will never fix

A framework handles how the page reaches the crawler. It does not decide what the page says. The target keyword, the answer given in the first paragraph, the sources cited, internal links and the company's reputation elsewhere on the web remain the core of SEO and of visibility in AI answers. A perfectly fast Astro page that does not answer the customer's question will be neither well ranked nor cited.

The same goes for visibility in ChatGPT, Claude or Perplexity. Readable HTML lets the AI read your page. It does not make the AI cite you: the structure of the answer and the trust your site inspires count for more. That is the work we describe on our GEO and AI visibility page.

Astro is also a code project. Anyone who changes the site works through the files or through an AI coding tool, which our article on what Claude Code and ChatGPT Codex change in website development describes in detail.

We build Astro sites where SEO and readability for AI are part of the layout from the start: our Astro agency in Montreal page presents how we work and the major brands that use Astro.

Already have a site and want to know what AI reads on it? Start with our AI crawler log analysis.

How would you like to send this email?

Frequently asked questions about Astro SEO

Does an Astro site rank better on Google than a WordPress site?

Not automatically. Astro produces light pages that pass Core Web Vitals more often. Google uses these metrics in its ranking. Google also states that good results do not guarantee top positions: the most relevant content comes first. A light, well-maintained WordPress site can rank just as well.

Can ChatGPT and Claude read my site if it uses a lot of JavaScript?

Perhaps not. In December 2024, the Vercel and MERJ study saw no OpenAI or Anthropic crawler execute JavaScript. Content that only appears after a script runs may be missed. An Astro site serves the text in the initial HTML, which avoids the problem.

Does Astro create the sitemap and robots.txt on its own?

The sitemap, yes, with the official @astrojs/sitemap integration and the site address declared in the configuration. The robots.txt, no: it is created in the public/ folder or generated by a page in the project.

Will I lose my rankings if I move to Astro?

Not if every address stays the same or gets a 301 redirect declared with your host. The former site's title tags, descriptions and structured data must also be carried over. Rankings may fluctuate for a few weeks while Google crawls the new site.

Do I need an llms.txt file on an Astro site?

It is not necessary. Google writes that no AI-specific file is required to appear in its generative answers. An Astro site can generate one on every release if you want it, from the same data as your pages.

Sources and references
  1. Vercel and MERJ (Giacomo Zecchini, Alice Alexandra Moore, Malte Ubl, Ryan Siddle), The rise of the AI crawler, December 17, 2024, accessed October 31, 2026.
  2. Google Search Central, Understand the JavaScript SEO basics, accessed October 31, 2026.
  3. OpenAI, Overview of OpenAI Crawlers, accessed October 31, 2026.
  4. Anthropic, Does Anthropic crawl data from the web, and how can site owners block the crawler?, accessed October 31, 2026.
  5. Google Search Central, Understanding Core Web Vitals and Google search results and Understanding page experience in Google Search results, accessed October 31, 2026.
  6. HTTP Archive, technology report (share of sites passing Core Web Vitals on mobile, September 2026), accessed November 2, 2026.
  7. Astro, Why Astro? and Template directives reference, official documentation, accessed October 31, 2026.
  8. Astro, @astrojs/sitemap, Internationalization (i18n) Routing, Routing (redirects) and Images, official documentation, accessed October 31, 2026.
  9. Google Search Central, Introduction to structured data markup in Google Search, accessed October 31, 2026.
  10. Google Search Central, Tell Google about localized versions of your page, accessed October 31, 2026.
  11. Google Search Central, Redirects and Google Search, accessed October 31, 2026.
  12. Google Search Central, AI features and your website, accessed October 31, 2026.
Gabriel Gervais
Gabriel GervaisPartner · Strategy, advertising and measurement

Gabriel almost always takes your first call and carries out your audit. He builds the strategy starting from your growth goal: where to put your budget, which market to test and how to connect each lead to a real sale in your CRM. He mainly leads engagements for three goals: Optimize the profitability of your digital campaigns, Develop a new market, and Generate demand and growth. With Geneviève, he also works on organic search (SEO), AI visibility (GEO) and conversion rate optimization (CRO). The sales a Google Ads or Meta Ads campaign brings in depend on the page that receives the click. He writes mainly about marketing strategy, paid advertising and measurement.

About Falia →

Keep reading

Tout AI visibility and GEO →
01
AI visibility and GEO·5 min read

One robots.txt signal to refuse AI training: most businesses have nothing to add

→
02
AI visibility and GEO·4 min read

ChatGPT launches its analytics tool for businesses: the November 6 rumour is confirmed

→
03
AI visibility and GEO·17 min read

How to improve your business's AI visibility: 7 steps in order

→
Other topicsStrategySEOPaid advertisingConversionAI visibilityWeb designeCommerce
← All insights