Shopify storewide SEO checklist: a practical audit order

Audit a Shopify store in dependency order: access, indexability, template output, page usefulness, internal paths, structured data, performance, then measurement. That order prevents a common waste: rewriting hundreds of descriptions before discovering that a template emits the wrong canonical, a priority collection has no internal links, or the store is still private.

Download the audit CSV and the storewide review checklist. They separate what was directly observed from what still needs proof. A green row means the stated check passed on the inspected URL and date; it does not certify the whole store.

Choose the audit that matches the problem

Use this storewide checklist for crawl access, templates, products, collections and technical dependencies. Use the blog content audit when the decision is whether to keep, refresh or consolidate an article. For one product page's missing buying facts, start with the product-information HTML audit.

These are different jobs. A pasted article-body score cannot establish whether the live store is indexable, and a technically valid page can still leave a buyer's question unanswered. Record the failed check and the actual URL before choosing a tool or assigning a rewrite.

Set the sample and evidence rules

Start with a representative sample instead of claiming you inspected every URL:

• the homepage and primary domain;
• the top three collections by business priority;
• five important products, including one with variants and one unavailable item;
• three evergreen posts and one recent post;
• one standard page, one policy page and the 404 page;
• every distinct template or market/language pattern;
• any URL recently renamed, hidden or migrated.

Add rows when a problem repeats. If the same missing description appears across three products using one template, inspect the template and a larger product sample before calling it storewide.

Use four evidence labels in the CSV:

Label	Meaning
Observed	You opened the public URL or rendered source and saw the result
Reported	Shopify, Search Console or another named report supplied the value
Inferred	Several observations suggest a cause, but the cause is not isolated
Not checked	No reliable evidence was collected yet

This keeps “not checked,” “zero,” and “failed” separate. A URL absent from a site: search is not proof that it is unindexed; Google recommends URL Inspection for that question (Google Search Central, site: operator, read 10 September 2026).

1. Confirm the domain, crawl access and indexability

Open the canonical storefront, robots.txt and sitemap.xml on the primary domain. Confirm the store is publicly accessible, alternate store domains redirect as intended, and the sitemap returns the Shopify-generated index.

Shopify automatically generates sitemap.xml with products, primary product images, pages, collections and blog posts, and updates it as those resources change. International domains can have their own sitemaps (Shopify Help Center, finding and submitting a sitemap, read 10 September 2026). Submission helps discovery; it is not an indexing guarantee.

Inspect at least one URL of every sampled type in Google Search Console. Record whether Google can access it, the declared and selected canonical, the last crawl if available, and any explicit exclusion. Do not treat a successful live test or indexing request as proof that the page is indexed.

Use the Search Console workflow for Shopify blogs when an inspection result needs diagnosis, and the blog-not-indexed guide for the narrower published-but-missing case.

Read the whole robots.txt, including Shopify's default groups. If the store has a customized robots.txt.liquid, compare it with the current intended policy before changing anything. Shopify warns that incorrect edits can lose traffic and recommends retaining its Liquid-generated defaults so platform updates continue to flow through (Shopify Help Center, editing robots.txt, read 10 September 2026). The Shopify AI-crawler guide separates search, training and user-triggered agents.

2. Inspect what each template actually renders

View page source and the rendered page for one URL from every template. Record:

• one non-empty <title>;
• at most one meta description tag with page-specific content;
• one canonical link pointing to the preferred URL;
• one clear visible H1;
• crawlable content and links present after rendering;
• the intended robots meta directive;
• relevant structured data without contradictory duplicates.

Shopify's theme guidance exposes admin titles through page_title, descriptions through page_description, and the preferred URL through canonical_url; those elements belong in the document head (Shopify.dev, SEO metadata, read 10 September 2026). A value saved in the admin is not proof that a customized theme outputs it correctly.

Check alternate states too. An unavailable product, an empty collection and a paginated collection can render different metadata or headings from the normal template. If variants use query parameters, confirm the canonical and visible product state stay coherent.

3. Review products for decision-ready facts

For each sampled product, check that a buyer can identify the item, selected variant, current price and availability, material or ingredients where relevant, dimensions or quantity, use or care, shipping/return route, and the evidence behind claims. The exact fields depend on the category; do not paste a generic checklist into medical, food or safety copy without source review.

Then inspect the search listing and main heading. The product title should distinguish the item; the meta description should summarize this product rather than repeat a storewide slogan. Images need descriptive alt text when they convey product information.

The product-information HTML audit shows why source extraction alone is insufficient: rendered accordions can expose facts that a simple initial-HTML pass misses. Its sample is limited and does not prove what any crawler sees, so inspect both views.

4. Review collections as comparison pages

A collection page should explain what belongs in the set and how a buyer chooses among it. Check its H1, short introduction, filters, product-card labels, pagination, out-of-stock behavior and links to deeper guidance. Avoid making every collection description the same paragraph with a swapped category noun.

The collection-page audit provides a focused checklist for that page type.

