Two WordPress sites is a hobby. Five is a job you did not apply for. If you manage multiple WordPress sites — your own, or clients’ — this is about the ways people actually cope, and where each one falls down.
It is never the big things. Nobody forgets to renew a domain. What piles up is the small stuff: an image with no alt text, a headline too long for Google, a plugin update you keep meaning to look at, a contact form nobody has tested since March. Each one takes four minutes. You have forty of them across six sites, and no afternoon in which to do them.
It is never a single big failure. It is attrition.
First, be honest about where the time goes
It is worth timing yourself once, because the answer is usually not what people expect. Across the sites we look after, the work splits roughly like this:
- Getting in. Finding the right login, the right site, the right screen. Two or three minutes before any work starts.
- Finding out what is wrong. Clicking through pages to spot the missing description, the broken link, the image nobody described.
- The actual change. Usually the fastest part. Often under a minute.
- Checking it worked. Skipped more often than anyone admits.
The change itself is rarely the problem. It is the finding and the getting there. Any approach that only speeds up the typing is solving the wrong quarter of the job.
Four ways to manage multiple WordPress sites
1. By hand, one site at a time
It works. It is also the reason the list never gets shorter. Doing the same four-minute job on six sites is not twenty-four minutes — it is twenty-four minutes plus six lots of context switching, and by site four you have forgotten what you came in for.
Fine up to about three sites. Past that it quietly stops happening at all.
2. A multi-site dashboard
Tools like ManageWP and MainWP connect all your sites to one screen. They are built around maintenance: updates, backups, uptime, security scans. For that they are genuinely good, and if updates and backups are your problem, start there.
What they are not built for is the content itself. They will tell you a plugin needs updating. They will not tell you that eleven of your posts are going to Google with a summary nobody wrote.
3. WordPress Multisite
One WordPress install running many sites, sharing plugins and themes. Excellent when the sites are genuinely related — a chain of shops, a university’s departments, a network of local branches.
Wrong tool when they are not. Unrelated client sites on one Multisite means one update can break all of them at once, and moving a site out later is a genuinely unpleasant afternoon. If your sites have nothing to do with each other, this is not it.
4. Asking an assistant to do it
The newer option: connect your sites to an AI assistant, and describe what you want in ordinary words. It reads the sites, tells you what is wrong, and makes the change.
The interesting part is not the writing. It is the finding. Which brings us to the thing worth showing.
What “finding out what is wrong” looks like
This is a real shop with forty-three posts. One question, and the answer took a few seconds:
Check the SEO on my 12 newest posts.
Average 88/100 across 12 posts.
Two things worth your time:
1. Eleven of twelve summaries are auto-generated
from your excerpt. Only one was written by hand.
2. Every headline runs 62-75 characters. Google
cuts off around 60, so the ending never shows.Nobody had done anything wrong. The site looked fine. But eleven of twelve posts were reaching Google with a summary nobody had written, and every headline was being cut off mid-sentence in the search results.
Finding that by hand means opening twelve posts, scrolling to the SEO box on each, counting characters, and then checking what the live page actually serves — because most SEO plugins fill in a summary when you leave one blank, so the box being empty tells you nothing.
That is the part worth automating. Not the typing — the looking.
What to look for, whatever you choose
Five questions that sort the useful from the merely busy:
| Ask this | Why it matters |
|---|---|
| Does it read the live page or the database? | They disagree. An SEO plugin generates a summary when the field is blank, so the database says “missing” while Google sees something perfectly fine. Read the wrong one and you fix things that are not broken. |
| Does it check the change actually landed? | Saving a value and that value reaching Google are different events. A caching plugin sits between them. |
| What happens on the site you forgot about? | The site that has not been touched in a year is where the problems are. It needs to be as easy to reach as the one you use daily. |
| Does it need your password? | It should not. WordPress can issue a separate key for an application, revocable from your own profile in seconds. |
| What does it cost at ten sites? | Per-site pricing is fine at two and painful at twelve. Check the number you will be paying next year, not this month. |
The honest limits
None of this decides what to write, or designs anything. It does the work you already know needs doing, faster than you could click it. If you do not know what your sites need, no tool here will tell you what your business should say.
And whatever you use, keep backups. Anything that can change six sites quickly can change six sites wrongly, quickly.
Where PressHand fits
PressHand is the fourth option above. You connect your sites once — no password typing, WordPress issues a key that you can revoke yourself — and then you ask for things in plain words. It reads the live pages rather than the database, and checks that changes actually reached the page.
It is one payment for every site you own, not a monthly fee per site, which is the whole reason it exists. The list above is the honest version: if updates and backups are your problem, a maintenance dashboard is a better fit. If the problem is the forty small content jobs nobody gets to, this is what we built.
See what it costs, or compare it with the nearest alternative.