Moving our own website and DNS to Cloudflare

The site ran on Azure Static Web Apps, with DNS in Azure DNS. When the Azure subscription behind both was closed, we moved the site and the domain's DNS to Cloudflare.

The site is now a static Next.js export on Cloudflare Pages, built and deployed automatically on every push to the main branch. Before switching DNS, we copied every mail record to Cloudflare and checked each one against the live values. We also found and removed an out-of-date DNSSEC record at the .app registry that was causing lookups to fail for some mail servers.

Updating Next.js and running a dependency audit took the site from 9 known vulnerabilities, 1 of them critical, to none. Security headers, including a Content Security Policy and HSTS, are served from Cloudflare. A GitHub Actions workflow checks dependencies, types and the build on every change, and runs weekly to catch new advisories.

The contact, API suggestion, early access and Studio request forms all send to one form service and arrive in a shared inbox with their own subject lines. Cloudflare Turnstile and a hidden honeypot field filter automated submissions.

Every page has structured data describing the organisation, services, articles and FAQs. The site publishes a sitemap, an RSS feed and an llms.txt summary for AI assistants, and preview copies on Cloudflare's own domain are excluded from search results.