Confirm priority collections are reachable through menus or contextual links. Google says ecommerce navigation can help it understand relationships, and recommends paths from menus to categories and subcategories to products (Google Search Central, ecommerce site structure, read 10 September 2026). The goal is a useful path for shoppers; a sitemap does not replace navigation.

5. Review blog posts and supporting pages

Each important post should answer one recognisable question, state the useful answer early, use a meaningful H2 outline, cite or attribute checkable claims, and link to relevant collections or products in context. Check author and date presentation, image alt text, search listing and live destinations.

Use the Shopify blog SEO guide for field-level review and the product-linked article guide for the editorial path into the catalog. The blog SEO audit evaluates text that you paste with deterministic rules; it does not fetch the URL, verify claims or test the published theme.

Review About, contact, shipping, return and policy pages as buyer-support content, not as keyword targets. Their job is to establish clear business and transaction information. Check that product and cart paths link to the relevant current policy, especially if a policy URL changed.

6. Trace internal links and retired URLs

Pick every priority destination and find at least one relevant incoming link on the rendered site. Google says every page you care about should have a link from another page and recommends concise, descriptive anchors (Google Search Central, link best practices, read 10 September 2026). Record orphan candidates, generic anchor text, broken links and avoidable redirect hops.

For renamed or removed content, test the old URL. Shopify manages redirects under Content > Menus > View URL Redirects, and redirects operate only from paths that are broken rather than still serving a valid page (Shopify Help Center, URL redirects, read 10 September 2026). Redirect an old product to a genuinely similar replacement or useful collection, not automatically to the homepage.

7. Validate structured data against visible facts

Current Shopify-supported and Theme Store themes include structured data by default, according to Shopify's sitemap and search-display guidance (Shopify Help Center, finding and submitting a sitemap, read 10 September 2026). Inspect before installing another schema layer.

Run product and article samples through Google's Rich Results Test, then use the Schema Markup Validator for schema.org syntax that has no Google feature. Compare name, URL, image, price, currency, availability, author and dates with the visible page. A passing test confirms eligible markup syntax for the tested page; Google explicitly does not guarantee a rich result (Google Search Central, structured-data guidelines, read 10 September 2026).

The dedicated Shopify structured-data guide covers Product, variants, Article and the narrow FAQ boundary. Use the title and meta-description examples when the problem is page identity rather than schema.

8. Use real-user performance, then investigate regressions

Shopify's Web Performance reports cover Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift using real-user data, with desktop and mobile views. The data can be delayed by up to 36 hours and covers the last 90 days (Shopify Help Center, web performance reports, read 10 September 2026). Record the measurement window and device mix.

Look for changes after theme releases, app installs, new tag-manager code, media-heavy sections or navigation changes. Use PageSpeed Insights to investigate specific templates, but do not present one synthetic run as the experience of all customers. Shopify identifies themes, apps and manually added third-party code as major performance factors (Shopify Help Center, improving web performance, read 10 September 2026).

Worked example: a fictional audit triage

Illustrative example — Northwind Pantry is fictional. Every quantity and evidence label in this scenario is synthetic; no live store was tested.

Imagine that this fictional audit sample produces 26 issue rows. Instead of reporting “26 SEO errors” as though every row were independent, the fictional reviewer groups them by root cause:

Finding	Evidence	Priority	Action
Product template emits two Product objects with different availability	Synthetic: observed on 3 of 5 fictional samples	High	Identify theme/app owners; remove the contradictory source; retest
Two priority collections have no known incoming link	Synthetic: observed in fictional navigation and content sample	High	Add relevant menu or guide links; verify rendered anchors
Seven products share one generic meta description	Synthetic: observed in fictional page source	Medium	Write page-specific descriptions, starting with traffic/revenue leaders
One old recipe URL returns 404 despite active external visits	Synthetic: fictional Search Console report plus fictional URL observation	Medium	Redirect to the closest replacement and test the old URL
LCP changed from Good to Poor after a homepage video launch	Synthetic: fictional reported correlation	Investigate	Compare theme/app timeline; do not claim the video caused it yet
FAQ markup passes syntax validation	Synthetic: fictional validator result	Low	Do not promise a Google FAQ result; keep only if it serves another valid use

The audit ends with owners, dates and retest conditions. It does not convert every observation into a speculative ranking forecast.

Turn findings into a release queue

Fix blockers and template-wide contradictions first, then high-value orphan paths, broken destinations, repeated metadata gaps and page-specific content. Batch changes by root cause and retest representative URLs after each release.

For a repeatable editorial inventory after the technical pass, continue with the Shopify content-audit guide. Keep its content decisions linked to the technical issue IDs so a rewrite does not obscure an unresolved indexability or template problem.

Measure with Search Console, Shopify reports and your own change log. Separate eligibility from outcome: crawl access is not indexing, indexing is not a high ranking, valid structured data is not a rich result, and traffic is not an attributed order. For AI visibility, use the manual prompt-and-paste free check to record mentions and visible source links; it does not fetch your store or prove why an assistant chose an answer.