Default WooCommerce tab labels are one of those small details that quietly tell customers whether a store was built with care or thrown together in an afternoon. “Description,” “Additional Information,” and “Reviews” work fine on a generic demo store, but on a real storefront they read as leftover placeholder text. A furniture shop might want “Dimensions & Materials” instead of “Additional Information.” A supplement brand might want “Ingredients” and “Lab Results” instead of the stock labels. Renaming these tabs is a five-minute job once you know where to look, and it’s one of those changes that makes a store feel intentional rather than default.
This guide covers every practical way to rename WooCommerce product tabs, from a copy-paste code snippet through to plugin-based editing and full template overrides, along with the mistakes that trip people up (hook priority conflicts, text domain typos, and child theme issues being the three most common).
Why the Default Tab Labels Exist and Why You’d Change Them
WooCommerce ships with three tabs by default: Description, Additional Information (populated from product attributes), and Reviews. These labels are deliberately generic because the plugin has to work for every category of product imaginable, from digital downloads to physical goods with dozens of variations. The moment your store specializes, though, generic labels start costing you clarity.
A few real scenarios where renaming pays off: a skincare brand renaming “Description” to “How to Use,” an electronics retailer renaming “Additional Information” to “Specs & Compatibility,” a print-on-demand shop renaming “Reviews” to “Customer Photos,” or a wine store renaming “Description” to “Tasting Notes.” None of these require new functionality. They just relabel what’s already there, which is exactly why the code-based method below is so lightweight.
Method 1: The Code Snippet Approach
This is the method most WooCommerce developers reach for first because it’s fast, doesn’t add another plugin to your stack, and gives you full control over exactly which tabs get renamed. The filter you need is woocommerce_product_tabs, and it fires late enough in the template rendering process that you can safely rename, reorder, or even hide tabs entirely.
Rather than editing functions.php directly through the Theme Editor (which is risky since one syntax error can take your entire site down), the safer path is a small site-specific plugin or, if you already use one, adding the snippet through Code Snippets or WPCode. Either way, here’s the core snippet:
add_filter( 'woocommerce_product_tabs', 'wbcom_rename_product_tabs', 98 );
function wbcom_rename_product_tabs( $tabs ) {
if ( isset( $tabs['description'] ) ) {
$tabs['description']['title'] = __( 'How to Use', 'your-text-domain' );
}
if ( isset( $tabs['additional_information'] ) ) {
$tabs['additional_information']['title'] = __( 'Specifications', 'your-text-domain' );
}
if ( isset( $tabs['reviews'] ) ) {
$tabs['reviews']['title'] = __( 'Customer Feedback', 'your-text-domain' );
}
return $tabs;
}A couple of details matter here that the copy-paste tutorials online often skip. First, the priority number (98 in this example) matters. WooCommerce and some themes hook into this filter at different priorities, so if your rename doesn’t seem to take effect, try changing 98 to a higher number like 99 or 100 to make sure your function runs last. Second, always wrap each rename in an isset() check. If a theme or plugin has already removed one of the default tabs, trying to rename a tab key that doesn’t exist will throw a PHP notice, and on a site with debug mode visible, that notice can leak straight onto the front end.
If you sell variable products and want the Additional Information tab to reflect attribute-specific language (“Color & Size Options” instead of a generic label), you can even make the title conditional on the product category using wc_get_product() inside the same function.
Method 2: Reordering and Adding Tabs at the Same Time
Since you’re already editing the tabs array, it’s worth knowing you can reorder tabs in the same function using the priority key, or add an entirely custom tab (say, “Shipping & Returns” or “Size Guide”) without needing a separate plugin:
function wbcom_add_shipping_tab( $tabs ) {
$tabs['shipping'] = array(
'title' => __( 'Shipping & Returns', 'your-text-domain' ),
'priority' => 25,
'callback' => 'wbcom_shipping_tab_content',
);
return $tabs;
}
add_filter( 'woocommerce_product_tabs', 'wbcom_add_shipping_tab' );
function wbcom_shipping_tab_content() {
$heading = esc_html__( 'Shipping and Returns', 'your-text-domain' );
$body = esc_html__( 'Orders ship within 2 business days. Returns accepted within 30 days of delivery.', 'your-text-domain' );
printf( '%1$s %2$s', $heading, $body );
}This is genuinely useful once you realize renaming and adding tabs is the same mechanism. A lot of store owners pay for a “custom tabs” plugin when a ten-line snippet does the same job, with the added benefit of not adding another dependency that needs updates and compatibility checks every WooCommerce release.
Method 3: Using a Plugin (No Code Required)
Editing PHP isn’t for everyone, and that’s a completely reasonable position to hold, especially on a store where downtime means lost revenue. Two well-established plugins handle this without touching code:
Custom Product Tabs for WooCommerce by Itthinx is free on WordPress.org and lets you rename, reorder, hide, and create new tabs from a visual settings screen under Products. It’s a lightweight plugin from a developer with a long track record in the WooCommerce ecosystem (they also maintain the popular Groups membership plugin), so compatibility tends to hold up well across WooCommerce updates.
YITH WooCommerce Tab Manager is the premium alternative if you want more granular control, like assigning different tab sets to different product categories or building rich tab content with YITH’s own content blocks. YITH is one of the more established WooCommerce extension developers, and this plugin in particular is well suited to stores with varied product catalogs that need different information architecture per category.
Whichever plugin you pick, the workflow is roughly the same: install, activate, navigate to the tab settings, rename the existing tabs, save. No FTP, no code editor, no risk of a fatal error taking your checkout page offline mid-sale.
A Word of Caution on “All-in-One” Product Page Plugins
Be careful with plugins that promise to handle tabs, layout, upsells, and a dozen other features in one bundle. These tend to load a lot of extra CSS and JavaScript on every single product page, whether you use the features or not, and that has a measurable effect on page speed and, by extension, conversion rate. If all you need is renamed tabs, reach for a plugin that does exactly that rather than a suite plugin that happens to include it.
Method 4: Editing the WooCommerce Template Files Directly
The most hands-on method, and the one that gives you complete control over markup as well as labels, is overriding WooCommerce’s template files in a child theme. This is worth doing when you need more than a label change, like restructuring how the tab content itself is displayed.
Step 1: Confirm you’re working in a child theme. Editing parent theme files directly means every theme update wipes your changes. If you don’t already have a child theme, WordPress makes this straightforward: create a folder in wp-content/themes/, add a style.css with the correct header referencing the parent theme, and a functions.php that enqueues the parent stylesheet.
Step 2: Copy the template. Locate wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php and copy it into your child theme at the exact same relative path: wp-content/themes/your-child-theme/woocommerce/single-product/tabs/tabs.php. WooCommerce’s template override system will automatically pick up your copy instead of the plugin’s original.
Step 3: Edit the copy. Inside this file you’ll find the loop that iterates over $product_tabs and echoes each title. You can adjust the markup, add icons next to tab names, or change how the active tab is styled, all without touching WooCommerce core files (which would be overwritten on the next plugin update anyway, taking your changes with it).
Step 4: Test on staging first. Template overrides are the method most likely to break when WooCommerce ships a major update, because if the plugin changes the structure of tabs.php upstream, your outdated copy in the child theme keeps overriding it with old markup. Check your child theme’s template files against WooCommerce’s changelog whenever you update, and consider using your host’s staging environment to test major WooCommerce updates before they hit production.
Which Method Should You Actually Use?
If you just need to rename existing tabs, the code snippet in Method 1 is the right call for almost everyone. It’s five lines of well-understood code, it survives theme and plugin updates without issue, and it doesn’t add a dependency you have to keep updated. If you’re not comfortable editing code at all, Custom Product Tabs for WooCommerce is a solid, actively maintained free option that won’t slow down your product pages. Reach for the full template override only when you need structural changes beyond a label, like custom icons or a different tab layout entirely, and always test it against staging before a major WooCommerce release.
One thing that’s easy to overlook: whatever method you choose, keep your new tab titles short. Tab labels wrap awkwardly on mobile screens once they exceed roughly 20 characters, and WooCommerce’s default tab styling doesn’t truncate long titles gracefully on smaller viewports. “Ingredients & Sourcing” fits. “A Complete Breakdown of Every Ingredient We Use” does not.
How Tab Renaming Interacts With SEO and Schema
This is a detail almost every tutorial on this topic skips, and it matters more than the visual rename itself. WooCommerce automatically outputs Product schema markup (structured data that search engines read to build rich snippets), and the Reviews tab is directly tied to the aggregateRating and review properties in that schema. Renaming the visible tab label to “Customer Feedback” or “What Buyers Say” doesn’t touch the underlying schema output, which continues to reference reviews correctly behind the scenes. Google doesn’t read your tab labels for schema purposes, it reads the structured data block, so cosmetic renames are safe from an SEO standpoint.
Where people do run into trouble is when they use a plugin (or write custom code) to fully remove the Reviews tab rather than rename it, thinking it declutters the page. Doing that while WooCommerce continues to output review schema creates a mismatch: your structured data claims review content exists, but there’s no visible way for a user to find it, which can trigger a “content not visible to users” flag in Google’s Rich Results Test. If you rename Reviews, keep it functional. If you remove it, disable the schema output for it too, either through Rank Math’s schema settings or by filtering woocommerce_structured_data_product.
Similarly, if you rename Description to something like “Overview” or “Story,” check that any FAQ or HowTo schema you’ve added through Rank Math or Yoast doesn’t reference the old tab name in its configuration. Most SEO plugins pull content directly from the post body rather than the tab label, so this is rarely an issue, but it’s worth a quick check on stores with heavy custom schema setups.
Troubleshooting: When the Rename Doesn’t Show Up
A handful of specific issues account for almost every “I added the code but nothing changed” report in WooCommerce support forums:
Caching. If your site runs a page caching plugin like WP Rocket, LiteSpeed Cache, or W3 Total Cache, or if your host runs server-level caching (common with managed WordPress hosts), the old tab labels can be served from cache for hours after your code change goes live. Clear the specific product page from cache, or purge the full cache, before assuming the snippet failed.
Priority conflicts. As mentioned earlier, if a theme or another plugin also hooks into woocommerce_product_tabs, whichever function runs last wins. If your theme is a heavily customized WooCommerce theme (BuddyX and Storefront both do light tab customization for layout purposes), your rename might get overwritten if it runs at a lower priority number than the theme’s own hook. Bump your priority to 999 to force it to run last, then dial it back down only if you discover a genuine conflict with something else that needs to run after you.
Page builder overrides. If you’re using Elementor or a similar builder with a dedicated “Theme Builder” template for single products, the builder may render its own tabs widget rather than pulling from WooCommerce’s native tabs system. In that case, the code snippet approach won’t have any visible effect, because the page isn’t using WooCommerce’s default tabs template at all. Check whether your product page is built with Elementor’s Product Tabs widget instead, and rename directly within that widget’s settings.
Wrong tab key. The array keys for the default tabs are always description, additional_information, and reviews, regardless of what their current visible titles say. If another plugin has already renamed a tab and you’re trying to target it by a title string rather than these fixed keys, your filter won’t match anything. Always target the array key, never the display title.
Method Comparison at a Glance
| Method | Coding required | Best for | Survives theme updates |
|---|---|---|---|
| Code snippet (functions.php filter) | Minimal, copy-paste | Simple renames, no new plugin dependency | Yes |
| Custom Product Tabs for WooCommerce | None | Store owners who prefer a settings screen | Yes |
| YITH Tab Manager | None | Category-specific tab sets, richer content blocks | Yes |
| Template override (tabs.php) | Moderate, PHP/HTML editing | Structural changes beyond labels | Only if you track WooCommerce core updates |
Frequently Asked Questions
Will renaming a tab break existing product reviews or attribute data? No. The rename only changes the visible label. The underlying data (review entries, product attributes powering the Additional Information tab) is stored independently of the tab title and is untouched by any of the methods above.
Can I set different tab names for different product categories? Yes, though it requires slightly more code than the basic snippet, or a plugin like YITH Tab Manager that supports category-specific tab configurations natively. In custom code, you’d check has_term() inside your filter function before applying category-specific labels.
Does this work with WooCommerce Blocks and the new product editor? Yes. The woocommerce_product_tabs filter operates at the template rendering level on the storefront, which is independent of whether you’re using the classic product editor or the newer block-based one in the admin. Both write to the same underlying tab system on the front end.
My theme doesn’t show tabs at all, just accordion sections. Does this still work? Some themes render WooCommerce’s default tabs as an accordion on mobile or as the default layout entirely, using CSS to restyle the same underlying markup. The filter still works because you’re renaming the tab title in the data array, not the visual container. If your theme uses a completely custom tabs system instead of WooCommerce’s built-in one, check the theme’s documentation for its own renaming mechanism.
Should tab order change along with the names? Sometimes, yes. If you’ve renamed “Additional Information” to something more prominent, like “Why It Works” for a supplement or cosmetics product, it often makes sense to raise its priority so it appears earlier. Priority is a simple integer: Description typically sits at 10, Additional Information at 20, Reviews at 30. Lower numbers render first, so setting your renamed tab’s priority to 15 would slot it between Description and Additional Information without disturbing the rest of the order.
Mobile Tab Behavior Worth Testing
Product tabs are one of the more overlooked mobile UX details on WooCommerce stores. On a desktop layout, four or five tabs sit comfortably in a horizontal row. On a 375px-wide phone screen, the same tabs either wrap to a second line, get squeezed until the text truncates, or the theme converts them into a horizontally scrolling strip that a fair number of shoppers never realize they can swipe. After renaming your tabs, check how the new labels render on an actual phone, not just a resized browser window, since font rendering and tap-target spacing can behave differently on real devices than in a simulated viewport. If a renamed tab causes wrapping or overflow that didn’t happen with the shorter default label, it’s worth trimming the new title by a word or two rather than letting the layout break for mobile shoppers, who make up the majority of traffic on most WooCommerce stores today.
Backing Up Before You Touch Anything
This bears repeating even though it sounds obvious: back up your site, or at minimum your theme files and database, before making any of these changes, especially the template override method. A misplaced closing brace in a functions.php snippet or a broken PHP tag in a template file can produce a white screen on every product page, and diagnosing that under pressure while customers are trying to check out is not a position anyone wants to be in. Plugins like UpdraftPlus make this a two-minute task, and it’s two minutes well spent.
Renamed correctly, your product tabs stop looking like a WooCommerce demo and start looking like part of your brand. It’s a small change, but on a product page, small changes to information architecture are often the ones customers notice first, even if they couldn’t tell you exactly what changed.