Page Content Guard

Description

Project page: https://harbouratelier.uk/wordpress-plugins/page-content-guard/

Page Content Guard is a local content-state monitor for important pages, posts and supported public custom post types.

It can report when monitored content:

  • is permanently deleted,
  • is no longer published,
  • receives a changed permalink,
  • has a stored title that differs from an optional accepted baseline,
  • has clearly blank standard WordPress content,
  • loses a required saved-content fragment.

Administrators receive privacy-safe Site Health checks for the monitor schema and a bounded sample of stored monitor data. Native WordPress content lists show a compact linked state for monitored items and can be filtered to monitored or unmonitored content. Unmonitored rows remain blank in the added column. A compact WordPress dashboard widget shows active, paused, unchecked and currently problematic monitor counts without exposing titles, URLs, rules or issue details.

Page Content Guard checks WordPress records and standard post_content stored in the database. It does not open or render the public page, test HTTP status, submit forms, execute shortcodes, render dynamic blocks, restore content, block changes, provide uptime monitoring or protect against hacking.

No external API, account, telemetry, analytics, remote image or tracking request is used.

FREE and PRO

The FREE edition is usable without an expiry date and has no quantitative limit on active monitors or required fragments. It includes manual checks and checks after relevant content changes.

Page Content Guard Pro is a separate add-on. It adds scheduled checks, email notifications, incident history, advanced stored-value integrity checks, forbidden fragments and bulk tools.

Compare FREE and PRO: https://harbouratelier.gumroad.com/l/Page-Content-Guard-PRO

Privacy

The plugin stores monitor configuration, current issue state, operational timestamps and – when integrity checks are enabled – SHA-256 baseline fingerprints, capture times, small display snapshots or attachment IDs, and optional WordPress revision IDs in the local WordPress database. Full post_content is not copied into an integrity baseline. It sends no data to the developer or another hosted service. If PRO email notifications are enabled, issue summaries are passed to the site’s configured WordPress mail system and the selected recipients.

Screenshots

Installation

  1. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, or copy the page-content-guard directory to /wp-content/plugins/.
  2. Activate Page Content Guard separately on the intended site.
  3. Open Page Content Guard > Monitors.
  4. Select Add Monitor and choose an important published content item.
  5. Configure the available checks and select Save & Check.

Network-wide activation on Multisite is not supported. Individual-site activation is supported.

FAQ

Does this test the public page?

No. It checks the WordPress content record, generated permalink and standard stored post_content. It does not make an HTTP request or render frontend output.

Will it work with a page builder?

Existence, publication and usable-permalink checks may work for an eligible content type. Blank-content and fragment checks inspect standard post_content only, so they may not represent content stored exclusively in builder-specific fields.

How does title integrity work?

Title integrity is optional and disabled by default. When you enable it, Page Content Guard records the exact title value currently stored by WordPress as the baseline. A later stored-title change opens one stable problem. Saving the monitor does not silently update the baseline. The problem resolves when the title returns exactly to the baseline, the check is disabled, or an administrator explicitly accepts the current title as the new baseline.

Does FREE run scheduled checks or send email?

No. FREE checks after relevant content events and through manual Check or Check all actions. Scheduling, notifications, stored-content/excerpt/featured-image integrity, forbidden fragments, incident history, Bulk Setup and Accept All Current URLs are supplied only by the separate Page Content Guard Pro plugin.

What happens when PRO is deactivated?

All non-paused monitors and all required fragments remain active in FREE. PRO integrity baselines, forbidden rules, PRO history and PRO settings are preserved but their paid behavior remains unavailable until compatible PRO reactivation.

Can I review WordPress revisions from a problem?

When the monitored post still exists, revisions are enabled and the current user may edit that content, Page Content Guard shows links to the native WordPress revisions screen. Revision availability is optional context only and never changes the monitoring result.

What happens when content is deleted?

The monitor remains and reports a missing-content problem using its retained title, post type and expected URL snapshots.

What happens when I uninstall the plugin?

Data is preserved by default. The Settings screen includes an explicit option to remove all Page Content Guard FREE and PRO tables, settings, run state and scheduled events when the FREE plugin is deleted.

Does this make my site legally compliant?

No. The plugin can monitor selected stored wording, but it does not provide legal advice or guarantee compliance.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Page Content Guard” is open source software. The following people have contributed to this plugin.

Contributors

Translate “Page Content Guard” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

2.3.3

  • Hardened administrator request handling with shape validation, unslashing and context-appropriate sanitization.
  • Updated localized JavaScript configuration names to use the plugin’s unique HAPCG namespace.

2.3.1

  • Removed the previous FREE limits on active monitors and required fragments, so all valid non-paused monitors and fragments remain active without PRO.