Back to Case Studies
OperationsOwn system· Sep 2026

Taking Website Publishing Off a Person

Website posts were copied onto my two sites by hand, and the hand step kept failing. I moved the job to a daily script, with checks that stop a bad post before it goes live.

Key Results

  • 3 hand-done website publishes in a row had failed before the switch
  • 8 of 8 daily 09:30 runs from 17 to 24 Sep 2026 ran and logged a result
  • 4 items saved to the sites by the script in 9 days
  • 4 live runs found an item already published and skipped it, 0 overwritten
  • 1 case study held back 2 days in a row by a check, with an alert each day

What was broken

Every week three pieces go onto my two websites: a case study on one day and a blog post on each of the other two. A person on my team did this by hand. They read the week's posting sheet, opened each site's admin page and copied every piece in.

It looked like simple work, and it kept going wrong. Three runs in a row failed. One title came through at 106 characters, one case study went live with its results, description, category and period all empty, and another title came through at 85 characters, all in capital letters.

None of this was the person's fault. Copying text into a form is exactly the kind of work a tired person gets wrong, and nothing checked the page before it went live.

There was a second problem, and it was mine. I'd written myself a note saying that only a signed-in browser could write to the sites, so I believed the hand step couldn't be removed. The note was right that one key was locked, but it drew far too wide a conclusion from that one fact, and I never went back to test it until the failures forced me to.

What I built

First I tested the belief. Each site has its own admin login, and a script can log in with the admin password, get a session and write a post or a case study, with no browser and nobody sitting at the machine. I checked this on both sites, and it worked. The login details stay private and never appear in any log.

Then I built a daily job that runs at 09:30. It reads the posting sheet, finds the website items and sends each one to the right site. It leaves the social posts in the same sheet alone, because those still need a real person.

Before anything is saved, a set of checks runs:

  • Title length. The title plus the site name must fit in 60 characters.
  • No titles written in all capitals.
  • No empty fields.
  • No client names in a case study.
  • No writer's notes left in the text.
  • The live site comes first. If the item is already there, the job skips it.

If any check fails, nothing goes up. The job writes the reason to a file and queues an alert for me. I added the alert on purpose, because I'd never open the file on my own, and a job that stops without telling anyone looks exactly like a quiet week.

I also decided that I won't approve each post. Only two kinds of item still come to me: a case study that might name a client, and anything that fails my voice check.

What changed

The daily job ran on all 8 days from 17 to 24 September, and each run left a clear line in the log, even on days when there was nothing to publish.

In 9 days the script saved 4 items to the sites. On 4 live runs it found an item that was already published, skipped it and overwrote nothing. That matters, because saving the same item a second time would have reset the date on a live page without anyone seeing it happen.

The checks did their job too. One case study was held back two days in a row because a setting it needed was missing, and an alert went out each day. Once the setting was fixed, the same case study went live that afternoon.

Social posts stay with the person who handled them before, because that's where a human is really needed.

What I would do differently

I'd test my own notes sooner. One wrong line in a note kept a person on a copying job that a script could have done all along.

I'd build the "already live" check on the first day. Without it, a job that runs twice can undo its own work.

I'd treat counts with more care. The admin page on one site showed 21 posts while the public site showed 20, because one post was unpublished, so the admin number and the live number aren't the same thing.

And I'd write down how to change the login safely before I ever need to do it.

Want a similar result?

Let's talk about installing the right operating system for your business.

Book a Call

Pick a time that suits you.

Book a call