Plugin Pulse Beta
← Pulse
G

GET Params

by Nathan Singh · Uncategorized

Shortcodes allowing you to display GET parameters from the current URL in pages and posts, or show/hide content depending on GET param values

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

Health

D 50/100

Stale · Likely abandoned

Active installs

1K+

≈1.5K estimated

Momentum

+57%

low volume, under 1,000 downloads a month

Biggest opportunity: “get”, “params” and “shortcode” 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 →
50 Health · D
Maintenance 3/100
Rating quality 89/100
Support 70/100

Install conversion

How it's measured →

7.6%

of downloads still active

At least 1K of 13.1K lifetime downloads are still running, above its category: the median Uncategorized plugin keeps 0.6%, across 17,781 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Uncategorized 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 7+ years — the top precursor to removal once a vulnerability is found.
  • Compatibility drift. Tested only up to WordPress 5.2.30, well behind 7.1.

Details

Version
1.1
Last updated
7.3y ago
Added
2014-01-05 · 12 yrs old
Requires WP
4.0
Tested up to
5.2.30
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.

35 / 100

Under-optimized

Most to gain: Update recency

Update recency 1/100

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

WP compatibility 10/100

Tested up to WordPress 5.2.30; the current branch is 7.1

Rating quality 72/100

5.0★ over 15 reviews, weighted for review count to 4.3★ and held back under 25 reviews

Listing tuning 92/100

4 of 5 tags set · short description in place

Support resolution 0/100

0 of 1 support threads resolved in the last 2 months

To rank higher: Last updated 2665 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 5 Oct 2022 · 1,491 days · wp.org + Plugin Pulse archive

+57% low volume vs prior 30d
113 Nov 2026

30-day downloads

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

2463 Nov 2026

Directory rank

wp.org popularity rank over time · lower is better

6.5K3 Nov 2026

Health trend

Composite health score, snapshotted daily

503 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.

2463 Nov 2026

Release cadence

No release in a year
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

0

releases in the last 12 months

7.3y ago

latest release · v1.1 · 18 Jul 2019

2

tagged releases on record

Recent releases

1.1 · 18 Jul 20191.0 · 20 Nov 2015

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 100% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v1.1 100%

Estimated active installs

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

tracked estimate
1K–2K ≈1.5K

Crossed into this band 2.8 years ago; the previous band took 3.3 years to cross, which places it about 50% of the way through.

Install history since 19 Apr 2015

1K3 Nov 2026

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 1 Nov 2026

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

  • ✓ Says what it does "Shortcodes allowing you to display GET parameters from the current URL in pages and posts, or show/hide con..."
  • ! Has a FAQ Only 2 questions in the FAQ; 3 or more gives an assistant something to match.
  • ! FAQ asks real questions 0 of 2 FAQ entries are headings, not questions ("undefined").
  • ! Names who it is for One audience phrase ("use this"); say who the plugin is for and what they use it for.
  • ! Names what it works with Names no plugin, service or platform it works with.
  • ! Headings and lists 4 headings and 0 lists; assistants quote headed sections and bullet lists, not paragraphs.
  • ✓ Enough to quote 2,128 characters of description.
  • ✓ Tags match the text 3 of 4 tags appear in the text; "vars" does not.

Growth timeline

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

  1. 2024-01-06 2K+ → 1K+ down after 1221 days in tier
  2. 2020-09-02 500+ → 2K+ up after 1383 days in tier
  3. 2016-11-19 200+ → 500+ up

Embed this report card

Drop a live Pulse card for GET Params into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/get-params" width="480" height="300" style="border:0" loading="lazy" title="GET Params — Plugin Pulse"></iframe>
Preview card ↗

GET Params: 1K+ active installs, 5.0★ (15 reviews). Plugin Pulse (WP Mayor), as of 2026-11-03. https://plugins.wpmayor.com/plugin/get-params

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