Broad Keyword Targets That Do Not Match the Product Page
Observable evidence: Compare Search Console queries, the landing page copy, onsite search terms, and paid-search query data when the store has it. The issue is visible when a page is written to pursue broad phrases such as 'cool t-shirts' or 'men's shirts' even though the inventory is differentiated by a specific material, fit, use case, or design. Industry benchmarks put conversion on broad terms 10-15% lower than on specific, long-tail queries: a broad search is often just a browsing phase, whereas a specific search indicates a buyer who knows exactly what they want.
Consequence and owner: A mismatch can consume editorial and acquisition effort without giving the most relevant product families clear search coverage. SEO should own the query diagnosis, while merchandising or product teams should confirm that any proposed wording accurately describes what is sold.
Correction: Assign each important collection or product family a primary search task based on real inventory and observed language. More descriptive phrases such as 'heavyweight organic cotton oversized tees' or 'vintage style graphic tees for musicians' are appropriate only when the page can substantively satisfy that intent.
Verification: After recrawling and reindexing have had a chance to occur, compare the edited page's query mix, impressions, clicks, and onsite behavior with its pre-change baseline. Look for a larger share of specific, purchase-ready queries and track conversion on the edited page over the same period.
Example: A collection can target 'sustainable bamboo fiber t-shirts for athletes' only when the listed garments and audience positioning make each part of that description accurate.
Severity: critical
Product Pages That Hide Fabric and Fit Facts
Observable evidence: Review a representative product template as rendered text, not just as a shopper looking at images. If material, garment weight, construction, fit, care, or measurements exist only inside graphics or are absent entirely, the page gives both shoppers and crawlers limited product detail. Attribute searches can include language such as '240 GSM cotton,' 'pre-shrunk side-seamed shirts,' or 'ring-spun cotton' when those descriptions genuinely apply.
Consequence and owner: The page may be a weaker match for detailed apparel queries, and shoppers may have less information for comparing feel, weight, cut, and construction. Product merchandising should own the facts; SEO or content should own readable presentation. Missing fit and quality details can also lead to higher return rates from customer confusion, so track returns for the affected products alongside search data.
Correction: Publish verified specifications in crawlable text, using only information supplied or confirmed by the product team. Useful fields can include composition, fabric weight, construction, care, and fit measurements when they are known and relevant.
Verification: Check the rendered page and source behavior to confirm the details are accessible, then review whether the page begins receiving impressions for accurate attribute queries. Also test whether a shopper can find the same facts without needing an image-only chart.
Example: If the specification is documented, '100% combed ring-spun cotton, 4.3 oz, 32 singles' gives a buyer concrete information that a generic softness claim does not.
Severity: high
Product Images With Weak Delivery or Descriptive Context
Observable evidence: Sample key product pages and inspect image dimensions, transferred file size, crawlability, lazy-loading behavior, filenames, alt text, and the image references used by existing product data. Large, uncompressed images slow rendering and harm Core Web Vitals, while missing or generic alt text provides less descriptive context. Without descriptive alt text and Product structured data, items are less likely to appear in Google Images, Google Lens, Google AI Overviews, shopping surfaces such as the 'Popular Products' carousel, or other Google AI features, although markup alone does not guarantee placement.
Consequence and owner: Shoppers may encounter slower pages, and search systems may receive less useful context about what an image depicts. Ecommerce engineering should own delivery and crawlability; merchandising or content should own accurate image descriptions and product-data alignment.
Correction: Serve appropriately sized images in a modern format such as WebP when the platform, browser support, and quality requirements make that suitable. Keep important product images accessible to crawlers, write concise alt text for the visible image, and make any existing Product structured data match information users can actually see.
Verification: Retest page performance and rendered image elements, inspect image indexing where the available tools expose it, validate product data, and check whether the products begin appearing in image and shopping results.
Example: For the relevant product photo, 'Model wearing black heavyweight oversized street-wear t-shirt' communicates the image content better than 'IMG_001.jpg'.
Severity: high
Inventory Changes That Send Useful URLs to the Wrong State
Observable evidence: Crawl retired products and seasonal collections, then review inventory status, internal links, external links, historical search entries, and any real replacement page. Deleting a page that external links still point to turns those links into 404 errors and discards the link equity the page built; that matters most when shoppers or important links still reach the address and a genuinely useful alternative exists. Temporarily unavailable products are a different case when the item is expected to return and the page remains useful.
Consequence and owner: Poor lifecycle decisions can strand useful links, lose the authority and rankings a product line built each time it is refreshed or retired, create irrelevant redirect paths, or leave shoppers at an avoidable dead end. Merchandising should define whether an item is temporary, discontinued, or replaced; SEO and engineering should implement the corresponding URL behavior.
Correction: Keep a temporarily out-of-stock page available when the product is expected back and the content remains useful. For a permanent retirement, use a 301 redirect only when a close successor or genuinely relevant collection exists; otherwise preserve a truthful not-found state and remove stale internal links.
Verification: Re-crawl the affected addresses, inspect redirect targets for topical relevance, confirm internal navigation no longer points to retired inventory unnecessarily, and test the entry path a shopper would follow from an old search result or referral.
Example: Redirecting a '2023 Summer Collection' landing page to the '2024 Summer Collection' page maintains its ranking power when the newer collection is the closest useful destination. Check first that an archived version would not better answer the original intent.
Severity: medium
Variant URLs Without a Deliberate Indexing Decision
Observable evidence: Crawl a product family and compare variant URLs, titles, visible copy, canonicals, internal links, and index status. Multiple URLs are not inherently a mistake. The problem appears when near-identical size or color states are independently crawlable or indexable without a documented reason for which version search engines should prefer.
Consequence and owner: Duplicative variants dilute ranking power, make index coverage and page-level signals harder to interpret, and often leave several weak pages competing for substantially the same query. Technical SEO and ecommerce engineering should own the URL and canonical rules; merchandising should identify colors or editions that are materially distinct.
Correction: Define the intended index state by variant type. When size URLs represent the same core product, point duplicative versions to the preferred product with an appropriate canonical. Give a color its own indexable page only when the store intends to maintain a stable, useful page that offers distinct content and serves genuine color-specific demand; otherwise keep the color as a selection or parameter state aligned with the preferred canonical.
Verification: Re-crawl canonicals and internal links, compare the indexable set with the documented plan, and inspect which URL search results surface for representative product queries. A mismatch means the implementation or linking strategy needs another review.
Example: A 'Classic White Tee' may serve as the preferred product URL while 'Small,' 'Medium,' and 'Large' remain purchase selections rather than separate search landing pages.
Severity: critical
One Landing Page Trying to Serve Retail and B2B Custom-Order Searches
Observable evidence: Compare headings, calls to action, offer details, and incoming queries on pages that mention both ready-to-buy apparel and custom printing. A shopper searching for 'funny graphic tees' expects a catalog path, while someone researching 'bulk screen printing for corporate events' needs substantiated information about decoration methods, order requirements, artwork, fulfillment, pricing process, or turnaround. A page that switches between those tasks without a clear primary purpose gives each audience a less focused experience.
Consequence and owner: Blended retail and B2B intent can make a landing page harder to use, blur which search task the page is meant to answer, and leave high-ticket bulk orders on the table. Ecommerce or sales operations should define the retail and custom-order journeys; SEO and content should translate those journeys into page purposes that reflect the actual offer.
Correction: Separate retail shopping content from custom or wholesale information when the business truly offers both and each topic has enough useful material for its own page. Create location-specific content only for a genuine location with information that is useful to people considering that location, not merely to multiply service-area coverage.
Verification: Confirm that each page has a dominant task, appropriate calls to action, and a query set consistent with that task. Evaluate retail and custom-order conversion paths independently so one audience does not obscure the other.
Example: 'Custom T-Shirt Printing for Charity Marathons' belongs on a dedicated page only if that service is actually available and the page explains the relevant ordering considerations instead of repeating generic custom-printing copy.
Severity: medium
Reviews and Markup That Do Not Match the Visible Product Evidence
Observable evidence: Compare visible product reviews, ratings, identifiers, and review counts with any structured data emitted on the same page. Flag stale or mismatched values, markup for information users cannot see, and feedback workflows that select only expected positive reviewers. Eligible customers should be asked consistently for honest feedback without incentives, discouraging criticism, or filtering requests by anticipated sentiment.
Consequence and owner: Without valid review markup, a listing lacks the rating data that makes stars eligible to appear, and a flat listing can lose clicks to competitors with visible ratings. Inaccurate markup can fail validation or misrepresent the page, while selective review requests can distort the feedback program. Google still decides whether stars or another rich presentation appear. Ecommerce engineering should own the markup; the customer-experience team should own the feedback process.
Correction: Use review-related structured data only when it follows the applicable documentation and corresponds to visible, eligible product information. Keep the request process sentiment-neutral, and moderate user-submitted photos or text for authenticity, policy, privacy, and relevance without suppressing legitimate negative feedback.
Verification: Validate the markup, compare every represented field with the visible page, and monitor actual search appearance for stars and review counts. Separately audit review-request eligibility to confirm the same rule applies regardless of whether the customer is expected to leave favorable or unfavorable feedback.
Example: A technically valid page is one where visible rating information and the markup agree, which makes the store's best-selling tees eligible for star ratings and review counts directly in Google search results.
Severity: high
