ArciCode Page Guard

By ArciCode

0+ active installationsVersion 0.4.4

Find out when a page breaks after an update: missing styles, errors, missing buttons or a broken layout.

Description

ArciCode Page Guard keeps an eye on your most important pages. After every plugin, theme or WordPress update, on a schedule or when you press “Check now”, the pages are opened on a computer and a phone screen, compared with the last good version and checked for problems:

  • page errors (500, 404, PHP and “critical error” messages, blank pages)
  • missing header, menu, footer, “Add to cart” button or contact form
  • styles or scripts that failed to load, broken images, content wider than a phone screen
  • pages hidden from search engines by mistake (noindex), “lorem ipsum” text, HTML code shown as text
  • SSL certificate that is about to expire

A page that looks wrong is opened again several times over a few minutes before anything is reported, so a cache that is still rebuilding after an update does not raise an alarm. Normal content changes (new posts, prices, banners) are told apart from breakage.

The panel shows first what needs a look: a short explanation and a before / now slider of the place that changed. Pages that are fine are folded away. When you changed a page on purpose, “This is fine” makes its new look the reference. The update log shows which plugin, theme or WordPress version changed, from which version to which. You get an e-mail when something breaks and another one when everything is fine again.

Checking service

The pages are opened and compared by the ArciCode Page Guard checking service, not on your server, so the checks do not slow your site down. This plugin is the part that runs on your site: it tells the service which pages to check, asks for a check after updates and shows the results. Without the service the plugin still keeps the update log, but makes no checks.

To connect a site, open Page Guard → Settings, enter your e-mail address (or the connection code of a paid plan) and press “Connect”. The free plan covers one site and 5 pages, checked after updates and once a week; paid plans cover more pages and sites and check daily. Nothing is sent anywhere until you press “Connect”.

External services

