Ecommerce SEO Checklist for a New Online Store

The short answer

For a new online store, SEO begins with three separate questions: can Google crawl the page, can Google index the page, and is the indexed page relevant and useful enough to rank for a particular search? Publishing answers none of them automatically.

Start with a coherent launch set: the homepage, useful category pages, complete product pages, and essential service pages. Confirm that each intended search page loads publicly, is not accidentally blocked from crawling or indexing, and uses the preferred public domain. Give every page a distinct title, main heading, description, purpose, and internal path. Then submit the sitemap in Google Search Console, inspect representative URLs, and record the result.

Download the editable ecommerce SEO audit worksheet. Open it in Excel, Google Sheets, or Numbers and replace the examples with every URL in your core launch set. The sheet separates checks you can complete in preview from immediate post-publish checks and ongoing Search Console monitoring, so evidence that cannot exist yet does not create a fake release gate.

Crawl, index, and rank are different outcomes

Google describes Search as a sequence of crawling, indexing, and serving results. Crawling is Googlebot fetching resources from URLs it has discovered. Indexing is Google analyzing a fetched page and deciding whether and how to store it. Ranking happens later, for a particular query, when Google selects and orders eligible results. Google explicitly says that meeting its technical requirements does not guarantee crawling, indexing, or serving. That distinction is the foundation of an honest launch audit.

A crawl pass is not an index pass. An index pass is not a ranking promise. If a page is absent from results, diagnose the earliest failed stage rather than rewriting copy at random.

1. Define the core index set before publishing

Create a URL inventory before you audit settings. Include only pages that have a clear customer job and enough real information to stand alone:

• the homepage, which identifies the business, range, and principal shopping paths;
• categories that represent meaningful groups shoppers seek or browse;
• product pages with accurate names, prices, images, availability, and useful decision information;
• necessary delivery, returns, contact, and business-information pages where applicable.

Do not publish empty categories, placeholder products, unreviewed supplier text, or near-duplicate pages targeting slight keyword variations. There is no required product-description length or category word count. Ask whether the page resolves its shopping task with distinctive, truthful information.

Map every intended URL to one purpose and audience need. If two categories answer the same need with nearly the same products, merge or differentiate them. The product and category planning guide helps establish that source structure.

Decision rule: pass when every launch URL has a distinct purpose, complete content, and a place in the customer journey. Hold any page that is empty, duplicative, factually incomplete, or unsupported by navigation.

2. Check crawl and index controls conceptually

The accountable release owner must record the actual public configuration, consulting technical or SEO support when needed. The audit should cover these controls without assuming where a switch lives:

1. Public access: the preferred URL loads without authentication, a staging password, or an error response.
2. Crawl rules: robots.txt does not unintentionally disallow pages or resources Google needs to fetch. Remember that a crawl block is not the same as a reliable indexing exclusion.
3. Index directives: pages intended for Search do not carry an accidental noindex. Pages intentionally excluded should use an appropriate supported method selected by the technical owner.
4. Duplicate consolidation: protocol, host, path, and parameter variants resolve consistently, and the preferred version is communicated correctly. Redirect and canonical behavior requires implementation-level verification.
5. Rendered content: meaningful names, headings, descriptions, links, prices, and product information are available to crawlers rather than appearing only after a user action.

Use one final public hostname throughout the inventory. A custom domain is not itself an SEO setting, but consolidating promotion and links around one public address reduces ambiguity. Coordinate this with the custom-domain and publishing guide.

Decision rule: hold the affected URL if it is protected, errors, redirects unexpectedly, declares an unintended indexing exclusion, or exposes conflicting preferred versions. Resolve the evidence before promoting that URL; do not infer a fix from page appearance alone.

3. Give each page a clear search identity

Review four elements together: the page purpose, visible main heading, HTML title, and meta description. They should describe the same page without repeating an identical template everywhere.

Google recommends a descriptive, concise <title> for every page and warns against vague, boilerplate, or stuffed titles. There is no magic character count: title links can be truncated to fit the device, and Google may generate a different title link from several page signals. Write for recognition and differentiation.

Useful patterns are:

• Homepage: brand plus the actual product range or proposition, not “Home.”
• Category: category name plus a useful differentiator when true, not a chain of synonyms.
• Product: exact product name plus the most decision-relevant identifier or attribute, with concise branding if useful.

The main heading should make the page purpose unmistakable. Do not hide the important description inside an image. A category introduction can clarify what belongs and how to choose. Product copy should answer buying questions factually; never manufacture features to make a phrase fit.

Google primarily creates snippets from page content and may use the meta description when it describes the page better. Write a unique, human-readable summary for priority pages, but treat it as a suggestion, not guaranteed result text. Avoid lists of repeated keywords and site-wide generic descriptions.

Decision rule: pass when the URL inventory shows one distinct title, main heading, description, and purpose for every core page. Fail duplicates, placeholders, keyword lists, and metadata that promises something the visible page does not deliver. Do not use keyword-density formulas.

4. Build a storefront hierarchy that serves shoppers and crawlers

A coherent ecommerce structure usually runs from homepage to category or subcategory to product. Google says it uses the relationships between pages, including menus and cross-page links, to understand site structure. Important products and categories should therefore receive real links, not exist only in an internal search box.

The homepage should explain what the store sells and link to the most important shopping paths. Use the homepage design guide to order those paths for people first. Each category should serve one defensible grouping, introduce it plainly, link to its products, and provide useful subcategory paths when the catalog genuinely needs them. The category-page guide covers the selection experience.

Use customer-language navigation labels. Link menus to categories, categories to products, and relevant content to related pages when it helps the next decision. “Linen tablecloths” explains more than “click here.” Do not force every page into the header or add indiscriminate footer links. Map priority paths with the ecommerce navigation guide.

