Orphan SKU Discovery Audit

Sitemap inclusion gets treated as discovery, so a product listed in one is assumed reachable. A URL with no internal links pointing at it is crawled late, ranks weakly and is dropped first when crawl demand tightens. On a large catalogue the cause is structural: infinite scroll with no paginated fallback, a grid capped at 60 items, or a range reachable only through a filter, and none of that appears in a sitemap coverage report.

Le fichier de compétence

---
name: orphan-sku-discovery-audit
description: Use when a large share of products sit in the XML sitemap but are rarely crawled or never indexed, and nobody can explain how a crawler is meant to reach them.
---

# Orphan SKU Discovery Audit

Sitemap inclusion gets treated as discovery, so a product listed in one is assumed reachable. A URL with no internal links pointing at it is crawled late, ranks weakly and is dropped first when crawl demand tightens. On a large catalogue the cause is structural: infinite scroll with no paginated fallback, a grid capped at 60 items, or a range reachable only through a filter, and none of that appears in a sitemap coverage report.

## Ce qu’il vous faut d’abord

- A full crawl started from the home page with sitemap discovery switched off, so it measures real link paths
- The complete sellable SKU list from the database or feed, to diff against what the crawl found
- Server logs showing Googlebot hits per product URL across 30 days
- Search Console page indexing export split by sitemap

## Méthode

1. Crawl from the home page with sitemap discovery disabled. Anything unreachable this way is orphaned regardless of what the coverage report says.
2. Diff the crawl result against the full SKU list. The missing set is the orphan list, and on catalogues using infinite scroll it is usually far larger than anyone expects.
3. Record click depth for every SKU the crawl did reach. Depth past roughly 4 correlates with slow crawling on large sites, so the depth histogram sizes the problem before you change anything.
4. Trace how the deep and orphaned products are meant to be reached. The answer is almost always a filter, a search box or a scroll event, none of which emit a crawlable anchor.
5. Add real paginated anchors behind any infinite scroll and verify them in the rendered DOM rather than the source, since the pagination frequently exists only after the script runs.
6. Cross-check the orphan list against the logs and against demand. A product that is properly linked and still unvisited after 30 days has a demand problem, and retiring part of that set is the honest answer.
7. Re-run the sitemap-free crawl after the fix and report the shift in the depth histogram rather than the orphan count alone, because moving a SKU from depth 9 to depth 7 changes nothing.

## Ce que ça produit

An orphan list and a click-depth histogram for the full catalogue, with the navigation and pagination changes required to bring the tail inside four clicks.

## Là où ça dérape

- Running the audit crawl with sitemaps enabled, which hides the orphans and produces a clean report on a broken structure
- Treating sitemap inclusion as a discovery path, so orphans stay orphaned while coverage looks acceptable
- Fixing depth by dumping thousands of links into the footer, which spreads equity thinly and is discounted anyway
- Measuring success as a lower orphan count when the newly linked products are still six clicks from the home page

---

Extrait de la bibliothèque de compétences QuQi - https://www.quqi.io/fr/skills/orphan-sku-discovery-audit

Ce qu’il vous faut d’abord

• A full crawl started from the home page with sitemap discovery switched off, so it measures real link paths
• The complete sellable SKU list from the database or feed, to diff against what the crawl found
• Server logs showing Googlebot hits per product URL across 30 days
• Search Console page indexing export split by sitemap

Méthode

1. 01 Crawl from the home page with sitemap discovery disabled. Anything unreachable this way is orphaned regardless of what the coverage report says.
2. 02 Diff the crawl result against the full SKU list. The missing set is the orphan list, and on catalogues using infinite scroll it is usually far larger than anyone expects.
3. 03 Record click depth for every SKU the crawl did reach. Depth past roughly 4 correlates with slow crawling on large sites, so the depth histogram sizes the problem before you change anything.
4. 04 Trace how the deep and orphaned products are meant to be reached. The answer is almost always a filter, a search box or a scroll event, none of which emit a crawlable anchor.
5. 05 Add real paginated anchors behind any infinite scroll and verify them in the rendered DOM rather than the source, since the pagination frequently exists only after the script runs.
6. 06 Cross-check the orphan list against the logs and against demand. A product that is properly linked and still unvisited after 30 days has a demand problem, and retiring part of that set is the honest answer.
7. 07 Re-run the sitemap-free crawl after the fix and report the shift in the depth histogram rather than the orphan count alone, because moving a SKU from depth 9 to depth 7 changes nothing.

Ce que ça produit

An orphan list and a click-depth histogram for the full catalogue, with the navigation and pagination changes required to bring the tail inside four clicks.

Là où ça dérape

• Running the audit crawl with sitemaps enabled, which hides the orphans and produces a clean report on a broken structure
• Treating sitemap inclusion as a discovery path, so orphans stay orphaned while coverage looks acceptable
• Fixing depth by dumping thousands of links into the footer, which spreads equity thinly and is discounted anyway
• Measuring success as a lower orphan count when the newly linked products are still six clicks from the home page

Utiliser cette compétence dans votre propre IA

Le fichier téléchargé est un simple markdown dont l'en-tête porte le nom et le déclencheur. Quand un assistant sait charger des compétences tout seul, c'est cet en-tête qu'il lit pour décider que celle-ci s'applique.

Plus dans SEO e-commerce