SEOmise
  1. Home
  2. All modules
  3. Website health
  4. Site manager

Website health

Site manager Beta

Manage multiple WordPress sites: versions, plugins, updates and vulnerabilities

Manage multiple WordPress sites and other platforms in one grid: uptime, versions, plugins and themes, updates waiting, known vulnerabilities and plugins closed, abandoned or losing their licence.

Illustration of the screen, without data.

Why it matters

From the problem to what SEOmise does

The problem

Ten sites, ten admin screens

To know which sites need updates, which run a plugin with a known hole, or which plugin was pulled from WordPress.org, you log in to every site one by one. Paid licences run out without warning, and an old PHP version goes unnoticed until the host turns it off.

What Site manager does

Manage multiple WordPress sites: versions, plugins, updates and vulnerabilities

  • Every site in one grid. Uptime, WordPress, PHP and database versions, the number of plugins and themes, how many need an update, are vulnerable or are expiring, and one Site care score per site. Filter by needs updates, vulnerable, down, PHP end of life or no backup.
  • By plugin. One row per plugin across all your sites: on how many sites, which versions are in use, active or inactive, and the newest version. Open a row to see every site with it. The same for themes, and for Composer packages on Laravel sites.
  • Expiring plugins. Plugins WordPress.org has closed (they get no more fixes), plugins with no update for two years, and paid licences you enter by date, with a warning 30 days before they end. Nothing is guessed.

How it works

Three steps, start to finish

  1. Connect your sitesThe SEOmise connector for WordPress or Laravel, or the PHP file. Sites on Shopify, Wix, Webflow and other platforms are listed too.
  2. SEOmise reads what each site runsTwice a day, read-only and signed: versions, plugins and themes with the updates WordPress itself found. Nothing on the site is changed.
  3. Hear about what mattersAn e-mail for a new vulnerability, a plugin closed on WordPress.org or a paid licence that is about to end.

Features

What you get with Site manager

Every site in one grid

Uptime, WordPress, PHP and database versions, the number of plugins and themes, how many need an update, are vulnerable or are expiring, and one Site care score per site. Filter by needs updates, vulnerable, down, PHP end of life or no backup.

By plugin

One row per plugin across all your sites: on how many sites, which versions are in use, active or inactive, and the newest version. Open a row to see every site with it. The same for themes, and for Composer packages on Laravel sites.

Expiring plugins

Plugins WordPress.org has closed (they get no more fixes), plugins with no update for two years, and paid licences you enter by date, with a warning 30 days before they end. Nothing is guessed.

Known vulnerabilities and changed core files

The WordPress, plugin and theme versions your sites run, checked every six hours against a vulnerability database, with the severity and the version that fixes it: "Update to 10.0.2 to fix". Each WordPress core file is compared with WordPress.org's published checksums: changed files and PHP files that are not part of WordPress are listed. The user names of every site's administrators are listed too, so forgotten accounts are easy to spot (never e-mail addresses or passwords).

PHP errors, uptime, certificates and domains

New fatal errors and warnings, one line per file and line, with how often they happened. Never the visitor's data or the request. From Website watch: uptime over 30 days and the days left on the certificate and the domain name, for every platform.

Every job, step by step

Reading a site shows each step with its tick, its own progress bar with the real numbers and the item it is on. If a site goes quiet you see "Still working on …", and if it looks stuck you can wait, retry the step or cancel. Leave the page and the top bar keeps the job in sight.

Safe updates with automatic rollback

WordPress, plugins and themes updated with WordPress's own upgrader, after a restore point. Then the home page and the pages you name are checked (HTTP 200, no PHP fatal error) and the screenshots compared; if a check fails, the old version is put back by itself. Update windows, undo from the history, and bulk actions: install, switch on, switch off or delete a plugin across many sites, or apply a saved plugin set, each site with its own job and undo.

Backups with restore, hourly if you need it Beta

Full, then only what changed: files in chunks named by their fingerprint, the database table by table, encrypted on the site with its own key and sent straight to storage in the EU, or to your own S3 or Dropbox, each checked with a test write before it is used. Every backup is checked, a test restore runs every month, and a restore makes a restore point first so it can be undone. Download it as one archive with a one-time installer. An extra on top of Backups for busy sites: the database every hour and the files every six hours, with the same encrypted, checked backups and one-click restore. In early access: ask for it with "Add Backups" on Site manager's Sites screen.

