Astro and Sanity are the stack we recommend for content-heavy sites that need excellent performance, structured content and deep integrations. The site you are reading is built on Astro. This guide explains how the stack works, why it is strong for SEO and AI search, what it costs to run in 2026, and when it is the right choice over a visual builder.
Astro in 2026: what changed
Astro had a big year. On January 16, 2026, Cloudflare announced that The Astro Technology Company was joining Cloudflare. The announcement committed to keeping Astro open source and to supporting it as the best framework for content-driven sites “whether they host on Cloudflare or elsewhere.” Cloudflare named Unilever, Visa and NBC News among the brands using Astro, said Webflow and Wix run on Astro on Cloudflare, and launched an Astro Ecosystem Fund with partners including Webflow, Netlify, Wix and Sentry.
Astro 6 entered beta the same week, adding support for more JavaScript runtimes, faster performance and shorter build times. For clients, the practical takeaway is stability: the framework now has the backing of a large infrastructure company and stays portable.
Why Astro and Sanity
- Astro ships zero JavaScript by default. Pages are static HTML, with interactive “islands” only where needed, such as a pricing calculator or a search box.
- Sanity stores structured content. Content is modeled as typed documents, so the same posts, products and FAQs can power the website, an app and email.
- Editors get a custom studio. Fields, validation, previews and workflows are tailored to the team, not a generic admin.
- Everything is portable. The code is yours, content can be exported, and the site can move between Netlify, Vercel and Cloudflare without a rewrite.
How the stack fits together
- Model content in Sanity as documents such as pages, posts, authors, services and FAQs, with validation rules for SEO fields.
- Fetch content in Astro with Sanity’s GROQ query language, at build time for static pages or on request for frequently changing content.
- Generate pages as static HTML with Astro’s content layer, then deploy to an edge network such as Netlify, Vercel or Cloudflare.
- Trigger rebuilds with webhooks when editors publish, so the live site updates within a minute or two.
- Add islands only where needed using React, Svelte or Vue components for interactive features.
SEO and AI search advantages
Static HTML loads quickly and is easy for search engines to crawl. It also matters for AI search: crawlers from ChatGPT, Claude and Perplexity read raw HTML and do not always run JavaScript, so content that only appears after client-side rendering can be missed. With Astro, every word is in the HTML from the start.
Because content is structured, generating SEO assets is simple and consistent:
- Sitemaps, RSS feeds and canonical tags generated from content
- JSON-LD schema for articles, FAQs, services, products and breadcrumbs built from typed fields
- Open Graph images generated per page
- An llms.txt and a full-text llms-full.txt built automatically for AI assistants
Core Web Vitals scores of 95 to 100 are normal on Astro sites, because there is little JavaScript to slow down Interaction to Next Paint.
What it costs to run
| Item | Free tier | Paid |
|---|---|---|
| Sanity | 20 seats, 10,000 documents, 250k API requests, 100 GB bandwidth | Growth $15 per seat/month, 25,000 documents |
| Hosting (Netlify, Vercel, Cloudflare) | Generous free tiers for static sites | Team plans priced per member, plus usage |
| Search (Algolia), forms, analytics | Free tiers available | Scales with usage |
For a typical marketing site with a blog, running costs are often under $50 per month. The trade-off is that changes to layouts and new templates need a developer, so budget for an ongoing development retainer rather than platform fees.
Integrations
Because it is code, the stack connects to anything with an API: HubSpot or Salesforce for leads, Algolia for search, Stripe for payments, and product data from your own backend. Integrations can run at build time, on the edge or in serverless functions, and API keys stay on the server.
Astro + Sanity vs Webflow vs Next.js
| Criteria | Astro + Sanity | Webflow | Next.js + headless CMS |
|---|---|---|---|
| Default JavaScript | None | Light | Moderate to heavy |
| Visual page building | Limited | Excellent | Limited |
| Content modeling | Excellent | Good | Excellent |
| App-like features | Islands | Limited | Excellent |
| Lock-in | None | High | Low |
| Best for | Content sites, docs, marketing at scale | Marketing teams | Web apps with marketing pages |
Common mistakes on headless builds
Headless sites fail in predictable ways. The ones we see most often when we take over other teams’ projects:
- No preview. Editors cannot see a draft before publishing, so they stop trusting the CMS. Set up Sanity’s Presentation tool or a draft preview route from day one.
- Unstructured rich text everywhere. If every page is one big rich text field, you lose the benefits of structured content. Model FAQs, quotes, CTAs and author details as their own fields.
- Client-side rendering for content. Fetching content in the browser hides it from crawlers and slows the page. Render it on the server or at build time.
- Slow rebuilds. Large sites that rebuild everything on every publish frustrate editors. Use incremental builds or on-demand rendering for frequently updated sections.
- No redirect management. Add a redirects document type in Sanity so editors can manage 301s when they change slugs, instead of filing a ticket.
- Missing SEO fields. Every document type that becomes a page needs a title, description, Open Graph image and noindex option, with sensible fallbacks.
When it is not the right fit
If your marketing team wants to design new layouts visually without developers, Webflow or Framer will suit them better. If the product is a logged-in web app with lots of interactivity, Next.js may be the better base. Astro and Sanity reward teams with structured content, performance goals and ongoing development support.
“Astro is the rare framework that makes the fast choice the default choice. You have to work to make it slow.”
Sources
- Cloudflare acquires Astro, January 16, 2026
- Sanity pricing, October 2026
- Astro documentation