Discussion starter: a technical SEO question, posted with an answer from Niraj Raut to open the thread. If you have dealt with this on a site, reply with what you saw, especially where it differs.
- Technical SEO
- WordPress SEO
Product specs load only when a tab is clicked on a WooCommerce store. Split them into separate URLs, or does that just create thin pages?
Disclosure: Niraj Raut, who posted this answer, runs the SEO consultancy linked at the end of it.
1 reply
-
Niraj Raut
Do not split the specifications into separate URLs. A page per product’s specifications would be thin, duplicate the product’s main page and compete with it. The right question is whether the specifications are in the page’s HTML when it loads, even if hidden behind a tab. Google indexes content in tabs and accordions that is present in the HTML, and it treats such content normally under mobile-first indexing. What it may not see is content that is fetched only when a user clicks the tab. WooCommerce’s default product tabs render their content in the HTML, but some themes and plugins load tab content on demand. Check the rendered HTML with URL Inspection; if the specifications are there, you are fine, and if not, change the theme or plugin so they are.
How to check
- Run URL Inspection’s live test on a product page and view the rendered HTML.
- Search the HTML for a specific value that appears only in the specifications tab, such as a dimension or model number.
- If it is present, Google can read it. If it is absent, the tab loads content on click.
- Repeat for a few products and templates, since plugins can behave differently on different product types.
Options depending on what you find
Finding Action Specifications in HTML, hidden by the tab No change needed for search Specifications loaded on click by a theme or plugin Change settings, theme or plugin so tab content renders in the page HTML Specifications only in a PDF Add the key specifications as an HTML table on the page Specifications that shoppers need to compare quickly Consider showing a summary above the fold, with full details in the tab Why separate URLs are a bad idea
- Each specification page would have little unique content beyond the specifications themselves.
- They would compete with product pages for product-name and model-number searches.
- They would double the number of crawlable product URLs.
- Shoppers want specifications alongside price, images and the add-to-basket button, not on another page.
Making specifications work harder
- Present specifications as an HTML table with clear labels and units.
- Use WooCommerce attributes consistently, so the same specification has the same name across products, which helps filters and comparisons.
- Include the most searched specifications, such as dimensions, compatibility and materials, in the product description or summary as well.
- Keep Product structured data consistent with the visible specifications where you include them, for example GTINs and brand.
Hypothetical example:
A WooCommerce store selling camera equipment uses a theme that loads the “Specifications” tab through a request when clicked. URL Inspection shows none of the specifications in the rendered HTML, and product pages rank poorly for specification-based searches such as lens mount and focal length. The store switches the tab setting to render content with the page, adds a short summary of key specifications near the top, and standardises attribute names. Within a couple of months, product pages begin appearing for searches that include specifications, and the store did not need to create a single new URL.
Watch for this:
Some performance plugins defer or lazy-load tab content to speed up the initial page. That can remove the specifications from the HTML Google sees. Check the rendered HTML after installing or changing any optimisation plugin.
Variable products need the same check
WooCommerce variable products often show specifications that change with the selected variation, such as dimensions or weight for different sizes. Those details are frequently loaded by script when a shopper chooses a variation, so the initial HTML may contain only the default variation’s details or none at all. Check what the rendered HTML includes for variable products specifically. A table showing specifications for all variations, or at least the most important ones, in the page HTML gives search engines and shoppers the full picture without requiring a selection first.
Tabs and user experience
Tabs are fine for users when the most important information is visible without clicking. For many products, shoppers look for a few key specifications before anything else. Showing those in the main product summary and leaving the full list in a tab gives both quick answers and completeness, and keeps the page tidy on mobile.
Keep specifications on the product page, confirm with URL Inspection that tab content is in the rendered HTML, fix any theme or plugin that loads it on click, present specifications as a clear HTML table, and avoid creating separate specification URLs.
Need help with this on your own site?
Niraj Raut works with businesses in Nepal, Australia, the UK, Europe and the US on technical SEO, ecommerce SEO, local SEO and AI search.
Add a reply Cancel reply
Replies are open to approved members. Log in or apply to join.