Skip to content

Misc

Checkout SEO on Shopify: why /checkout is blocked and what you can change

Published

Why /checkout is blocked from indexing — and why that's correct

The /checkout path on every Shopify store is blocked from search-engine crawling by the platform's default robots.txt. This is intentional and irreversible — checkout pages contain order-specific session data, payment context, and customer authentication state. They're not indexable surfaces; they're transactional flows. The block is permanent. No customisation is required; no customisation is supported. The interesting boundary in 2026 is what HAPPENS at checkout — checkout extensibility (Extensions, Functions, Pixels) replaces the deprecated Scripts framework starting June 30, 2026.

Shopify's editing-robots-txt doc2 lists /checkout in the default block list alongside /admin, /cart, /collections/*+*, /search, and /policies/. The block is part of the platform's default-rule list — Shopify maintains it; you don't touch it.

Web Bot Auth signatures don't grant checkout access

Shopify's Web Bot Auth feature (HTTP message signatures for first-party crawlers and audit tools) carries a critical exclusion: signatures don't grant access to your Shopify Checkout. Verbatim from the Crawling your store doc: 'Signatures don't grant access to your Shopify Checkout due to the additional layers of checkout security.' This means even legitimate first-party audit tools — accessibility scanners, performance auditors, custom monitoring — cannot reach checkout pages programmatically. Manual testing in a real browser session is the only path.

Per Shopify's crawling-your-store doc1, the verbatim warning is: "Signatures don't grant access to your Shopify Checkout due to the additional layers of checkout security." The architectural reason: checkout enforces additional security layers (CSRF protection, session validation, payment processor handshakes) that signature-only authentication can't satisfy. The carve-out is not a bug; it's a protection.

Shopify Scripts deprecation — June 30, 2026

The April 9, 2026 Shopify dev docs changelog announced Shopify Scripts will be deprecated on June 30, 2026. Functions now cover the use cases Scripts used to handle: discounts, shipping, and payments. The migration deadline noted in the changelog is April 15 to avoid execution stoppage. After June 30, 2026, Scripts no longer execute — any business logic that depends on Scripts will silently stop firing. This is the biggest 2026 backend change on Shopify.

Per the Shopify dev docs changelog3, the deprecation message: "Shopify Scripts will be deprecated on June 30, 2026. Functions now cover discounts, shipping, payments; migrate from Scripts by April 15 to avoid execution stoppage." The two paths for any Script-based logic: (1) rewrite as a Shopify Function (the preferred path; Functions are the modern equivalent); (2) replace with a third-party app that implements equivalent logic via Functions or Extensions.

The SEO connection: Scripts that controlled discount visibility or shipping calculation often affected product price display on PDPs and collection pages. When a Script stops firing, prices may shift, discounts may stop applying, and the resulting PDP content (price, availability, shipping language) changes — affecting both Catalog eligibility (price > $0 gate) and AI shopping engine reasoning. Migrate Scripts before June 30 and audit downstream content for shifts.

Extensions and Functions vs Scripts — the modern surface

Checkout extensibility on Shopify in 2026 is Extensions (UI blocks inside checkout) and Functions (backend logic). Extensions let apps inject UI components into checkout — upsell modules, custom fields, post-purchase blocks. Functions run server-side logic at key points — discount calculation, shipping rate logic, payment customisation. Together they replace what Scripts and the legacy Checkout.liquid customisation used to do. The April 1, 2026 changelog added per-app visibility into which Extensions and Functions each app uses.

Per the April 1, 2026 changelog4, you can now see Extensions, Functions, and Pixels per app under Settings > Apps. This is critical for checkout speed auditing — accumulated Extensions on checkout slow down the highest-revenue page in the funnel. The app-bloat audit pattern from cluster 1J applies here too: review which apps inject UI or logic into checkout, prune the ones not earning their keep.

What this means for SEO and conversion

Three implications. (1) Checkout is not an SEO surface — don't try to optimise it for search. The /checkout block is permanent. (2) Audit tools have a checkout blind spot — supplement with manual testing or analytics-derived data. (3) The Scripts deprecation is a real deadline — migrate any Script-dependent logic by June 30, 2026 or accept silent execution failure that may affect price display, discount application, and Catalog eligibility downstream.

The SEO surface stops at /cart. Cart pages are blocked by default too (per the same robots.txt default-rule list2), but cart is less locked down than checkout — analytics can reach it, Web Bot Auth signatures may reach it depending on configuration, and theme customisation lives there. Checkout is the harder boundary.

The conversion implication: every checkout optimisation has to happen inside Shopify's Extensions/Functions framework or in pre-checkout cart pages. The cart page is your last classic-SEO-adjacent surface; checkout is post-funnel territory. Plan the user journey accordingly — get every CRO and SEO signal you need before the buyer hits /checkout.

Keep reading