Back to frontpage

TagHider Plugin Compatibility & Server Requirements
TagHider Plugin Compatibility

Built for modern WordPress stores and clean product pages.

TagHider Plugin is designed to hide visible product tags from the public storefront while keeping tags active in the WordPress and WooCommerce system background.

Recommended Server Requirements

For best performance, security and long-term stability, TagHider should be installed on a modern WordPress hosting environment.

PHP Version

Recommended: PHP 8.3 or newer

Minimum suggested: PHP 8.1+

Older PHP versions may work on some sites, but they are not recommended for production stores.

🗄

Database

Recommended: MariaDB 10.6+ or MySQL 8.0+

Use a maintained database version for better WordPress performance and reliability.

🔒

HTTPS / SSL

Required for live stores: valid SSL certificate

HTTPS is strongly recommended for all WordPress and WooCommerce websites.

Compatibility Overview

TagHider focuses on storefront display control. It does not remove tags from WordPress, WooCommerce, the database, filters, search logic or admin tools.

Component Recommended Status Notes
WordPress Latest stable version Supported Designed for modern WordPress installations.
WooCommerce Latest stable version Supported Best suited for WooCommerce product pages, archives and tag visibility control.
Classic Themes Modern maintained themes Supported Works with most standard WooCommerce template structures.
Block Themes Modern block-based themes Supported May depend on how the theme outputs product tag elements.
Page Builders Elementor, Gutenberg and similar builders Theme-dependent If a builder uses custom tag widgets, extra CSS rules may be needed.
Caching Plugins Any maintained cache plugin Supported Clear cache after activating or changing TagHider settings.
SEO Plugins Yoast, Rank Math, AIOSEO etc. Compatible Tags remain in the system and can still work in the background.
Multisite Per-site activation recommended Depends on setup Test carefully before network-wide activation.

Suggested PHP Settings

TagHider itself is lightweight, but WooCommerce stores benefit from healthier PHP limits.

memory_limit

Recommended: 256M or higher

WooCommerce stores, product imports and large plugin stacks need enough memory.

max_execution_time

Recommended: 120 seconds

Useful for heavier stores and admin operations.

upload_max_filesize

Recommended: 64M or higher

Helpful when working with themes, plugins and product media.

Pre-Installation Checklist

Use updated WordPress
Keep WordPress core updated before installing new plugins.
Use updated WooCommerce
TagHider is intended especially for WooCommerce product tag visibility.
Take a backup
Always back up files and database before installing plugins.
Clear cache
After activation, clear cache from caching plugins, CDN and browser.
Test product pages
Check single products, category pages, shop archive and search results.
Check custom themes
If your theme uses custom tag layouts, minor CSS adjustments may be needed.
Important: TagHider does not delete product tags. It hides their public visual output where supported. Tags can still remain available for organization, SEO workflows, product filtering logic, admin search and background use.

Compatibility FAQ

Does TagHider remove tags from WooCommerce?

No. TagHider hides visible tag output from the storefront. Tags remain stored in WordPress and WooCommerce.

Will SEO plugins still see my tags?

TagHider is designed to hide visual tag clutter, not destroy taxonomy data. SEO behavior can still depend on your SEO plugin, theme and settings.

Does it work with every theme?

It should work with most standard WordPress and WooCommerce themes. If a theme outputs tags using a heavily customized layout, extra theme-specific CSS may be required.

Why do I still see tags after activation?

Clear your cache first. If tags are still visible, the theme or page builder may be using custom tag markup that needs an additional hide rule.

Is TagHider heavy?

No. The plugin is intended to be lightweight. The main purpose is clean visual control, not complex database operations.