Replace Your Client Site Spreadsheet With a List That Keeps Itself Current

Every agency has the sheet. One row per client site, and a column for everything anyone once needed to know: client, URL, CMS, version, PHP, host, notes, renewal date. It was accurate the afternoon it was made.
Spreadsheets have a poor record even when somebody is checking them. Ray Panko’s review of spreadsheet field inspections reports that “Collectively, these studies found errors in 94% of the spreadsheets studied.” A client site spreadsheet has a second problem on top of typing mistakes: the sites keep changing after the cell was filled in.
Look closely and the sheet mixes two kinds of column. Some hold facts a machine can read from the site: the CMS version, PHP, the database, the SSL expiry, the nameservers, the hosting network. The others hold facts only a person knows: which client the site belongs to, what you call the hosting provider, the notes, when to review the retainer. The first kind starts going stale the moment anyone clicks Update. The second kind is what the sheet is actually for.
This post sorts a typical sheet column by column into three piles: read automatically, typed once into mySites.guru, and better kept in your accounts or CRM system. In mySites.guru the list of sites is read from the sites themselves at every snapshot, so the first pile stops being your job.
The 47-second film below shows the swap: the sheet going stale, then the same list read from the sites, grouped by client, with the care plan as a checklist and a CSV for finance.
Transcript
Your client site spreadsheet was right the day you typed it. Then a host moved PHP, a plugin updated, and no one wrote it down.
Meet a site list that keeps itself current. In mySites.guru. Versions, PHP, database and SSL come from every site, at every snapshot. Tag each site by client, then group the whole list by tag. The monthly care plan becomes a checklist, ticked site by site.
The client conversations go on a schedule. Review the retainer, every year. Finance still wants a sheet? Export one whenever you need it. The list stays right without anyone retyping it.
Your client site list, in mySites.guru.
Why does a client site spreadsheet go stale so fast?
A client site spreadsheet goes stale because the facts in it change on the site and no one writes the change back. Core releases, extension updates and PHP changes on the server all alter what a row should say, and the person who clicked Update had no reason to open the sheet afterwards.
The release numbers show how fast a hand-typed version column rots. The WordPress versions page lists 14 releases on the latest branch in 2026 by 28 October: 6.9.1 to 6.9.4, then 7.0 on 20 May with 7.0.1 to 7.0.4, then 7.1 on 19 August with 7.1.1 to 7.1.4. Security releases went out on six dates: 6 August, 12 August, 17 September, 22 September, 6 October and 28 October.
Joomla is no slower to move than WordPress. The Joomla roadmap shows 10 patch releases on the 5.4 branch, from 5.4.1 on 25 November 2025 to 5.4.10 on 13 October 2026. Bug fixes for Joomla 5.x ended that same day, and the branch is security only until 12 October 2027. A version cell typed in January was wrong many times over by autumn, on every row, for both platforms.
PHP moves underneath all of it. Each PHP branch gets two years of full support and then two years of security fixes only, according to PHP’s supported versions page, and security support for PHP 8.2 ends on 31 December 2026. A host can change the PHP version on a server overnight without anyone at the agency touching a thing, which is how hand-kept PHP columns went stale during PHP2Shell.
The update is applied on the site, and the row keeps saying what it said.
Which columns mySites.guru reads from the site
Here is a typical sheet, one row per column, with where each one lives in mySites.guru and who fills it in.
| Spreadsheet column | In mySites.guru | Filled in by |
|---|---|---|
| Site URL and name | Site column on All Your Sites; name editable in Config | URL read, name typed once |
| Client | A tag per client, in its own colour | You, once per site (bulk tagging works) |
| CMS and version | CMS column, with Joomla lifecycle status | Read at every snapshot |
| PHP version | PHP column, pill coloured by support status | Read at every snapshot |
| Database version | Database column, green, yellow or red by end of life | Read at every snapshot |
| SSL expiry | SSL column and the SSL Expiration Dates page | Read automatically |
| DNS provider and nameservers | DNS column; email when nameservers change | Read at every snapshot |
| Server hostname | Hostname column | Read from the site |
| Hosting provider | Provider column, set on the Web Servers page | You, once per server |
| Extensions and versions | Extensions pane per site, Extensions CSV for all sites | Read at every snapshot |
| Uptime | Monitor created when the site is added | Automatic |
| Notes | Notes tab on each site, encrypted | You |
| Retainer review or check-in date | A repeating reminder | You, once |
All Your Sites, the page at /sites/, replaces the sheet’s main tab. Each row has the site’s favicon, friendly name and URL, then a CMS column with the platform icon and exact version (Joomla rows also say current, security only or end of life), a PHP pill coloured by support status, and a Database column that turns green, yellow or red from end-of-life data. SSL, DNS, Hostname, Provider and Server name columns exist too and are off by default, and a Cloudflare column appears once a Cloudflare token is connected.
The list regroups by PHP, platform, CMS status, needs attention, database, tag, hostname, provider or DNS provider. Your sort, grouping, columns, column order, widths and density are saved in the browser, separately for phone and desktop, and can be backed up to your account at /account/table-layouts. Filters live in the URL, so a filtered view is a link you can send to a colleague.
It is one list whether you manage multiple WordPress sites, multiple Joomla sites or both.
Each site also has a Hosting Information pane that lays the hosting out as a five-layer path: Domain & DNS, Edge & certificate, Web server, PHP and Database. It keeps “Here since” dates and a Hosting changes history that records when the server, the PHP version or the database changed, and the hosting network is looked up automatically. A spreadsheet has no such column, because no one types in what a cell used to say.
Nameservers are read on every snapshot. You get an email and a Timeline entry when they change, or when they go missing twice in a row, and SSL certificate expiry dates are read for you as well. mySites.guru does not read WHOIS, so there is no registrar and no domain expiry date. That column stays with your registrar account.
What do you still type in yourself?
You type in the facts no site can report about itself: which client a site belongs to, what you call the server and its provider, your private notes, and the dates you want to be reminded of. Each is entered once in mySites.guru, beside the data it describes, and nothing overwrites it.
Start with the client. mySites.guru has no client-name field and no per-site custom fields, so the client goes on a tag or into the site’s friendly name. Tags are managed on the Site Group Tags page, each with a name, a colour, a show-in-left-menu switch and an order. They show beside the site name, you can filter by one, and you can tag a selection of sites in bulk. Tags belong to the company, so the whole team sees the same set.
One group per site
Group by Tag on All Your Sites files each site under one tag only. A site with both a client tag and a retainer tag appears in one group, so the grouped list reads best as a list of clients when each site has one client tag. For the retainer view, filter by that tag instead.
The host column becomes the Web Servers page at /servers/. Each server there takes a Provider (up to 64 characters), a Server name (up to 80) and Notes (up to 500, plain text). The Provider box is pre-filled with a guess from the hostname, which is never saved on its own, and you can set the provider on many servers at once. That page groups by Provider by default, so “everything on that host” is the first thing you see.
The notes column becomes the Notes tab under Manage Site, headed “Your private notes about this site”. It is one plain-text box per site, stored encrypted, and the site’s row shows a notes icon when there is something in it. Notes are for context a colleague would need before touching the site, and they are not included in the CSV export or the API.
The date column is where most sheets are weakest, and in mySites.guru it becomes a reminder. A reminder has a title, Markdown notes, links, linked sites, an assignee and up to three dates (remind, alert and due), and it can repeat every so many days, weeks, months or years. The starters are a security talk, a retainer review, a client report, a client check-in and a restore test, which says what reminders are for: the conversations you owe a client. They arrive by email, push or webhook, there is a private iCal feed, and a site with an overdue or due-soon reminder shows a pill on All Your Sites.
If the sheet has a tab of monthly ticks, that is a care plan checklist: a reusable template that can be tied to tags. A started checklist has an owner, a deadline, a repeat and chase emails, with a tick and a note per site, and some items tick themselves from mySites.guru checks.
Two columns only partly make the move. There is no “responsible person” field on a site, so ownership is the reminder’s assignee, the checklist’s owner and the list of allowed sites on each team member, who has Full access or None, View or Manage per area. Joomla download keys can be saved per vendor and applied to all the sites running that product, but that is no licence register and it holds no renewal dates.
Read the full postThe columns that should leave the sheet entirely
Two kinds of column should not move into mySites.guru at all, and one of them should not be in a spreadsheet either.
The admin password column is the dangerous one. A spreadsheet gets emailed, copied and shared with whoever needed the list of URLs, and the passwords in it go along too. The UK’s National Cyber Security Centre gives the alternative in one line: “A password manager stores passwords safely for you.” CISA says the same from the other direction: “Rather than write them down, use a password manager!”
Spreadsheets also leak more than their authors can see. In August 2023 the Police Service of Northern Ireland released a spreadsheet with a hidden tab in a freedom of information response, exposing details of 9,483 officers and staff, and the ICO fined it £750,000. A file with a column of client logins has that same weakness each time it is attached to an email.
mySites.guru has no password vault
mySites.guru stores no CMS passwords for you to look up. The Notes box on a site says “Never store passwords here”, and the Notes on a server say the same. Put the passwords in a password manager and delete the column.
What replaces the column for daily work is the one-click Admin login on each site row, so no one needs to look up a password to reach a client’s admin console. When the question is about people, Universal User Management searches and manages CMS users across sites.
The other kind is money. Contract value, invoice dates and what each client pays belong in your accounts or CRM system. mySites.guru does not bill or invoice your clients and does not try to be that tool.
How do I move my spreadsheet into mySites.guru?
You connect the sites, then type in only the columns a person has to supply. There is no CSV or URL-list import, and most of the sheet does not need one: once a site is connected, its version, PHP, database, SSL and DNS columns are read from the site.
Sites go in one of two ways. The Add Site wizard connects them one at a time. For a server full of them, Hosting Panel Discover works with cPanel/WHM or DirectAdmin: it scans every hosting account for Joomla and WordPress installs and connects up to 50 selected sites per run. Adding sites straight from the server is the quicker route when the sheet’s host column says the same thing on forty rows. An uptime monitor is created for each site as it is added, so that column is finished before you have typed anything.
Sort the columns. Mark each column in the sheet as read from the site, typed by you, or belonging in another system.
Add the sites. Connect each one with the Add Site wizard, or use Hosting Panel Discover on a cPanel/WHM or DirectAdmin server.
There is no CSV import. Discover connects up to 50 selected sites per run.
Tag each site with its client. Create one tag per client and apply it to that client's sites, in bulk where you can.
Group by Tag files each site under one tag only.
Describe your servers. Set the Provider, Server name and Notes for each server on the Web Servers page.
The provider can be set on many servers at once.
Move the notes and the dates. Paste each site's notes into its Notes tab and turn every review date into a repeating reminder.
Never paste passwords into a notes box.
Retire the sheet. Move passwords into a password manager, leave billing in your accounts or CRM system, and archive the spreadsheet.
Export a CSV when someone needs a file.
Do the first step properly and the rest is short. The pile you have to type is usually the smallest of the three.
The spreadsheet finance still wants is an export
The spreadsheet does not have to disappear. Somebody in finance will still want one, and a client may ask for a list of their sites. The difference is that the file is generated when someone asks for it, and no one has to maintain it.
The Export CSV button on All Your Sites offers four scopes: Selected rows, Filtered table, Full table and By platform. The columns are url, name, site_version, platform, php_version, last_backup, last_audit, previous_audit, last_snapshot, is_hacked, server_hostname, provider, server_name, upgrades_available and tags. Filter to one client’s tag, export the filtered table, and that is the sheet finance asked for. Site notes are left out of the CSV and the API. Extensions have their own CSV, with one row per site and extension, and each checklist run exports to CSV too.
For anything that should stay live, skip the file. GET /api/v1/sites with the api:sites:read scope returns platform, version, php_version, db_version, nameservers, dns_provider, hosting_network, tags, last_audit and last_backup for each site. The MCP tools list_sites, get_site and list_site_summaries give an AI assistant the same list to answer questions from.
The version a client sees is a Client Report, scheduled per set of sites from /reports/.
Start with the sorting. Take your client site spreadsheet, mark each column as read from the site, typed once or kept elsewhere, then create a mySites.guru account and connect the sites. The columns that used to rot are read for you from then on.
Every Site in Your Account From One API or MCP CallRead the full postFurther Reading
- What We Don't Know About Spreadsheet Errors Today - Ray Panko's EuSpRIG 2015 paper, the source of the 94% figure from field inspection studies.
- WordPress versions - each WordPress release with its date.
- Joomla roadmap - release dates and support windows for each Joomla branch.
- PHP supported versions - which PHP branches still get fixes, and until when.
- NCSC: password managers - the UK National Cyber Security Centre on where passwords belong.




