Scope and decision

A backlink cannot make an unclear product page useful or repair a broken category path. Review one category, one ordinary product and one variant before expanding acquisition. This checklist helps you decide what to inspect; it has not scanned your store.

What to inspect first

Separate a symptom from a diagnosis. A missing product in a report may be undiscovered, excluded, redirected or simply outside that report's coverage. Record the URL and observed response before changing templates. Mark unavailable evidence as unknown rather than assuming the issue is fixed.

Worked decision matrix

In a fictional outdoor store, a waterproof bag can only be found through search. A color option changes the URL, while internal links use a different version. First add a relevant category path; then inspect the variant relationship instead of buying links to every URL variation.

  • Search-only discovery: Observed symptom: The product is found through internal search but not category links.; Repair decision: Add a relevant crawlable category-to-product path.; Retest: Follow public category links and inspect their href values.
  • Variant URL conflict: Observed symptom: Links, sitemap and canonical refer to inconsistent product representations.; Repair decision: Document the intended variant model and align signals with it.; Retest: Inspect a main product and a variant; do not assume every variant must be merged.
  • Thin product evidence: Observed symptom: The page repeats a name but omits size, compatibility or useful selection details.; Repair decision: Add accurate product-specific information that answers the purchase task.; Retest: Check claims against the actual product and read the page as a new buyer.
  • Stale destination: Observed symptom: A removed product still receives navigation links that lead to an error or irrelevant page.; Repair decision: Choose a relevant replacement when one exists; otherwise explain removal appropriately.; Retest: Check the old response, destination and internal links; avoid blanket homepage redirects.
  • Filter crawl growth: Observed symptom: Many filter combinations produce repetitive or empty pages.; Repair decision: Decide which combinations serve a real search task and manage the rest deliberately.; Retest: Sample filtered URLs, links and crawl rules; distinguish crawling from indexing.

Choose the next action

Prioritize errors that prevent customers reaching or understanding the intended product. For each proposed fix, identify the owner and a success check. A filter URL that answers a distinct useful task deserves different treatment from countless empty combinations; do not block every parameter by habit.

Keep a useful review record

Keep before and after observations separate. After a navigation repair, follow category links in a public view and check the anchor destination. After a URL change, inspect status and destination. A successful browser visit is not proof of indexing; record search evidence separately if available.

  • Choose a representative category, product and variant.
  • Write the observed evidence before proposing a fix.
  • Assign a repair owner and an explicit retest.
  • Keep unknown, repaired and independently verified states separate.

Limits and next steps

The matrix is not a complete technical audit. Stock changes, international versions and complex rendering may require deeper checks. Canonical hints and robots rules serve different purposes; a crawl block alone does not prove removal from search. Resolve uncertainty before calling a repair complete.

This is a manual planning aid, not a live audit, supplier catalog or ranking prediction. Examples are fictional. Nothing is fetched or submitted; downloaded files stay on your device.