Adobe Commerce Cloud SEO Agency

Adobe Commerce Cloud (formerly Magento Commerce Cloud) is the managed PaaS tier of Adobe Commerce. SEO differs from open-source Magento or self-hosted Adobe Commerce in three concrete ways: (1) infrastructure constraints — Cloud uses Fastly as a managed CDN and full-page-cache layer, so canonical and Vary header behavior is determined by Fastly VCL, not Apache/Nginx; (2) indexer scheduling — Cloud runs indexers on a fixed cron, so cache-purge and reindex windows affect crawler-seen content; (3) deployment cadence — Cloud's two-environment model (staging, production) and integration-via-Git workflow constrain how SEO tickets land. We architect SEO to fit Cloud's operational envelope rather than fight it.

1Digital® Agency has 14 years on Adobe Commerce / Magento — we've been building, optimizing, and migrating on the platform since 2012. We're trusted by 400+ brands with a 4.9/5 rating across 941+ verified reviews. Our team covers SEO, theme engineering (Hyvä and Luma), backend module development, B2B catalog architecture, indexer tuning, Fastly VCL adjustment, and SEO-safe migrations on and off the platform.

Fastly serves as both CDN and FPC on Adobe Commerce Cloud. Two SEO pitfalls: (1) cached pages can serve stale canonical tags if a page's canonical changes after cache population — purges must be wired to canonical-impacting events (category move, URL key change, slug rewrite); (2) Vary headers must include only the dimensions that genuinely change indexable content, never user-session cookies, or you'll fragment cache and serve crawlers per-session HTML. We audit VCL, tune purge rules, and verify cached HTML matches what Googlebot sees via Search Console URL Inspection.

Magento indexers (catalog_product_price, catalog_product_attribute, catalog_url, etc.) populate the flat tables and URL rewrite tables that drive PDP and category rendering. SEO consequences: (1) catalog_url indexer is responsible for URL rewrite consistency — a stalled indexer can leave new products at SKU-style URLs instead of friendly slugs; (2) URL rewrite chains accumulate over time, so every rename adds a 301 hop, eventually impacting crawl budget; (3) indexer cron windows determine when newly created categories appear in sitemaps. We schedule indexers to align with crawler activity windows and prune stale URL rewrites on a quarterly cadence.

Configurable products are the parent SKU; simple products are the variant SKUs. Default Magento behavior creates one indexable parent PDP, with variants accessible via dropdowns and not as standalone URLs — usually correct for SEO. Two configurations matter: (1) "Use Default Value" for canonical handling per variant determines whether variant URLs (when explicitly enabled) canonicalize back to the parent — they should, unless variants are genuinely separate products by intent; (2) Product schema must emit at the configurable parent with Offer ranges (priceRange) or per-variant Offer entries inside a single Product, not as duplicate Products. We standardize on parent-level Product + Offer-array schema and disable variant URL indexation by default.

Layered nav generates URL parameters (?color=blue&size=M) by default — most of which should not be indexed. SEO patterns: (1) canonical tag on filtered URLs points back at the unfiltered category to prevent duplicate-content cannibalization; (2) selectively whitelisted "category landing" filter URLs (e.g. /shoes/men or /shoes/blue-running) are promoted to indexable category pages with their own meta, content, and schema; (3) robots.txt or meta-robots noindex,follow applied to non-promoted facets. For B2B catalogs, faceted nav often needs customer-group-aware behavior — visible filters change per group, so canonical strategy must respect group context.

Adobe Commerce B2B (separate license tier) introduces customer-specific catalogs, shared catalogs, company hierarchies, quote workflows, and negotiable pricing. SEO strategy: (1) public-facing catalog SEO covers the marketing surface — categories, top products, content; (2) authenticated buyer portal carries noindex,nofollow so Google doesn't try to index gated pages; (3) shared catalogs (one catalog per company segment) require canonical pinning to the public catalog to avoid duplicate-product issues; (4) requisition list URLs and quote draft URLs always carry noindex. We architect the indexable/gated boundary and emit appropriate meta-robots per route.

Adobe Commerce supports headless via REST and GraphQL APIs, often paired with Next.js, PWA Studio, or Vue Storefront on the front end. SEO ownership moves from the Luma/Hyvä theme to the headless front-end repo. We follow the same playbook as our headless commerce SEO program: SSR-first render strategy, sitemap orchestration at the front-end origin, schema injection at the layout level, llms.txt deployment, and crawler-equivalent HTML verification. Adobe Commerce Cloud's API rate limits matter — we cache GraphQL responses at the edge and rate-shape sitemap-generation jobs to stay within plan limits.

Yes. Hyvä is the modern Tailwind/Alpine-based theme stack; Luma is the legacy Knockout/RequireJS stack. SEO differences are mostly performance: Hyvä typically delivers green Core Web Vitals out of the box (LCP under 2.5s, INP under 200ms, CLS under 0.1), while Luma needs aggressive optimization (RequireJS bundling, Knockout binding deferral, CSS critical path extraction). Both can rank — Hyvä makes it cheaper. We audit theme output, deferred JS, and render-blocking CSS regardless of stack and produce a per-template CWV improvement plan.

Phase 1: technical audit covering Fastly VCL, indexer schedule health, URL rewrite chain depth, canonical and hreflang topology, Product schema completeness, configurable-product handling, faceted-nav indexation, and Core Web Vitals per template. Phase 2: corrective work — VCL tuning, indexer schedule alignment, schema graph rebuild, faceted-nav rules, theme-level CWV fixes (Hyvä or Luma). Phase 3: keyword-to-category mapping, content briefs, AI-engine optimization (llms.txt, entity-rich PDPs), and citation tracking. Replatforming brands often pair this with a Magento to Shopify Plus migration evaluation; if Cloud is the right home, we tune for it.