Technical SEO for SuiteCommerce: A Lean Guide

Check what the server and search crawler receive before adding SEO code. Fetch a product, category, and faceted URL in a fresh session. Record the status, canonical, robots directive, title, primary content, structured data, and internal links.

Keep crawl signals server-visible

A crawler should not need a late browser event to discover the canonical or noindex rule. Generate those signals in the initial response where the application's supported rendering path allows it.

Use robots.txt to control crawling, not to remove an already indexed URL. A blocked crawler may not see a page-level noindex. Google documents the distinction in its robots meta tag guidance.

Choose canonical URLs deliberately

Each indexable product and category should have one preferred, stable URL. Use that form in internal links and XML sitemaps. Redirect retired URL forms when there is a clear replacement.

Do not canonicalize different products or meaningfully different filtered pages just because their templates look alike. Follow Google's duplicate URL guidance and test the raw response after release.

Classify parameters into sort controls, tracking values, filters, and indexable landing pages. There is no safe hard-coded number of facets after which every URL should be blocked. Search demand, product overlap, and crawl volume matter.

Google's faceted navigation documentation explains the two broad choices: prevent crawling of unnecessary facet URLs, or make crawlable facet URLs consistent and efficient.

Add structured data from visible facts

Product structured data can help Google understand price, availability, ratings, shipping, and return information. It does not guarantee a rich result.

Generate JSON-LD from the same source used by the visible page. Do not emit a rating when no eligible review aggregate exists. Do not mark an item in stock based on a template default. For variants, currencies, or customer-specific prices, model only what the public page truthfully offers.

Use Google's current product structured data documentation and validate representative pages with Rich Results Test and Search Console.

Improve content and links before automation

A category needs useful products and a path from the site's navigation. A product page needs a clear name, useful description, specifications, images, price or purchase context, and links to its category where appropriate.

Automated title and description templates are useful defaults, but inspect collisions and truncation. A generated paragraph that only swaps a category name does not add useful content.

Measure page experience without inventing SEO gains

Core Web Vitals are part of Google's page experience systems, but relevance still matters. Use field data at the 75th percentile and page-level lab tests to find slow templates. Google's Core Web Vitals report documentation explains how Search Console groups URLs.