Plugin Pulse Beta
← Pulse
T

Third Party Cookie Eraser

by Andrea Pernici · Privacy & Consent

Also makes 7 other plugins · 1.1K+ installs across the portfolio →

Remove all the occurence of third party embed inside posts, pages and widgets until consent. Plugin requirement PHP >= 5.3

Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.

⚠ Stale⚠ Likely abandoned⚠ Few reviews⚠ Open vulnerability

Health

D 48/100

Stale · Likely abandoned · Few reviews · Open vulnerability

Active installs

100+

≈150 estimated

Momentum

+24%

low volume, under 1,000 downloads a month

Biggest opportunity: “cookie”, “cookie law” and “third party cookie” aren't earning a slot. You list them, but you're not in the first 24 results for those searches. WordPress.org counts only your first five tags, so free the slot for a search you can win.

How scoring works →
48 Health · D
Maintenance 3/100
Rating quality 74/100
Support 70/100
Security 65/100

48 health vs 69 average across 917 Privacy & Consent plugins

Install conversion

How it's measured →

2.6%

of downloads still active

At least 100 of 3.9K lifetime downloads are still running, in line with its category: the median Privacy & Consent plugin keeps 2.1%, across 503 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Privacy & Consent plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.

High removal-risk signals

63/100

Maintenance and integrity signals that tend to precede a WordPress.org removal. Not an official status, a heads-up to act.

  • Long abandoned. No update in 11+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 4.2.39, well behind 7.1.

Details

Version
1.0.2
Last updated
11.4y ago
Added
2015-05-23 · 11 yrs old
Requires WP
2.6
Tested up to
4.2.39
Requires PHP
—

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

34 / 100

Under-optimized

Most to gain: Update recency

Update recency 0/100

Updated 4179 days ago, past the ~180 days where wp.org starts discounting

WP compatibility 3/100

Tested up to WordPress 4.2.39; the current branch is 7.1

Rating quality 51/100

5.0★ over 1 review, weighted for review count to 4.1★ and held back under 25 reviews

Listing tuning 92/100

4 of 5 tags set · short description in place

To rank higher: Last updated 4179 days ago — ship an update; wp.org decays a listing's search weight after ~180 days.

Get the full rank-higher report →

Daily downloads

Since 3 Nov 2024 · 730 days · wp.org + Plugin Pulse archive

+24% low volume vs prior 30d
62 Nov 2026

30-day downloads

Rolling 30-day volume · peak 90 · peaks are release surges

833 Nov 2026

Directory rank

Ranked about #13,300 to #16,400, alongside the other plugins at 100+ installs. Plugins with the same install count swap places between wp.org requests, so this is where most of them sit. Checked monthly, last on 1 Nov 2026.

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

8303 Nov 2026

Estimated active installs

The public count shows “100+”. Our estimate pins where the real number sits.

modeled estimate
100–200 ≈150

Modeled within the band wp.org reports; tightens as we track daily.

Install history since 15 Sep 2026

1003 Nov 2026

Security history

via Wordfence Intelligence

1 open vulnerability affects the current version (1.0.2). 0 of 1 disclosed are patched.

  1. 2024-11-28 CVE-2024-53755 Cross-Site Request Forgery Affects <= 1.0.2 No patch available

Vulnerability records provided by Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. License and terms.

CVE records: Copyright 1999-2026 The MITRE Corporation. CVE terms of use.

AI assistants

How it's measured →

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

This plugin’s searches fall outside the topics measured so far. See the topics measured so far.

Readme readiness

3 of 8 pass · checked 31 Oct 2026

Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.

  • ✓ Says what it does "Remove all the occurence of third party embed inside posts, pages and widgets until consent. Plugin require..."
  • ! Has a FAQ No FAQ section.
  • ! FAQ asks real questions No FAQ to judge.
  • ! Names who it is for Never says who the plugin is for or what they use it for.
  • ! Names what it works with Names no plugin, service or platform it works with.
  • ✓ Headings and lists 3 headings and 4 lists.
  • ! Enough to quote 743 characters of description; under 1,000 there is little to quote.
  • ✓ Tags match the text 3 of 4 tags appear in the text; "third party script" does not.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

No tier crossings observed yet.

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for Third Party Cookie Eraser into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/third-party-cookie-eraser" width="480" height="300" style="border:0" loading="lazy" title="Third Party Cookie Eraser — Plugin Pulse"></iframe>
Preview card ↗

Third Party Cookie Eraser: 100+ active installs, 5.0★ (1 reviews). Plugin Pulse (WP Mayor), as of 2026-11-03. https://plugins.wpmayor.com/plugin/third-party-cookie-eraser

Spotted a number that looks wrong? Report a data issue and we'll check it against the source.