Cannibalisation
640 plugins
For 640 plugins a changelog or version URL outranked the plugin page for the plugin’s own name. Searchers landed on release notes with no price and no buy button.
FAULT 1 / 4
A fictional business. The figures are a modelled scenario, not a client result.
BITKOPPEL · TECHNOLOGY & SAAS · LEIPZIG
+71% organic plugin sales
12 months · Europe · Technology & SaaS · Commerce SEO plan
01THE SIGNAL PATH
Plugin pages competed with their own changelog and version URLs, categories were thin paginated lists, and internal links barely reached long-tail plugins.
Bitkoppel sells checkout, shipping, tax and media plugins for online shops, built by 300 independent developers. Every release created a new version page and every plugin kept a public changelog, so Google spent its time on release notes while the plugin pages that take the money sat lower. Category pages were twelve plugins at a time, page after page, and every “bestsellers” box pointed at the same three products. Most of the catalogue never got a link worth crawling.
ONE PLUGIN, MANY DOORS
For the search “kassenwart plugin”, Google ranked an old version page at #7 and the plugin page itself at #14.
02AUDIT
640 plugins
For 640 plugins a changelog or version URL outranked the plugin page for the plugin’s own name. Searchers landed on release notes with no price and no buy button.
FAULT 1 / 4
38,600 URLs
38,600 indexable changelog and version URLs against 2,400 plugin pages: an average of 16 near-duplicates per product, each taking a share of crawl and links.
FAULT 2 / 4
1,120 pages
48 categories split into 1,120 paginated pages of 12 plugins each, with the same boilerplate intro and no subcategories. Page 9 of “Shipping” was the only route to some plugins.
FAULT 3 / 4
61%
61% of plugins sat four or more clicks from the homepage. The 1,680 long-tail plugins had 1.4 internal links each, almost all from their developer’s profile.
FAULT 4 / 4
03THE PATCH
Built on our Commerce SEO plan: SEO for shops and marketplaces where the catalogue, the categories and the internal links decide what sells.
01
Every version URL 301-redirected to an anchor on its plugin page, and each changelog folded into a “Version history” section there. One URL per product now collects all the links, reviews and release news.
301 → /plugins/kassenwart#v4-2-1
02
1,120 thin paginated pages rebuilt as 310 category and subcategory hubs with 48 plugins per page, written intros, compatibility filters that stay out of the index, and self-canonical pagination.
48 → 310 hubs · noindex filters
03
A link model in place of one bestsellers box: “works with” links between compatible plugins, subcategory hubs linking down to every plugin, and developer pages linking across, so each plugin gets links from pages about the same job.
≤ 3 clicks · ≥ 6 links per plugin
04
SoftwareApplication markup with Offer, version and review data on every plugin page, built from the catalogue and validated nightly, so prices and ratings from real reviews can show in results.
SoftwareApplication · Offer · AggregateRating
04PATCH IT YOURSELF
Each category page has a fixed amount of link signal to pass on. Split it across its cables, patch the long-tail plugins in, then fold the changelog URLs into their plugin pages and watch the noise drop.
CATEGORIES · OUT
PLUGINS · IN
Choose a category jack, then a plugin jack, to patch a cable. Choose the same pair again to pull it out.
Patch: 9 cables.
Model: each category splits its link signal evenly across its cables; each plugin also has signal from its own backlinks. With separate changelog URLs, part of every plugin’s signal lands on its version pages. Illustrative units, not measurements. THRESHOLD 12
05SEQUENCE
MONTHS 1–2
Full crawl of 46,000 URLs, a cannibalisation map from Search Console, the internal link graph and organic sales per plugin.
MONTHS 3–4
Version URLs redirected to plugin-page anchors, changelogs merged in, sitemaps and the developer upload flow changed so new releases never create a page.
MONTHS 5–7
48 categories rebuilt as 310 hubs and subcategories, with intros written alongside the developers and filter URLs kept out of the index.
MONTHS 6–9
The internal link model shipped in three releases: “works with” links, subcategory listings, then developer cross-links. Click depth checked weekly.
MONTHS 8–12
SoftwareApplication markup, merchant listings and review snippets, then new hubs for gaps found in on-site search.
06OUTPUT
Organic plugin sales / month
+71%
1,840 → 3,150 sales a month
Changelog & version URLs indexed
38,600 → 0
Folded into 2,400 plugin pages
Long-tail plugins with organic sales
410 → 1,290
out of 1,680 long-tail plugins
Plugins within 3 clicks of home
39% → 96%
from 39% before the work
Modelled scenario for a fictional business — not a client result. Rankings, traffic and sales are never guaranteed; see our Terms.
The plugin page wins back its own name
Search: “kassenwart plugin”
Plugin page, before
#14
Month 12
#2
Running a marketplace or a large catalogue where the long tail never gets seen? Start with the Commerce SEO plan, or tell us what you sell.