Plugin profile · observed daily since 02 Aug 2026
Advanced WP Hide Referer
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by wplabs throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very early-stage: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day over the last 7 days, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 15 Aug | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (1) · active installs (10+) · version (1.1) · support threads (0) · threads resolved (0)
27 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- No release in 4,134 days (11.3 years). The last was 04 May 2015.
- Declares compatibility only up to WordPress 4.2.39, while 7.1 is current. The author has not confirmed it runs on the last 29 releases.
- wplabs publishes no other plugin in the directory, so there is no wider activity to compare against.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
- 02 Aug 202626 days agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 25 Oct 20169.5 years agoDormancy threshold crossed540 days since the last release (2015-05-04). Dormancy is a maintenance observation, not a judgement about the owner.
- 04 May 201511 years agoVersion 1.1 released
- 04 May 201511 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by wplabs for all 27 days we have observed it.
- It was last released 11 years ago (04 May 2015).
- Its author declares it tested up to WordPress 4.2.39; WordPress is now on 7.1.
- WordPress.org reports 10+ active installs.
- It carries 1 rating, averaging 5.0 out of 5.
What we don’t know yet
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
Hide elements or redirect users based on referrer domains. Useful for blocking partners, scrapers, or altering content per source.
This plugin allows a user to login by specific referer.
Webmasters can use this tool to prevent their site from appearing in the backlink statistics of another webpage and server logs of referred pages as r …
When visitors is referred to your site from a search engine, the plugin is showing them related posts to their search on your blog.
Ban visitors from certain sites from viewing or adding comments.
Block/blacklist known (and custom) spam referring domains at the WordPress level with an HTTP 403 Forbidden page.
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Advanced WP Hide Referer: a person reads every submission, and corrections get a reply within 5 business days.