What Claude (Anthropic) with web search answered for static site hosting (agencies) on 2026-10-28

Claude (Anthropic) with web search claude-opus-5 asked 2026-10-28

Coverage: Claude (Anthropic) with web search. Other engines not included.

The question asked, verbatim: best static site hosting for agencies

Brands named, in the order the engine gave

1. Cloudflare mentioned
   Cloudflare Pages / Workers Static Assets - my default for agency work, and it's not close on cost.
2. Cloudflare Pages mentioned
   Cloudflare Pages / Workers Static Assets - my default for agency work, and it's not close on cost.
3. Cloudflare Pages / Workers mentioned
   Cloudflare Pages / Workers Static Assets - my default for agency work, and it's not close on cost.
4. Workers mentioned
   Cloudflare Pages / Workers Static Assets - my default for agency work, and it's not close on cost.
5. Vercel mentioned
   Vercel - reach for this when the client site is Next.js, or when the deliverable includes anything dynamic (ISR, middleware, image optimization).
6. Next.js mentioned
   Vercel - reach for this when the client site is Next.js, or when the deliverable includes anything dynamic (ISR, middleware, image optimization).
7. Netlify mentioned
   Netlify - still the most mature and the broadest framework support, and the built-in form handling genuinely saves you standing up a backend for brochure sites with a contact form.
8. Cloudflare R2 + Cloudflare mentioned
   Cloudflare R2 + Cloudflare in front, or S3 + CloudFront - for the long tail of "this site will never change again." Archive sites, event microsites, campaign landing pages.
9. S3 + CloudFront mentioned
   Cloudflare R2 + Cloudflare in front, or S3 + CloudFront - for the long tail of "this site will never change again." Archive sites, event microsites, campaign landing pages.
10. Archive mentioned
    Cloudflare R2 + Cloudflare in front, or S3 + CloudFront - for the long tail of "this site will never change again." Archive sites, event microsites, campaign landing pages.
11. Cloudflare Workers mentioned
    If you want one answer: standardize on Cloudflare Workers Static Assets, keep a Vercel Pro seat for the Next.js jobs, and don't migrate anything that currently works.

Sources the engine cited

Is one of these your site? Its page lists every recorded answer that cited it, with the questions, the pages and the dates, and carries the alert for the next citation.

The answer, as recorded

## The short list, in the order I'd actually reach for them **1. Cloudflare Pages / Workers Static Assets** - my default for agency work, and it's not close on cost. Unlimited bandwidth and unlimited sites even on the free tier, 500 builds/month, no commercial-use restriction. That matters enormously when you're carrying 30 client sites and one of them gets on Hacker News - you never get a surprise bandwidth bill you have to awkwardly pass on. Paid Workers is $5/mo. Caveat worth knowing: Cloudflare is steering new projects toward **Workers with Static Assets** rather than Pages. Pages is *not* deprecated and existing projects keep working with no forced migration, but if you're standardizing a stack today, build new sites on Workers Static Assets so you're on the path getting new features. ([Cloudflare docs](https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/), [Pages vs Workers 2026](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/)) **2. Vercel** - reach for this when the client site is Next.js, or when the deliverable includes anything dynamic (ISR, middleware, image optimization). The DX is the best in the category and deploy previews per pull request are genuinely how you should be doing client review rounds - send a URL, not a screenshot. Pro is $20/seat/mo and build minutes are now credit-metered, so model that before you commit a big portfolio. ([tech-insider comparison](https://tech-insider.org/vercel-vs-netlify-vs-cloudflare-pages-2026/)) **3. Netlify** - still the most mature and the broadest framework support, and the built-in form handling genuinely saves you standing up a backend for brochure sites with a contact form. The honest caveat: the April 2026 pricing overhaul moved it to a 300-credit free plan and 20 credits per GB of bandwidth, which went over badly. It's $19/seat/mo. I'd pick it for the forms and the framework coverage, not for price. ([Netlify pricing discussion](https://answers.netlify.com/t/still-dont-understand-pricing-especially-with-clients-creating-their-own-account/104109)) **4. Cloudflare R2 + Cloudflare in front, or S3 + CloudFront** - for the long tail of "this site will never change again." Archive sites, event microsites, campaign landing pages. No seats, no build minutes, pennies a month. Not worth the plumbing for your active work, but it's the right home for the 40% of a mature agency's portfolio that is effectively frozen. ## The agency-specific thing nobody's comparison chart covers Per-seat pricing is the trap. On Netlify and Vercel alike, the cheap path is to keep every client site in **one agency-owned account** and invoice the client a hosting line item yourself - rather than each client having their own org with your developers as billed seats. That's cheaper, but it means you own the account, and you need an answer in your contract for what happens at handoff or if the relationship ends. Both platforms support transferring a project to another account; agree on that mechanism up front rather than at the breakup. Cloudflare sidesteps a lot of this because sites aren't seat-priced. Also: keep client **DNS** separate from client **hosting**. Put domains in Cloudflare (or leave them in the client's registrar) regardless of who hosts the site. Migrating a host is a day's work; untangling a domain you don't control from a client who's stopped replying to email is a month's. **If you want one answer:** standardize on Cloudflare Workers Static Assets, keep a Vercel Pro seat for the Next.js jobs, and don't migrate anything that currently works. Sources: - [Cloudflare: migrate from Pages](https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/) - [Cloudflare Pages vs Workers: which to use in 2026](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/) - [Vercel vs Netlify vs Cloudflare Pages 2026](https://tech-insider.org/vercel-vs-netlify-vs-cloudflare-pages-2026/) - [Best static site hosting 2026](https://pandastack.io/blog/best-static-site-hosting-2026) - [Netlify community: pricing with client accounts](https://answers.netlify.com/t/still-dont-understand-pricing-especially-with-clients-creating-their-own-account/104109) - [Best hosting & deployment tools for agencies](https://peerpush.com/best/for/agencies/uc/hosting-deployment)

Near this answer

The same question, recorded on other dates: 2026-10-26, 2026-10-23, 2026-10-21, 2026-10-19, 2026-10-18, 2026-10-16, 2026-10-14, 2026-10-11, 2026-10-08, 2026-10-06, 2026-10-03.

static site hosting, asked for other audiences: startups (asked 2026-10-28).

Other categories with a recorded answer: api management platforms, application performance monitoring, ci cd platforms, code repository hosting.

Play this answer: which brand was named first?

Markdown edition · JSON record · the question page, with every recording · Answer Watch · AEO Watch

Answer Watch records what one AI answer engine said on one date, nothing more. Each page names the engine and the model, carries the date the question was asked, and lists the brands that appeared in the answer in the order the engine gave them, with the sources it cited. It is a measurement, not a ranking, not a recommendation and not a claim about the world. Brands that did not appear in an answer are not named on any public page. Coverage: Claude (Anthropic) with web search. Other engines not included.