usdigitalmarketingindex.com SEO
How can related-product links expose complementary products to search crawlers?
Updated November 15, 2026
By being real links, present in the page’s HTML, from a product to the accessories, parts, and companions that truly go with it. A related-products block does two jobs when it is built that way. It shows a shopper what else is needed, and it gives a crawler a direct path from one product page to others that may sit deep in the catalog. Both depend on two conditions. The relationship has to be factual: the accessory fits, the refill is the right one, the part is for that model. And the link has to be followable: an anchor element with a URL in the markup the server sends. A carousel filled in by a script after loading, or a “recommended for you” block that changes with every visit, may deliver neither.
Accessory and compatibility relationships
Start from data, not from an algorithm’s guess.
| Relationship | Example | Basis |
|---|---|---|
| Required accessory | A thermostat that needs a wall plate sold separately | Manufacturer documentation |
| Compatible accessory | A room sensor that pairs with the thermostat | Manufacturer compatibility list |
| Consumable | The filter a unit takes | Part number in the manual |
| Spare part | A replacement display | Parts catalog |
| Companion product | A boiler and the flue kit that fits it | Installation manual |
| Successor or predecessor | The model that replaces this one | Manufacturer statement |
| Alternative | A similar product at a different price | Merchandising judgment; label it as an alternative |
Compatibility is a factual claim that a customer acts on. A wrong “fits your model” produces a return at best. Record the source of each relationship in the product data, and do not publish a compatibility link without one.
Keep the types distinct on the page. “Compatible accessories”, “Spare parts”, and “Similar products” are different statements, and each block should contain only what its heading says.
Crawlable links
Google’s guidance for ecommerce sites is direct on the mechanism: include links on pages using anchor tags, and do not rely on scripts for navigation, because “Googlebot might not detect navigation from JavaScript code” (Google’s guidance on URL structure for ecommerce sites). The same passage asks for meaningful text inside the link, such as the title of the product being linked to.
A crawlable related-product block:
<section aria-labelledby="accessories-heading">
<h2 id="accessories-heading">Compatible accessories for the T200</h2>
<ul>
<li><a href="/products/t200-wall-plate/">T200 wall plate</a></li>
<li><a href="/products/t200-room-sensor/">T200 room sensor</a></li>
<li><a href="/products/c-wire-adapter/">C-wire adapter</a></li>
</ul>
</section>
Forms that may not expose anything:
| Implementation | Risk |
|---|---|
| Block inserted by a third-party recommendation script after load | Absent from the served HTML; present only if rendering succeeds |
| Items wrapped in elements with click handlers and no <!–INLINECODE0–> | Not links |
| Links to tracking redirect URLs | The crawler meets a redirect or a blocked path, not the product |
| Carousel that loads further items on swipe | Later items never in the HTML |
| Personalized block | Different links on every fetch; nothing stable |
| Links to the canonical URL plus tracking parameters | Duplicate URLs for each product |
The reliable design renders the compatibility-based links on the server, to canonical product URLs, with the product name as anchor text. A personalized carousel can sit alongside for shoppers.
Avoiding irrelevant recommendation loops
An automated “customers also viewed” block can end up linking popular products to each other: the same few bestsellers on every page, each linking to the others, while the accessories and parts that need exposure receive nothing.
A sample product-to-accessory link graph for the fictional T200, with the compatibility evidence for each edge:
T200 Thermostat
|-- requires --> T200 wall plate [manual p.4: "wall plate sold separately"]
|-- works with -> T200 room sensor [compatibility list, manufacturer site]
|-- works with -> C-wire adapter [manual p.6: wiring options]
|-- replaced by -> T300 Thermostat [manufacturer announcement]
T200 wall plate
|-- fits --> T200 Thermostat [same source]
|-- fits --> T200 Multi [parts catalog]
T200 room sensor
|-- works with -> T200 Thermostat, T200 Multi [compatibility list]
C-wire adapter
|-- works with -> T200, T200 Multi, T300 [adapter data sheet]
Properties of a sound graph:
- Every edge has a source.
- Edges run in both directions where the relationship does: the accessory links back to the products it fits.
- No edge exists only because both products are popular.
- A product with no real relationships has no block.
- The number of links per block is limited to what is true, not padded to fill a row.
Loops to remove: blocks where A links to B, B to C, and C to A with no relationship among them; “related” lists identical across an entire category; and blocks dominated by items the store wishes to promote regardless of fit.
Success checks
| Check | Method | Pass condition |
|---|---|---|
| Links in served HTML | Fetch a product page without JavaScript | The block and its anchors are in the source |
| Followable URLs | Read the <!–INLINECODE1–> values | Canonical product URLs, no tracking redirects |
| Rendered view | URL Inspection, rendered HTML | Block present |
| Accessory depth | Crawl the site; record click depth of accessory pages | Shallower than before the block was added |
| Orphans | Compare crawl with catalog | No accessory reachable only by search |
| Accuracy | Sample 20 relationships against their recorded sources | All correct |
| Reciprocity | For each accessory, check it lists its parent products | Present |
| Stability | Fetch the same page twice | Same links |
| Stock | Check that links to discontinued items are handled | Removed or pointing to successors |
Then look at behavior in the store’s own data: whether shoppers use the block, whether accessories are bought with their parent products more than before, and whether returns for incompatibility fall. Any change in how accessory pages perform in search is observed over time in Search Console. It is not something this guide forecasts.
Maintain the relationships. When a product is replaced, its accessory edges need review: the successor may take different parts.
Lateral links between articles follow the same logic, relevance first and links that can be followed, and are covered in the guide to when two supporting articles within one topic cluster should link directly to each other.
The rule: link products that truly belong together, on the evidence of documentation, with plain anchor links in the served HTML.
Add your comment to this answer