Dynamic XML sitemap for one-of-a-kind inventory
Evidence required: the live XML sitemap, a recent crawl, Search Console sitemap status, and examples of newly added and sold inventory URLs. Pass/fail: pass when indexable inventory intended for search is represented correctly; fail when the sitemap is stale, contains unintended URLs, omits important indexable inventory, or leaves accidental 404 errors after inventory changes.
Severity: high when crawl discovery or indexation is materially affected. Owner: web developer or technical SEO owner. Corrective action: update sitemap generation rules to follow actual inventory status instead of assuming every sold item should disappear.
Validation: recheck the sitemap, crawl the affected URL set, and confirm the intended response and indexation state. Tools: Google Search Console, Yoast SEO, RankMath
High-resolution image performance
Evidence required: page-weight measurements, Core Web Vitals data where available, representative catalog pages, and visual inspection of maker's marks, patina, restoration, and condition details.
Pass/fail: pass when images remain detailed enough for collector evaluation without unnecessary transfer weight; fail when delivery is visibly degraded or image weight creates material performance problems.
Severity: high on image-heavy templates with measurable loading issues. Owner: developer plus photography or catalog team. Corrective action: use appropriately sized assets, supported formats such as WebP, responsive image delivery, compression, and lazy loading where appropriate.
Validation: retest representative pages and compare both performance and visual detail. Tools: PageSpeed Insights, ShortPixel, Cloudinary
Breadcrumb and hierarchy markup
Evidence required: visible breadcrumb paths, internal category relationships, source markup, and structured-data validation. Pass/fail: pass when breadcrumbs reflect the real hierarchy, such as Home > Furniture > Seating > Victorian Armchairs, and any markup matches the visible path; fail when the hierarchy is misleading, inconsistent, or marked up differently from the page.
Severity: medium unless navigation or crawling is materially impaired. Owner: information-architecture owner and developer. Corrective action: repair taxonomy, breadcrumb links, and markup together rather than adding schema to a confusing structure. Validation: crawl the path and test eligible structured data. Tools: Schema.org, Google Rich Results Test
Sold-item response handling
Evidence required: a list of sold URLs, response codes, backlinks, organic impressions, replacement relevance, and current internal links. Pass/fail: pass when each sold URL has an intentional outcome; fail when a useful page becomes an unexplained 404 or an unrelated redirect.
Severity: high for linked or searched URLs. Owner: ecommerce manager with SEO review. Corrective action: keep useful sold references live, redirect only when a genuinely relevant replacement exists, or remove a page when no useful destination remains. Validation: recrawl changed URLs and review affected backlinks and search traffic. Tools: Screaming Frog, Ahrefs
HTTPS and transaction security
Evidence required: valid certificates, secure checkout and form paths, mixed-content checks, and browser validation. Pass/fail: pass when users can browse and submit sensitive information over valid HTTPS; fail when certificates, redirects, or mixed content create security warnings.
Severity: critical for transaction or inquiry paths. Owner: developer or hosting administrator. Corrective action: repair certificate, redirect, and mixed-content configuration. Validation: test representative pages and transaction flows in current browsers. Tools: Let's Encrypt, Cloudflare