
Meta Title and Description Length: What Google Says (2026)
How long a meta title and meta description should be, what Google says about limits and rewrites, a before and after table, and a 7 step checking routine.
Web Design
Two plans can both cost the same each month and cover very different work. This guide gives you a checklist of what a monthly maintenance plan should include, how the list changes on Webflow, WordPress, Shopify and Framer, what plans usually leave out, and the red flags to watch for. Checked 3 November 2026.
A monthly maintenance plan is a standing agreement. Someone looks after your site every month, so you do not have to hire help each time something breaks. It is not a one-off fix and it is not a redesign.
Sellers describe these plans in similar terms. In the pages we read on 3 November 2026, common parts were monthly updates, backup checks, security scans, uptime monitoring and a monthly report. Higher tiers added speed work. Several sellers say new features, design changes, content updates and hosting are outside the base plan, and that anything outside it is quoted separately. Emergency work such as malware removal was included in the top tiers of one provider and sold on the side for the lower ones.
That last point is the lesson. The same word, "maintenance", covers a very small plan and a very full one. So read the task list before you read the price.
Use this list when you compare plans. A good plan answers each line in writing.
| # | Item | What to ask |
|---|---|---|
| 1 | Updates | What gets updated: the platform, plugins or apps, and the server software? How often? |
| 2 | Backups | How often, where are they stored, and how fast can you restore one? |
| 3 | Security and uptime | Who watches the site, and who is told when it goes down? |
| 4 | Fixes | Are broken forms, links and layouts fixed inside the plan, and is there a cap? |
| 5 | Content edits | Are small text and image changes included? How many per month? |
| 6 | Speed checks | Which pages are tested, and what do you receive afterwards? |
| 7 | Report | What lands in your inbox each month? |
| 8 | Accounts and exit | Are the domain, hosting and analytics in your name, and can you leave with everything? |
If a plan cannot answer item 2 or item 8 in a clear sentence, treat that as a warning. Backups decide whether a bad day is a small problem or a lost site. Accounts decide whether you can walk away.
The eight items do not weigh the same on every platform. This table shows where the work sits. The "Platform handles" column is the general split between a hosted builder and a self-managed site. Confirm the detail with the maker or the studio, since plans and features change.
| Item | WordPress | Webflow | Shopify | Framer |
|---|---|---|---|---|
| Updates | Core, theme, every plugin and the PHP version, so this is the biggest task | Platform is updated by the maker, your work is custom code and integrations | Platform is updated by the maker, your work is the theme and apps | Platform is updated by the maker, your work is any embedded code and plugins |
| Backups | Needed from the host or a plugin, and you should confirm restores work | Ask how versions are restored and how long they are kept | Ask how theme and product data are protected and restored | Ask how version history and restore work |
| Security and uptime | Scans, a firewall and login checks, since you own the stack | Mostly the platform, so the plan watches forms and third-party scripts | Mostly the platform, so the plan watches apps and staff access | Mostly the platform, so the plan watches forms and embeds |
| Fixes | Plugin clashes, white screens, broken layouts | Layout bugs, form errors, CMS issues | Theme bugs, checkout or cart script problems | Layout bugs, form errors, CMS issues |
| Content edits | Often billed apart | Common add-on, or part of a request queue | Product and page edits, often billed apart | Common add-on, or part of a request queue |
| Speed checks | Image, plugin and database weight | Image and script weight | App scripts are the usual cause | Image and embed weight |
| Report | Updates done, backups taken, scans run | Requests done, pages changed | Orders-side issues are yours, so ask what the report covers | Requests done, pages changed |
WordPress sits on the heavy end for a reason you can verify. The WordPress documentation says that minor core updates, which carry maintenance and security fixes, are enabled by default, while plugins and themes are generally not updated automatically (checked 3 November 2026, WordPress developer documentation). The same page says to back up before updating and to check that the backups can be used. So on WordPress, someone has to own the plugin and theme updates and the backup test. If a plan does not name that person, you are paying for less than you think.
For the PHP part of that job, see our guides on how to check and update PHP on WordPress and how to back up WordPress before a PHP update.
Most plans stop at routine upkeep. These are the jobs that tend to fall outside the monthly fee.
When a plan lists none of these as excluded, ask. A short exclusions line is often a sign nobody thought about it, not a sign that everything is covered.
Put the plans side by side, using the checklist, and score each line as included, capped or not included. Then check the allowance numbers.
| Question | Why it matters |
|---|---|
| How many edit requests a month? | A cap of two means the third request is billed or waits. |
| How fast is a request done? | "Within 48 hours" and "when we can" are very different promises. |
| Do unused requests roll over? | Many plans do not carry them, so you pay for edits you did not use. |
| Who responds in an emergency, and how fast? | Ask for a time, not an adjective. |
| What does the monthly report show? | A report that lists real work is proof the plan ran. |
Price comes last. Also check the notice period. Once two plans cover the same tasks, the cheaper one wins. If they differ in tasks, work out what the missing tasks would cost you on their own. Our cost guide has the published prices to compare against.
Maintenance keeps a site healthy. It does not grow traffic, and for that our website audit checklist is the better start.
A plan is not always the right answer. Keep it simple if one of these fits.
| Your situation | A sensible approach |
|---|---|
| A small Webflow, Framer or Squarespace site your team edits and rarely changes | Pay the platform bill and fix things as they come |
| A site that changes a few times a year | Pay for one-off help when you need it |
| A WordPress site | A plan, or a named person who owns updates, backups and security |
| A Shopify store with many apps | A plan or a twice-yearly app review |
This guide does not apply if you run your own hosting or have an in-house developer who already does these jobs. In that case, use the checklist to audit what they do, not to buy a plan.
We build and look after sites on Webflow, Framer, WordPress and Shopify, and also on Wix, Squarespace and custom builds. When a client asks about upkeep, we start with the eight-part list above and agree which lines they need, so the plan matches how often the site changes. Our Webflow maintenance service describes what a plan covers. For a build or a rebuild, our Webflow development and WordPress development pages explain how we work. Projects are priced from scope, never by the hour. The client owns the design, copy and code after the final payment, and the domain, hosting and analytics accounts sit in the client's name.
Most plans include updates, backups, security and uptime checks, fixes, speed checks and a monthly report. Content edits vary, so ask how many are included. Plans differ in the size of each task, which is why the written list matters more than the name of the plan.
It depends on the platform and the scope, and sellers publish wide ranges. Our maintenance cost guide lists the platform bills and the care plans six studios publish, with the date each was read. Use it to see where a quote sits.
It is worth it when your site changes often or runs on software that needs updates, such as WordPress. It is less useful for a small hosted site that rarely changes. Count the hours you would otherwise spend, and the cost of a day offline.
Commonly new features, redesigns, hosting, licences and large content work. Some plans also exclude emergency recovery after a hack. Always ask for the exclusions in writing.
Yes, though less than WordPress. The platform is looked after by its maker, but forms, integrations, content and layout fixes still need an owner. Our Webflow forms guide shows one area where small problems appear.
They need less server-side work than WordPress, because the platform runs the hosting. They still need someone to review apps, scripts, content and speed. Our Shopify website cost guide and Framer website cost guide show the running costs for each.
Ask for a monthly report that lists updates applied, backups taken and requests completed. You can also spot-check, for example by asking to see a recent backup date or the last update log. A plan that cannot show this is hard to trust.

How long a meta title and meta description should be, what Google says about limits and rewrites, a before and after table, and a 7 step checking routine.

WebP vs JPG for a website: keep WebP on the page, convert to JPG or PNG for uploads and email. Decision table and browser support checked 3 November 2026.

How many words fit a 1, 2, 5 or 10 minute speech, voice-over or explainer video, with pace ranges from sources read today and a table you can check.