Skip to content
William Alexander
  • Home
  • Case Studies
  • Personal Projects
  • Articles
  1. Home
  2. Articles
  3. What Marketing Directors Need to Know About Website Maintenance
Higher Ed Web

What Marketing Directors Need to Know About Website Maintenance

The non-technical guide to keeping your institution's website secure, fast, and effective

August 23, 2025 8 min read

Key Takeaways

  • Website maintenance is an ongoing investment, not a one-time cost—budget 15-20% of build cost annually
  • Security updates can't wait; a breach during enrollment season is a nightmare scenario
  • Performance degrades over time without active management; slow sites cost you applicants
  • Content maintenance is marketing's responsibility; technical maintenance is IT's
  • Document everything: hosting credentials, vendor contacts, update schedules, emergency procedures
Overview

Why This Matters to Marketing

You didn't get into marketing to manage server updates. But if you're responsible for your institution's web presence, website maintenance is now part of your world—whether you like it or not.

I've worked with marketing directors at universities who inherited websites they didn't build, running on platforms they don't understand, maintained by vendors they've never met. When something breaks, they're the ones explaining to leadership why the admissions portal is down during application season.

I thought maintenance was IT's problem until our site got hacked. Then it was very much my problem—I was the one on the phone with the president.

Marketing Director, Regional University

This article won't turn you into a systems administrator. But it will give you enough understanding to ask the right questions, make informed decisions, and avoid the preventable disasters that derail careers and enrollment goals.

Framework

The Four Pillars of Website Maintenance

Website maintenance breaks down into four categories. You don't need to do all of this yourself, but you need to ensure someone is.

1. Security

Protecting your site from hackers, malware, and data breaches. This includes software updates, security monitoring, SSL certificates, and access control.

2. Performance

Keeping your site fast and reliable. Includes hosting management, database optimization, caching, image optimization, and uptime monitoring.

3. Functionality

Ensuring everything works correctly. Forms submit, links don't break, integrations stay connected, and features function as expected across devices.

4. Content

Keeping information accurate and fresh. Outdated content damages credibility and SEO. Broken links frustrate users and hurt search rankings.

The Marketing/IT Split

Generally, IT owns pillars 1-3 (security, performance, functionality). Marketing owns pillar 4 (content). But marketing needs visibility into all four because they all affect the user experience you're responsible for.

Security Deep Dive

Security: What Can Go Wrong

University websites are high-value targets. You have student data, financial information, and a .edu domain that spammers love to exploit. A breach isn't just embarrassing—it can trigger federal reporting requirements and erode the trust you've built with prospective students.

The Non-Negotiables

  • Software updates: WordPress core, plugins, and themes need updates within days of release—not months. Hackers actively scan for sites running outdated software.
  • SSL certificate: That padlock in the browser. It encrypts data and is required for any forms. Should auto-renew, but verify it's happening.
  • Backups: Daily automated backups, stored off-site, tested regularly. If you can't restore from backup, you don't have backups.
  • Access control: Who has admin access? Is it documented? Do you revoke access when people leave? Use strong passwords and two-factor authentication.
  • Monitoring: Someone should be watching for suspicious activity, failed login attempts, and file changes.

The 48-Hour Rule

When a security update is released for your CMS, you have roughly 48 hours before hackers start mass-scanning for vulnerable sites. If your maintenance process can't turn around critical updates that fast, you're at risk.

Questions to Ask Your IT Team or Vendor

  1. How quickly are security updates applied?
  2. How often are backups taken, and where are they stored?
  3. When was the last backup restoration test?
  4. Who has admin access to the website?
  5. What monitoring is in place for security incidents?
Performance Deep Dive

Performance: Speed Matters More Than You Think

Every second of load time costs you visitors. Studies show 53% of mobile users abandon sites that take over 3 seconds to load. For a university during application season, slow performance directly translates to lost applicants.

What Affects Performance

  • Hosting quality: Cheap hosting means shared resources and slow response times. University sites need quality hosting, especially during traffic spikes.
  • Database health: Databases accumulate clutter over time—post revisions, spam comments, orphaned data. Regular cleanup keeps queries fast.
  • Image optimization: A single unoptimized image can add seconds to load time. Every image should be compressed and properly sized.
  • Caching: Proper caching serves pre-built pages instead of generating them fresh for every visitor. Dramatic performance improvement.
  • Code efficiency: Poorly coded plugins and themes slow everything down. Regular audits identify the culprits.

The Enrollment Season Test

Your site needs to perform well under peak load, not just average load. Test performance under stress before application deadlines, not during them. Traffic spikes can expose problems that don't appear during normal operation.

Metrics to Monitor

Metric Target Why It Matters
Page Load Time Under 3 seconds Users abandon slow sites
Time to First Byte Under 600ms Indicates server responsiveness
Uptime 99.9%+ 99% = 87 hours of downtime/year
Mobile Performance Score 80+ Most users are on mobile
Content Deep Dive