This plugin relies on the ArciCode Page Guard checking service, run by ArciCode (https://arcicode.dev/).

What the plugin sends, and when. Only after you press “Connect” in Page Guard → Settings: the address of your site, the e-mail address you entered (or your connection code), the plugin version, the site language and the site’s connection key, which lets the service read the page list and deliver results. While the site is connected, opening the plugin’s settings asks the service for the state of the connection (the site address and the key are sent). This happens at most every ten minutes; right after “Connect” it is asked every few seconds for up to two minutes, until the service has verified the site, and when the service did not answer it is asked again two minutes later. “Disconnect”, and deleting the plugin, tell the service to forget the site.

What the service reads from your site. Once connected, the service calls your site every few minutes with the connection key and reads:

  • the address of your site, the plugin version, the site language and time zone
  • the list of public page addresses to check and your Page Guard settings (pinned pages, areas to ignore, page limit, how often to check)
  • whether a check was requested, and why (for example “plugin update: Example Plugin 1.2 → 1.3”), and which pages you marked “This is fine”

The service then opens your public pages the way a visitor does (its User-Agent contains “ArciCodePageGuard”) and takes screenshots of them. Pages behind a login, the checkout and account pages are not opened.

What the service sends back. The result of each check: page addresses, the problems found and small copies of the screenshots. They are stored on your site in the uploads folder (arcicode-page-guard/), closed to visitors; the plugin shows the pictures in its panel to administrators only. The 15 latest checks are kept and everything is removed when the plugin is deleted.

Where the screenshots go. The service keeps the reference screenshot of each checked page and the pictures of recent checks on its server in the European Union. When a page changed, a crop of the changed area of the screenshot, together with the page address, is sent to Anthropic’s Claude model for a verdict (broken or just changed content): terms, privacy policy. Only public pages are involved; anything a visitor can see on them (for example names in public reviews) can appear in a screenshot.

To stop all of this, press “Disconnect” in Page Guard → Settings or delete the plugin. Creating a new connection key also cuts the service off at once.

Service terms: https://arcicode.dev/page-guard/terms/ · Privacy policy: https://arcicode.dev/page-guard/privacy/

Installation

  1. Install the plugin from Plugins → Add New, or upload the zip file there, and activate it.
  2. Open Page Guard → Settings, enter your e-mail address (or the connection code of a paid plan) and press “Connect”.
  3. The first check starts within a few minutes. It takes the reference pictures; later checks compare with them.
  4. Optional: in Settings, pin the pages that matter most and add the e-mail address that should get the alerts.

FAQ

Does it check pages that need a login?

No. Only public pages are opened, the same way a visitor sees them.

Why did a page change but stay “OK”?

Normal content changes (new posts, prices, banners) are recognised as content changes, not breakage.

What happens when the whole site is down?

The checking service notices that the site no longer answers, checks the pages without the plugin and sends the alert itself, to the e-mail address the site was connected with, because the site cannot send e-mail while it is down. The result appears in the panel once the site is back.

The checking service is blocked by my firewall. What now?

Allow requests whose User-Agent contains “ArciCodePageGuard”, or the address of the service. A page the firewall blocked is shown as “Unknown”, not as broken.

Does it work on a multisite network?

Each site of a network has its own key, settings and results. Connect the sites you want checked one by one.

Screenshots

Changelog

0.4.4

  • The folder with the check results is closed to visitors as a whole, pictures included; the panel shows the pictures to administrators only.
  • Every check gets a long random id.
  • Translation files are no longer part of the WordPress.org package; a copy shipped with its own translation still loads it.

0.4.3

  • When a “This is fine” could not be applied (the page looked different by the time it reached the checking service, or newer results had come in), the panel says so next to the button instead of leaving you to think it was.

0.4.2

  • A theme uploaded as a zip file over the active theme is shown in the update log with its name and version.
  • An upload stopped at “already installed” is no longer logged as an update.
  • The External services section names the AI provider (Anthropic) and links the service terms and privacy policy.

0.4.1

  • Tested with WordPress 7.1.
  • A site that is checked with its connection key no longer asks to be connected; connecting to the service is folded away.

0.4.0

  • “Connect” button: a site connects itself to the checking service with an e-mail address (free plan) or a connection code (paid plans).
  • The settings show the plan, its limits and a link to manage the subscription; “Disconnect” stops the checks.
  • Deleting the plugin tells the service to forget the site.

0.3.0

  • Simpler panel: three states (OK, Needs a look, Broken), pages shown by their titles, pages that are fine folded away.
  • Before / now slider for the place that changed.
  • “This is fine” button: a page changed on purpose gets its new look as the reference.
  • “Check now” usually starts within two minutes; the panel shows that a check is running and refreshes by itself.
  • Technical settings moved under “Advanced”.

0.2.0

  • The update log shows versions (“Example Plugin 1.2 → 1.3”).
  • Results in the language of the site; pages are opened with the site’s language and time zone.
  • The pictures show the place that changed, not only the top of the page.
  • E-mail also for site-wide problems (SSL certificate) and when everything is fine again; a failed e-mail is tried again.
  • Up to 100 pages per check are stored (before: 40, whatever the setting).
  • A page that was already failing when first seen is reported every time, not accepted as normal.
  • Results are stored under long random names and the result files are closed to visitors; unfinished uploads are cleaned up.
  • A check requested while another one is being stored is no longer lost.
  • The page list is rebuilt after updates and after a change of the link structure or front page.
  • Works when activated for a whole network; removing the plugin cleans every site of the network.

0.1.3

  • Every published page is checked, plus one stable example of each post type, product type and category archive, read from the database.
  • New setting “Most pages per check” (default 40); the panel shows how many pages were over the limit.
  • Checkout and account pages are left out.

0.1.2

  • Uploading a zip over an existing plugin is logged as an update of that plugin; inactive installs and own updates do not ask for a check.

0.1.1

  • Agent API answers are never stored by page caches (LiteSpeed and others).
  • Panel says “not connected yet” before the first agent connection.

0.1.0

  • First version: panel, history, settings, update log, e-mail alerts and agent API.