CloneMise: staging, moves and clones Beta

A staging copy hidden from search engines, behind a password, with e-mails held; push it to live after a preview, with a backup of live first and one-click undo; move a site to a new host or clone it to a new domain, with addresses rewritten safely in serialised data and JSON; or deploy a copy over SSH. Only your own sites, and each copy pairs as its own site. In early access: ask for it with "Add Backups" on Site manager's Sites screen.

The Firewall, per site, and never locked out Beta

On WordPress it runs before every other plugin, from a small must-use loader written only when you allow it: a translated subset of the OWASP Core Rule Set, virtual patches for the vulnerabilities found on that site until you update, sign-in lock-outs after wrong passwords and an optional bot check, xmlrpc.php closed, bad bots refused while real search engines get through, and your own address and country lists. It learns for a week before it blocks, and every rule update logs for a day first. Laravel sites get the same rules as a middleware; other platforms get the edge firewall or the steps for their host's. One click switches the firewall off, in the app or in WordPress. And if you ever cannot reach either, delete one file by SFTP and it stops at once. In early access: ask for it with "Add Firewall" on Site manager's Sites screen.

A daily malware scan Beta

Core and plugin files compared with their published versions, PHP files that should not be in the uploads folder, and suspicious files checked with YARA and ClamAV on our servers. Each finding comes with three ways to fix it: do it yourself, with help, or for you, putting back the clean published copy (or moving the file out of reach) with a restore point and undo. In early access: ask for it with "Add Firewall" on Site manager's Sites screen.

Monthly maintenance reports

Updates done, backups, uptime, attacks blocked, vulnerabilities patched, malware found and cleaned, and speed, for each client site from the Reports centre. White label puts your agency's name on it and no one else's.

Before and after

What changes with Site manager

Before: without Site manager. After: with Site manager. Drag the handle, or use the arrow keys, to compare.

Without Site manager

  • Log in to every site to see what needs updating
  • Hear about a vulnerable plugin from the news
  • A paid licence runs out and updates stop

With Site manager

  • Every site, plugin and update on one screen
  • An e-mail when a plugin you run has a known hole, and a virtual patch until you update
  • Attacks blocked before WordPress loads, and a malware scan every day
  • Licence and closed-plugin warnings before they bite
BeforeAfter

Illustration of the difference, not a measured result.

Prices

Pay per site, only for what you use

Start with Site manager; add Backups or the Firewall to the sites that need them, or the bundle for all three.

Site manager Beta

€1.99 a site a month

Sites and plugins views, expiring plugins, vulnerabilities, PHP errors and uptime for every site.

The Agency package includes 10 sites.

Backups Beta

€2.49 a site a month

Daily and on-demand backups with restore, 30 days kept, encrypted and stored in the EU.

Hourly backups: +€1.49 a site a month.

Firewall Beta

€2.00 a site a month

A firewall with virtual patching, login protection, bad-bot blocking and a daily malware scan.

Site care bundle Beta

€5.49 a site a month

Site manager, Backups and the Firewall together for a site.

Save 15% against €6.48 bought separately

Each has a 14-day free trial for up to 5 sites. Extras are bought per site, and the bundle covers the sites it is bought for. CloneMise copies (staging, moves, clones) are included with Backups; without Backups each copy is €4.99.

What it needs

No surprises after you sign up

Turn a card over for the detail.

The SEOmise connector on each site for the full view

The SEOmise connector on each site for the full view

WordPress gets everything; Laravel its versions and packages. Without a connector, Site manager shows uptime, the certificate and the domain, with the steps to check the rest.

Paid per site

Paid per site

Site manager on its own, per site and month, with nothing else to buy. The Agency package includes 10 sites, and there is a 14-day free trial for up to 5 sites.

Add SEO any time

Add SEO any time

Start with Site manager alone and add an SEO package later, or add Site manager to your package from the Store. Nothing is lost when you move between them.

Every platform

Whatever your site runs on

What Site manager does on each kind of website, from SEOmise's site connectors to step-by-step guidance.

WordPress

WordPress and WooCommerce
Fully supported

