A WooCommerce category description is usually missing because the active product-archive template does not render it, a page builder replaced the default archive output, or CSS hides the element. First confirm the description is saved on the correct product category, then inspect the public HTML. A WooCommerce SEO fix should preserve both the shopping layout and crawlable category context.
If the text exists in the HTML but is invisible, investigate styling or collapsed content. If it is absent from the HTML, investigate the taxonomy template, WooCommerce archive hook, block-template structure or builder conditions.
Quick diagnosis: where did the category description disappear?
| Test result | Likely cause | Next action |
|---|---|---|
| Description is empty in Products > Categories | Nothing was saved for that term | Edit the exact category and save a description. |
| Text is in page source but not visible | CSS, accordion or display setting | Inspect the element and computed styles. |
| Text is absent from source | Template, hook, block or builder omission | Check the product-category archive template. |
| It appears in a default theme | Active theme or child-theme override | Compare archive templates and hooks. |
| Admins see it but visitors do not | Cache, personalization or responsive rule | Purge caches and test signed out on mobile and desktop. |
WooCommerce’s product-taxonomy documentation explicitly notes that category descriptions are optional and that only some themes display them, usually beneath the category name. That detail matters: saving the field does not guarantee that the active storefront template contains an output location. See WooCommerce’s category and taxonomy documentation.
Did you edit the correct WooCommerce category?
Go to Products > Categories, locate the category used by the public URL, and edit it. Check the name, slug, parent and description before saving. Parent and child categories are separate terms, so copy added to “Shoes” will not automatically appear on “Women’s Trail Shoes.”
Then open the public category URL in a signed-out browser window. Do not test only the main Shop page. The shop archive and a product-category archive can use different templates, even when they look similar.
Is the description present in the HTML?
This one test divides the problem cleanly. View the page source and search for a distinctive sentence from the description.
- Found in source: WordPress rendered the content. Check CSS, responsive visibility, accordions, overlays and JavaScript.
- Not found in source: the server never printed it. Move to the theme, hook, block-template or builder checks.
- Found twice: two templates or widgets may be outputting the term description, with one copy hidden or positioned incorrectly.
Use a sentence that is unique to this category. Searching for a generic word like “products” can produce a false match elsewhere in the page.
At the WordPress level, term_description() retrieves the description for the current taxonomy term when no term ID is supplied. The official WordPress term description reference helps confirm that storing the term and printing it in a template are separate steps.
Does your classic theme call the WooCommerce archive-description hook?
Classic WooCommerce templates commonly provide an archive-description action area. WooCommerce’s own customization example attaches a category image to woocommerce_archive_description, which confirms the hook’s role in product-category archive output. See the official category archive hook example.
If a custom theme copied an old archive template or removed that action, the saved term description may never render. Compare the active template with the current WooCommerce template structure. Make changes in a child theme, staging site or version-controlled codebase. Editing the parent theme directly makes the fix disappear at the next update.
Do not add the description function blindly. If the hook already runs elsewhere, you can create duplicate copy. First identify what the template calls and what functions are attached.
Is a block theme controlling the product category template?
Block themes can replace PHP archive layouts with templates managed in Appearance > Editor. Open a product category while logged in, then inspect the template used for that archive. Look for the archive title, product collection and a term-description or equivalent content block.
A block may exist but sit inside a hidden group, an alternate template part or a desktop-only layout. Use List View to understand the nesting. Save changes in staging first because product archive templates often serve every category, not just the one you are testing.
Did a page builder replace the WooCommerce archive?
Elementor, Divi and other builders can apply a custom archive template through display conditions. The description saved in WooCommerce will not appear unless the builder template includes a widget or dynamic tag for the current product-category description.
- Open the builder’s theme or template area.
- Find the template assigned to product archives.
- Review its display conditions for all categories, selected categories and exclusions.
- Add the dynamic archive or term description in the intended location.
- Preview more than one parent and child category before publishing.
The wrong instinct is to paste static copy into the template. That repeats one category’s text across every archive. Use the current term’s dynamic description.
Could CSS be hiding a description that already exists?
Inspect the description element in browser developer tools. Look for display: none, visibility: hidden, zero height, clipped overflow, white text on a white background, or a mobile breakpoint that removes the block.
Also check “read more” components. A collapsed description may be present and indexable, but if the control fails, shoppers cannot use it. Test keyboard access and mobile behavior instead of treating visual presence as the only requirement.
Are cache and optimization layers serving an old template?
Purge the page cache, object cache, CDN cache and builder-generated CSS after confirming the template. Then test in a private window while signed out. Logged-in administrators often bypass full-page caches, which explains why a description can appear for the editor but not for customers.
Do not purge first and call the issue solved. Cache can hide a fix, but it does not explain why the original template omitted the description.
What if the description shows in the wrong position?
Many stores want a short introduction above the product grid and a longer buying guide below it. The default hook position may not match that design. Move or split the content deliberately, but preserve a useful opening near the category title and avoid pushing products far down the page.
| Location | Best content | Purpose |
|---|---|---|
| Above product grid | Two or three concise sentences | Confirm category, audience and main buying distinction. |
| Below product grid | Selection guidance, materials, fit, care and FAQs | Answer deeper questions without blocking browsing. |
| Sidebar or filter area | Short supporting labels only | Do not force the main description into a cramped column. |
For SEO, the copy must exist in the rendered HTML and remain specific to the category. For conversion, it must help someone choose. A visible wall of generic keywords satisfies neither goal.
A safe troubleshooting order
- Confirm the term description is saved on the exact category.
- Open the category URL, not only the Shop page.
- Search the public HTML source for a unique sentence.
- Check the classic archive hook or block-template structure.
- Review page-builder archive conditions and dynamic fields.
- Inspect CSS and responsive states.
- Purge caches and regenerate builder CSS.
- Test parent categories, child categories, pagination and mobile layouts.
Change one layer at a time. Switching themes, disabling plugins and adding code simultaneously can make the description reappear without telling you which change fixed it.
Common mistakes after the description starts showing
- Printing the same static paragraph on every category.
- Outputting raw term content without the platform’s normal sanitization and formatting.
- Adding a second H1 inside the description.
- Hiding hundreds of words behind an inaccessible control.
- Editing the parent theme and losing the fix during an update.
- Testing only while logged in or only on desktop.
When should you ask for WooCommerce help?
Get specialist help when custom templates, multilingual taxonomies, builder conditions or child-theme overrides interact, or when a store update removes descriptions across many categories. Organic Cart Studio can diagnose the rendering issue and connect the repaired category pages to broader ecommerce SEO priorities without turning every archive into a long article.
FAQs
Where do I add a WooCommerce product category description?
In WordPress admin, go to Products > Categories, edit the exact category, enter the description and save. Whether it appears depends on the active archive template.
Why does the description show in admin but not on the storefront?
The database value can exist while the theme or builder template omits its output. Check the public HTML source to distinguish a template issue from a CSS issue.
Can I show the category description below the products?
Yes, but the implementation depends on the theme or builder. Keep a short category cue near the top and place longer selection guidance below when that supports browsing.
Will changing themes fix the missing description?
A default theme test can identify the active theme as the cause. It is a diagnostic step, not always the final fix, because your production design and custom templates still need repair.
Does a category description guarantee better rankings?
No. Useful category copy can clarify relevance and help shoppers choose, but rankings also depend on intent match, products, internal links, technical quality, competition and authority.
Leave a Reply