Check Shopify SEO by connecting each product and collection URL to useful content, descriptive metadata and a clear discovery route. Review the actual published page and sitemap output together. Use the worksheet below to decide what each destination should answer, which changes need verification and where a crawl-control question needs separate investigation before an edit.
Which question should a product or collection page answer?
Start with the customer’s task. A product page should help someone assess that particular item, while a collection should help them understand and compare the relevant group. Write the distinguishing information before choosing a title or adding search terms. Keep the catalogue’s actual attributes and availability evidence behind the public description.
Shopify recommends readable, unique product and collection descriptions. Documentation. Ask the editor to explain what makes the page useful beyond repeating a name and category. For a collection, decide which selection questions it helps answer and which products genuinely belong there. Keep an explicit owner for changes to the collection’s purpose or membership.
Shopify uses the entered content title to generate a page H1. Documentation. Compare the entered title with the rendered main heading after editing. A theme or content change should still leave the reader with an understandable page subject. Include both a product and a collection in the proposed inspection rather than assuming the same output from every content type.
How should metadata and imagery support that destination?
Shopify allows meta descriptions for products, collections, pages and blog posts. Documentation. Write a summary appropriate to the particular page. A collection description should explain the selection represented there; a product description should help identify the item and the information the page provides. Keep the wording tied to the visible content and the business’s actual offer.
Shopify recommends image alt text that accurately describes what the image displays. Documentation. Use that instruction when preparing the image brief and the actual alt text. Identify what the image shows and how it relates to the page. Do not turn the alt field into a list of service locations or unrelated catalogue terms.
Shopify notes that search engines can rewrite page titles and descriptions. Documentation. Inspect the website’s metadata separately from a search result observation. Record the page URL, the configured wording and the actual output. If the search display differs, keep the query and observation context with that evidence instead of assuming the administrative field failed to save.
An original product-and-collection URL worksheet
Use this practical checklist for representative catalogue destinations. Complete it before a significant content or URL change, then add observed results after the authorised change. It connects editorial decisions to the outputs the site actually serves.
| Destination question | Information to record | Verification to request |
|---|---|---|
| Product identity | Item reference and intended public URL | Does the destination show the intended item? |
| Collection purpose | Selection question and membership rule | Can a reader understand why these items are grouped? |
| Page promise | Title, description and visible heading | Do they describe the same useful content? |
| Discovery route | Referring page and actual link destination | Can the intended destination be reached directly? |
| Sitemap entry | Sitemap file and listed public URL | Is the intended page represented where expected? |
| Changed destination | Old reference and agreed subsequent treatment | Have affected links and outputs been checked? |
| Crawl question | Current rule and affected URL examples | What specific problem would a rule change address? |
Keep an exception row for a page whose editorial purpose is unclear. Similar catalogue items may need careful distinctions, while some groupings may not justify their own destination. Resolve that content question before creating another page or changing crawl rules to hide an unresolved duplication problem.
When proposing a URL change, identify the existing references that matter to the business and agree the intended handling of the old destination. Ask the implementer to demonstrate the actual supported behaviour and retain the observed result. Keep that change policy with the site’s wider URL decisions rather than assuming an automatic outcome.
How should the sitemap be examined?
Shopify automatically generates sitemap.xml for its stores. Documentation. Shopify locates sitemap files at the root of a store domain. Documentation. Open the actual file for the intended domain and identify the relevant section. Use a representative product and collection from the worksheet so the inspection follows the same content already reviewed.
The generated sitemap index links to separate product, collection, blog and page sitemaps. Documentation. Shopify automatically updates sitemap files when supported store content is added. Documentation. Compare the listed destination with the published page after adding a representative item through the normal content process. Record the observation and any discrepancy. If a route is missing or stale, investigate its publication and domain context before manually inventing another sitemap arrangement.
Shopify says Google does not guarantee the time needed to crawl and index a store. Documentation. Treat submission and observation as separate steps in the search workflow. A sitemap can help discovery, while the site’s public pages, content and access conditions still need their own review. Record what the search tooling actually reports rather than promising an indexing date.
Hypothetical example: a collection changes its purpose
Imagine a collection previously grouped one type of product, then is repurposed around a different selection. The title changes, but the old introductory copy and several internal links still describe the earlier group. This hypothetical example tests whether the page’s promise and discovery context remain aligned.
Use the worksheet to write the new purpose and membership rule. Compare the visible heading, summary, images and listed products with that purpose. Review the referring links and identify any wording that would lead a reader to expect the old selection.
Then inspect the actual public destination and sitemap entry after the authorised edit. Keep the content version and observation date together. If the public URL also changes, include the agreed old-destination treatment in the same verification record rather than judging the new page alone.
When should crawl controls be changed?
Write the exact access problem and representative URLs before proposing a crawl-rule edit. Keep ordinary product content, collection usefulness and internal navigation decisions separate from that technical change. A rule should have a clear intended effect that can be reviewed against actual examples.
Use the Shopify robots.txt guide for that focused worksheet. Keep broader country and account constraints with Shopify in Zambia. For the store brief, see online stores and SEO. Get started with the product and collection examples you need the website to present more clearly.
Have the catalogue owner identify who approves a collection membership change and who checks its public description afterwards. Add that responsibility to the worksheet so the next catalogue edit follows an agreed review route.
By Spout Team. AI-assisted drafting by Codex using the linked primary documentation.