Wishlist Bot Shield

$0.00

Download free

No account, no licence key. Every capability is included and nothing expires.

Downloaded 149 times

Stop crawlers following wishlist links such as ?add_to_wishlist=123 and leaving wishlist rows for visitors who do not exist. Rejects nonce-less and known-crawler requests, challenges the rest and rate-limits them before your wishlist plugin runs. Free to download and use.

Description

Your wishlist button is a plain link, and crawlers follow it. Wishlist plugins render the button as ?add_to_wishlist=123&_wpnonce=… . Search engines, social scrapers and AI crawlers follow that link on every paginated shop and category page. Each follow is a real request, and on many wishlist plugins it is a real database write: a wishlist row is created for a visitor who does not exist. A robots.txt rule does not stop a spoofed or rotating user agent, and a per-IP firewall rule blocks real customers along with the bots.

What it does, before your wishlist plugin runs

Wishlist Bot Shield inspects the wishlist action request and decides before your wishlist plugin processes it. There is nothing to change in the wishlist plugin and no template to edit.

  • Nonce guard. A wishlist action request with a missing or malformed nonce is rejected before the wishlist plugin sees it. A valid but expired nonce is challenged rather than hard-blocked, so a shopper on a stale page can still complete the action.
  • Known crawler and automation block. Requests whose user agent is a known crawler, scraper or automation tool are blocked, case-insensitively, and only on wishlist action URLs.
  • JavaScript and signed-cookie challenge. Anything that does not look like a browser that has already visited is shown a small self-contained test that a spoofed user agent or a non-executing crawler cannot pass.
  • Rate limits. Per-visitor and site-wide limits answer HTTP 429 with a Retry-After header instead of processing another request.

See exactly what was happening

The Overview screen shows how many wishlist requests were blocked and challenged over the last seven days, the top offending user agents and daily totals. A Premise check panel reads the same first-party log over 30 days and reports how many distinct visitors triggered it, so you can see whether the bot-write problem is real on your store before anything is enforced.

The Wishlist Bot Shield Overview screen showing 5 requests blocked and 2 challenged over seven days, a top-offending user agents table naming several crawlers, and a daily total for one day

The Blocked Requests log lists every decision newest first, with the verdict, reason, query argument, method, user agent and a hashed address. Filter by verdict, reason or argument, page through the rows and export the current view to CSV.

The Blocked Requests log showing eight rows with verdicts, reasons, query arguments, methods, user agents and hashed addresses, plus verdict, reason and argument filters and an Export CSV link

Monitor mode records the verdict and reason that enforcing would have applied without blocking a single request, so you can confirm the rules match real traffic before you switch to enforce.

The Wishlist Bot Shield settings screen with Monitor selected, the protection toggles, a per-visitor limit of 30 requests per ten minutes, a site-wide limit of 300 per minute and a seven-day log retention

A WordPress dashboard widget carries the same headline numbers and the top three user agents, and links straight to the log.

The Wishlist Bot Shield dashboard widget showing 5 requests blocked and 2 challenged in the last seven days with the top three user agents

Stop the search leak at the source

Wishlist action URLs are also a search problem, and the shield cleans them up at the source: a Disallow rule for each watched argument in robots.txt, an X-Robots-Tag: noindex, nofollow header, a noindex robots meta tag, and a canonical link with every wishlist argument stripped. A request that carries no wishlist argument is not touched at all.

Everything is included, and it is free

There is one edition of Wishlist Bot Shield. Every feature is included and free to download and use: no key, no trial, no time limit and no capability that switches off.

  • Rejects wishlist action requests with a missing or malformed nonce before the wishlist plugin processes them.
  • Blocks known crawler, scraper and automation user agents on wishlist action URLs.
  • Challenges anything that does not look like a browser with a JavaScript and signed-cookie test.
  • Applies per-visitor and site-wide rate limits, with HTTP 429 and Retry-After.
  • Logs blocked and challenged requests with the offending user agent and a salted address hash, with CSV export and a dashboard widget.
  • Adds robots.txt Disallow rules, X-Robots-Tag noindex/nofollow, a noindex robots meta tag and canonical tags that strip wishlist arguments.
  • Records what enforcement would have done, without blocking anything, in monitor mode.
  • Prunes the log daily under a configurable retention period, seven days by default.

How it works

  • A wishlist action request arrives carrying add_to_wishlist or add-to-wishlist.
  • The shield checks the nonce, then matches the user agent against the crawler and automation list.
  • A request that is not already verified is shown the JavaScript and signed-cookie challenge once.
  • Verified browsers are allowed through to your wishlist plugin; repeated unverified requests hit the rate limits and receive HTTP 429 with Retry-After.
  • Every decision is written to the log, and old rows are pruned daily.

What it does not do

