Webflow maintenance plan: what Webflow handles and what you still do

Webflow maintenance is lighter than WordPress maintenance because Webflow runs the hosting, SSL, security patches and backups for you. What's left still needs a person every month: content changes, forms and integrations, custom code, SEO and accessibility checks, page speed, and Webflow's own platform changes. Published care plans and retainers run from about $400 to $8,000 a month, and mine start at $150 a month for 4 hours.

I'm Chirag Singh. I've built Webflow sites since 2023 and look after sites on monthly care plans. Everything Webflow-specific below comes from Webflow's own pages, read on 29 Oct 2026, and every price is linked to the page that publishes it.

What does Webflow hosting already handle?

Webflow handles the server side of maintenance on every paid Site plan. That covers hosting, the CDN, SSL certificates, platform security updates, DDoS protection and backups. There are no plugins or server software for you to update.

Webflow's hosting page says it "combines the power of AWS infrastructure with Cloudflare's global CDN," that "every Site plan automatically includes SSL and TLS," and that there are "no updates to run, packages to install, or capacity planning." Free certificates renew on their own. Its security page lists "automated patches and updates with no customer maintenance," DDoS protection and rate limiting for all sites, SOC 2 Type II and ISO 27001.

How Webflow backups work

Webflow saves a restore point on every 50th auto-save, and paid Site plans keep unlimited backups. There are no scheduled backups, per Webflow's Help Center article Save and restore backups. You can save a named backup at any time with Command + Shift + S on a Mac or Control + Shift + S on Windows, and preview any backup before restoring it.

A restore isn't a clean undo, though. The same article lists side effects: reCAPTCHA keys have to be added again, bot protection is switched off, scheduled CMS items go back to the publish queue, and "published on" dates change to the restore time. Someone has to check the site after every restore, so I've put backups in the shared column of the diagram below.

What still needs a person on a Webflow site?

Anything that depends on your content or the tools you connect still needs a person. Webflow keeps the platform running. It doesn't know that your contact form stopped reaching your CRM, or that a page you published last week has no meta description.

Content and the CMS

Prices, team members, offers and dates go out of date on every site. Someone has to update them, publish new CMS items, and clear out stale drafts. On a Client-First build your own team can do most of this, so a care plan mostly picks up what they don't have time for.

Forms and integrations

Forms can break without anyone seeing an error. A CRM changes its API, a Zapier step loses its login, or a spam filter starts eating real leads, and nobody notices until sales asks where the enquiries went. Spam settings need care too. Webflow's own guide to reCAPTCHA on Webflow forms (updated 10 Apr 2026) says the native integration only supports the v2 checkbox, applies to every form on the site, and makes submissions fail on any form missing the reCAPTCHA element.

Custom code and third-party scripts

Webflow patches its platform, not the scripts you paste into it. Chat widgets, consent banners, analytics tags and custom JavaScript each come from a vendor that can change or break them. Each one also adds weight to every page, so a script for a tool you stopped paying for is worth removing.

Webflow's own platform changes

Webflow retires features and changes plans, and someone has to act before the date. Its feature sunsets page lists three recent ones. Logic stopped working on 27 Jun 2025. User Accounts ended on 29 Jan 2026. The legacy Editor and its white-labelling ended on 4 Aug 2026. Any site that used Logic for form routing or User Accounts for logins needed rebuilding on another tool, which I cover in alternatives to Webflow Logic and User Accounts.

Plans change too. On 13 May 2026 Webflow merged its CMS and Business plans into Premium, and existing sites in Freelancer or Agency Workspaces move to the new prices at their first renewal on or after 16 Nov 2026, per Webflow's pricing help article. My post on Webflow pricing plans explains what that means for your renewal.

SEO, accessibility and speed

Search Console reports new indexing errors and broken URLs, but only to someone who opens it. Accessibility slips the same way, one image without alt text at a time. The WebAIM Million 2026 report (updated 30 Mar 2026) found detectable WCAG failures on 95.9% of the top million home pages, with low-contrast text on 83.9% and missing alt text on 53.1%.

Webflow's Audit panel runs 4 accessibility checks (alt text, link text, skipped heading levels and duplicate IDs) and flags missing meta titles, descriptions and schema. It doesn't check inside components, CMS-bound images or text colour contrast, so those stay manual.

Speed drifts as pages gain images, videos and scripts. Google's Core Web Vitals targets are a Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of page loads. I go deeper in my post on Webflow site speed.

A monthly Webflow maintenance checklist

