Ecommerce SEO Checklist

Use this for: Stores planning or improving search landing pages.

List the actual product range and the questions buyers ask. Inspect search results for relevant phrases in your target market, then assign browsing needs to categories, specific items to product pages and advice to guides. Use existing pages when they already fulfill the task. Do not create a new landing page for every keyword variation.

1. Start with the real assortment and buyer questions.
2. Compare observed result types.
3. Assign a useful destination for each distinct need.

Use this for: Search-facing product categories.

In the commerce editor, create or refine categories around meaningful product types, uses or compatibility. Assign appropriate products, give the category a clear name and add a short introduction explaining the selection. Keep the product grid easy to reach. A category needs a useful range and purpose, not a fixed product count or word quota.

1. Define the category’s inclusion rule.
2. Assign relevant products and write the introduction.
3. Preview the grid and useful buying guidance.

Use this for: Public categories and products.

Edit the store’s navigation and category templates so relevant departments link to categories and those listings link to the products they contain. Use descriptive text links with real destinations. Add useful breadcrumbs and related-category links where they help orientation. Do not rely on the search box as the only way to find products.

1. Add the main shopping destinations to navigation.
2. Ensure category grids link to their products.
3. Test the complete path at desktop and phone widths.

Use this for: Important category and product landing pages.

Open the category or product’s SEO title and meta description fields in your commerce editor. Name the real category or model and a useful distinguishing attribute where relevant. Write a description that previews the actual selection or buying information. The product name, visible H1 and SEO title may use separate controls, so preview all three. Search engines can show different title or snippet text.

1. Edit the correct page’s SEO fields.
2. Check the visible title and main heading.
3. Save and inspect the public title and description.

Use this for: Individual product pages.

In the product editor, write a clear opening explaining what the item does, then add verified dimensions, materials, compatibility, included parts and relevant limitations. Use headings such as “Rack compatibility” and “What is included” when they help. Preserve accurate manufacturer specifications, but add your own useful explanation rather than rewriting facts for novelty.

1. Gather verified product facts.
2. Write the use case and decision-critical details.
3. Check the published sections and unanswered buyer questions.

Use this for: Product and category imagery.

Choose accurate product images showing the item, important details and scale where needed. Resize to the intended display and zoom requirements, compress while preserving detail, then upload to the product media fields. Describe informative images in alt text and verify that the correct image follows each variant. Check the final result on mobile.

1. Select meaningful accurate views.
2. Resize and compress, then upload.
3. Set suitable alt text and check the displayed variant.

Use this for: Products with selectable variants.

Configure size, color or capacity options in the catalog and test direct links to selected variants. Use stable paths or query parameters that reproduce the intended selection. For a single-page variant design, the base product is commonly the canonical; a multipage design needs its own deliberate treatment. Ask a developer to align URL, canonical and ProductGroup output with the actual model.

1. Configure genuine options and identifiers.
2. Test direct entry to each important selection.
3. Align URL and structured-data behavior with the page model.

Use this for: Stores exposing filter or sort URLs.

Before exposing every filter combination, decide which selections deserve maintained landing pages. Give those a useful assortment, stable URL and relevant links. For the remaining sorting and filter space, have the developer scope crawl controls to the actual parameter patterns. Use noindex when exclusion from indexing is the goal and the directive can be crawled; robots rules alone do not guarantee removal.

1. Choose any valuable stable filtered landing pages.
2. Separate sort and low-value filter URL patterns.
3. Implement and test the narrow crawl/index policy.

Use this for: Categories longer than one result batch.

Configure the category template with real links to later result pages even when the interface uses load more or infinite scroll. Each paginated page needs its own address and appropriate self-canonical, rather than declaring page one as the canonical for every batch. Keep product links available in the rendered content.

1. Check the listing’s later-page addresses.
2. Provide sequential crawlable links.
3. Verify page-specific canonicals and product links.

Use this for: Public catalog URLs intended for search.

Choose the preferred live address for each intended landing page and configure canonical output consistently. Link internally to that address and include the intended canonical version in the sitemap. Open the generated sitemap, test sample URLs and submit it in Search Console. Exclude redirects and retired addresses from the current sitemap.

1. Set canonical rules for actual URL classes.
2. Align navigation and generated sitemap entries.
3. Submit and inspect processing.

Use this for: Stores using product structured data or a Merchant Center feed.

Configure your platform’s product structured-data integration to use the real name, image, price, currency and stock fields. Use the merchant-listing requirements for pages where shoppers buy from you. Validate representative output with the Rich Results Test. If you use Merchant Center, map the same current offer and identifiers into the feed and review its product issues. Never invent ratings or identifiers.

1. Map verified catalog fields to the integration.
2. Test product and variant output.
3. Compare feed and page facts after synchronization.

Use this for: Products that change availability or leave the catalog.

Define what the storefront should do when an item is temporarily unavailable, returning seasonally or permanently retired. Keep useful temporary-stockout pages with accurate availability and sensible alternatives. When permanently removing a page, redirect only to a relevant replacement; otherwise return a proper not-found response and remove outdated navigation. Update offer data and feeds at the same time.

1. Define the distinct inventory states.
2. Configure messages, purchase controls and response rules.
3. Synchronize links, offers and feeds.

Use this for: Launched or launch-ready store templates.

At phone width, browse a category, choose a product and variant, and inspect delivery and return information. Use a test mode where available and stop before any real purchase. Fix broken controls, obscured details and excessive image or script work. Then establish Search Console views for category and product groups so future comparisons use the same pages and market.

1. Complete the non-purchase mobile journey.
2. Investigate specific rendering or performance problems.
3. Save comparable category/product report views and recheck after releases.