The limits are real and worth knowing before you rely on it.

  • It does not stop every crawler. A headless, JavaScript-capable crawler can still pass the challenge, and the user-agent list, rate limits and challenge are all filterable so you can tighten them without a code change.
  • A full-page cache or CDN that serves the wishlist URL without running PHP is harmless – no wishlist write happens – but that request is invisible to the log.
  • It does not modify the wishlist plugin, its storage or its templates. It does not touch an ordinary page or a request with no wishlist argument.

If the problem is occasional, a firewall rule may be enough. This is for a store where the wishlist argument is a sustained problem.

Requirements

  • WordPress 6.0 or higher.
  • PHP 7.4 or higher.
  • A wishlist plugin that uses a query-argument action URL, which is the common pattern.
  • WooCommerce is optional. With or without it, the plugin registers its own top-level Wishlist Bot Shield menu with Blocked Requests and Settings beneath it. The required capability is manage_woocommerce when WooCommerce is active and manage_options when it is not, and a dismissible notice appears only on the plugin’s own screens when WooCommerce is missing.
  • HPOS: not applicable. The plugin reads and writes no order, customer, coupon or session data, so there is nothing for High-Performance Order Storage to change.
  • No runtime dependencies and no account.

Frequently asked questions

Does it work with HPOS?

HPOS does not apply. The shield inspects request arguments and headers and writes only its own log table; it never calls an order, refund, customer, coupon or session API, so there is no order storage for it to be incompatible with.

Does anything expire or stop working?

No. Wishlist Bot Shield is free to download and use, with no key, no trial and no time limit. Every capability is available from the moment you activate it and stays available.

Can I use it on client sites?

Yes. The plugin is GPL-2.0-or-later and there is no per-site key or activation limit, so you can install it on any site you manage.

Do you offer refunds?

There is nothing to refund: the plugin is free to download and use, with no purchase and no account.

Does it require WooCommerce?

No. WooCommerce is expected on a store, but it is not required. Without it the shield still protects wishlist action URLs and the menu stays in place; the required capability becomes manage_options instead of manage_woocommerce.

Will it break my wishlist plugin?

No. The shield only inspects requests that carry a watched wishlist argument and leaves every other request untouched. Allowed requests reach your wishlist plugin exactly as before.

What happens to a real customer?

A real browser sees the challenge once, sets the signed cookie and is then allowed. A shopper whose browser blocks cookies is blocked after one reload instead of being caught in a loop.

Can I tune the rules?

Yes. The wbs_bot_user_agents filter replaces or extends the crawler list, and wbs_watched_query_args changes which query arguments are treated as wishlist actions.

Where is my data stored?

In your own WordPress database. One custom table holds the wishlist query argument, the verdict and reason, the HTTP method, a user-agent string truncated to 200 characters and salted hashes of the visitor address and fingerprint; the raw address is never stored and the admin screens show only the hashes. Rows are pruned daily and kept seven days by default. A default install makes no outbound request. The full details are in the privacy note on this page.

Where do updates come from?

This build is not in the WordPress.org plugin directory, so there is no automatic update channel. The version you download here is the version you run; when a newer version is published, download it again from this page.

Updates and licensing

Wishlist Bot Shield is a single free edition released under the GPL-2.0-or-later licence. There is no key, no activation limit and no account, and nothing switches off over time.

Because the plugin is not distributed through the WordPress.org plugin directory, there is no automatic update channel: the version you download here is the version you run, and a newer version is downloaded again from this page.

A dormant licence client is bundled in includes/License/ as a privacy matter only. It is off by default, the free build provides no screen that asks for a key, and a default installation never contacts it. If a site owner ever opts in, it can contact the TillFoundry licence server; the privacy note on this page lists exactly what it would send.

Additional information

Requires WordPress

6.0 or higher

Requires PHP

7.4 or higher

Requires WooCommerce

Optional – works without it; the plugin's own menu stays in place

HPOS compatible

Not applicable – no order data is read or written

Licence

Free – no key, no expiry, no site limit

What is included

Everything below is included in this plugin.

  • Rejects wishlist action requests with a missing or malformed nonce before the wishlist plugin processes them
  • Blocks known crawler, scraper and automation user agents on wishlist action URLs
  • JavaScript and signed-cookie challenge that a spoofed user agent or a non-executing crawler cannot pass
  • Per-fingerprint and global rate limiting on wishlist action requests, with HTTP 429 and Retry-After
  • Blocked-request log with top offending user agents and salted address hashes, plus a WordPress dashboard widget
  • robots.txt Disallow rules, X-Robots-Tag noindex/nofollow, a noindex robots meta tag and canonical tags that strip wishlist arguments
  • Monitor mode that records what enforcement would have done without blocking anything
  • Daily pruning of the request log under a configurable retention period

Reviews

There are no reviews yet.

Be the first to review “Wishlist Bot Shield”

Your email address will not be published. Required fields are marked *