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

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

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. per-seat mentioned
   That rules out most per-seat pricing.
2. Cloudflare mentioned
   Cloudflare (Workers with Static Assets, or Pages).
3. Workers mentioned
   Cloudflare (Workers with Static Assets, or Pages).
4. Vercel mentioned
   Vercel.
5. Next.js mentioned
   Where I'd go if your client work is predominantly Next.js - it's the reference platform and you'll fight nothing.
6. Netlify mentioned
   Netlify.
7. Hugo mentioned
   Framework-agnostic in a way that suits mixed Astro/Hugo/Eleventy shops.
8. Kinsta mentioned
   Kinsta Static Site Hosting.
9. WordPress mentioned
   Worth naming specifically for agencies already on Kinsta for WordPress clients - free static hosting, 260+ CDN locations, and it lives alongside the WordPress sites in one dashboard with one invoice.
10. GitHub Pages mentioned
    GitHub Pages.
11. Cloudflare Workers mentioned
    What I'd actually do: Cloudflare Workers/Pages as the house standard for client sites, Vercel as the exception for Next.js-heavy clients who'll pay for it, and bill hosting to the client's own account where you can - agency-owned hosting accounts become a liability at offboarding time.
12. Cloudflare Pages compared
    - mecanik.dev - Cloudflare Pages vs Workers in 2026 (https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/)

Sources the engine cited

The answer, as recorded

# Best static site hosting for agencies The agency case is different from the solo case: you're hosting many small sites, you need per-client isolation and billing, and you don't want hosting costs to scale with how many designers touch a dashboard. That rules out most per-seat pricing. **1. Cloudflare (Workers with Static Assets, or Pages).** My default recommendation for agencies. Flat $20/mo Pro - not per user - unlimited bandwidth on every tier including free, and unlimited projects, so twenty client sites cost the same as one. The largest CDN footprint of the three. One caveat worth knowing: Cloudflare now points new projects at **Workers with Static Assets** rather than Pages. Pages still gets support and bug fixes, but Workers gets the roadmap - so start new client builds on Workers unless you specifically want the pure git-push simplicity of Pages. Bonus for agencies: you can keep DNS, WAF, and email routing for the client in the same account. ([Cloudflare migration guide](https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/), [Pages vs Workers in 2026](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/)) **2. Vercel.** Where I'd go if your client work is predominantly Next.js - it's the reference platform and you'll fight nothing. Excellent preview deploys for client review, which is genuinely the best client-approval workflow in the business. But it's $20/seat/month plus credit-metered build minutes and bandwidth, and the Hobby tier is explicitly non-commercial, so you can't park small client sites there. For an agency that's the expensive option. ([pricing comparison](https://devplaybook.cc/blog/vercel-vs-netlify-vs-cloudflare-pages-hosting-comparison/)) **3. Netlify.** Still the best pick if you want built-in form handling, identity, and split testing without wiring up third parties - that saves real hours on brochure sites. Framework-agnostic in a way that suits mixed Astro/Hugo/Eleventy shops. The April 2026 pricing change to a credit model (300 credits free, 20 credits/GB bandwidth) made the economics harder to predict for client sites with spiky traffic, which is why it's third rather than first. ~$19/seat/month. ([comparison](https://htmlpub.com/blog/vercel-vs-netlify-vs-cloudflare)) **4. Kinsta Static Site Hosting.** Worth naming specifically for agencies already on Kinsta for WordPress clients - free static hosting, 260+ CDN locations, and it lives alongside the WordPress sites in one dashboard with one invoice. Consolidated billing matters more than people admit when you're reselling. ([overview](https://www.websiteplanet.com/blog/best-static-site-hosting/)) **5. GitHub Pages.** Not for client work, but I'd still name it: internal docs, style guides, status pages, your own agency site. Free, free TLS, custom domains, zero config. Keep it off the client-facing list because there's no preview deploys and no server-side anything. **What I'd actually do:** Cloudflare Workers/Pages as the house standard for client sites, Vercel as the exception for Next.js-heavy clients who'll pay for it, and bill hosting to the client's own account where you can - agency-owned hosting accounts become a liability at offboarding time. Sources: - [developers.cloudflare.com - migrate from Pages](https://developers.cloudflare.com/workers/static-assets/migrate-from-pages/) - [mecanik.dev - Cloudflare Pages vs Workers in 2026](https://mecanik.dev/en/posts/cloudflare-pages-vs-workers-which-to-use-in-2026/) - [devplaybook.cc - Vercel vs Netlify vs Cloudflare Pages](https://devplaybook.cc/blog/vercel-vs-netlify-vs-cloudflare-pages-hosting-comparison/) - [htmlpub.com - Vercel vs Netlify vs Cloudflare](https://htmlpub.com/blog/vercel-vs-netlify-vs-cloudflare) - [websiteplanet.com - best static site hosting](https://www.websiteplanet.com/blog/best-static-site-hosting/) - [bootstrap.build - static website hosting providers compared](https://bootstrap.build/articles/static-website-hosting/)

Near this answer

The same question, recorded on other dates: 2026-10-16, 2026-10-14, 2026-10-11, 2026-10-08, 2026-10-06, 2026-10-03, 2026-10-01, 2026-09-29, 2026-09-27, 2026-09-25, 2026-09-23.

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

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

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.