Keeping Your Website Fit

Subheader

Stay effective and keep improving after launch

Lead-in

Launching your site isn’t the end of the work. That’s the bad news.

Even after you settle back into your day-to-day, your website still needs you. There’s still so much you can and should do.

The good news: the work spreads out across the year, and the effort rises and falls. But measuring your data and making steady improvements is needed to keep your website effective long after launch.

Featured Image

group of work colleagues discussing strategy in a meeting

Sections

Launching a new site can be disruptive—to your users, your search traffic, your editors, and your bottom line. That’s normal. People resist change, so expect some negative feedback from regular visitors (and your own team) who liked things the way they were.

Over time the positives should outweigh the negatives, and your improvements will prove themselves out. But you need to keep paying attention. Only once the site is live can you track how well it’s actually landing.

Things to be tracking:

Bug testing and triage — almost every launch ships with a few bugs; have a system to track and resolve them as they surface.
Analytics — watch for any drop in traffic or engagement on your key pages.
Search performance — a tool like Google Search Console flags pages that aren’t being indexed or found. You may need redirects where URLs have changed.
Performance and accessibility —even if both passed at launch, scan again on the live site; the production server can behave differently than your test environment.

You’re not redoing anything yet. You’re confirming it all works as intended and staying ready for quick fixes. A good support team can handle this for you, if you’d rather outsource it.

Once the stress of launch passes, you can move into a more predictable maintenance schedule.

On a CMS like Drupal, that means regular software updates, both to core and to any modules you run. Updates come out steadily, from critical security patches and bug fixes to new features and enhancements.

Regular updates keep the site secure and make it less likely that any single update breaks something. Let updates pile up and run several at once, and you raise the odds of errors, and make them harder to diagnose.

Beyond software, your content needs regular attention too. Scan monthly for accessibility compliance, spelling and grammar, broken links, performance, and SEO.

Testing all of that by hand every month is a lot of work. Fortunately, several site-monitoring tools can help. They crawl your site automatically, run tests against each of these concerns, and document the findings for you and your support team.

Popular options include Siteimprove, DubBot, and Acquia Web Governance, focused mainly on digital governance, accessibility, and quality assurance. Most also include SEO checks for the core, on-page elements such as URLs, page titles, and meta descriptions.

Sites drift over time. Content changes, needs change, and things break. A full site crash is obvious. The smaller problems are harder to spot.

Twelve months after launch, and every year after, we recommend a series of audits to catch problems that come with the passing of time.

Audits may include:

Design — are pages still consistent, professional, and on-brand? Do your images and design choices still serve your message?
Search — how is your internal site search performing? What does the data show, and where could it improve?
Accessibility — are there lingering issues from automated testing to address? Are editors following the compliance guidelines on new content? Have you repeated your manual testing? Any new standards to account for?
Security— is your server locked down and personal data protected? Are backups still running as planned? Have spam and bots affected your traffic?
Content— is your information still accurate, clear, and relevant? Is the voice consistent? Does the copy still serve your goals and audience?
Performance — how fast do pages load across devices? Any new (or lingering) blockers to clear?

In each case, the point isn’t to fix what was wrong at launch. It’s to address what’s changed since.

Take accessibility. Even with monthly automated WCAG testing, automated tools have limits—by most estimates they catch only 50% of accessibility issues. Manual testing is needed to catch the rest.

That means keyboard testing, screen-reader checks, and reviewing the semantic structure of key pages. You may have alt text on your images—but does it actually make sense? Do your videos include useful transcripts and captions? And with accessibility deadlines approaching, have you made your documents accessible too?

Under our ongoing support plans, there are a few ways to handle this work. Clients who’ve banked unused hours can put them toward any of these audits. Or we scope a mini-project to take them on.

Keeping your site secure and current is critical. But it’s only the baseline. To be truly effective, a website needs continuous improvement.

No amount of upfront planning beats watching how people actually use the site—seeing what works and fixing what doesn’t. There are a few ways to address this.

Robust reporting

Which metrics matter most for your site, and how easily can you track them? Traffic and engagement are always central to knowing where people drop off, and what brings them in.

But what outcomes are you after? Are there specific events to track, such as registrations, forms completed, appointments scheduled, applications submitted, etc.?

Good decisions need good data. By launch, you should have an analytics dashboard that puts every key data point at your fingertips. The easier it is to read, the more likely your team is to actually use it and build on it.

And as trends and technology change, your reporting needs to keep up. For example, can you measure how much of your traffic now comes from AI? How are you showing up in citations?

Idea boards and mini-projects

Do you and your team have a place to capture new ideas as they come, and a way to act on them when the time (and budget) is right?

For our clients, we offer regular check-ins and, optionally, an idea board—a space to record new initiatives, improvements, and questions whenever they come up. When budget frees up, or the need grows urgent, we move an idea into action: a mini-project or support ticket, with a time-and-cost estimate and the right people assigned.

Without a system in place, new ideas will fall through the cracks. But it’s those new ideas that give your site life, and let you build upon what you’ve learned–from analytics, team discussions, new tools, changing regulations, and shifting trends.

I’ve written about this elsewhere, but the question hanging over all this maintenance and improvement is: when is it time for the next full redesign? Or do you even have to?

The short answer, of course, is that it depends. If your organization is going through major shifts—mission, brand, services—a full redesign is worth considering.

But if you keep the site current with continuous improvement, you may be able to put off a full redesign indefinitely. Rather than budgeting for a large, costly rebuild, invest steadily—month to month and year to year—to keep the site effective and engaging.

The total cost may come out similar. The difference is a site in a state of continuous engagement, instead of one playing catch-up every three to five years after a long, slow slide.

About the Author

About the author