Next.js 16 Cloudflare Static SEO Kit

About this skill

Most "deploy Next.js to Cloudflare" guides assume you're running a server. This skill is for the other case: a Next.js 16+ App Router site that ships as a 100% static export (output: 'export') to Cloudflare Workers Static Assets, with no Node.js server at runtime. That constraint breaks things quietly. proxy.ts (the renamed middleware.ts in Next.js 16), Server Actions, ISR, cookies, and next/image's default loader all either fail the build or silently do nothing under static export — and most teams find this out in production, not in development. This skill front-loads that knowledge: a proven next.config.js, a wrangler.toml tuned for Workers Static Assets (not Cloudflare Pages, which is the legacy path here as of 2026), a self-hosted image pipeline (build-time WebP generation + a custom next/image loader, no paid transform service), a self-hosted/subsetted font setup, and a technical SEO checklist (Metadata API, sitemap.ts/robots.ts, JSON-LD). It ends with a verification procedure, not a promise — the steps to actually confirm a 100/100 PageSpeed score on the live deployment, and what to check first if it isn't 100. Use this if you're setting up a new static Next.js + Cloudflare project, or debugging one that's failing to build or scoring below 100 on PageSpeed.