Webflow error

Updated 11 October 2026

Short answer

Webflow hosts and serves your site, so most problems are a Webflow incident (check its status page), changes that were published to the .webflow.io staging address but not your custom domain, or a custom domain whose DNS doesn't point at Webflow. If something on the page broke after adding custom code, the custom code is the likely cause.

What's the problem

Your Webflow site won't load on your domain, shows old content, shows a certificate warning, or a feature (form, interaction, embed) stopped working.

Why it happens

  • A Webflow incident.
  • Publishing: changes published to staging but not to the custom domain.
  • DNS: records missing, wrong, or not yet updated after a change.
  • SSL or redirect problems on the custom domain.
  • Custom code in the page or site settings causing errors.
  • Billing or plan changes on the site.

How to fix it

  1. Check Webflow's status page.
  2. Publish again, making sure your custom domain is selected.
  3. Check your domain's DNS against Webflow's domain settings, and remove conflicting records.
  4. Wait for DNS to update if you just changed it (up to the old records' TTL).
  5. Remove recent custom code if a feature broke, and check the browser console.
  6. Check the site's plan and billing in Webflow.

What Preventionlabs checks

One click runs the full report on your domain. For this problem it shows whether your site loads, how fast, and where its redirects go; uptime checked every 5 minutes, with an email when the site goes down and when it is back; up to 50 pages from your sitemap, listing any that fail or are slow, plus broken links on them; your DNS: nameservers, addresses, DNSSEC, and records pointing at services that no longer exist; whether HTTPS works and http visitors are sent to it. It has no connection to your site builder, so check its status page as well.

Run your free report

Your first report is free, no card needed. Then A$50 a month, up to 10 domains. Read-only: it never changes anything.

Sources

  1. Webflow: Webflow Statusstatus pageGet email notifications whenever Webflow creates , updates or resolves an incident.
  2. Cloudflare: Time to Live (TTL)official docsTime to Live (TTL) is a field on DNS records that controls how long each record is cached and — as a result — how long it takes for record updates to reach your end users.

Related

Framer error Most Framer site problems are the custom domain: wrong or extra DNS records, AAAA records blocking SSL, or a Cloudflare proxy. Check DNS against Framer. Domain not working Check three things in order: the domain hasn't expired, its nameservers are the ones you expect, and its DNS records point at your current host. "Your connection is not private" The browser couldn't verify your site's certificate: it's expired, for the wrong domain, or not trusted. Fix or renew it on your server. JavaScript error Open the browser console (F12). The red error names the problem, the file and the line. That's the starting point for every JavaScript error.

Preventionlabs is independent and not affiliated with Webflow. Product names are used only to describe the problem.

← All of Website builders