Use this to manage URL authority and prevent duplicate content issues across the storefront. This ensures search engines focus on the "master" version of a page, consolidating ranking power and protecting crawl budget.

Canonicalization Strategy

Use a self-referential canonical tag on every unique product, category, and CMS page (the "clean" URL should point to itself).
Use absolute URLs (including https:// and the full domain) to avoid ambiguity between environments, protocols (HTTP vs HTTPS), or subdomains.
Ensure the canonical target is indexable: it must return a 200 OK status and must not have a noindex tag.

E-commerce Specific Scenarios

Faceted Navigation & Filters: - Point the canonical to the main category for URLs created by sorting (?sort=price), view toggles (?view=grid), or tracking parameters (e.g., ?utm_source=...).
- Only allow a unique canonical if the filter creates a distinct, high-value landing page (e.g., a specific "Brand + Category" combination with high search volume).
Product Variations: - If a product has multiple URLs for different colors/sizes but the content is nearly identical, point the canonical to the primary product version.
- If each variation is a distinct marketing asset with its own unique description and SKU, use a self-referential canonical for each.
Cross-Categorization: When a product lives in multiple categories (e.g., /sale/product and /electronics/product), pick the most relevant or original path as the canonical to avoid splitting authority.

Technical Rules

Single Tag Policy: Ensure only one <link rel="canonical"> exists in the <head>. Multiple tags cause search engines to ignore the instruction entirely.
Sitemap Alignment: The URL defined as canonical must match the URL listed in the sitemap.xml. Discrepancies send conflicting signals to crawlers.
Pagination: For paginated results (e.g., ?page=2), use a self-referential canonical. Do not point page 2 to page 1, as this prevents search engines from discovering products deeper in the catalog.

Más de este repositorio

mismo repositorio

vtex-login-headless

decocms/storefront-skills

Diagnose and fix headless login issues on VTEX storefronts — covering authorized domain setup and simulating an authenticated session by copying VtexIdclientAutCookie cookies.

2026-07-0912

deco-bot-rendering

decocms/storefront-skills

Use when debugging what crawlers or bots see on a deco site, verifying if SSR is active for bots, or diagnosing firstByteThresholdMS behavior.

2026-07-0112

seo-sections

decocms/storefront-skills

Use when a site's SEO metadata (title, og:tags, LD+JSON) is missing, incomplete, or handled by a weak custom component. Covers configuring the apps SEO sections for general pages, PDPs, and PLPs via the deco admin.

2026-07-0112

variants

decocms/storefront-skills

Configure deco.cx Variants — the mechanism that swaps the value of a section, page, image, message, or ANY custom-typed prop based on a matcher rule (device, cookie, date, A/B test, geo, path, query string, etc.). Use when the user asks to A/B test a section, personalize a page per audience/segment, show different banners per device or location, schedule a promotion by date/cron, add a new variant-able type (promotion, VTEX segment, product list, menu items), write a custom matcher, or generally wire up `website/flags/multivariate*` in `.deco/blocks/*.json`. Covers the JSON shape (`variants: [{ value, rule }]`), the resolution order (first match wins, catch-all last), every built-in matcher (`always`, `never`, `device`, `date`, `cron`, `random`, `cookie`, `host`, `pathname`, `queryString`, `userAgent`, `location`, `site`, `environment`, `multi`, `negate`), how to compose them with `multi` (and/or) and `negate`, the 8-line boilerplate to create your own `flags/multivariate/<type>.ts`, the shape of a custom `ma

2026-07-0112

setup-blog

decocms/storefront-skills

Install and configure the Blog Manager on a deco-site storefront. Covers the blog app, page routes, sections, Blog Manager MCP connection in Studio, and first-run brand context initialization.

2026-06-2912

deco-ecommerce-qa

decocms/storefront-skills

Use when inside a deco.cx ecommerce repository (deco.ts present, decobot in PR history) and the user wants automated QA for purchase-journey correctness — set up E2E coverage, test the add-to-cart / checkout flow, or scaffold a CI gate for the store with the @decocms/qa engine. NOT for load/cache performance testing (use deco-e2e-testing) or hand-written Playwright spec files.

2026-06-2912

name	canonical
description	Use this to manage URL authority and prevent duplicate content issues across the storefront

Canonicalization Strategy

Use a self-referential canonical tag on every unique product, category, and CMS page (the "clean" URL should point to itself).
Use absolute URLs (including https:// and the full domain) to avoid ambiguity between environments, protocols (HTTP vs HTTPS), or subdomains.
Ensure the canonical target is indexable: it must return a 200 OK status and must not have a noindex tag.

E-commerce Specific Scenarios

Faceted Navigation & Filters: - Point the canonical to the main category for URLs created by sorting (?sort=price), view toggles (?view=grid), or tracking parameters (e.g., ?utm_source=...).
- Only allow a unique canonical if the filter creates a distinct, high-value landing page (e.g., a specific "Brand + Category" combination with high search volume).
Product Variations: - If a product has multiple URLs for different colors/sizes but the content is nearly identical, point the canonical to the primary product version.
- If each variation is a distinct marketing asset with its own unique description and SKU, use a self-referential canonical for each.
Cross-Categorization: When a product lives in multiple categories (e.g., /sale/product and /electronics/product), pick the most relevant or original path as the canonical to avoid splitting authority.

Technical Rules

Single Tag Policy: Ensure only one <link rel="canonical"> exists in the <head>. Multiple tags cause search engines to ignore the instruction entirely.
Sitemap Alignment: The URL defined as canonical must match the URL listed in the sitemap.xml. Discrepancies send conflicting signals to crawlers.
Pagination: For paginated results (e.g., ?page=2), use a self-referential canonical. Do not point page 2 to page 1, as this prevents search engines from discovering products deeper in the catalog.