This is the check I run on a care-plan site each month, in this order. You can run it yourself with a Webflow login and access to Google Search Console.

1. Submit every form on the live site, and confirm that the notification email and your CRM or automation tool both received the entry.
2. Open Site settings and check plan usage: bandwidth against the included amount, CMS items against your plan's limit, and the renewal date.
3. In Google Search Console, check the Pages report for new "not indexed" or 404 URLs, and the Core Web Vitals report for pages marked poor.
4. Run PageSpeed Insights on the home page and your busiest template, and compare the result with last month's.
5. Crawl the site for broken internal and outbound links, then fix them or add 301 redirects.
6. Open the Audit panel and clear its flags. Then check text contrast and the alt text on CMS images by hand.
7. Review custom code in site and page settings. Remove scripts for tools you no longer use and test the ones you keep.
8. Go through the CMS: publish or delete stale drafts, check scheduled items, and update prices, people and dates.
9. Read Webflow's updates and feature sunsets pages for anything that touches your site.
10. Review access. Remove people who've left, drop seats nobody uses, and confirm everyone has two-factor login on.
11. Save a named backup before any large change.
12. Write three or four lines on what changed and what's next, so the next person knows.

Once a quarter, add three things: compare your plan with real usage, review the five pages that bring the most traffic, and test the site with a keyboard and a screen reader.

What should a Webflow care plan include?

A Webflow care plan should state its hours, its turnaround time and exactly what the monthly check covers. If any of those is vague, you can't tell whether you're getting what you pay for. A Webflow support retainer billed by the hour works too, as long as the same three things are written down.

Before you sign any plan, mine included, look for these:

• A set number of hours a month, and what happens to unused hours.
• A turnaround time in business days for normal changes.
• A monthly check of forms, links, speed and errors, with a short written report.
• Monitoring of forms and integrations, as well as page edits.
• Handling of Webflow's platform changes, such as retired features and plan renewals.
• A clear list of what's excluded, including who pays Webflow and your domain registrar.
• A notice period to change or stop the plan.
• A review of the build first, if the person looking after the site didn't build it.

How much does Webflow website maintenance cost?

Published Webflow maintenance prices run from about $400 a month for a freelancer's 5-hour plan to $8,000 for an agency's 80-hour retainer. Most of the range is hours: plans that look expensive usually include 20 to 80 hours a month.

Sources: the Contra listing, which bills extra time at $50 an hour; theCSS Agency (updated 11 Jun 2026), which also puts light freelancer support at "a few hundred to about $1,000/month"; and BRIX Templates (updated Nov 2025), which also lists unlimited-request plans at $1,495–$5,000.

Divide price by hours to compare plans fairly. The 20-hour agency retainers in BRIX's figures work out to $100–$150 an hour, and the 5-hour Contra plan to $80. My plans come to $36–$38 an hour, partly because I work from New Delhi and partly because I'm one person with no account team to pay for. You get the developer directly, and you don't get an on-call support desk.

Your Webflow Site plan, your domain and any Webflow add-ons are billed on top of any care plan, by Webflow or your registrar.

My Webflow care plans

My care plans are $150, $290 or $550 a month, for 4, 8 or 15 hours of changes. They run month to month with 30 days' notice to change or stop, and paying yearly gets you two months free. The tiers are listed on my Webflow maintenance service page.

Every plan includes the monthly check of forms, links, speed and errors, changes to pages and content, form and integration monitoring, upkeep of custom code, handling of Webflow platform changes, and a short monthly report. Unused hours roll over one month, then expire. If a month needs more, I tell you before you go over, then either quote the extra work or move you up a plan, whichever costs you less.

I also look after sites I didn't build. I review the build first, and the plan reflects what I find. Sites I build also come with 30 days of free fixes after launch, separate from any care plan.

I don't offer round-the-clock, on-call support with guaranteed response times. If your site needs that, an agency with a support team is the better fit. New features beyond your plan hours, such as a calculator or a new integration, are quoted separately as custom code work.

Do you need a Webflow care plan at all?

Not always. If your team edits content in Webflow, the site has little custom code, and someone will run the checklist above every month, you can skip a plan and pay for one-off jobs when they come up.

A plan makes sense when the site brings in leads through forms and integrations, when it runs custom code, or when nobody on your team will open Search Console each month. It also helps when Webflow changes something, since the person on the plan has already read the notice.

To set a plan, book a 30-minute call on Zoom. Send the site link when you book, so I can look at the build before we talk.