A button can work perfectly and still send an enquiry to the wrong place.
WadeBush Enquiry Guard checks whether the destinations in selected public pages match an administrator-approved business list. For example, a redesigned contact page might display your new office number while its call button still dials the previous number.
Approve your business destinations, select the pages that matter and run a manual check. Every finding includes the page, destination, short link label and a practical explanation.
There are no account requirements, trials, scan quotas, remote licence checks or tracking. Everything included in this plugin is usable without payment. Practical per-response safety limits are 2 MB of HTML and 5,000 links; exceeding them produces an unreadable result, never a successful partial check.
A broken-link check asks whether a destination responds. Enquiry Guard asks whether the link agrees with your approved destination and whether a required route still appears. It never calls a number, sends an email, opens an external booking destination or submits a form.
Checks use signed-out, server-returned HTML, including server-rendered theme headers, menus, footers, Gutenberg and Elementor output. Content generated only after JavaScript runs is not inspected. HTML hidden attributes and template contents are skipped, but CSS-hidden anchors may be included. Mobile, geographic, consent and personalised variants may differ.
Only published, non-password-protected WordPress pages and the homepage can be selected. Posts, PDFs, QR codes, plain-text contacts and form recipient settings are outside this version’s scope.
Supported WhatsApp links: wa.me/NUMBER, api.whatsapp.com/send?phone=NUMBER and web.whatsapp.com/send?phone=NUMBER. Short links such as wa.link are not resolved.
Booking checks match explicitly approved full HTTP/HTTPS URLs. They ignore fragments, trailing slashes and tracking keys (utm_*, gclid, fbclid and msclkid), but retain application query values. Other ordinary links are not classified as booking links.
An administrator must approve the correct destinations. A result without findings means no configured mismatch was found at the time of the check. It is not verification of ownership, inbox delivery, phone availability or a complete enquiry journey.
PHP 8.1+ with DOM support and WordPress 6.6+. Your host must allow public loopback HTTP requests. WordPress’s safe HTTP API can block localhost and private-network destinations. Requests never follow redirects. Multisite network activation is not supported; activate separately on individual sites.
Scans make unauthenticated GET requests to the selected published page URLs on your own site’s origin. These requests include the plugin name/version and site URL in the user agent and can appear in your hosting logs. No cookies or visitor credentials are sent.
The plugin does not contact the author, a cloud service, a booking provider, WhatsApp, or an email recipient. There is no telemetry, visitor analytics or external API.
Configuration and reports stay in your WordPress database. Reports retain public page URLs, normalised contact destinations, short link labels and findings. Full page HTML and mailto subject/body text are not retained. Reports are restricted to administrators.
A separately distributed Pro add-on adds scheduled scans, optional email alerts when scheduled findings change or clear, the last 50 scan summaries and change records, CSV export and printable client reports. None of its premium code is included in this free plugin. Pro requires this free plugin. The free plugin operates independently.
All PHP, JavaScript and CSS files in this ZIP are the original human-readable source. There is no compilation, bundler or build step and no third-party runtime library bundled with this plugin.