Blog / How the internet works /

What a web administrator does every week

Ask five people what a web administrator does and you’ll get five answers. “Fixes the website.” “Does the SEO.” “Uploads the news.” “Something with servers?”

All of them are partly right. The truth is that the job is mostly rhythm: a set of small, repeated checks that stop big problems from happening. I’ve been doing it for a few years at Royal Arts Academy, where I look after the digital content and the WordPress side of things, and the week has a shape. Here’s roughly what it looks like, and how you can borrow it if you run a site of your own.

I covered the wider job in what a web administrator actually does (it’s not just SEO). This post is the calendar version.

Monday: look before you touch

The week starts with reading, not changing.

  • Check the site is up and working. Open the homepage, a recent post and a key page, ideally on a phone as well as a laptop.
  • Look at what happened over the weekend. Any uptime alerts? Failed form submissions? Odd comments? Spam in the inbox?
  • Check analytics and Search Console. I’m looking for sudden changes, not detail: a traffic drop, a page that vanished from search, a new error report.
  • Plan the week’s content. What’s scheduled, what’s late, what needs a decision.

If something is broken, Monday is when you find it before your visitors do. It’s not glamorous, but it’s the most valuable hour of the week.

Tuesday and Wednesday: the production days

This is where the visible work happens.

  • Publishing. Writing, editing or formatting posts, adding images, setting titles and descriptions, checking links, scheduling.
  • Images. Resizing and compressing before upload, writing sensible alt text and file names. Big uncompressed images are the quickest way to slow a site down.
  • Pages and layout fixes. A button that moved, a banner to replace, a form that needs a new field.
  • Working with the team. Writers, designers and presenters send requests in all directions. Half of the job is turning a vague “can we change the thing” into a clear task.

A publishing calendar makes this calmer. I wrote about what one did for us in what a publishing calendar did for our content team.

Thursday: maintenance

Thursday is for the unglamorous things that keep a site healthy.

  • Back up before changing anything. Every time.
  • Update safely. Small plugin and theme updates first. Larger ones, like a page builder or anything touching forms or checkout, get more care. I read the changelog and update one at a time, so if something breaks I know what did it.
  • Check security basics. Who logged in? Any new admin users? Old accounts that should be removed?
  • Look for broken links and missing images. Links rot quietly. A weekly look beats a yearly clean-up. I explained how in how to find and fix broken links on a WordPress site.
  • Spam and comments. Clear them out before they pile up.

The point of doing updates on a set day is that you never end up with a site six months behind because “it’s working, so don’t touch it”. Outdated software is one of the most common reasons sites get hacked. I made that case for phones in software updates: why “remind me tomorrow” is a security risk, and it applies to websites just as well.

Friday: tidy up and look ahead

  • Check speed. Run a page or two through a test, and see whether anything new has made them slower.
  • Review search performance. Which pages are getting impressions, which queries are rising, which pages could do with a better title or an internal link.
  • Update the notes. A short log: what I changed, what broke, what to watch. Future you will be grateful.
  • Prepare next week. Drafts ready, images sized, requests answered.

The unplanned part

Every week also has the stuff that wasn’t in the plan:

  • A page that suddenly looks wrong after an update.
  • A request that “must go live in an hour”.
  • A login that stopped working.
  • A form that sends emails to the wrong person.
  • A hosting hiccup that has nothing to do with you but is still your problem.

I’d say about a fifth of the week disappears into things like this, though that’s a feeling, not a measurement. The planned routine matters because it’s what protects you when these show up. If you know the site was backed up on Thursday and monitored all week, a fire is annoying rather than frightening.

What you can copy

If you run your own site, you don’t need an hour a day. A one-hour weekly routine covers most of it:

  1. Check it’s working (home, key page, mobile).
  2. Back up, then update.
  3. Look at Search Console for errors and big changes.
  4. Check forms and contact paths actually deliver.
  5. Write down what changed.

Do those five things in the same order each week and you’ll catch most problems early.

What the job isn’t

It isn’t constant fixing, and it isn’t a purely technical role. Much of it is communication: translating between people who want things and a site that has limits. It’s also not about knowing everything. You need to know where to look, and to be calm when something breaks.

Key takeaways

  • A web administrator’s week is mostly repeated checks, with some fires in between.
  • Read first, change second.
  • Back up before updating, and update on a schedule.
  • A written log saves hours later.
  • You can run a small site on one hour a week if you’re consistent.

What would your five-point Monday check look like for your own site?