Content Maintenance: Marketing's Domain

This is where marketing can't delegate. Outdated content is your responsibility, and it's more damaging than most people realize.

The Content Decay Problem

Content doesn't stay fresh on its own. Faculty leave. Programs change. Phone numbers get reassigned. Events pass. Links break. Without active maintenance, your site gradually becomes a liability.

Google notices. Outdated content ranks lower. Broken links hurt your SEO. Users notice too—nothing says "we don't care" like a 2023 calendar on your 2026 website.

A Quarterly Content Audit Checklist

  • ☐ Check all contact information for accuracy
  • ☐ Verify faculty and staff listings are current
  • ☐ Review and remove past events
  • ☐ Update program information and requirements
  • ☐ Test all forms to ensure they submit correctly
  • ☐ Run a broken link checker
  • ☐ Review analytics for underperforming pages
  • ☐ Check that emergency/safety information is current

Assign Content Owners

Every section of your site should have a named person responsible for its accuracy. Generic ownership means no ownership. Create a content governance document that maps pages to people.

Financial Planning

Budgeting for Maintenance

Here's the uncomfortable truth: your website is never "done." It requires ongoing investment to remain secure, functional, and effective.

The 15-20% Rule

Budget 15-20% of your initial website investment annually for maintenance. A $100,000 website needs $15,000-20,000 per year. This covers:

Category Typical Annual Cost Notes
Hosting $2,000-10,000 Quality managed hosting, not bargain shared
Security & Updates $3,000-8,000 Regular updates, monitoring, SSL
Technical Support $3,000-10,000 Bug fixes, troubleshooting, small changes
Performance Optimization $1,000-3,000 Database cleanup, speed improvements
Content Updates Varies Often internal staff time

This doesn't include major new features, redesigns, or significant content creation—those are separate capital projects.

The False Economy

Cutting maintenance budget doesn't save money. It defers costs while accumulating risk. When something breaks—and it will—emergency fixes cost 3-5x what prevention would have. Plus the reputational damage of downtime.
Best Practices

Documentation: Your Insurance Policy

What happens if your web developer wins the lottery tomorrow? Or your IT contact retires? Document everything.

Essential Documentation

  • Hosting credentials: Where is the site hosted? Login information? Who's the account holder?
  • Domain registration: Where is the domain registered? When does it expire? Who can make changes?
  • CMS access: Admin accounts, password recovery options, two-factor backup codes
  • Vendor contacts: Who built the site? Support contacts? Contract terms?
  • Integration credentials: APIs, third-party services, analytics accounts
  • Emergency procedures: Who to call when the site is down? Escalation path?

Store this documentation securely but accessibly. A password manager or secure shared drive works. Don't put it all in one person's head.

Implementation

Building Your Maintenance Calendar

Maintenance shouldn't be reactive. Build a calendar that ensures nothing falls through the cracks.

Sample Maintenance Schedule

Weekly:

  • Check uptime monitoring for issues
  • Review security alerts
  • Apply any critical security updates

Monthly:

  • Apply non-critical software updates
  • Review analytics for anomalies
  • Test key conversion paths (application, contact forms)
  • Check backup status

Quarterly:

  • Content audit (see checklist above)
  • Performance testing
  • Security audit
  • Review and update documentation

Annually:

  • Full UX review
  • Accessibility audit
  • Vendor/contract review
  • Budget planning for next year
  • Disaster recovery test

Frequently Asked Questions

How much should a university budget for website maintenance?

Plan for 15-20% of your initial website investment annually. A $100,000 site needs $15,000-20,000/year for hosting, security, updates, and improvements. This doesn't include content updates or major new features—those are separate.

What happens if we skip website maintenance?

Security vulnerabilities accumulate, making you a target for hackers. Performance degrades as software becomes outdated. Eventually, something breaks catastrophically—often during a critical period like enrollment season. Recovery costs 3-5x what prevention would have.

Who should be responsible for university website maintenance?

Technical maintenance (updates, security, hosting) belongs with IT or your web team. Content maintenance (accuracy, freshness) is a shared responsibility with department stakeholders. Marketing should own the overall experience and coordinate both sides.

How often should a university website be updated?

Security updates: within 24-48 hours of release. Core software updates: monthly. Content audits: quarterly. Analytics review: monthly. Full UX review: annually. The key is consistency—sporadic maintenance creates risk.
Higher Education Website Maintenance Marketing Web Strategy Leadership
William Alexander

William Alexander

Senior Web Developer

25+ years of web development experience spanning higher education and small business. Currently Senior Web Developer at Wake Forest University.

Related Articles

Higher Ed Web

Why WordPress Multisite Makes Sense for Universities

8 min read
WordPress Enterprise

Why Your WordPress Site Is Slow (And How to Fix It)

10 min read

Need help with your university's website maintenance?

I help institutions build sustainable maintenance programs that protect their investment.

© 2026 williamalexander.co. All rights reserved.