SEO SearchTerms Tagging 2 was a WordPress plugin designed to turn incoming search-term data into keyword tags or a keyword list on a page. Historical discussions describe it as useful for discovering phrases visitors used, but they also raise unresolved questions about WordPress compatibility, storage, server load, maintenance and SEO side effects. Treat it as legacy software: verify its current code and test it on a staging site before enabling it on a live installation.
What SEO SearchTerms Tagging 2 was built to do
The plugin’s central idea was simple: identify search terms associated with visits to a page and display those terms as tags, typically near the bottom of the content. Historical forum descriptions present it as a way to see the language people used to reach a site and reuse that language when improving pages or internal anchor text.
That function is different from ordinary keyword research. It reflects terms connected with visits to your own site, rather than a broad database of search-volume estimates.
How the term-capture workflow should be understood
- A visitor arrives on a WordPress page after using a search engine.
- The plugin attempts to associate a search phrase with that visit.
- It stores or processes the phrase and can render it as a tag or keyword list.
- An administrator can use the resulting phrases for content planning, terminology and internal-link decisions.
The historical material does not establish whether every version records only searches that produced a click or also records queries for which the site merely appeared in results. Do not assume it provides impression-level data unless the version’s documentation or code confirms that behavior.
#1 Best Overall
What is documented, and what remains uncertain
| Question | What historical sources indicate | What you must verify |
|---|---|---|
| Primary purpose | Incoming search terms can be displayed as keyword tags or a list. | Exactly where terms appear and which templates are supported. |
| Custom post types | Users asked about custom-post-type support. | Whether your post type works without code changes. |
| Storage | Users asked how and where terms are stored. | Database tables, options, cleanup behavior and privacy implications. |
| Server usage | Historical support questions raised server-load concerns. | Query frequency, caching compatibility and impact on your hosting plan. |
| WordPress compatibility | Compatibility with different WordPress versions was repeatedly discussed. | Whether the current plugin code runs on your PHP and WordPress versions. |
| Maintenance | Users questioned updates and whether the plugin had been abandoned. | The live plugin listing, developer repository, recent commits and support responses. |
Is SEO SearchTerms Tagging 2 safe?
There is no authoritative evidence in the historical discussions proving that the plugin itself causes a search-engine penalty. Some users nevertheless worried that automatically creating many keyword pages or links could leave an SEO footprint, produce excessive or repetitive tags, or coincide with ranking losses. Those reports are anecdotal and do not demonstrate causation.
The practical risks are easier to define:
- Outdated code: an old plugin may fail on modern WordPress or PHP, conflict with another plugin, or contain unpatched vulnerabilities.
- Uncontrolled output: noisy, duplicated or low-value tags can make a site harder to crawl and less useful to readers.
- Resource use: term processing and database queries may increase page-generation time or database growth.
- Data governance: search phrases can reveal sensitive or personal information, so retention and display need review.
Use a staging copy, back up the database, restrict the output to a controlled template area and monitor error logs and query performance. Do not publish every captured phrase automatically.
How to see the incoming terms
The WordPress.org auto-tags directory historically listed an add-on named SEO SearchTerms Admin. Its stated role was to list incoming search terms generated by SEO SearchTerms Tagging 2, giving administrators a reporting view instead of relying only on front-end tags.
Because both the base plugin and add-on have a legacy support history, confirm that their versions are compatible with one another and with your WordPress and PHP stack before installation. If the add-on cannot be maintained safely, export or review whatever data the base plugin already records rather than adding another unmaintained component.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Compatibility checks before installation
- Confirm the source. Use the current WordPress.org listing or the developer’s repository, not an unverified download mirror.
- Check runtime requirements. Match the plugin’s stated WordPress and PHP requirements to the versions running on your host.
- Inspect update history. Look for a recent release, resolved support issues and a functioning security-reporting channel.
- Test content types. Verify posts, pages and each custom post type you intend to use.
- Measure overhead. Compare page response time, database size and server logs with the plugin disabled and enabled.
- Review output controls. Set limits, prevent duplicate terms and exclude private, transactional or sensitive pages.
- Prepare rollback. Keep a database backup and document how to disable the plugin and remove its generated output.
If any of these checks cannot be completed, choose a maintained reporting or keyword-tracking tool instead of deploying this plugin on production.
Can its data improve SEO?
Historical users reported that the phrases helped them discover wording for page revisions and anchor text. These are personal experiences, not controlled tests, so they do not establish a ranking benefit. Treat the terms as ideas for editorial research: group variants, remove spam and irrelevant phrases, then decide whether a phrase genuinely matches search intent and the page’s subject.
Rank #4
Do not create a tag for every observed query. A small, curated vocabulary is more useful than an automatically expanding archive of thin or duplicate pages.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How to compare it with a modern alternative
The historical record does not provide an apples-to-apples performance comparison with current plugins. Evaluate any replacement on the following dimensions:
| Comparison axis | Why it matters | Question to ask a replacement vendor |
|---|---|---|
| Current compatibility | Prevents PHP, WordPress and theme conflicts. | Which WordPress and PHP versions are supported today? |
| Reporting versus automatic tagging | Reporting is usually safer than publishing every term. | Can terms be reviewed without rendering public tag links? |
| Volume and duplication controls | Limits reduce thin content and database clutter. | Can you cap, merge, exclude or manually approve terms? |
| Performance and storage | Term collection can affect queries and database growth. | What is stored, for how long and how is it cleaned up? |
| Maintenance history | Regular releases reduce security and compatibility risk. | When was the last release and how are vulnerabilities handled? |
| Support channel | Unanswered issues are costly on a production site. | Is there an active support forum, repository or paid support path? |
What the SitePoint reference can—and cannot—establish
The supplied title points to a SitePoint Forums entry labeled “#2 by ezine,” in the CMS and WordPress area. The exact post text, date and recommendation are not available here, so its wording and authorship should not be presented as verified fact. The broader historical record supports identifying SEO SearchTerms Tagging 2 as a search-term tagging plugin, but not attributing a specific claim to that forum reply.
Bottom line for a WordPress site in 2026
SEO SearchTerms Tagging 2 is best understood as a legacy way to collect and display phrases associated with incoming visits. Its concept can inform content decisions, and the SEO SearchTerms Admin add-on was intended to expose the terms in an administrative view. However, current maintenance, compatibility, storage behavior and capture rules remain unsettled. Unless a live code and compatibility review shows that it is maintained and safe for your stack, use a supported reporting tool and keep search-term data private, curated and separate from automatic public tagging.
Quick Recap
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.
