Webflow maintenance in 2026 is mostly about change that happens around your site, not inside it. Since June 2025 Webflow has retired Logic, User Accounts and the legacy Editor, and Google has moved every classic reCAPTCHA key to Google Cloud. None of that was a bug on your site, and every one of them could stop a form, a login or an editor from working without a single page being touched.
This guide is for the marketing lead or founder who owns a Webflow site after launch. It sorts maintenance into what breaks, what drifts and what a monthly retainer should cover, using Webflow's own changelogs and pricing page, Google's documentation and independent web studies, all read on 2026-11-04.
What Webflow maintains for you
Start with what you are not buying. Webflow's hosting page says every Site plan includes SSL and TLS certificates that renew automatically, DDoS and bot protection through its CDN provider, and "ongoing, automatic backups" you can preview and restore. Its pricing page lists unlimited automatic backups for one-click restore on every plan. These are vendor claims, but they describe the product as shipped, not something you configure.
That removes the core updates, plugin updates and backup jobs that fill most WordPress care plans. What Webflow does not do is watch what you connected to it: a HubSpot embed that stopped loading, a Zapier step pointing at a renamed field, a reCAPTCHA key owned by someone who left. It does not review your content either. That is where Webflow maintenance actually lives.
What breaks: platform and third-party changes
Breakage on Webflow usually arrives as a dated announcement, months in advance, sent to whoever owns the Workspace. The risk is that nobody reads it.
| Change | Key date | What stopped working | What the owner had to do |
|---|---|---|---|
| Webflow v1 API deprecated | 31 March 2025 | v1 integrations lost maintenance and support; new v1 site tokens could no longer be created | Move custom integrations to v2 tokens, webhooks and apps |
| Webflow Logic retired | 27 June 2025 | Native Logic flows | Rebuild flows in Zapier or Make |
| reCAPTCHA classic keys moved to Google Cloud | Automatic migration from Q4 2025; API access locked for unmigrated keys in Q1 2026 | Classic keys without a Google Cloud project | Migrate the key, or confirm the automatic migration landed in a project you control |
| Webflow User Accounts retired | 29 January 2026 | Member logins, gated pages and the related APIs and webhooks in every API version | Move members to a partner such as Memberstack or Outseta |
| Legacy Editor retired | Automatic migration from 4 May 2026; Editor gone on 4 August 2026 | The old Editor and its white-label branding | Check that each editor landed on the right client or limited seat |
Source: Webflow v1 API deprecation notice; Webflow updates, Deprecating Logic and User Accounts; Webflow Developer changelog, 29 January 2026; Webflow legacy Editor migration page; Google Cloud reCAPTCHA migration overview, last updated 2026-10-26
Every change came with notice: Webflow allowed new User Accounts activations until 31 January 2025, a year before the shutdown. The problem is who receives it. Notices go to Workspace owners, and on many sites that is still the agency that built it, or an employee who has moved on.
Forms are the weakest point. Webflow's spam protection guide lists four layers: reCAPTCHA, Cloudflare Turnstile, spam filtering and honeypot fields. It warns that once reCAPTCHA validation is on, any form without a reCAPTCHA element fails to submit. A newsletter form added a year after launch without the element quietly stops sending.
Plan changes create work too. Webflow now sells a Basic plan at $15 a month billed yearly with 10 GB of bandwidth, and a Premium plan from $25 a month billed yearly with Webflow CMS. Our post on Webflow CMS limits after the 2026 plan change covers the new item and Collection caps. A site that grows past its bandwidth for two consecutive months is upgraded automatically, which the finance team sees before the marketing team does.
What drifts: content, links, speed and accessibility
Drift does not stop anything working. It makes the site slightly worse each month, and the evidence is that most sites never get it reversed.
| Drift | Evidence | How it shows on a Webflow site |
|---|---|---|
| Broken links | 23% of news pages and 21% of government pages contain at least one broken link (Pew Research Center, 2024) | Outbound links in old blog posts, renamed CMS slugs without a redirect |
| Disappearing pages | 38% of pages from 2013 and 8% of pages from 2023 were no longer accessible in October 2023 (Pew) | Deleted landing pages and CMS items still linked from emails and ads |
| Third-party weight | 92% of pages load at least one third party; the median top-thousand site loads 66 (HTTP Archive Web Almanac 2024) | Tags added through custom code and never removed |
| Accessibility | 95.9% of the top million home pages had detectable WCAG 2 failures; 53.1% had missing alt text and 83.9% low-contrast text (WebAIM Million 2026) | New CMS images without alt text, new sections built in off-brand colours |
| Search basics | Google tells site owners to keep redirects "generally at least 1 year" after a URL move (Google Search Central) | Redirects deleted during clean-up, meta descriptions left blank on new items |
Source: Pew Research Center, When Online Content Disappears, 2024; HTTP Archive Web Almanac 2024, Third Parties; WebAIM Million 2026; Google Search Central site move guidance
None of these figures is specific to Webflow. They measure the web as a whole, and we use them as a proxy because the mechanism is the same on any CMS: several people add content over two years, and nobody owns the cumulative effect.
Speed drift is a third-party problem. Webflow serves pages from a global CDN and offers image conversion to WebP and AVIF, according to its hosting page. What slows a Webflow site after launch is usually what gets pasted into custom code: chat widgets, heatmaps, extra tag managers. Our Webflow page speed guide lists the fixes that actually move Core Web Vitals. The pass mark does not move: Google's thresholds are 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint and 0.1 for Cumulative Layout Shift, at the 75th percentile of page loads.
CMS drift is a structure problem. A "Summary" field starts holding HTML. A case study Collection starts holding press releases. Two years later, the templates no longer match the content.
A Webflow maintenance calendar
Most of this work is checking, not building. The calendar below is how we would split it for a typical marketing site of 30 to 300 pages. It is our working order, not an industry standard.
| Cadence | Checks |
|---|---|
| Weekly | Submit every form on the live site; confirm the notification and any CRM or automation step arrived |
| Monthly | Broken links and 404s in Google Search Console; new CMS items for meta descriptions and alt text; bandwidth and plan usage in Webflow; Core Web Vitals field data |
| Quarterly | Custom code and third-party scripts, removing anything unused; seats and guest access; integrations re-tested end to end; Webflow and Google changelogs for anything dated in the next six months |
| Annually | Domain and DNS renewals; redirect list against current URLs; accessibility pass on key templates; the site plan against actual traffic and CMS item count |
Source: Octo working checklist; Webflow pricing page; Google web.dev Core Web Vitals thresholds
The weekly form test matters most and costs least, because a failed form loses leads the same day. The monthly row is covered in more depth in our Webflow SEO checklist.
What a monthly Webflow maintenance retainer should cover
Scope a retainer around the calendar above plus the work your team cannot do in Webflow themselves. Five blocks cover most sites: monitoring (the form tests and monthly checks, the least visible and most valuable work), a platform watch (someone reads Webflow's and your vendors' changelogs and flags what applies before the date), content and CMS operations, search and accessibility hygiene, and small builds under a fixed hour ceiling. If your site was handed over properly, as our Webflow client handover kit describes, your team does the simple edits and the retainer covers the rest.
| Usually in scope | Usually out of scope |
|---|---|
| Form and integration monitoring | Security patching, SSL and backups, which Webflow already provides |
| Platform and vendor change watch | Rebuilding a feature Webflow retired, such as moving members off User Accounts |
| CMS publishing and clean-up | New sections or pages that need new design |
| Redirects, meta and alt text | Content writing and SEO strategy |
| Script and access reviews | Site plan and Workspace fees, which the client pays Webflow directly |
| Small builds under an agreed ceiling | Redesigns and migrations |
Source: Octo scoping practice
Response times. Agree them in writing, per type of request. As one vendor reference, Digidop, a Webflow agency, says most support requests are delivered within one to seven business days and sells a 10-hour package with no commitment.
Retired features are projects. A good retainer flags a retirement early. It should not absorb a membership migration into ordinary monthly hours.
Price. Our guide to white label Webflow maintenance retainers, publishing this month, compares published plans. We quote maintenance per project, based on the size of the site and what is connected to it.
When you do not need a retainer
A five-page site with one form, no CMS and no integrations needs a weekly form test and an annual review, which an in-house marketer can do in an hour a month. A retainer starts to pay for itself when several people edit the CMS, forms feed a CRM or automation, custom code loads third-party scripts, or paid traffic lands on the site. Most B2B marketing sites meet at least two of those. Whatever you choose, make sure someone on your team owns the Workspace, the reCAPTCHA project and the domain registrar first.
What this means for your Webflow maintenance plan
Treat Webflow maintenance as operations, not repairs. The platform keeps hosting, certificates and backups in order. Your job, or your retainer's, is the tools, content and people around it: test forms weekly, read changelogs quarterly, review scripts and access, and keep CMS content clean. We built more than 20 Webflow sites in twelve months as Web Tonic's white-label partner, and we would scope maintenance around this calendar. Our marketing websites service page explains how we build and support Webflow sites after launch.
