CMS optimization automation
One script logs into all eleven hotel sites and fixes the same mistake everywhere at once.
Eleven property sites, all on the same CMS (ProcessWire), all built by an outside agency, all carrying the same recurring errors. A typo in a shared template. Wrong-state boilerplate pasted into a description. An amenity a property no longer has, like a pool advertised years after it was gone. Fixing that by hand, one site at a time, is exactly the kind of work that never actually gets done.
How it works
A Python tool drives a persistent Chrome profile logged into all eleven CMS installs, scheduled on the always-on mini. The fixes are declarative, just a list of edits, and the applier is dry-run by default. It only writes with an explicit apply flag, then verifies on the live page. The working model is one fix swept across all eleven at once, so I review a single batch and it lands everywhere together.
- A typo sweep across the shared template, portfolio-wide in one pass
- A "Book Direct & Save" banner added to every site that lacked one
- A false-amenity scrub that stripped features a property no longer has
- Session handling that logs in fresh in one process each run, because the CMS holds its session cookies in memory
It is live and running. Because the edits are declarative, each new content policy is a few lines instead of eleven manual sessions, and the dry-run plus live-page verify means I trust it before anything publishes.
This is a marketing coordinator's month of busywork turned into a scheduled job. The exceptions (a typo, a stale amenity, a missing book-direct nudge) get caught and fixed once, everywhere. I set the policy, the agent enforces it across the whole portfolio.