Lavkush Most common Webflow problems are not bugs. They are small settings: a page published to the wrong domain, a CMS item still set to draft, a form sent to the wrong email, or a cached old copy of your site. The good news: almost every Webflow problem has a simple fix, and most need no code. This guide covers the 12 problems Webflow users face most often, why each one happens, and the exact steps to fix it.
New to Webflow? Our guide on how to build a website in Webflow covers the full setup first. Now, let us fix things.
The 12 Most Common Webflow Problems (and Their Fixes)
1. Your changes are not showing on the live site
Cause: You published to the wrong domain, or your browser is showing a cached (old saved) copy of the page. Fix: Publish again and tick every domain you use, including your custom domain, not just the webflow.io staging address. Then hard-refresh the live page with Ctrl + Shift + R (Cmd + Shift + R on Mac). Webflow's own guide on how to publish or unpublish a Webflow site covers the publish panel. Still stuck? Open the site in a private window. If it looks right there, it was cache all along.
2. Form submissions are not arriving
Cause: The notification email in your form settings is wrong, the messages land in spam, or you tested inside the Designer preview, where forms never send. Fix: Go to Site settings, then Forms, and check the notification email address. Publish the site, open the live page, and send a real test. Then check the Forms tab, where every submission is stored even when the email goes missing, and search your spam folder too.
3. CMS items are not appearing on the site
Cause: The item is still a draft, the collection list has a filter that hides it, or the list limit pushes it out of view. Fix: Open the collection and check the item status first. Draft items never appear on the published site. Next, select the Collection List on your page, open its settings, and remove or correct any filters. Finally, check the "limit items" setting. Publishing the item and republishing the site fixes this nine times out of ten.
4. Your custom domain is not connecting, or SSL is stuck
Cause: Your DNS records are wrong or have not spread yet, or an old record is fighting the new one. Fix: Follow Webflow's guide to quick connect a custom domain and copy the A and CNAME records exactly as shown. Remove old A records pointing elsewhere. Then wait: DNS can take a few hours, and SSL is issued only once records are correct, so a "not secure" warning usually fixes itself.
5. Your site is not appearing on Google
Cause: The site is brand new, indexing is switched off in the page settings, or the site is still behind a password. Fix: Search Google for site:yourdomain.com. If nothing appears, check Site settings, then SEO, and make sure the auto-generated sitemap is on. In each page's settings, confirm sitemap indexing is enabled, and remove any site password under Site settings, General. Then submit your sitemap in Search Console and give it a few days. New sites are rarely instant.
6. Images are making your pages heavy and slow
Cause: Large photos uploaded straight from a phone or camera, sometimes 5 MB each. Fix: Resize images before uploading. A full-width banner rarely needs more than 1920 pixels wide, and content images are fine at 800 to 1200 pixels. Compress them, and prefer WebP where you can. The Asset panel shows every file's size, so heavy files are easy to spot and replace.
7. The Designer feels slow, or elements seem "stuck"
Cause: Usually a class mix-up. The element is styled by a combo class, or a parent has a fixed height or hidden overflow, so your change happens somewhere you cannot see. Fix: Select the element, read the class list in the Style panel from left to right, and check its parents in the Navigator. If the Designer itself is slow, close extra tabs and remove huge embedded videos. Most "stuck" elements are one wrong class, not a broken site.
8. The layout breaks on mobile breakpoints
Cause: Fixed widths, big pixel margins, or a flex row that never wraps, built on desktop and never checked smaller. Fix: Work through the breakpoints from tablet down to mobile portrait. Replace fixed pixel widths with percentages where things overflow, reduce large side padding, and set flex children to wrap. Styles flow downward: a desktop change affects every smaller breakpoint, but a mobile change does not flow back up.
9. Interactions and animations are not triggering
Cause: The trigger is attached to a different element than you think, or the element starts hidden and the "show" step is missing. Fix: Open the Interactions panel, select the element, and read the trigger list carefully. Check the first step of the animation: if the element starts at 0% opacity, there must be a step that brings it back. Some interactions only behave correctly after publishing, so test live before you panic.
10. Site search is not finding your pages
Cause: The page was excluded from search results in its settings, or the search index has not updated since you published. Fix: Open the page settings and make sure "Exclude this page from site search results" is off. Then republish and wait: Webflow rebuilds the search index after publishing, never instantly. Search only covers published content, so draft CMS items and unpublished pages will never appear, however nicely you ask.
11. You keep hitting CMS or plan limits
Cause: Every Webflow plan has caps: CMS items, monthly form submissions, bandwidth, and pages. Fix: Check your usage in Site settings and delete old test items and unused submissions to free space. If you regularly hit the ceiling, the plan is simply too small for the site now. Our breakdown of how much Webflow costs compares plan limits side by side, so you can see which tier removes the limit that keeps stopping you.
12. You worry about losing work, and backups confuse you
Cause: Many users do not know Webflow saves backups automatically, so one wrong click feels dangerous. Fix: Relax. Webflow creates automatic backups as you work, and you can save a manual one with Ctrl + Shift + S (Cmd + Shift + S on Mac). To restore, open Site settings, then Backups, preview the version you want, and restore it. Restoring replaces the Designer version, so save a fresh backup first.
Quick-Reference Table
| Problem | Likely cause | First fix to try |
|---|---|---|
| Changes not live | Wrong domain or cache | Publish to all domains, hard-refresh |
| Form emails missing | Wrong notification email | Check Site settings > Forms |
| CMS item hidden | Draft status or filter | Publish item, check list filters |
| Domain not connecting | Wrong DNS records | Re-add A and CNAME records |
| Not on Google | Indexing off or too new | Enable sitemap, submit to Search Console |
| Slow pages | Oversized images | Resize and compress before upload |
| Element "stuck" | Wrong class styling it | Read classes in the Style panel |
| Mobile layout broken | Fixed widths, no wrap | Use %, reduce padding, wrap flex |
| Animation not firing | Trigger on wrong element | Check Interactions panel steps |
| Search misses pages | Page excluded from search | Turn off the exclude setting |
| Plan limits hit | Plan too small | Delete test data or upgrade |
| Fear of losing work | Backups unknown | Site settings > Backups |
Frequently Asked Questions
Why does my Webflow site look different in the Designer and on the live site?
Almost always caching or an unpublished change. Publish to every domain, then hard-refresh the live page or open it in a private window. If the private window looks right, your browser was showing an old copy.
How long do Webflow DNS changes take?
Usually a few minutes to a few hours, rarely up to 48 hours. SSL is issued only after DNS points to Webflow correctly, so let them settle before changing anything again.
Can I undo a mistake in Webflow?
Yes. Undo works while you edit, and for bigger accidents Webflow keeps automatic backups in Site settings, under Backups. Preview an older version and restore it, after backing up the current one.
Why is my Webflow Designer so slow?
Heavy pages are the usual reason: very large images, long pages with many elements, and embedded videos. Closing other tabs, splitting long pages, and compressing assets makes a clear difference.
Conclusion
Webflow problems feel scary in the moment, but the pattern in this list is friendly: a setting, a status, or a cache, not broken code. Publish carefully, check drafts and filters before redesigning anything, and keep your images light. When you get stuck, test on the live site in a private window and fix one thing at a time. Your site will forgive you. It keeps backups, after all.
Leave a Comment