“Website support” gets used as a catch-all term, usually shorthand for “someone you call when something breaks.” That’s part of it, but it’s the smallest part. What website support includes should cover four distinct kinds of work: stabilizing what you have, assessing where it’s falling short, improving it on purpose, and evolving it as your goals change. Skip any one of those and you end up either stuck in pure break-fix mode or paying for redesign work that regular attention would have made unnecessary.
If you’ve read Your Website Isn’t Delivering the Results You Need. Now What?, you’ve already seen the short version of this list tucked into an FAQ entry. We’ve also written about seven specific tasks that belong in a support plan, the tactical, get-your-hands-dirty kind of work. This post sits between those two: what website support includes, broken into four parts, and what it looks like in practice whether you’re running WordPress, Drupal, or something else entirely.
Elements of Support: What Website Support Includes
Assess
If you don’t know what’s wrong, you can’t fix it. And sometimes, you’re so close to the problems that you’ve stopped seeing them. Assessment means auditing some of the things you take for granted: usability, accessibility, performance, SEO, integrations, technical debt. These things all land in a “do it later” pile that gets ignored as part of the day-to-day.
This is where that earlier list of tasks actually lives. On WordPress, that means running a template and plugin audit. On Drupal, it’s reviewing content types, paragraph bundles, and the module bloat that accumulates over a few content migrations. The platform changes the specifics, but the question stays the same: what’s actually being used, and what’s just sitting there?
Stabilize
Stabilize is the floor everything else stands on: hosting, security patching, and uptime monitoring. You know, the stuff that wakes you up in the middle of the night when it’s broken, and is invisible the rest of the time?
On WordPress, that means core, theme, and plugin updates applied on a schedule instead of after something breaks, plus monitoring that catches a spike in failed login attempts or a slowing page before a visitor does. On Drupal, it’s the same idea applied to module updates and security advisories, which come from Drupal’s own security team rather than a patchwork of third-party plugin maintainers, so the cadence looks a little different but the discipline doesn’t. On other platforms, the update mechanism changes, but the principle holds: patch before something breaks, not after.
This is the behind-the-scenes work to keep the lights on. It’s also the foundation that everything is built on, which is why you need to keep cracks at bay.
Improve
Improve is where assessment turns into action: UX refinements, feature work, performance optimization, accessibility remediation, and content management, the work that determines whether your team can actually keep pace with your own campaign calendar. This is the part most people picture when they hear “support,” the actual fixing.
Content management is worth calling out on its own, since it’s the piece most often treated as a UX nice-to-have instead of an operational requirement. When a marketer can’t launch a new page without a developer, that’s not a fact of life, it’s friction support is supposed to remove. On WordPress, that usually means building or cleaning up Gutenberg block patterns so your team can assemble a page from approved pieces. On Drupal, it means configuring Layout Builder permissions so editors get real flexibility within guardrails. Either way, this is the work that shows up in your campaign calendar as much as your analytics, faster launches, fewer bottlenecks, less time waiting on a ticket queue. If you’re not sure how much this is actually costing you, that’s exactly what the Campaign Agility Test is built to surface.
Evolve
Evolve is the part that gets skipped most often, because things aren’t on fire anymore. There’s no broken form demanding an emergency fix, no security flaw that’s being exploited. It’s just a backlog of decisions about where the site could go next, and nobody owns them.
This is also where the bigger conversation should happen on purpose instead of by accident. Perhaps your next step is a platform migration, a rolling redesign, or even a full rebuild. Most organizations don’t decide they need a redesign. They wake up one day and realize they’ve needed one for a year and nobody said so. A partner who’s actually been on your site, assessing it and improving it along the way, is in a position to tell you that before it becomes obvious. One who only shows up when something’s broken is guessing right along with you.
You Don’t Have to Choose Between Supporting Your Site and Improving It
Here’s the real answer to “how do I improve my website without starting over”: you don’t. You stabilize what’s already working. You look at what isn’t working and fix it with purpose, not duct-tape and chewing gum. And you repeat that process as your goals change. None of that requires tearing anything down, and none of it happens by itself.
Not every site needs all four of these at the same intensity. Some organizations are one good Stabilize layer away from sleeping through the night. Others need Assess and Improve running on a regular cadence to keep pace with their own goals. A few need all four, including someone helping them figure out where the site should go next. Our Support page breaks down what each level looks like in practice.
That’s the reality of what website support includes. It’s not a list of services tacked onto a contract. Think of website support as four different ways of paying attention to something that’s quietly doing real work for you every day.