Test five realistic tasks on desktop and mobile: reach a priority category from the homepage; reach a product from that category; return to the parent category; find delivery information; and find a second relevant product without returning to a search engine.

Decision rule: pass when every core product is reachable through ordinary links, priority categories have clear prominence, anchors describe destinations, and the five tasks succeed. Fail any orphan core page, broken link, misleading label, or path that depends solely on site search or user-only interaction.

5. Audit product images as content

Images can help people assess products and help Google understand the page. Use short, descriptive filenames before upload where the workflow permits: blue-linen-tablecloth-140x200.jpg is more informative than IMG_1042.jpg. Keep each image near relevant text.

Write alt text for the image’s purpose in context: “Blue linen tablecloth with hemstitched edge on a six-seat table.” Decorative images need the appropriate empty alternative treatment, not keywords. If an image is a link, its alternative text helps communicate the destination. Confirm primary images load and do not hide critical facts inside pixels.

Decision rule: pass when important images load, filenames are understandable where editable, and alt text communicates the image’s relevant content without stuffing. Fail missing products, generic alternatives repeated across a gallery, filenames that leak internal data, or essential information available only in an image.

6. Review the mobile version as Google’s primary view

Google uses the mobile version of a site’s content for indexing and ranking. A visually attractive desktop page is therefore insufficient. On a real phone, confirm that the same essential product information, headings, links, images, and metadata are available; primary content must not require a click, swipe, or typing action merely to load.

Check phones for readable text, stable layout, usable menus, clear names and prices, tappable links, uncut images, and a complete homepage-to-product path. Test on a slower connection. Responsive layouts may change presentation, not remove evidence a buyer or crawler needs.

Setka can generate homepage, category, and product surfaces from the store brief and catalog, support navigation and editable copy, provide mobile layouts, and let a merchant preview before explicitly publishing. That whole-store context can make structural review more coherent. It does not prove technical search controls, indexing eligibility, rendering behavior, performance, or rankings. Treat preview as a review environment, then verify the published public URLs independently.

Decision rule: fail launch when mobile loses meaningful content or links, requires interaction to reveal primary content, creates horizontal scrolling that blocks use, or prevents a core shopping task. Pass only after representative real-device tests and public-URL inspection.

7. Find and submit the sitemap

A sitemap is a discovery aid, not permission to index and not a ranking accelerator. First ask the platform or technical owner for the public sitemap location and verify that Googlebot can fetch it. It should list absolute preferred public URLs that you actually want in results, rather than staging URLs, redirects, duplicates, or excluded pages.

In Search Console, submit the sitemap URL and record its status and last-read date. Submission is only a hint, not a guarantee of download, crawling, or indexing. Success does not mean every listed page entered the index.

Decision rule: pass when the sitemap is publicly fetchable, reports Success, and a sample matches the approved core index set. Fail a fetch error, wrong hostname, or material presence of redirects, staging URLs, duplicates, or pages not intended for Search.

8. Establish the Search Console baseline

Verify a Search Console property that covers the chosen public domain. Keep ownership with the business and give collaborators the minimum access they need. Then collect evidence in this order:

1. URL Inspection: inspect the homepage, every priority category, and representative products. Record the indexed status, last crawl if shown, page fetch result, indexing allowance, and Google’s selected preferred URL. Use the live test to diagnose the currently published page; use the indexed result to understand Google’s stored view. Request indexing for a small number of important new or corrected URLs, not as a substitute for links and a sitemap.
2. Page indexing: compare indexed and non-indexed totals with the intended URL inventory. Investigate reasons by representative URL. A large count is not automatically good; the right pages matter.
3. Sitemaps: confirm the submitted file remains readable and review indexing by the sitemap when useful.
4. Performance: once data appears, record clicks, impressions, click-through rate, and average position by page, query, and device. Search Console may take time to show data for a new property.

Interpret examples carefully. If a category earns impressions but few clicks, inspect its queries, title, description, and content; low CTR alone does not prove the title is the cause. If a product has no impressions, confirm indexing, search need, and internal links. If mobile impressions rise but clicks do not, compare query intent, result presentation, and the mobile page. Google advises focusing more on impression and click trends than position alone.

The practical launch sequence

Run the work in dependency order:

1. Freeze the preferred domain and core URL inventory.
2. Hold incomplete, duplicate, or placeholder pages.
3. In preview, complete unique titles, headings, descriptions, useful copy, internal paths, images, and real-device tasks.
4. Have the responsible owner verify the intended crawl, index, preferred-URL, and rendering configuration before publication.
5. Publish only the approved core pages.
6. Immediately test the public response, crawl and index directives, preferred URL, rendered content, links, and sitemap. If a critical public check fails, stop promotion and fix or withdraw the affected URL.
7. Verify Search Console, submit the sitemap, inspect priority URLs, and save the first available baseline.
8. Revisit index status and performance after Google has had time to process the pages; keep monitoring separate from launch approval.

A page is ready to publish when its critical PRE-PUBLISH checks pass or the page itself is held. POST-PUBLISH fields remain pending until a public URL exists; they are not reasons to pretend the preview failed. Complete them immediately after publication and act on failures. ONGOING indexing and performance fields become evidence over time, never a ranking promise.

Official sources

This checklist was checked against primary Google documentation on 31 August 2026:

• How Google Search works
• Title links in Google Search
• Control snippets and write meta descriptions
• Help Google understand an ecommerce site structure
• Google image SEO best practices
• Mobile-first indexing best practices
• Build and submit a sitemap
• Inspect and troubleshoot a URL in Search Console
• Performance report tasks and interpretation

When the release checks pass, publish the core pages only. Then complete the index baseline in Search Console, record the evidence in the worksheet, and use actual crawl, index, impression, and click data to choose the next improvement.