32 checks between “published” and technical readiness.
Use this checklist to inspect the crawl, indexation, rendering and trust signals behind a Shopify store—before producing another article.
Choose the failing stage before using the checklist
This is a manual inspection sequence, not an automated score or a certification. Begin with one product, one collection, one guide and one translated equivalent that actually exist. Record the template and apps involved; a passing homepage cannot clear a different product template.
If a buyer cannot open the page or use its essential controls, start at access. If the page works but is absent from search, start at index evidence. If it is indexed but gets weak clicks, examine the query and promise before changing technical directives. Mark an absent feature “not applicable” with a reason; do not manufacture a finding to fill every box.
Reviewed October 9, 2026. Each numbered check below needs a recorded observation. The form at the end stores one optional local record; it does not perform these tests.
01–04: Access and discovery
- Open the exact landing URL. Record its response and final destination, including variant, language and market conditions. A browser homepage success does not explain a Merchant Center product-fetch failure. Start with the unavailable-product guide for that specific symptom.
- Read robots rules and response failures separately. A Disallow rule and an unreachable robots.txt are different states. Do not unblock every route to obtain a green test. On hosted Shopify, do not promise origin logs you cannot access; preserve available platform and edge evidence.
- Follow a real internal link. Navigate from a relevant collection or guide directory to the sample page. Record the link destination, not just whether the page appears in site search. A page should not rely solely on a sitemap for reader discovery.
- Check the sitemap that owns the URL. Compare the final canonical URL with its sitemap entry. Shopify’s generated sitemap and a separately hosted content sitemap have different owners; do not edit a platform-generated file as though it were your static export.
Collection filters and sorting create many crawlable URL variants. Before adding robots.txt rules, read Shopify filter URLs and SEO for the defaults and how to measure crawl waste.
05–08: Index evidence and URL identity
- Check both HTML and HTTP indexing directives. Record an intentional noindex separately from an accidental one. Robots blocking is not a reliable substitute for removing an indexed URL, and it can prevent Google from seeing a noindex directive.
- Compare the declared and selected canonical. Save the page’s canonical and Google’s selected canonical with inspection time and last crawl. A self-reference is not automatically correct; examine genuinely duplicate URLs and conflicting signals.
- Read the inspection state literally. “Unknown”, “discovered”, “crawled but not indexed” and an access failure require different follow-up. A successful live test does not establish inclusion or predict Google’s canonical selection.
- Document parameters and pagination before consolidating. Test what a filter, sort, variant and next-page URL actually shows. Do not point every paginated page to page one or remove a useful variant destination just because its URL has a question mark.
Products reachable at /collections/…/products/… are the most common URL-identity issue on Shopify. Duplicate product URLs shows how to check and fix the theme links.
09–12: The page’s promise and answer
- Compare the title, main heading and opening answer. They should identify the same task or product. A unique title does not justify a second article with the same answer; a fixed character count is not a Google acceptance rule.
- Find the missing decision information. Ask what a reader still cannot decide after reading. On a collection that may be compatibility or trade-offs; on a guide it may be prerequisites, an exception or a verification step. Add evidence, not a generic introduction to increase length.
- Inspect media in context. Confirm the image loads, depicts the stated item or clearly serves as an illustration, and has useful alternative text where needed. Essential specifications must also be available as text. Decorative images do not need keyword-filled descriptions.
- Trace material claims to a source. Check changing platform rules against primary documentation and product facts against the actual catalog. Remove unsupported results or endorsements. A hypothetical example must not be presented as customer evidence.
13–16: Product and commercial consistency
- Fix one offer identity. Record product, variant, market and currency, then compare visible price and stock with the relevant feed item. A product-family starting price is not necessarily the selected offer price.
- Inspect existing structured-data owners. Inventory theme and app output before adding markup. Multiple scripts are not automatically wrong; contradictory entities or offers are. A ProductGroup can describe the full family while the interface selects one variant.
- Test the applicable delivery and return terms. Use the same destination and product conditions across the page and the next buying step. Do not publish an unverified delivery guarantee. Stop before an actual order unless an authorized test procedure exists.
- Separate temporary stockouts from retirement. Confirm whether replenishment, a suitable successor or neither applies. Keep useful information where warranted; an unrelated homepage redirect is not an equivalent replacement. See the stockout decision guide.
17–20: Mobile use and performance
- Identify the measurement scope. In PageSpeed Insights, record whether field data describes this URL or the origin and whether it is available. A lab run is a controlled diagnostic; missing field data is not a passing result.
- Inspect the actual bottleneck. Identify the largest-content element and its request path before changing image priority. Blanket preloads and removing every script can harm other interactions. Retest the same conditions after a bounded change.
- Complete the essential interaction. At phone width, use navigation, variant selection and cart access; repeat relevant steps with a keyboard and visible focus. Check text zoom, labels, overlays and horizontal overflow. Pixel dimensions alone do not establish accessibility.
- Retest dependencies after an app or theme change. Confirm consent, analytics and buying controls with their owners. A duplicate theme is useful for theme tests but does not isolate every store-wide app or checkout configuration.
21–24: Language and market acceptance
- Visit the locale directly without relying on a remembered choice. Confirm content language, currency and destination restrictions. Record any automatic redirect. A language selector label alone does not prove that the underlying page exists.
- Match genuine equivalents. Compare the task and substantive content of language pairs. Do not use a homepage as the alternate for a missing translated article.
- Check reciprocal annotations and canonical roles. Verify valid language codes, full alternate URLs and return references. Avoid canonicalizing every translation to English. Follow the multilingual guide for routing decisions.
- Exercise cross-system navigation. If a separate CMS serves articles, move from an article to the corresponding storefront language and back. Test the actual destinations; a shared header appearance does not prove shared routing or sessions.
25–28: Search and measurement
- Fix a comparable reporting slice. Save complete dates, search type, country, device and page scope. Keep site totals separate from article totals; unavailable or suppressed query data is not zero demand.
- Inspect the query behind a low CTR. Consider position, intent and result format before rewriting the snippet. Do not impose a universal target on branded, informational and product searches.
- Reconcile sources without equating them. GSC clicks, analytics sessions and orders measure different things. Check consent and instrumentation changes before attributing a divergence to lost SEO. Use the measurement guide.
- Mark migrations and simultaneous changes. Keep raw old/new URL data, language changes, campaigns and inventory events on the timeline. A single before-and-after comparison does not isolate the effect of one edit.
29–32: Safe implementation and closure
- Assign one accountable output owner. Identify which template, application, CMS or routing layer writes the faulty field. Agree the intended result before two integrations overwrite each other.
- Capture the precise recovery point. Back up the affected files and settings, check for concurrent changes and define recovery. Some retired API resources cannot simply be recreated; do not call every rollback reversible.
- Separate simulated and real business events. Use a non-selling test environment or explicitly approved procedure for transactions. Label synthetic records and check destination receipts without counting them as customers.
- Close only the proven state. Record the deployed change and repeatable acceptance result. Crawling, indexing, ranking and revenue remain separate observations. Keep unresolved dependencies open rather than awarding a general “SEO passed”.
A worked URL move: what evidence would be enough?
Illustrative scenario: an English guide moves from /en/guide.html to /guide.html, and the Chinese equivalent stays at /zh/guide.html. First confirm the old English URL really served that same task. If the root previously served Chinese, its historical metrics must not silently become an English baseline.
Check the old route’s permanent redirect, the new page’s direct response, updated internal links, sitemap ownership and reciprocal language annotations. Then record Google’s indexed observation separately. A coherent release can pass technical acceptance while the new canonical has not yet been processed. If the new route serves the wrong language, repair the mapping before making further content changes.
Record one finding and its acceptance
Write what failed, the exact conditions, the responsible owner and the recovery step. Save a downloaded copy before replacing an existing browser record.
Sources and next step
These checks synthesize an editorial workflow, not a Google or Shopify certification. Primary references: Shopify SEO documentation, URL Inspection, canonical signals, localized URLs and PageSpeed measurement.
Use the main guide to decide priorities, or the tools page to choose evidence. Paid audit scope is separate from this free manual checklist.