For WooCommerce

Which is why most auto-linking plugins do nothing useful on a shop. They read the standard editor field, and a WooCommerce store keeps its text in product descriptions, short descriptions, category texts and custom fields — places those plugins never look.

Three differences change how internal linking works on a store.

The important pages are categories, not products. A category page is what has a chance at a broad search term; individual products compete for long-tail variants and often for nothing at all. So the flow should run from product descriptions and blog posts into categories, not the other way round. Most shops have it backwards — categories enlace out to dozens of products, and nothing links back.

Product text is short and repetitive. A blog post has room for context; a product description has three paragraphs, half of which are shared across a range. A threshold and a per-page cap matter more here than anywhere, because a rule that fires on every occurrence turns a product page into a link list.

The catalogue changes without anyone editing text. Products come and go, categories get restructured, seasonal lines disappear. Every one of those events cuts internal links that nobody remembers making — which is why shops accumulate orphan pages faster than blogs do.

The Pro version processes WooCommerce product descriptions and category texts like any other content, and it reads fields built with Advanced Custom Fields — not only the standard editor content.

That last part is what decides whether a plugin is usable on a real store. Any shop past a certain size keeps its material in custom fields: care instructions, technical specifications, sizing notes, ingredient lists. On a well-built store that is where most of the words live. A tool that reads only post_content sees a fraction of the catalogue and reports success anyway.