Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchSEO SearchTerms Tagging 2 is a legacy WordPress plugin that turned incoming search terms into post tags and keyword lists. Its records document an old release and known security vulnerabilities, so it should not be installed on a live site without a qualified security review. The available records do not establish that it works with current WordPress versions or that its advertised SEO benefits improved rankings.
What SEO SearchTerms Tagging 2 did
Historical listings describe the plugin as using search terms that brought visitors to a site to generate tags and keyword lists for posts. Its stated aim was to strengthen on-page SEO and increase the number of indexed pages; those promotional claims are not evidence of ranking gains or guaranteed results. ChoosePlugin’s historical record documents the plugin’s former purpose.
As an Amazon Associate I earn from qualifying purchases.
A separate plugin, SEO SearchTerms Admin, was listed as an add-on that showed incoming search terms in a metabox under the post editor, allowing an editor to review them. The WordPress.org directory record says it was tested through WordPress 3.6.1; that old metadata does not establish present-day maintenance or compatibility. WordPress.org’s auto-tags directory contains the historical listing.
Is it compatible with current WordPress?
The available records do not establish compatibility with current WordPress releases. The historical record for SEO SearchTerms Tagging 2 identifies version 1.535, last updated 9 May 2012, and tested with WordPress 3.2.1. These are historical details, not a current compatibility claim. WPCore’s historical plugin archive records those details.
#1 Best Overall
The WordPress.org support archive includes historical topics about plugin updates, high server usage, custom post types, errors, and whether the plugin had been abandoned. These posts show that users raised maintenance and compatibility concerns over time; they do not show how the plugin behaves on a current WordPress installation or how common the reported problems were. The support archive is useful as a record of those past concerns, not as a current support channel or compatibility test.
Why the security history matters
Wordfence records CVE-2015-9458 for SEO SearchTerms Tagging 2 through version 1.535. Its advisory describes SQL injection through the pk_stt2_db_get_popular_terms count parameter, exploitable via CSRF, and says no patch is known. The same record lists CVE-2015-9459, a reflected cross-site scripting vulnerability. Read the Wordfence advisory.
This security record is a reason not to install an old copy on a production site without qualified review. It does not prove that every fork or modified version contains the same vulnerabilities; the cited advisory concerns the recorded version line, and it is not a test of every copy in circulation.
What to do if you find it on a site
Choose an approach based on whether the plugin is already installed and whether you need to preserve its data or output:
Quick Recap
Best Value
Rank #4
- Not installed: Do not add an old copy to a live site. The historical release record and security advisories are not evidence of present-day support.
- Installed but not needed: Keep it disabled while you assess its stored data and any tags or front-end output it created. Back up the site before removing or changing legacy plugin data.
- Installed and still in use: Ask a qualified WordPress security professional to review the exact copy and its role. If further inspection is needed, use an isolated staging copy rather than experimenting on the production site.
- Looking for query reporting: Replace it with a currently maintained approach chosen for your needs. The historical records discussed here do not verify a particular modern replacement as an equivalent.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




