Technical SEO for VTEX stores: definitive guide
Technical SEO is the foundation of organic traffic for any VTEX store. There is no point investing in content, link building or conversion optimization if Google cannot crawl, index and understand your pages correctly. VTEX offers native SEO tools, but the default configuration is rarely sufficient to compete in competitive niches. This guide covers all the technical optimizations needed to maximize organic visibility on VTEX stores.
Sitemap and crawling
VTEX automatically generates sitemaps at /sitemap.xml listing products, categories, brands and custom pages. The sitemap is periodically updated by the platform. Key concerns: verify that all relevant pages are included in the sitemap. Pages created via CMS or custom landing pages may not be automatically included. Submit the sitemap to Google Search Console and monitor crawl errors weekly. Configure robots.txt to block pages that should not be indexed: /checkout, /account, /api, internal search pages with parameters and combined filters that generate duplicate content. Use the Disallow directive carefully: blocking too much prevents Google from finding important pages.
Canonical tags and duplicate content
Duplicate content is the most common SEO problem in VTEX stores. Products accessible via multiple URLs (via category, search, collection), filters generating infinite parameter combinations and pagination without canonicals create thousands of duplicate pages that dilute authority. Configure canonical tags on all pages. In VTEX, the default canonical points to the cleanest product URL (/product/p). For categories with filters, the canonical should point to the category without filters. For pagination, each paginated page should have a self-canonical (pointing to itself). Never leave a page without a canonical: Google will choose on its own and does not always choose correctly. In the VTEX admin, check SEO settings in CMS > Settings > SEO.
Structured data (Schema.org)
Structured data allows Google to display rich snippets in search results: review stars, price, availability, breadcrumbs and FAQs. On VTEX, implement the following schemas. Product on all PDPs: name, description, image, sku, brand, offers (price, availability, priceCurrency). AggregateRating when reviews exist. BreadcrumbList on all pages to show navigation hierarchy. Organization on the homepage with logo, name, contact and social networks. FAQPage on pages with frequently asked questions. For Store Framework, create a custom component that injects JSON-LD via script tag. For FastStore, use Next.js Head component. Validate all schemas with Google's Rich Results Test before publishing. Monitor structured data errors in Search Console under Enhancements.
Meta tags and heading structure
Title tags are the most important on-page factor for SEO. On VTEX, configure title templates by page type: products should have [Product Name] - [Category] | [Store Name]. Categories should have [Category Name] - [Qualifier] | [Store]. Keep titles under 60 characters. Meta descriptions should be unique per page, between 120-155 characters, and include a call-to-action. On PDPs, include price or benefit in the description to increase CTR. Heading structure: each page should have exactly one H1 (product name on PDP, category name on PLP). H2s for main sections, H3s for subsections. Never skip levels (H1 directly to H3). In Store Framework, verify that blocks like rich-text use the correct heading level via blockClass prop and do not generate duplicate H1s.
Crawl budget and indexation
Crawl budget is the number of pages Google crawls on your site per session. VTEX stores with large catalogs (10,000+ SKUs) and combinatorial filters can generate millions of possible URLs, wasting crawl budget on low-value pages. To optimize: use noindex on combined filter pages without search volume. Block sorting and display parameters in robots.txt or via URL Parameters in Search Console. Implement pagination with limits (do not let Google crawl page 500 of a category with 3 products per page). Monitor the crawl stats report in Search Console: if Google is spending budget on irrelevant pages, correct it. For stores with very large catalogs, consider a segmented sitemap by type (products, categories, brands) to prioritize what matters.
Hreflang for multilingual stores
VTEX stores operating in multiple countries or languages need hreflang to indicate to Google which version to serve for each market. Implementation on VTEX can be done via link tags in the head of each page or via sitemap with hreflang attributes. Each page must declare all its alternative versions including itself. Include x-default pointing to the main version (usually the headquarters country). Common errors: asymmetric hreflang (page A points to B but B does not point to A), URLs with 404 in hreflang, and missing x-default. For VTEX stores with multi-domain (store.com, store.co.uk, store.com.mx), configure hreflang on each domain pointing to equivalents. For single stores with language binding, use VTEX CMS multi-language settings.
Performance as an SEO factor
Since 2021, Core Web Vitals are a ranking factor in Google. VTEX stores with LCP above 4 seconds, high CLS and slow INP lose positions to faster competitors. The impact is greater on mobile, where most e-commerce traffic occurs. For SEO, the most impactful performance optimizations are: reduce LCP below 2.5s (preload hero image, optimize TTFB), eliminate CLS (dimensions on images, reserve space for banners), improve INP (defer scripts, code splitting). Monitor Core Web Vitals in Search Console under the Experience tab. Pages with Poor status lose ranking opportunities. Pages with Good status gain competitive advantage. For stores that cannot optimize performance on Store Framework, migrating to FastStore or headless frontend is the most effective long-term SEO solution.
Tools and monitoring
A SEO monitoring setup for VTEX includes: Google Search Console for indexation, crawling, Core Web Vitals and errors. Google Analytics 4 for organic traffic by landing page, conversion and revenue. Screaming Frog for periodic technical audits (monthly crawl). Ahrefs or Semrush for monitoring positions, backlinks and competitors. PageSpeed Insights for performance by URL. Schema Markup Validator for structured data validation. Configure alerts for: more than 20% drop in weekly organic traffic, increase in crawl errors, important pages leaving the index, and Core Web Vitals degradation. Complete technical audits should be done quarterly, with targeted reviews after each significant deploy.