Letting Faceted Navigation Multiply Crawlable URL Variants
Evidence: Crawl exports, server logs, internal link reports, or Search Console may show large families of parameterized or filtered collection URLs created by combinations such as size, color, material, and price. The mistake is not the existence of filters. It is allowing low-value combinations to remain widely discoverable when they do not need independent search visibility. Review how filter URLs are generated, linked, canonicalized, and indexed before deciding on a remedy.
Consequence: Search crawlers can spend attention on repetitive filter states while important collection and product URLs remain deeper in the discovery path. The result can be unnecessary crawl overhead, duplicate or near-duplicate indexing signals, and slower discovery of inventory changes. Do not assume that every filtered URL consumes a fixed crawl budget or directly causes ranking loss; verify the pattern on the store.
Correction: Reduce unnecessary discovery of low-value filter combinations, keep primary collection URLs easy to reach, and use robots.txt.liquid only where crawl blocking is appropriate. Canonical handling, internal links, indexability, and parameter behavior should be reviewed together because blocking alone does not consolidate every signal.
Owner: Technical SEO lead with the Shopify theme or storefront developer, plus merchandising input where certain filtered views have genuine search value.
Verification: Re-crawl the same collection paths, compare discoverable filter URL counts, inspect canonical and robots directives, and confirm that priority collection and product URLs remain accessible.
Previously published example requiring source reconciliation: An apparel retailer with 5,000 SKUs was described as having over 40,000 indexed URLs from color and size filters, with the main Men's Jeans category reported on page 3. Keep this as an internal historical example unless the supporting source is reconciled.
Severity: critical
Keeping Collection-Aware Product Links While Canonicals Point Elsewhere
Evidence: Inspect product-card links across collection templates and compare them with each product page canonical. A representative product can be reachable at /products/blue-widget, /collections/widgets/products/blue-widget, and /collections/new-arrivals/products/blue-widget. The problem is not that alternate paths can exist. It is that a theme may repeatedly link to one form while declaring another as canonical. Confirm the pattern in rendered HTML and crawl data before changing theme behavior.
Consequence: Repeated internal linking to alternate paths can make site architecture less consistent and increase crawling of duplicate representations. Search engines can often consolidate duplicates, so the presence of multiple paths does not automatically mean authority is split. The risk is strongest when canonical output, redirects, internal links, and indexability do not agree.
Correction: Review the relevant product-card and product template logic and, where appropriate, standardize internal links on the preferred /products/ path. Confirm that breadcrumbs and collection context still work for users and that the canonical target matches the intended indexable version.
Owner: Shopify theme developer, reviewed by the technical SEO owner.
Verification: Crawl internal links to representative products, compare alternate paths with canonical output, and confirm that templates consistently link to the intended product URL after deployment.
Previously published example requiring source reconciliation: A home decor brand was described as seeing a 25% lift in product page rankings after consolidating 4,500 duplicate product paths into a single canonical structure. Preserve the figures as a historical internal example, not as a verified causal benchmark.
Severity: high
Using Third-Party SEO Apps Without Measuring Their Actual Front-End Cost
Evidence: Theme code, request waterfalls, rendered source, and performance diagnostics may reveal duplicated scripts, repeated JSON-LD blocks, app proxies, or Liquid injected by tools that overlap with native theme functions. The mistake is not using an app. It is allowing overlapping functionality to accumulate without checking what each app contributes to the rendered page.
Consequence: Additional JavaScript, Liquid processing, third-party requests, or duplicate markup can increase rendering work and complicate maintenance. Performance effects depend on implementation, so app presence by itself is not evidence of a Core Web Vitals problem.
Correction: Inventory every SEO-related app, identify the exact function it provides, remove redundant functionality, and move stable template logic into maintainable theme code when that reduces complexity without sacrificing required features. Re-test structured data and metadata after any removal so that deleting an app does not silently remove useful output.
Owner: Storefront developer with the SEO lead and the person responsible for app governance.
Verification: Compare request counts, rendered HTML, performance diagnostics, and structured data before and after the change on representative product and collection templates.
Previously published example requiring source reconciliation: A beauty brand was described as reducing document size by 40% after replacing three SEO apps with custom Liquid code for JSON-LD schema. Treat that as a historical example unless its underlying measurement is available.
Severity: medium
Editing robots.txt.liquid Without a Clear Crawl-Control Objective
Evidence: A crawl or log review may show /collections/types? and /collections/vendors? URL families, internal search URLs, tag pages, or filtered collections receiving crawler requests despite having little standalone value. Shopify supports robots.txt.liquid customization, but additional rules should follow observed URL patterns and a clear understanding of what remains discoverable and indexable.
Consequence: Unnecessary URL spaces can consume crawler attention and make diagnostic reports noisier. Overblocking can create a different problem by preventing crawlers from fetching URLs whose signals, links, or render state still need evaluation. robots.txt is a crawl directive, not a complete indexing or canonicalization strategy.
Correction: Add narrowly targeted rules only for URL patterns that do not need crawling, and coordinate those rules with canonicals, noindex decisions, navigation, and sitemap inclusion. Vendor or type collections that serve a real search or user purpose should not be blocked simply because they are auto-generated.
Owner: Technical SEO owner with developer review before deployment.
Verification: Test the resulting robots output, re-crawl allowed paths, monitor crawler behavior, and confirm that valuable collection, product, and resource pages remain fetchable.
Previously published example requiring source reconciliation: An electronics retailer was described as blocking 12,000 Vendor URLs and then seeing a 30% increase in crawl frequency on top-tier category pages. Keep the figures as an internal historical observation rather than a verified causal result.
Severity: high
Retiring SKUs or Renaming Handles Without a Redirect Decision
Evidence: A retirement workflow should record whether an old product or collection needs a 301 redirect. Crawl reports, backlink reports, analytics landing pages, or Search Console can then reveal legacy URLs that return 404 responses after deletions, migrations, or handle changes. Redirect chains can also appear when several past destinations are left in sequence.
Consequence: Users and crawlers following old internal or external links can reach dead ends, and valuable historical links may no longer resolve to relevant content. A not-found response is not inherently an SEO defect when the content is truly gone and no replacement exists; the mistake is failing to make a deliberate retirement decision.
Correction: For each retired SKU or changed handle, choose between keeping the page available with accurate status, using a 301 redirect to a genuinely relevant successor or parent category, or returning the appropriate missing-page response when no useful replacement exists. Avoid forcing every discontinued product to an unrelated destination, and collapse redirect chains where possible.
Owner: Merchandising or catalog operations for the retirement decision, with the developer or SEO owner implementing and checking redirects.
Verification: Re-crawl legacy URLs, inspect destination relevance, confirm direct redirect behavior where used, and monitor whether important external links still resolve to useful content.
Previously published example requiring source reconciliation: A fashion brand was described as recovering 15% of lost organic traffic after fixing 400 broken backlinks that were reaching 404 pages following a migration. The figures should remain historical until a source is reconciled.
Severity: critical
Uploading Large Product Images Without Verifying Delivered Image Behavior
Evidence: Performance diagnostics and browser inspection can show whether a 5MB source asset leads to oversized delivered images, poorly matched dimensions, missing responsive candidates, or a hero image that delays meaningful rendering. Shopify can transform and serve images efficiently when themes request them correctly, so the uploaded file size alone does not prove that users receive the original asset.
Consequence: Inefficient image requests can increase transfer size and delay visual rendering, especially on mobile connections. Image Search visibility also depends on crawlability, relevance, surrounding content, alt text quality, and indexability, not format alone.
Correction: Review theme image helpers, responsive srcset behavior, requested dimensions, compression, modern format delivery, lazy-loading placement, and the loading priority of above-the-fold media. Use supported Shopify image delivery behavior instead of assuming that every image must be manually converted before upload.
Owner: Front-end or Shopify theme developer, with content or merchandising staff responsible for source image quality and alt text.
Verification: Inspect delivered image URLs and dimensions on representative devices, compare transfer sizes, and re-run field or lab performance checks after the theme change.
Previously published example requiring source reconciliation: A furniture retailer was described as improving mobile LCP from 4.2s to 1.8s after optimizing product gallery images, alongside a reported 12% increase in mobile conversion rates. Preserve those figures as a historical internal example rather than claiming direct causation.
Severity: medium
Maintaining Structured Data Manually Instead of Tying It to Store Data
Evidence: Rendered HTML or structured data testing may reveal stale price, availability, review, breadcrumb, or organization values because markup was copied manually, duplicated by apps, or left disconnected from product data. The central mistake is maintainability: markup that does not update with the store can become inconsistent with visible page content.
Consequence: Inconsistent structured data can create validation errors or make pages ineligible for certain search presentation features. Structured data does not guarantee rich results, higher click-through rates, or ranking improvements, and optional or recommended properties should be used only when they accurately reflect page content.
Correction: Generate relevant JSON-LD dynamically from Shopify data or stable theme variables, keep only markup that matches visible page information, and avoid adding types or properties solely to chase a search enhancement. Product, breadcrumb, and organization markup should reflect the actual entity and page context. FAQ content may remain useful for readers, but FAQPage markup should not be added under this contract.
Owner: Shopify developer for implementation, with the SEO owner responsible for validating current search documentation and the content owner responsible for accuracy.
Verification: Test representative product and collection pages after updates, compare markup with visible price and availability, and monitor Search Console enhancement reports where applicable.
Previously published example requiring source reconciliation: The earlier version described missing rich snippets as producing a 20-30% lower click-through rate and described a nutritional supplement brand as seeing a 40% increase in clicks from the same ranking positions after comprehensive review and price schema. Keep these numeric claims only as historical source text requiring reconciliation; do not use them as verified benchmarks.
Severity: high
