Web design

Astro website: the architecture of falia.co, a case study of a bilingual site updated with AI

Gabriel Gervais
Gabriel Gervais

Partner · Strategy, advertising and measurement

November 20, 202614 min readLire en français →

ShareLinkedInFacebookEmail

Gabriel Gervais

Insights · Web design

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 website is a site built with Astro, an open-source framework that prepares each page in advance and sends it to the browser as ready-to-read HTML. Falia.co is a real example: on October 31, 2026, it had 843 pages in French and English, built with Astro 7.2.4, hosted on Cloudflare Pages and updated with Claude Code (Anthropic's coding tool). This article opens up its architecture layer by layer: the content, the two languages, the templates, what runs on demand, the redirects and what the site produces for search engines and AI. For each choice, we explain what it makes possible for a business.

Key takeaways
  • An Astro website serves pages that are already built. The server only works for the few features that need it, such as sending a form.
  • Articles live in validated content collections: a missing field stops the build before it reaches your visitors.
  • French and English come from a single table of page pairs. On October 31, 2026, 842 of falia.co's 843 pages carried their link to the other language.
  • A price, a service name or an address is changed in one place and carries over to every page that shows it.
  • Falia.co sends no JavaScript framework to the browser: no React, no Vue, no Svelte. The code it needs is limited to small scripts.
On this page
Definition

Astro architecture

Astro architecture is the way a site built with Astro is organized: content stored in files or collections, templates and components that lay it out, then a build step that produces HTML pages ready to serve. JavaScript is only sent to the browser for the parts that must react, called islands. Features that need a server (a form, a search) go through small functions at the host rather than through an application that runs all the time.

843pages built in French and English from 179 page filesFalia, October 31, 2026
2dependencies to run the site: Astro and its sitemap moduleFalia, October 31, 2026
1,125changes recorded in the site's history since August 20, 2026Falia, October 31, 2026

Why an Astro website for falia.co

Our former site ran on WordPress. We still build WordPress sites for our clients, and it is often the right choice for a team that wants a dashboard. For our own site, three needs led us elsewhere. The story of the move itself is in our article on migrating a website to Astro; here, we open up the result.

  • A lot of content, in two languages. On October 31, 2026, the site had 240 articles in each language (12 of them scheduled for the following weeks) and 105 glossary entries in each language. Astro describes itself as a framework designed for content-driven websites.
  • A site that AI updates. An Astro website is made of text files kept in a versioned repository. Claude Code reads them, edits them and runs the planned checks. Our pillar article on what AI changes in website development describes this way of working.
  • Fast pages without after-the-fact tuning. According to HTTP Archive's technology report, 71% of Astro sites passed Core Web Vitals on mobile in September 2026, compared with 48% of WordPress sites and 36% of Next.js sites. Wix did even better (81%), but its code cannot be hosted elsewhere.

Choosing a framework also commits the site's future. Cloudflare welcomed the Astro team on January 16, 2026. Its announcement stated that Astro would remain open source, MIT-licensed, open to contributions and deployable to any platform. The site therefore remains a set of standard files that any developer or coding agent can take over. Our Astro agency page presents the major brands that use it.

The architecture map of our Astro website

Here are the site's layers, from the one closest to the writer to the one closest to the visitor. Each row says what the layer does for us and what it makes possible for a business.

LayerOn falia.co, October 31, 2026What it makes possible
ContentTwo content collections, one per language, of 240 articles each, validated by a schemaAn incomplete article cannot be published by mistake
DataPrices, offers, goals and language pairs live in data filesA change made once applies everywhere
Templates2 page layouts and 52 components, nearly all bilingualA new page carries the brand from day one
Pages179 page files produce 843 built pagesA single route produces every page of the same type
BuildAstro builds the site, then 30 automatic checks verify itAn error blocks publication instead of reaching your customers
HostingCloudflare Pages serves the files. Seven small functions and a middleware run on demandNo database or application server exposed to visitors
Search engines and AISitemap, language tags, structured data and an index for AI, all generated on every buildWhat search engines read never falls behind the pages

Content: collections validated before going live

In an Astro website, content of the same shape is stored in content collections. For us, each article is a file that holds its title, date, author, category, meta description, text, FAQ and redirects. Astro's documentation explains that a collection's schema enforces the same structure on every entry. If a file does not match the schema, Astro reports it with an error. In practice, an article without a meta description or with a badly written date does not get through the build.

We added a rule to this mechanism: an article dated after today (Montreal time) does not exist for any page of the site. It stays in the repository and passes the writing checks, but it does not appear on the blog, in search or in the sitemap. Every morning around 6 a.m., an automated task checks whether an article has reached its date. If so, it triggers a new build and the article appears without anyone stepping in. On other days, it does nothing.

For a business, a month of articles can be prepared and reviewed in one go, then published at the chosen pace. French and English carry the same date and therefore go live on the same day.

Astro also offers collections that are read on every visit. Its documentation warns that they can cost performance. Our content changes a few times a day: we kept the collections that are read at build time.

Two languages, one table of pairs

Astro handles routing by language in its configuration. We chose French as the default language, without a prefix: Astro's documentation states that with this setting, URLs in the default language have no language prefix, while the others do. French pages are therefore at the root of the site and English pages under /en/.

English addresses do not translate French addresses word for word. Each carries the English keyword chosen for its page: /creation-de-site-web/ is paired with /en/web-design/. The site therefore has to be told which page matches which. For us, this mapping lives in a single table of pairs. The FR and EN links in the header, the footer and the language tags all come from it.

This single table solves a problem that Google describes in its documentation: if page X links to page Y as its version in another language, page Y must link back to page X. If the two pages do not point to each other, Google ignores the tags. With a single table, both directions come from the same row and cannot contradict each other. On October 31, 2026, 842 of the 843 built pages carried their fr-CA and en-CA tags, plus a default value (x-default) for visitors in another language.

The same mechanism keeps visitors on the right page when they switch languages, instead of sending them back to the home page. Our article on the language switcher explains why this detail matters in Quebec.

Templates and data: everything in one place

The site rests on 2 page layouts and 52 components. A component is a reusable piece of a page: the header, the footer, a form, the client case section, the author card of an article. Most receive the language as a parameter: a single file serves both versions.

Data follows the same logic. Prices live in a single data file, from which they feed the service pages, the pricing page, the structured data and the catalogue of offers. The day a price changes, the change is made in one place and every page that shows it follows at the next build. A check then confirms that every displayed price really comes from that file.

When an instruction asks to change a service name, Claude Code finds the single source instead of looking for the name across forty pages. Our article on how to edit your website with AI shows what such an instruction looks like day to day.

What the browser receives from an Astro website

Astro's documentation explains that the framework automatically strips client-side JavaScript out of every component unless you ask for it. To make a part interactive, you turn it into an island with a directive: client:visible loads the code when the part enters the screen, client:idle when the browser is idle. Server islands (server:defer) render personalized content separately without delaying the rest of the page.

Falia.co takes this principle far. The site depends on no JavaScript framework: neither React, Vue nor Svelte is installed. Its only two dependencies to run are Astro and its sitemap module. The menu, search, consent banner and forms rely on small scripts, with no framework. On October 31, 2026, Astro produced 8 files of them, for a total of 40 KB across the whole site.

We made another, less common choice: the stylesheet travels inside each page rather than beside it. It was the last request blocking display: about 4.4 KB compressed, but 150 ms of waiting on a slow mobile connection. The trade-off is deliberate: the stylesheet is no longer cached from one page to the next. On a site where most visits start on a page found in Google, the first impression matters more than the second page.

What runs on demand: Cloudflare functions

A pre-built site has no server waiting for visitors. Some tasks still need one: receiving a form, signing someone up for the newsletter, logging a search made on the blog. Cloudflare Pages offers functions for this that run on its network, on demand. Falia.co had seven of them on October 31, 2026.

01

Forms

The form is ordinary HTML. On submission, a function receives the request, checks the required fields, completes the website address the visitor typed without "https://", then passes the request on to our lead tracking. The visitor then lands on a confirmation page that sends the conversion signal only once.

02

The middleware in front of the site

A special function, the middleware, sees every request go by. It sends to falia.co any visit that arrives through the technical address Cloudflare gives the project, so that Google never sees two copies of the site. It closes work previews to search engines. Finally, it serves the redirects of old articles, described below.

Everything else is a file served as is by Cloudflare's network. For a business, the line is clear: what is content is pre-built. What must react to a visitor's action goes through a short function that can be read and tested on its own.

Redirects, on two levels

A site that replaces an old site inherits its addresses. For us, redirects live on two levels.

  • Cloudflare's redirects file. On October 31, 2026, it had 532 lines for about 53 KB: old service pages, renamed pages, removed test pages.
  • A table read by the middleware. In it, 751 old article addresses each lead to the article that took over their content, never to a category page.

Why two levels? Cloudflare's documentation states a limit of 2,000 static redirects and 100 dynamic redirects. We had fewer. Yet on September 29, 2026, we found that the end of our file was being ignored without any message: beyond roughly the first 64 KB, 290 redirects no longer responded. Article addresses moved to the middleware's table. A check now blocks any publication if the file goes over 62,000 bytes. The architecture lesson fits in one sentence: a limit you cannot see is verified by a check, not by memory.

The method for building the mapping table of old addresses is detailed in our article on website migration without losing rankings.

What the site produces for search engines and AI

A good share of the architecture is not visible on screen. It serves the search engines and AI systems that read the site. Everything is generated on every build, from the pages themselves.

What is producedOn falia.co, October 31, 2026
The sitemap826 addresses. Each carries the date of its last substantive change, read from the page's structured data. It also carries its links to the other language. Thank-you pages, search pages and pages kept out of the index are excluded.
Structured dataA JSON-LD block in every page: the site, the organization, the page type, the breadcrumb, services and their offers, and the FAQ when the page has one
The index for AI (llms.txt)A table of contents of about 10 KB, written for a system that reads the site without crawling it
The blog's search indexA file built from the articles, loaded only when the visitor clicks in the search field
Share images488 images in French and English, made on a workstation, never during the build
How we do it

The blog's search index first lived in a hand-written file. On September 21, 2026, it dated from September 4: eighteen articles published since then could not be found by the site's search. We moved it into the build, which recreates it from the articles themselves. A check blocks publication if a published article is missing from it. The same reasoning applies to the sitemap and the index for AI: anything that describes the site is calculated from the site, never beside it.

The limits of an Astro website

This architecture suits a business site, a content site or a catalogue. It requires a few trade-offs, worth knowing before you choose.

What you might expectHow it works on an Astro website like ours
A dashboard to edit pagesThere is none: you write an instruction to AI or edit the files. Astro can also display content from a headless CMS if your team wants an editor.
A change visible within a secondThe site is rebuilt on every publication, then the checks run. The delay is counted in minutes, not seconds.
A full online storeThe cart, payments and inventory stay on a commerce platform. Astro can serve the storefront of a Shopify store in headless mode.
Data that changes on every visitIt goes through a function, a server island or a collection read on demand, at some cost in performance
A site that maintains itselfThere are no plugins or database to update, but Astro and the checks evolve. The site needs someone who is responsible for it.

What it changes for your business

Each choice described here answers a business question. Validated collections reduce the risk of publishing an incomplete page. The table of pairs keeps your two languages aligned. Data kept in one place prevents two different prices for the same service.

None of these gains is automatic. They depend on decisions made at the start: which data deserves a single file, which rules become checks, who approves publication. AI executes, a senior signs off.

What it changes for you

Six questions to ask before choosing an Astro website

  • Is our site mostly content (services, articles, product sheets) or an interactive application?
  • How many times a month do we need to change it? Who will make those changes?
  • Must our two languages stay perfectly aligned, page for page?
  • Where do our prices, service names and contact details live: in one place or on every page?
  • Which features truly need a server (forms, appointment booking, client area)?
  • Will the code and the domain name be in our name?

A well-organized Astro website changes quickly because everything in it has its place.

Mostly want to update your site by writing your requests in your own words? That is the idea behind the AI-managed website, part of our web design expertise.

We build Astro websites with the same architecture as falia.co: our Astro agency page presents the framework, the major brands that use it and how we work.

How would you like to send this email?

Frequently asked questions about Astro websites

What is an Astro website?

It is a site built with Astro, an open-source framework that prepares each page in advance. The browser receives ready-to-read HTML and JavaScript is only sent for the parts that must react.

Is an Astro website good for SEO?

It starts with a speed advantage over WordPress: according to HTTP Archive, 71% of Astro sites passed Core Web Vitals on mobile in September 2026, compared with 48% of WordPress sites. Rankings still depend mostly on content, addresses, tags and structured data, which the architecture helps keep accurate.

Can an Astro website be in French and English?

Yes. Astro handles routing by language in its configuration. On falia.co, French is at the root and English under /en/. A single table of pairs produces the links between the two versions.

Can my team update an Astro website without knowing how to code?

Yes, by writing its requests to Claude Code or another coding agent, which edits the files. Each change goes through automatic checks, then waits for approval before going live.

Can an Astro website receive forms?

Yes. The form is ordinary HTML and submission goes through a small function at the host, which checks the fields and passes the request on to your CRM or lead tracking.

Does my Astro website depend on Cloudflare?

No. Astro is open-source software under the MIT licence, deployable to Cloudflare, Netlify, Vercel or AWS. Only the small functions specific to the host need adapting if you change platforms.

Sources and references
  1. HTTP Archive, technology report, share of sites passing Core Web Vitals on mobile, September 2026, accessed November 2, 2026.
  2. Astro, Why Astro?, official documentation, accessed October 31, 2026.
  3. Astro, Content collections, official documentation, accessed October 31, 2026.
  4. Astro, Internationalization (i18n) Routing, official documentation, accessed October 31, 2026.
  5. Astro, Islands architecture, official documentation, accessed October 31, 2026.
  6. Cloudflare, Astro is joining Cloudflare, blog post of January 16, 2026, accessed October 31, 2026.
  7. Cloudflare, Redirects and Functions, Cloudflare Pages documentation, accessed October 31, 2026.
  8. Google Search Central, Tell Google about localized versions of your page, last updated September 21, 2026, accessed October 31, 2026.
  9. Falia, falia.co repository and history, figures recounted on 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 Web design →
01
Web design·10 min read

Bilingual website: keeping French and English up to date with AI

→
02
Web design·17 min read

WordPress alternative: the real options and who each one suits

→
03
Web design·10 min read

Automated checks: how an AI-built website catches its own mistakes

→
Other topicsStrategySEOPaid advertisingConversionAI visibilityWeb designeCommerce
← All insights