Description
When a site breaks or loses traffic on Tuesday, you want to know what changed on Tuesday. The answer can be technical (a plugin update) or editorial (a page whose title or links were changed). Most tools only see one of the two. Muninn keeps both in the same place.
In Norse mythology, Muninn (“memory”) is one of Odin’s two ravens: every day it flies over the world and comes back to tell what it saw. This plugin does the same for your site.
Technical history
- WordPress, plugin and theme updates, with the previous and the new version.
- Installs, deletions, activations, deactivations and rollbacks.
- PHP version changes.
- Failed updates, with their error message, and updates cancelled by WordPress after a fatal error.
- Who did it: a user, an automatic update, or a change detected outside WordPress (FTP, hosting tools). Updates made outside WordPress are caught too: the plugin compares the installed versions with the last ones it saw.
Content history
For published posts, pages, products and other public content, Muninn compares the version before and after each save and logs what matters for SEO:
- Words added and removed, links added and removed, headings added and removed.
- Title and URL changes.
- SEO title, meta description and noindex (Yoast SEO, Rank Math, SEOPress).
- Content unpublished, trashed, restored, published again or deleted.
- Categories created, renamed, moved or deleted, navigation menu changes.
- Site settings: search engine visibility, permalink structure, homepage.
The Content tab also lists the scheduled posts and pages (next to go live first) and the drafts, including the ones pending review.
Only the log entry is stored, never a copy of the content.
At a glance
The page under Tools > Muninn also shows the technical environment (WordPress, PHP, database, HTTPS certificate), the updates done, pending and failed, the inactive plugins, the backups, and the essential plugins (security, backup, cache, SEO).
- Filter by type and period, search by name, export to CSV.
- Pending updates include premium plugins that use the WordPress updater.
- Backups: detects the backup plugins (UpdraftPlus, BackWPup, WPvivid, BlogVault, Jetpack, WP Umbrella, ManageWP, MainWP…) and managed hosts that back up sites themselves (WP Engine, Kinsta…). For UpdraftPlus, also shows the date, contents, size and storage of each backup (read only).
- Lightweight: one small table, no requests to third-party services.
For agencies: read-only dashboard connection
If you manage sites for clients, you can let your own dashboard read each site’s maintenance status (versions, pending updates, auto-update settings and history) through a dedicated read-only key. No administrator password to share: the key cannot change anything on the site, and you can replace or delete it at any time.
Nothing is ever sent anywhere until you create a key. The plugin does not phone home and does not track visitors.
Settings
Everything works as soon as the plugin is activated. Three things can be changed on the Tools > Muninn page:
- History length: kept forever (default), or 1 year, 6 months or 3 months.
- Log content changes: on by default. Uncheck it to keep the technical history only.
- Dashboard connection: off until you click “Create a key”. You can replace or delete the key at any time.
Installation
- Upload the plugin through Plugins > Add New > Upload Plugin, or search for “Muninn”.
- Activate it.
- Open Tools > Muninn. The history starts now: earlier updates cannot be known.
To connect a dashboard, click “Create a key” in the “Dashboard connection” box and copy the address and the key into your tool.
FAQ
Can it show updates made before it was installed?
No. WordPress does not keep this history, so the log starts when the plugin is first activated.
How does the dashboard connection work?
Send a GET request to /wp-json/tldr-seo-update-log/v1/status with the key in the X-TLDR-Key header. The answer (JSON) contains the versions, the pending updates, the auto-update settings, the log entries and, while content changes are logged, the scheduled content and the drafts (title, type, dates, author). Use since_id to fetch only the entries you do not have yet.
Is the key safe?
The key only gives read access to the information shown on the plugin page. It cannot log in, change settings or install anything. Replace it if you think it leaked.
What happens when I delete the plugin?
The history table and the plugin options are deleted. Export the log to CSV first if you want to keep it.
Does the plugin make any external requests?
The plugin does not send data to any third-party service and does not phone home. The only outbound connection it makes is to the site’s own domain, once a day, to read its HTTPS certificate directly (the same certificate your visitors’ browsers see). This is a connection from your server to your server, not to an outside party.
Changelog
2.1.1
- Admin notices from other plugins now behave as on any other WordPress screen: the extra script that moved them below the page title is removed.
2.1.0
- The page now has two tabs: “Updates” and “Content”. Each one can be opened directly from a link, and switching tabs is instant.
- A period list at the top of each tab (last 28 days, 3 months, 12 months, all, a year or a month) sets both the cards and the history, and the cards show the change against the previous period.
- Faster page: plugins and themes are read from the disk at most every 5 minutes instead of 3 times per page.
- Content tab: summary cards for the last 28 days (changes, published, edited, removed), the number of scheduled posts and the number of drafts, with the ones not edited for 3 months (probably forgotten).
- Content tab: new “Scheduled” and “Drafts” lists (drafts include content pending review). They follow the “Log content changes” box.
- Dashboard connection: the answer now includes the scheduled content and the drafts.
2.0.0
- Renamed “Muninn – Site Maintenance & Content History”. New plugin folder and text domain: muninn. The menu under Tools is now “Muninn”.
- Coming from “Maintenance Log by TL;DR SEO”: install this one, deactivate the old one, activate this one, then remove the old folder by FTP. Do not use “Delete” on the old plugin: it would erase the shared history. The history, the settings and the dashboard key are kept, and the dashboard address does not change.
- Translations now come from translate.wordpress.org.
1.10.0
- Content history: content taken offline (draft, pending, private or trash) then published again is now logged as “Published again”. Before, only a direct restore from the trash was logged, and WordPress restores trashed posts as drafts.
1.9.0
- New “Content history” block, between Backups and Dashboard connection, with its own period, type, search, pages and CSV export. The “Log content changes” box moved into it.
- “Update history” shows updates only again (WordPress, plugins, themes, PHP).
- Content history: the item links to the page.
1.8.1
- Fixed the Technical environment and Essential plugins lists, whose lines overlapped in 1.8.0.
1.8.0
- Content changes (setting “Log content changes”, on by default): for published posts, pages, products and other public content, the history shows the words added and removed, the links and headings added or removed, and changes of title, URL, SEO title and meta description (Yoast SEO, Rank Math, SEOPress). Also: noindex or index, moved to the trash, unpublished, restored or deleted.
- Categories (post and product categories): created, renamed, URL, description or parent changed, deleted.
- Navigation menus: links added or removed, order changed.
- Site settings: search engine visibility, permalink structure, homepage.
- The dashboard connection also returns the details of each change.
1.7.1
- History period filter: “All” moved to second place, right after “Last 28 days”, so it stays easy to reach after years of history.
- History: 10 rows per page instead of 50, so backups and settings below stay close.
1.7.0
- History: new “Period” filter. Last 28 days by default, then each month with changes, grouped by year (with “Whole year” at the top of each year), or everything. The CSV export follows the period.
- Number of entries shown under the history.
- “Done” card over the last 28 days (same as the client dashboard).
1.6.0
- Cancelled updates are logged: when the automatic update of a plugin causes a fatal error, WordPress (6.6 or later) puts the previous version back; this now appears as “Cancelled” (or “Cancellation failed” when WordPress could not put it back) instead of an update followed by a rollback.
- New “Cancelled” card next to “Failed”. Both only count what is not fixed yet: an update that failed then worked on the next try no longer shows as a failure.
- “Done” no longer counts cancelled updates.
- Inactive plugins: the card is replaced by a banner under the update cards, shown only when there are some.
1.5.0
- Renamed “Maintenance Log by TL;DR SEO”: the page covers more than updates (technical environment, backups, essential plugins). The menu under Tools is now “Maintenance Log”.
- New plugin folder and text domain: maintenance-log-by-tldr-seo. Coming from “TL;DR SEO Update Log”: install this one, deactivate the old one, activate this one, then remove the old folder by FTP. Do not use “Delete” on the old plugin: it would erase the shared history. The history, the settings and the dashboard key are kept.
1.4.2
- New “Inactive plugins” card next to the update cards, with a link to the inactive plugins list.
1.4.1
- Smaller summary cards. The technical environment and essential plugins are now two checklists side by side, with a score (for example 3/4 in order).
1.4.0
- The page now shows three rows, like the client dashboard: technical environment (WordPress, PHP, database, HTTPS certificate), updates (done, pending, failed) and essential plugins (security, backup, cache, SEO).
- The dashboard connection status moved to the Dashboard connection box.
1.3.1
- Fixed a fatal error introduced in 1.3.0 when reading file dates.
1.3.0
- Failed updates are logged, with the error message when WordPress gives one.
- Detects the cache plugin (WP Rocket, LiteSpeed Cache, WP-Optimize…) and the SEO plugin (Yoast SEO, Rank Math, SEOPress…).
- Date of the last update of each plugin and theme, estimated from its files (for updates made before the plugin was installed).
1.2.1
- Cards: long texts now wrap instead of being cut.
- HTTPS certificate checked once a day.
1.2.0
- Security: detects the active security plugin (Wordfence, Solid Security, Sucuri, All-In-One Security, Jetpack Protect, Patchstack…).
- HTTPS certificate: expiry date and issuer, checked once a day.
- Database: MySQL or MariaDB version, compared with what WordPress recommends.
- Backups: UpdraftPlus warnings are no longer counted as errors, and the messages are shown.
1.1.0
- Backups: detection of backup plugins and managed hosts; dates, contents, size and storage of UpdraftPlus backups.
1.0.1
- The menu under Tools is now named “TL;DR SEO Update Log”.
1.0.0
- First version.