Everything: versions, plugins and themes with their updates, vulnerabilities, core files, administrators, Site Health and PHP errors, through the WordPress connector.

Laravel

Sites built on Laravel
Partly automatic

PHP, Laravel and every Composer package with its version, through the Laravel connector. Updates stay with your developers.

Any PHP site

Custom PHP, CodeIgniter, Symfony, Drupal, Joomla
Partly automatic

The PHP version and the web server through the PHP connector file, plus uptime, certificate and domain, with the steps to check the site's own software.

Every other platform

Shopify, Wix, Squarespace, Webflow, static sites and the rest
Partly automatic

Shopify, Wix, Webflow and other hosted platforms update themselves: Site manager shows uptime, the certificate, the domain and the SEOmise app's status, with where to check your apps.

About the site connectors

Site manager is in beta

It is not on sale yet, so there are no prices for it. Leave your name and e-mail address and we will tell you as soon as you can use it.

Questions about it?

Ask Mise, our assistant, in the help centre, or book a call and we will tell you where Site manager stands and what you can use today.

Questions

Site manager: common questions

Does Site manager change anything on my sites?

Reading is read-only. Backups and restores need SEOmise Connector Pro and the permission you tick on the site; each runs as a job you can follow step by step, with a restore point first and undo. Safe updates and plugin actions work the same way, from the site's Updates panel or the by-plugin view.

Where are backups kept, and who can read them?

In SEOmise's storage in the EU by default (Amazon S3, eu-west-1, locked against changes for the days you keep them), or in your own S3-compatible storage or Dropbox, chosen per site (Google Drive follows once its upload steps are checked). Every chunk is encrypted on your site with its own key before it leaves, so the storage only ever holds encrypted data.

Can I copy a site I do not own?

No. CloneMise copies only your own sites: the site must be connected to your workspace or its domain verified. Each copy leaves out, by default, users who are not administrators, orders and personal data, caches and the pairing keys.

Where do the vulnerabilities come from?

From the vulnerability database SEOmise connects (WPScan is the first one built), checked every six hours against the exact versions your sites run. Until it is switched on, the security tab says so.

How do you know a plugin is abandoned or closed?

From WordPress.org's public plugin information: closed plugins and plugins with no update for two years. Paid plugins are not on WordPress.org, so you enter their licence end date yourself.

What does it read about administrators?

Only their user names and display names, so you can spot accounts nobody uses. Never e-mail addresses or passwords.

Is it only for WordPress?

No. WordPress gets the most, Laravel sites list their packages, and every other platform gets uptime, the certificate and the domain with the steps for that platform.

What if the firewall blocks me?

It starts in learning mode: for a week it only logs what it would block, and signed-in administrators are never blocked by its rules. One click switches it off, in the app or on the SEOmise Connector's Settings tab in WordPress. If you cannot reach either, delete wp-content/seomise-firewall/enabled by SFTP or your host's file manager and it stops at once.

What does the firewall send you?

For each blocked request: the rule, the names of the fields that matched, the address, country, method, path without its query string and the browser's name. Never what was typed, a request body or a cookie.

Where do the firewall rules come from?

From the OWASP Core Rule Set (Apache License 2.0), the open rule set most web application firewalls use, translated rule by rule for the plugin and the Laravel middleware, with our own signatures and the virtual patches for your site on top. The rule version in use is shown, and new rules log for a day before they block.

What does it cost?

A price per site and month, shown in the prices above. Backups (with Hourly backups on top), the Firewall and the Site care bundle are extras per site. A CloneMise copy is included with Backups; without Backups each copy is added to your next invoice. The Agency package includes 10 sites of Site manager, and there is a 14-day free trial for up to 5 sites.

Do I need an SEO package?

No. Site manager is sold on its own and only shows its own screens. If you want SEO later, choose a package under Billing: your sites and everything Site manager read stay.

Can I use Site manager now?

Site manager is in beta: it is not on sale yet. Use Ask for early access and we will e-mail you as soon as it is ready for you. Other modules and the plans are on the pricing page.

Be among the first to try Site manager

Site manager is in beta. Ask for early access and we will e-mail you when it is ready for you; nothing is bought.

No ranking guarantees: just clear work, with the evidence.