How to Manage Multiple Websites From One Dashboard (Without Losing Track of Any of Them)
- RedClaw Performance Team
- RedClaw Performance Team
- Date
- Reading time
- 10 min read
How to Manage Multiple Websites From One Dashboard
TL;DR: To manage multiple websites from one dashboard you need four things before any software: an inventory of every domain, registrar, expiry date and Search Console owner; a role model where the people who publish can't change the site; monitoring that checks each site shows the right content, not just that it answers; and a written handover for when an agent or branch manager leaves. The dashboard is where those rules live. Write the rules down first; the tool you need follows from them. We run more than 20 SEO↗ sites of our own, and most of the failures below are ones we hit ourselves.
Start with an inventory, not a tool
A multi-site inventory is one row per site with the domain, registrar account, expiry date, Search Console verified owner, GA4↗ property, template and the person responsible.
Every multi-site setup we've seen go wrong had a missing column here, usually the registrar account or the Search Console owner. Those two decide whether the head office actually controls a site. If the domain sits in an agent's personal registrar account, the site leaves when the agent does. If an outside agency is the only verified Search Console owner, HQ doesn't see warnings first.
| Column | Why it matters |
|---|---|
| Domain and registrar account | Whoever holds the registrar login holds the site |
| Expiry date | A lapsed agent domain becomes someone else's expired domain |
| Search Console verified owner | Receives manual-action and security notices |
| GA4 property and account | Traffic history stays with the account owner |
| Template | Tells you which sites a template change will hit |
| Responsible person | Who publishes, and who replaces them |
| Status | Live, paused, handing over |
The expiry column isn't busywork. ICANN's Expired Registration Recovery Policy↗ (checked 3 November 2026) requires registrars to send at least two reminders, about one month and about one week before expiry, and another within five days after. Those reminders go to the registrant's email. If that's an agent's personal inbox, nobody at HQ sees them. Put the expiry date in the inventory and send your own reminder 30 days out.
Pick the setup that matches who publishes
There are three common setups: separate sites with a management tool on top, WordPress Multisite, and a managed multi-tenant CMS. The right one depends on who publishes and who maintains.
| Setup | Who maintains the software | What publishers can change | Good when |
|---|---|---|---|
| Separate sites + management tool | You, per site | Whatever their role allows on each site | Sites are different products with different stacks |
| WordPress Multisite | Your Super Admin, once for the network | Site admins can still switch themes and change options | You have a WordPress developer in house |
| Managed multi-tenant CMS | The vendor | Only what the platform allows | Publishers aren't technical and turn over often |
On WordPress Multisite, the roles documentation↗ (checked 3 November 2026) reserves installing and updating plugins and themes for the Super Admin, but a site Administrator still keeps switch_themes, edit_theme_options, manage_options and delete_site. That's fine if each site's admin is your own staff. For agents, use a lower role. We compare costs in detail in multi-tenant CMS vs WordPress Multisite.
Separate "publish" from "change the site"
The single rule that saves the most time: the people who write content should not be able to change layout, menus, settings or tracking.
Agents and branch managers know their market. They are not web developers, and they shouldn't need to be. Most breakage we've seen on agent sites comes from someone changing a setting they didn't understand: a theme switch, an SEO plugin turned off "because it nagged", a tracking snippet pasted into a footer. Narrow roles stop all of that. HQ then owns structure and the agent owns content.
This is how we specified the role model for our own platform, the RedClaw Site Network, which is still in development: the head office has one account that opens and sees every site, and agents can only write posts and upload images. There's nothing else in their view to break.
Monitor content, not just uptime
Uptime checks tell you a server answered. For many sites you also need to check that each one shows the right site, the right page and the expected text.
We learned this on 4 July 2026. A deploy from the wrong folder put our main marketing site into the project behind our internal operations dashboard. The dashboard's home page returned 200, because it was now serving the marketing site, and the login page returned 404. It stayed that way for two days before anyone noticed. A plain uptime check would have stayed green the whole time. Our fix was a check every 10 minutes on three production URLs that looks for a piece of text that only the correct app shows, and alerts the owner if it's missing.
For a network of agent sites, the equivalent is cheap: for each site, pick one string that only that site's home page contains, usually the agent's name, and check for it. A site that shows the wrong agent, an empty template or another site's content fails the check even though it's "up".
Check that scheduled jobs did something
A scheduled job that runs on time but changes nothing looks exactly like a healthy job. Check its output, not its run log.
Our own example: a daily job was meant to redeploy our blog so that posts dated for that day would appear. On 20 September 2026 we found it had been pushing an empty commit every day to trigger a deployment hook that had stopped working back in June 2026. The job's history was all green. Scheduled posts weren't going live. We rewrote it to deploy directly, and to say plainly in its summary when it can't.
With many sites the same thing hides in backups, sitemap submissions and scheduled publishing. For each one, write down what proof of success looks like (a backup file of the expected size, a sitemap read date in Search Console, the post's URL returning 200) and check that, at least weekly.
Keep links and SEO rules consistent across sites
When many people publish, link formats, titles and outbound link attributes drift. Rules enforced in the publishing tool beat audits after the fact.
On our main site alone, with one editorial team, an audit on 30 August 2026 found 240 of 447 internal link targets (54%) did not return a clean 200: wrong URL forms, extra redirects, links to pages we'd removed. Spread that across 20 sites and 20 authors and you can't audit your way out of it. The rules have to be in the editor.
The rules we enforce in software rather than in a style guide: required title, description and author fields; outbound links to sign-up or commission pages marked rel="sponsored" automatically; canonical tags and sitemaps generated, never typed; no links between sites in the network. That last one is a policy matter as much as a tidiness one; the reasons are in our write-up of Google spam policies for multi-site networks. If your network has mirror domains or one brand on several domains, our large-site indexing guide covers how to handle them.
Plan the handover before anyone leaves
When an agent leaves, the site should move to HQ or a new agent in minutes. That only works if HQ already owns the domain, the Search Console property and the analytics.
Search Console has two kinds of owner. Google's permissions help page↗ (checked 3 November 2026) separates verified owners, who proved ownership with a token, from delegated owners added by a verified owner. It also warns that if all verified owners are removed, remaining users and delegated owners lose access after a grace period. So HQ should be a verified owner on every site, not a delegated one. Otherwise removing the departing agent's token can lock everyone out.
Our handover checklist, in order: transfer publishing access to the new person; confirm HQ is a verified owner in Search Console; remove the departing person's access; check the "About" page and author details now show the new person; and confirm the domain's registrant email is HQ's. On our platform the access step is one action in the head-office account. The other steps are the same on any setup.
FAQ
What's the easiest way to manage multiple websites?
Keep one inventory of every site's domain, registrar, expiry, Search Console owner and responsible person, then use a setup where publishers can't change site structure. The software matters less than those two habits.
Can I manage multiple websites from one dashboard without WordPress?
Yes. A managed multi-tenant CMS runs every site from one account. You trade plugins and customisation for narrower roles and vendor-run hosting and updates.
How do I stop agents from breaking their websites?
Give them a role that can publish but can't change themes, menus, settings or tracking. On WordPress Multisite that means a role below Administrator.
How should I monitor many sites?
Check for a piece of text unique to each site, not only that the server responds. Check scheduled jobs by their output, not their run history.
Who should own Search Console for agent sites?
The head office, as a verified owner on every property. Agents can be added as users.
Related Posts
- strategyGoogle Spam Policies That Matter for Multi-Site Networks: Doorways, Scaled Content, Link Spam, Expired DomainsFour Google spam policies decide whether an agent or franchise site network is a business or a liability. What each one says, and the compliant way to run 20+ sites.
- strategyMulti-Tenant CMS vs WordPress Multisite: What Running 20+ Sites Really CostsWordPress Multisite hosting can be cheap. The cost of 20+ agent sites sits in updates, plugins, permissions and SEO drift. A cost worksheet and when each option wins.
- strategyGEO Maintenance: Is It One and Done? AI Citations Have an 11-Day Half-LifeProfound tracked 883,000 pages for a year: AI citations fall by half a median 11 days after their peak. Why GEO maintenance is monthly work, plus our 5 steps.