Sitecore SEO

TL;DR — Sitecore is a big enterprise CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms., and it does not handle SEO for you. The basics every site needs — page titlesThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim., descriptions, a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., a sensible robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. — have to be set up, and Sitecore has a few traps that can quietly block your whole site or create duplicate pagesThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. Knowing they exist is most of the battle.

What Sitecore is

Sitecore is a Digital Experience Platform — a large, enterprise CMS that big companies use to run complex websites with personalization, multiple languages, and many sites in one install. It comes in two main flavors, and the difference matters a lot for SEO:

• Sitecore XP (Experience Platform) — the traditional, older style. It’s built on .NET and renders pages on the server, so search engines generally see finished HTML.
• XM Cloud — the modern, cloud version. Here Sitecore just stores the content, and a separate front-end website (usually built with Next.jsMaking sure search engines can crawl, render, and index content that depends on JavaScript.) pulls that content in and builds the actual pages. SEO is controlled in that front-end app, not inside Sitecore.

The big thing to know

Sitecore doesn’t give you much SEO out of the box. There’s an add-on called SXA (Sitecore Experience Accelerator) that provides the essentials — a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. control, and metadata fields — but you (or your developers) still have to set it all up. Without SXA, even basic things like a meta description field have to be added by hand.

Three traps to watch for

Sitecore has a few quirks that catch teams off guard:

1. The robots.txt that blocks everyone. If the robots field in Sitecore’s settings is left blank, Sitecore doesn’t serve an empty (permissive) robots.txt — it serves one that blocks every search engine. Blank does not mean “allow everything” here.
2. Aliases that duplicate pages. Sitecore lets you give a page a second URL (an “alias”). Both URLs return a normal “200 OKHTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page.” — there’s no redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. — so you end up with two live URLs for the same content, which is duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling..
3. Empty fields that don’t fill themselves in. Sitecore can set a default value for a field (a “Standard Value”), but if an author clears the field, it stays blank instead of falling back to the default. The result is pages with empty titles and descriptions.

Want the technical version — how SEO actually works on XP vs XM Cloud, the Next.js metadataNext.js SEO is the set of practices and built-in features that make a Next.js site crawlable, indexable, and rankable — rendering mode (SSG/SSR/ISR/Server Components), the App Router Metadata API, sitemap.ts/robots.ts conventions, next/image, and next/link. pipeline, hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others., and enterprise governance? Switch to the Advanced tab.

TL;DR — Sitecore ships with almost no SEO functionality; SXA adds the basics but needs configuration. The two platforms diverge completely: XP is server-rendered .NET (crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. see finished HTML, personalization renders server-side); XM Cloud is headless, where a Next.js front end controls the HTML and you manage SEO with Next.js metadataNext.js SEO is the set of practices and built-in features that make a Next.js site crawlable, indexable, and rankable — rendering mode (SSG/SSR/ISR/Server Components), the App Router Metadata API, sitemap.ts/robots.ts conventions, next/image, and next/link. APIs (generateMetadata, MetadataRoute) — with SSG/ISR the recommended renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. modes. The platform-specific traps: the default robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. blocks all crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. when the field is blank; item aliases return HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. on both URLs (true duplicate content, no canonical fix by default); and blank metadata fields don’t inherit Standard Values unless “Reset Blank” is enabled (blank ≠ NULL). At Sitecore’s enterprise scale, governance — a base SEO template, validation rules, environment control — is the real work. (Naming note: Sitecore’s docs now call the XM Cloud product SitecoreAI; the architecture below is unchanged.)

Two platforms, two completely different SEO models

The single most important thing to establish before touching anything: which Sitecore are you on? The product name is the same; the SEO mechanics are not.

• Sitecore XP (Experience Platform). Traditional .NET, server-rendered via Razor/MVC, deployed on-premise or in managed cloud. GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. generally receives finished HTML. SEO is managed inside Sitecore — in templates, Standard Values, and request pipelines.
• XM Cloud. Headless SaaS. Sitecore stores the content and exposes it over a GraphQL API (Experience Edge); a decoupled front end — almost always Next.js built with Sitecore JSS (JavaScript Services) — renders the HTML. SEO lives in the Next.js application layer. Sitecore holds the content; Next.js controls the output.

A naming note if you’re checking Sitecore’s own docs while reading this: as of mid-2026, Sitecore’s documentation site has renamed the composable SaaS product from “XM Cloud” to SitecoreAI — the old doc.sitecore.com/xmc/... and developers.sitecore.com/learn/accelerate/xm-cloud/... URL paths now redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. to .../sai/.../sitecoreai/... paths, and the platform’s own landing page describes it as “a cloud-native, SaaS, hybrid headless digital experience platform.” The architecture this article describes is unchanged — Experience Edge, GraphQL, a decoupled Next.js front end — but the front-end SDK is now published as Content SDK (open source, Next.js-first) rather than under the JSS name, and you’ll see “SitecoreAI” rather than “XM Cloud” in current screenshots and menu labels. I’ve kept “XM Cloud” in this article because that’s still the term most practitioners search for and most existing implementations run on, but don’t be thrown if your Sitecore rep or the Cloud Portal now says SitecoreAI — same platform, same SEO mechanics below.

In both cases the practical baseline is the same. As Fishtank’s Marcel put it back in 2018, “Sitecore ships with virtually no SEO functionality (with the exception of SXA which includes some basics).” That’s still the right mental model. SXA (Sitecore Experience Accelerator) is the layer that gives you a sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. module, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. management in the content tree, and standardized metadata fields. Without it, all of that is custom development.

This is squarely enterprise SEO territory. Sitecore implementations involve dedicated developers and solution partners, and — as I’ve written about enterprise sites generally — “the more likely you are to run into multiple tech stacks,” legacy systems, and split ownership across sections. Keep that in mind: on Sitecore, the fix for an SEO problem is often a template change or a pipeline override owned by a developer, not a setting you flip yourself.

Metadata — and the blank-vs-NULL trap

SEO fields (page titleThe title tag is the HTML title element in a page's head that specifies the document's title. It's the primary source for the SERP title link and a confirmed light ranking factor — but since August 2021 Google doesn't always show it verbatim., meta descriptionThe meta description is an HTML head tag — `<meta name=\"description\" content=\"…\">` — that suggests a short summary of the page for the search snippet. It's not a Google ranking factor, and Google rewrites it the majority of the time, but a good one can still lift click-through., Open GraphOpen Graph (OG) tags are `<meta>` elements in a page's head, defined by the Open Graph protocol (ogp.me, created by Facebook), that describe a page as a shareable object — its title, description, image, URL, and type. They control how a link preview card looks when the page is shared on Facebook, LinkedIn, Slack, Discord, WhatsApp, and iMessage. They are not a direct Google ranking factor, though Google reads og:title, og:image, and og:site_name as inputs to how a result appears. tags) live in your page data templates. The clean pattern is a base SEO template that every page template inherits from, so the fields exist everywhere. Ken Gray of Konabos notes the default gap directly: “out-of-the-box, Sitecore’s data templates might not include some of the Meta Data fields.”

Standard Values let you set sensible defaults for those fields (for example a $name token as a title fallback). But here’s the Sitecore-specific trap that produces missing metadata at scale. Sitecore’s own docs are explicit: “If the value of a field is NULL, the item contains the standard value for that field as defined in the data template for that item.” The catch is that a blank field is not NULL. When a content author clears a meta description, it becomes blank — and a blank field does not fall back to the Standard Value unless “Reset Blank” is enabled on that field. The result is pages renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. <meta name="description" content=""> instead of inheriting a default. On a large site, that’s thousands of empty descriptions nobody intended.

The fix is twofold: enable “Reset Blank” on metadata fields where a fallback is desired, and add validation rules that enforce non-empty titles and descriptions (and character limits) so authors can’t silently ship blanks.

URL management and the alias trap

Sitecore generates URLs from the content-tree path by default; clean URLs come from SXA settings or custom item resolvers.

The trap is item aliases — alternate URLs you can attach to any item. They look harmless and they are not SEO-neutral. As Dheer Rajpoot documented, “no redirect (no 301 or 302 HTTP status codeAn HTTP status code is the three-digit number a server returns with every response to tell a browser or crawler what happened to its request — success, redirect, client error, or server error. For SEO the code matters as much as the content: it tells Google and Bing whether to index a page, follow a redirect, retry later, or drop the URL from the index.) happens when you are using aliases in Sitecore,” which means “multiple URLs will be created for a single page URL.” Both the canonical URL and the alias return HTTP 200 with identical content — genuine duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling., and Sitecore does not auto-emit a canonical tagA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. to resolve it.

You have two governance-grade fixes:

1. Override the AliasResolver in the HttpRequest pipeline to inject a canonical tagA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. pointing at the real URL, or
2. Modify the alias pipeline to issue a 301 redirectA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank. instead of serving the alias directly.

My recommendation is the second: treat aliases as redirects, not alternate access URLs. Ken Gray’s advice applies broadly here — “use Sitecore’s canonical link management to specify the preferred version of a URL” — but on aliases specifically, a 301 is cleaner than relying on canonical hints.

Sitemaps

On SXA, configure the sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. at site/Settings → Search Engines Sitemap → Sitemap Mode. Two relevant modes: Stored in cache (the default — regenerates dynamically; good for frequently updated or Azure-hosted sites) and Stored in file (a static file; better for large sites that change infrequently, avoiding regeneration overhead). SXA automatically appends the sitemap URL to robots.txt, and the sitemap lives at /sitemap.xml. A common failure: if TargetHostName isn’t configured, the sitemap returns a 404.

On XM Cloud + Next.js, generate the sitemap programmatically with MetadataRoute.Sitemap, querying Experience Edge over GraphQL — which lets you exclude non-indexable URLs at the application layer. Sitecore’s own guidance notes that “Next.js offers built-in sitemap and robots.txt generation.”

Robots.txt — the default that blocks everything

This is the Sitecore trap with the highest blast radius. On SXA, robots.txt is configured in the content tree (site Settings → Robots content field), and you must republish the site after a change. The gotcha, straight from Sitecore’s docs: “If no rules are added, the system writes: ‘User-agent: * Disallow: /’” — which blocks every crawler. An empty robots field is not a permissive robots.txt; it’s a site-wide block. You must explicitly set:

User-agent: *
Allow: /

On most platforms a missing robots.txt means “crawl everything.” On Sitecore it can mean the opposite, so verifying production robots.txt is a non-negotiable launch step. On XM Cloud + Next.js, use MetadataRoute.Robots for a code-driven, type-safe robots.txt. Separately, CM (Content Management) instances and QA/staging environments should always disallow all — only the CD (Content Delivery) production instance should be crawlable.

Multilingual, hreflang, and multisite

Sitecore stores language versions as separate versions of the same item, not separate items. That, combined with language fallback (item-level or the more granular field-level, e.g. an es-MX → es-ES → en chain), can serve the same content at multiple language URLs — a duplicate-content vector unless hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. signals the relationship. And hreflang is not automatic in standard Sitecore; it has to be added to templates (SXA can generate it when configured), with full absolute URLs, bidirectional references, and an x-default. As John Mueller put it (cited by Jakub Koba), “TBH hreflang is one of the most complex aspects of SEO (if not the most complex one).” Don’t underestimate it.

Sitecore also natively supports multisite — many sites in one install, sometimes sharing content. Shared content across site boundaries needs a deliberate canonical strategy, and each site needs its own sitemap and robots.txt. This is exactly the kind of split-ownership, shared-infrastructure complexity I flagged in enterprise technical SEO: “Sometimes different people are responsible for different sections of the website or even different pages, which can make internal linkingLinks between pages on the same site. time-consuming.”

Headless rendering strategy (XM Cloud)

One layer-ownership point worth being explicit about, since it trips people up: XM Cloud environments have both an editing host and a rendering host, and they are not the same thing. Sitecore’s own docs draw the line clearly — the editing host exists only to power the WYSIWYG editing experience inside Page Builder/Design Studio, “is not set up or scaled for serving live traffic,” and sees internal (author-only) traffic. The rendering host is the public-facing Next.js app — hosted on Vercel, Netlify, or Azure, consuming content from Experience Edge, and scaled to serve real site visitors. Crawlers only ever hit the rendering host; the editing host’s rendering behavior (or an editing-host URL leaking into a sitemap or getting linked to) is not representative of what GooglebotGooglebot is Google's web crawler — the software that fetches pages so Google can index and rank them. It comes in two variants, Googlebot Smartphone (primary, under mobile-first indexing) and Googlebot Desktop, and runs an evergreen Chromium renderer. sees and isn’t something search engines should be able to reach at all.

On XM Cloud the rendering mode you choose in Next.js is the SEO decision. Akshay Sura (Konabos) lays out the four options cleanly:

The recommendation: SSG or ISR for SEO-critical content; reserve CSR for interactive UI only. Metadata is set via generateMetadata (App Router). David Austin (Fishtank) notes a performance nicety: “All fetch calls within generateMetadata are memoized, meaning identical URLs are only fetched once across the application, preventing redundant requests.” And as Sebastián Aliaga puts it, “The dynamic approach is the better method for Sitecore Headless as you’ll be able to take what’s part of the page’s layout data and incorporate it.”

Personalization — don’t cloak

Sitecore’s personalization is a real SEO consideration. On XP, personalization renders server-side, so Googlebot sees the default (un-personalized) experience — make sure that default is complete and SEO-optimized, not thin. On XM Cloud, client-side personalization (JSS) can hide content from crawlers that don’t run the JavaScript; pre-render the default with SSR, or personalize at the edge.

The hard rule across both: never serve different content to crawlers than to users — that’s cloaking, and it’s a guidelines violation. Never personalize the primary H1, FAQ content, or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. with client-side rules. Personalization should add to, never replace, the canonical content.

Structured data

Use JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. in <script type="application/ld+json">. On XP, render it from template fields in your Razor view or via pipeline; on XM Cloud, model schema fields in templates, retrieve over GraphQL, and render in the Next.js component. Prioritize FAQPage, HowTo, Product, Article, and BreadcrumbList. You can deploy via a tag manager — Martha van Berkel (Schema App) notes teams “typically use JavaScript to deploy Schema MarkupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. to Sitecore… both efficient and scalable” — but be aware client-side injection means AI crawlersAI crawlers are bots from AI companies that fetch web pages to train language models, build AI-search indexes, or answer live user questions. They come in three categories, each with its own user-agent tokens and its own robots.txt controls. may miss it, so prefer server-rendered JSON-LD for maximum coverage. Peter Lambrou (Codehouse) frames the payoff simply: “Add schema markup to the page HTML to make your search results appear more attractive.”

Enterprise governance — where the real work is

Single settings aside, the SEO outcome on a big Sitecore install is decided by governance. I’ve said before that enterprise sites are where technical SEO shines precisely because “enterprise sites can have complex infrastructures and a lot of legacy systems in place” — and “I doubt there’s a major website that is technically perfect.” The recurring Sitecore-specific governance items:

• Template sprawl. Multiple templates for the same purpose, each with different (or missing) SEO fields. Audit them; enforce a base SEO template that every page template inherits.
• Metadata validation. “Reset Blank” plus field-level validation so authors can’t ship empty or over-length titles and descriptions.
• Alias governance. A policy that aliases are only created with a canonical override or as 301s.
• Environment control. CM/QA/staging disallowed; production explicitly allowed and verified.
• Crawl budgetThe number of URLs an engine will crawl in a timeframe. at scale. Faceted navigationFaceted navigation (faceted search, product filtering) lets visitors refine a list of products or content by attribute — price, color, size, brand, rating. The SEO problem: each filter combination can spawn a distinct crawlable URL, turning a small catalog into millions of near-duplicate pages that waste crawl budget and dilute ranking signals., language versions, and parameter URLs can blow up the URL space; curate sitemaps and govern robots/noindexMeta tags are HTML elements in a page's head that pass metadata about the page to search engines and browsers. For SEO only a few matter — the title element, the meta description, and the robots meta tag — while meta keywords and most others are ignored. tightly. (See crawl budgetThe number of URLs an engine will crawl in a timeframe..)

AI summary

A condensed take on the Advanced version:

• Two platforms, two SEO models. Sitecore XP = traditional server-rendered .NET; crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. see finished HTML; SEO managed inside Sitecore (templates, Standard Values, pipelines). XM Cloud = headless SaaS; a Next.js front end (via JSS, now published as Content SDK) controls the HTML; SEO managed with Next.js metadataNext.js SEO is the set of practices and built-in features that make a Next.js site crawlable, indexable, and rankable — rendering mode (SSG/SSR/ISR/Server Components), the App Router Metadata API, sitemap.ts/robots.ts conventions, next/image, and next/link. APIs. Sitecore’s docs now brand this product SitecoreAI; the architecture is the same.
• Editing host ≠ renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. host. On XM Cloud, the editing host is internal-only (WYSIWYG editing, not scaled for live traffic); the renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. host is the public Next.js app crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. actually hit, served from Vercel/ Netlify/Azure and fed by Experience Edge.
• Almost nothing out of the box. “Sitecore ships with virtually no SEO functionality” — SXA adds sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. management, and metadata fields, but all need configuration.
• Robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. trap: a blank robots field makes Sitecore output User-agent: * / Disallow: / — blocking every crawler. Empty ≠ permissive; set Allow: / explicitly and republish.
• Alias trap: item aliases return HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. on both URLs with no redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. — true duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.. Canonical isn’t applied automatically; fix with a canonical override or a 301 pipeline change.
• Metadata trap: blank ≠ NULL. A cleared field does not inherit its Standard Value unless “Reset Blank” is enabled — a common source of empty titles/descriptions at scale. Add validation rules.
• Headless rendering: SSG/ISR recommended for SEO; SSR fine; CSR worst. Metadata via generateMetadata; sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing./robots via MetadataRoute.
• Never cloak: don’t personalize the H1An H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about., FAQs, or structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. for crawlers; keep the default experience SEO-complete.
• Enterprise governance is the real work: base SEO template, metadata validation, alias policy, environment control (block CM/QA/staging), and crawl budget curation.

Official documentation

Primary-source documentation — Sitecore’s own, plus the Google guidance that applies (Google has no Sitecore-specific docs).

Sitecore

• Search engine optimization (SEO) — XM Cloud / SitecoreAI — the documented SEO feature set: sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., language codes in sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. URLs, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't., image optimization. (This URL now 308-redirects to a .../sai/.../sitecoreai/... path — Sitecore’s docs have renamed the product SitecoreAI.)
• Configure the robots.txt file — SitecoreAI — the source of the default-block behavior; where the robots field lives and why you must republish.
• Configure a sitemap — SXA — Sitemap Mode (cache vs file), attributes, and the TargetHostName 404 gotcha.
• Standard values for data template fields — XM — the NULL-vs-blank inheritance model and tokenA token is the smallest unit of text (or image/audio/video) an LLM processes — roughly 4 characters, or about ¾ of an English word. A context window is the maximum number of tokens (input plus output) a model can hold at once, like its short-term memory. support.
• Environment, editing hosts and rendering hosts — SitecoreAI — the CM/editing-host/renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM.-host split: only the renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. host serves public (and crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index.) traffic.
• On-page SEO Optimization — Accelerate Cookbook (XM Cloud / SitecoreAI) — Sitecore’s own on-page checklist (H1sAn H1 tag is the HTML `<h1>` element that marks a page's primary heading — the big visible headline at the top of the content. It helps users, search engines, and screen readers understand what the page is about., alt textAlt text is the value of the `alt` attribute on an HTML `<img>` element — a short text substitute chosen for the image's purpose and context, not a literal description of what it shows. It makes images accessible to screen-reader users and helps search engines understand images, mainly for image search., redirects, mixed contentMixed content is when a page served over HTTPS loads a sub-resource — a script, stylesheet, image, iframe, or similar — over insecure HTTP. Browsers' current taxonomy is upgradable versus blockable; active mixed content (scripts, styles, iframes) is blocked, and passive mixed content (images, audio, video) is warned about or increasingly auto-upgraded, with exceptions like CORS-enabled images and srcset/picture candidates that are blockable, not upgradable.).
• Optimizing content for AI — Accelerate Cookbook (XM Cloud / SitecoreAI) — Sitecore’s GEOGenerative Engine Optimization (GEO) is the practice of optimizing content and brand presence so AI-powered search engines and assistants — Google AI Overviews, ChatGPT, Perplexity — cite, recommend, or mention you when generating answers. Google's position is that it's still SEO. guidance (SSR/SSG/ISR, component-based authoring, schema).

Google (general guidance that applies)

• JavaScript SEO basics — relevant to XM Cloud headless rendering.
• Crawling and Indexing — robots, sitemaps, canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it., crawl controls.

Quotes from the source

Verified, on-the-record statements from Sitecore’s docs and Sitecore-specialist practitioners.

Sitecore docs — the default-block behavior

• “If no rules are added, the system writes: ‘User-agentA user agent is the HTTP request header a client (browser, crawler, or bot) sends to identify itself. For crawlers, a short user-agent token — a substring of that string — is what robots.txt rules actually target.: * Disallow: /’” — Sitecore documentation, Configure the robots.txt file.
• “If the value of a field is NULL, the item contains the standard value for that field as defined in the data template for that item.” — Sitecore documentation, Standard values for data template fields. (And the catch: blank ≠ NULL.)

The baseline — “virtually no SEO functionality”

• “Sitecore ships with virtually no SEO functionality (with the exception of SXA which includes some basics).” — Marcel, Sitecore SEO Best Practices | Fishtank (Aug 2018).
• “out-of-the-box, Sitecore’s data templates might not include some of the Meta Data fields.” / “Use Sitecore’s canonical link management to specify the preferred version of a URL.” — Ken Gray, SEO Best Practices for Sitecore | Konabos (Jan 2024).

Aliases and duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling.

• “no redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. (no 301 or 302 HTTP status codeAn HTTP status code is the three-digit number a server returns with every response to tell a browser or crawler what happened to its request — success, redirect, client error, or server error. For SEO the code matters as much as the content: it tells Google and Bing whether to index a page, follow a redirect, retry later, or drop the URL from the index.) happens when you are using aliases in Sitecore” / “multiple URLs will be created for a single page URL.” — Dheer Rajpoot, Impact of Sitecore Aliases on SEO | BugDebugZone (Jul 2014).

Headless renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. (XM Cloud + Next.js)

• “SSG pre-renders HTML at build time, creating static files that can be served from a CDN.” / “Search engines can easily crawl the pre-rendered HTML.” / “Fully rendered HTML is ready for search engines to indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed..” / “Search engines may struggle with indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. JavaScript-rendered content.” — Akshay Sura, Master Rendering in Next.js with Sitecore XM Cloud | Konabos (Feb 2025).
• “All fetch calls within generateMetadata are memoized, meaning identical URLs are only fetched once across the application, preventing redundant requests.” / “metadata is one of those things we tend to leave to the bitter end.” — David Austin, Optimizing Metadata and SEO in Next.js for Sitecore XM Cloud | Fishtank (Oct 2023).
• “The dynamic approach is the better method for Sitecore Headless as you’ll be able to take what’s part of the page’s layout data and incorporate it.” — Sebastián Aliaga, Handling SEO in Sitecore XM Cloud Projects | DEV (Jun 2024).

Multilingual and schema

• “TBH hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is one of the most complex aspects of SEO (if not the most complex one).” — John Mueller, Google, cited by Jakub Koba, How to Customize Multilingual Features in Sitecore | kogifi (Jun 2025).
• “we typically use JavaScript to deploy Schema MarkupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. to Sitecore. This method is both efficient and scalable…” — Martha van Berkel, Implementing Schema Markup on Sitecore | Schema App.
• “Add schema markup to the page HTML to make your search results appear more attractive.” — Peter Lambrou, 10 SEO Tips for Your Sitecore Website | Codehouse (Dec 2022).

Enterprise context (my own)

• “Enterprise sites can have complex infrastructures and a lot of legacy systems in place.” / “I doubt there’s a major website that is technically perfect.” — me, Enterprise Sites Are Where Technical SEO Shines | Ahrefs.

Sitecore SEO launch & audit checklist

Run this before launch and on any inherited Sitecore site:

Crawl & indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. basics

• Production robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. is explicit (User-agent: * / Allow: /) — confirm the robots field is not blank (blank = blocks everyone) and the site is republished.
• CM, QA, and staging instances disallow all crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index..
• SitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. resolves at /sitemap.xml (SXA) or via MetadataRoute.Sitemap (Next.js); TargetHostName is configured so it doesn’t 404.
• SitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. lists only canonical, indexable URLs.

Metadata

• A base SEO template exists and every page template inherits it (title, description, OG fields).
• “Reset Blank” is enabled on metadata fields that should fall back to Standard Values.
• Validation rules enforce non-empty, length-bounded titles and descriptions.

URLs & duplicates

• Item aliases are either 301-redirected or carry a canonical override — no two HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. URLs for the same content.
• Canonical tagsA rel=\"canonical\" annotation — in the HTML <head> or an HTTP Link header — that tells search engines which URL is the preferred version of duplicate or near-duplicate content. are set, especially for content shared across multisite.
• URL consistency (www/non-www, trailing slashA trailing slash is the forward slash (/) at the end of a URL — example.com/page/ versus example.com/page. Except at the bare root domain, the two versions are different URLs to search engines, so you pick one format and enforce it., language prefix) enforced.

Multilingual

• HreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others. is implemented (bidirectional, absolute URLs, x-default).
• Language fallback isn’t silently duplicating content across language URLs.

Headless (XM Cloud) only

• SEO-critical content renders via SSG/ISR/SSR, not CSR.
• Metadata set via generateMetadata; JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. server-rendered (not client-only).
• No primary content (H1, FAQs, schema) hidden behind client-side personalization.

The Sitecore SEO governance framework

Sitecore SEOSitecore SEO is the set of technical, on-page, and governance practices applied to sites built on Sitecore — an enterprise Digital Experience Platform. Sitecore ships with very little SEO functionality by default; the work happens through SXA's SEO modules (on Sitecore XP) or the Next.js application layer (on XM Cloud headless), plus careful governance of templates, metadata inheritance, aliases, and robots.txt. scales when every page passes through the same five controls rather than relying on individual authors or one-off component fixes.

1. Base SEO template: every page template inherits the same title, description, canonical, social, and indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed. fields. A template without the base is a release defect, not an editorial exception.
2. Metadata validation: Standard Values supply fallbacks, Reset Blank handles cleared fields, and validation rules stop empty or invalid metadata before publish. Defaults and enforcement work together.
3. Alias governance: every alias either redirectsA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't. permanently to the canonical item or has an explicit canonical implementation. Two HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. URLs for one item are not an acceptable default.
4. Environment control: production explicitly allows crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor.; CM, QA, and staging explicitly disallow it. The live robots response is checked after every publish that touches the setting.
5. Crawl-surface curation: sitemapsA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. contain only canonical, indexable URLs, while language fallback, shared multisite content, facets, and parameters are reviewed as sources of expansion.

For XP, enforce these controls in templates, Standard Values, pipelines, and SXA. For XM Cloud, keep the same governance model but implement the output in the Next.js application through generateMetadata, MetadataRoute, server-rendered JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal., and the Experience Edge query layer.

Sitecore SEO cheat sheet

XP vs XM Cloud — where SEO is controlled

The three traps

Headless renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. modes — SEO ranking

• SSG → best (pre-rendered, CDN-served)
• ISR → great (static + background freshness)
• SSR → good (fully rendered per request)
• CSR → avoid for indexable content

Schema priority: FAQPage, HowTo, Product, Article, BreadcrumbList — server-rendered JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. (tag-manager injection may be missed by AI crawlersAI crawlers are bots from AI companies that fetch web pages to train language models, build AI-search indexes, or answer live user questions. They come in three categories, each with its own user-agent tokens and its own robots.txt controls.).

Common Sitecore SEO failures

The production site suddenly disappears behind a crawl block

Symptom: The live /robots.txt contains User-agent: * and Disallow: /, or crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. report a sitewide block.

Likely cause: The Sitecore robots field was left blank and published; blank is not permissive in this implementation.

Fix: Set an explicit production allow rule, republish the site, then fetch the live /robots.txt again. Confirm CM, QA, and staging remain disallowed separately.

An alias and the canonical item both appear as indexable pages

Symptom: Two URLs return HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. with the same content, and the alias does not redirectA redirect sends browsers and crawlers from a requested URL to a different one. An HTTP redirect specifically is a 3xx status code paired with a Location header; meta refresh and JavaScript redirects achieve a similar navigation without being a 3xx response themselves. Permanent redirects (301/308) are Google's signal the target should be canonical; temporary ones (302/303/307) aren't..

Likely cause: Sitecore’s item alias resolver serves the alternate path directly and does not add a canonical automatically.

Fix: Change the alias pipeline to return a 301 to the canonical item, or add a canonical override if the alias must remain accessible. Re-crawl both URLs: the preferred outcome is one 200 destination and one permanent redirectA 301 redirect is the HTTP status code for a permanent move: it tells browsers and search engines a URL has moved for good, and it's the strongest signal for consolidating a page's ranking signals onto the new URL. Google says permanent redirects don't cause a loss in PageRank..

Published pages have blank titles or descriptions

Symptom: Rendered metadata is empty even though Standard Values define a fallback.

Likely cause: An author cleared the field, creating a blank value rather than a NULL value; Standard Values do not replace it unless Reset Blank is enabled.

Fix: Enable Reset Blank where fallback is intended, add field validation, reset the affected items, and republish. Confirm the rendered source contains the fallback or the page’s intentional override.

The SXA sitemap returns 404

Symptom: /sitemap.xml does not resolve even though sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. mode is enabled.

Likely cause: TargetHostName is missing or the site definition points at the wrong host.

Fix: Configure the correct target hostname, clear the relevant cache if needed, and request /sitemap.xml on the production host again.

Prove a Sitecore robots.txt change is safe

Fetch the published production response

Test to run: After editing and republishing the robots field, request the live production /robots.txt directly.

Expected result: Production contains the intended explicit allow/disallow rules and does not fall back to a blanket Disallow: /.

Failure interpretation: The wrong item was edited, the change was not published, or the live site is serving cached or default content.

Monitoring window: Immediate after publish and cache refresh.

Rollback trigger: Restore the last known-good robots value immediately if the production response blocks all crawlersA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. or omits required protections.

Check environment separation

Test to run: Fetch /robots.txt on CM, QA, staging, and the production delivery host.

Expected result: CM, QA, and staging disallow crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor.; only the intended production host is crawlable.

Failure interpretation: The robots item, publish target, or host-specific site configuration is shared incorrectly across environments.

Monitoring window: Immediate after the change and after environment promotion.

Rollback trigger: Roll back if a non-production environment becomes crawlable or production inherits the non-production blanket block.

Confirm crawler-facing behavior

Test to run: Use Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version. on a representative production URL after the robots response is correct.

Expected result: The live test can fetch the page, and the rendered HTML contains the expected metadata and content.

Failure interpretation: Another crawl control, authentication layer, or cached robots response is still blocking Google.

Monitoring window: Run the live test immediately; allow normal recrawling time before judging report recovery.

Rollback trigger: Roll back related access-control changes if Google remains blocked while ordinary public requests appear open.

Tools for Sitecore SEO

Sitecore-side

• SXA (Sitecore Experience Accelerator) — the layer that provides sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. generation, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. management in the content tree, and standardized metadata fields. The default SEO toolkit for XP and XM Cloud.
• Sitecore Content Editor — field validation rules — enforce non-empty, length-bounded titles and descriptions so authors can’t ship blanks.
• Next.js MetadataRoute / generateMetadata (XM Cloud) — code-driven sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere., and per-page metadata pulled from Experience Edge via GraphQL.

Search-engine verification

• Google Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. — verify indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., inspect rendered HTML (URL InspectionA Google Search Console feature that reports how Google sees one specific URL on a property you own. By default it shows the last-indexed snapshot; a separate \"Test live URL\" mode fetches the current version.), submit sitemaps, watch the Page Indexing reportThe Google Search Console report (formerly Index Coverage) showing how many of your URLs are indexed vs. not indexed, and grouping the not-indexed ones by reason..
• Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. — separate verification and sitemap submission; matters more on headless because Bing lags on JS renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM..

Auditing & crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor.

• Ahrefs Site Audit and Screaming Frog SEO Spider — simulate a crawl to catch alias duplicates, empty metadata, redirect chainsA → B → C instead of A → C. Each hop loses link equity and adds latency., and blocked URLs at scale. Essential on a large Sitecore install.
• Google LighthouseLighthouse is Google's free, open-source tool that audits a page under simulated lab conditions and scores it 0–100 across Performance, Accessibility, Best Practices, and SEO. It's lab data — useful for debugging, not a ranking signal. — Sitecore’s own Accelerate Cookbook recommends it for page-speed and on-page checks.

Resources worth your time

My related writing

• Enterprise SEO — resource constraints, organizational complexity, and internal linkingAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. at scale — the world Sitecore lives in.
• Enterprise Sites Are Where Technical SEO Shines — legacy systems, multiple tech stacks, split ownership, and canonicalizationHow search engines pick one canonical URL among duplicates and consolidate signals onto it. at enterprise scale.

My speaking

• How Search Works (SlideShare) — crawlingCrawling is how search engines use automated bots (like Googlebot and Bingbot) to discover URLs and download pages. A page has to be crawlable to be indexed, but crawling on its own isn't a ranking factor., renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM., indexingStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed., and ranking; the renderingTurning HTML, CSS, and JavaScript into the final visual page and DOM. section is the part that matters most for headless Sitecore. (My standing disclaimer applies: “This is my understanding of systems… not going to be 100% complete or accurate.”)

From around the industry

• SEO Best Practices for Sitecore | Konabos (Ken Gray, Jan 2024) — structured best practices including metadata fields and canonical link management.
• Master Rendering in Next.js with Sitecore XM Cloud | Konabos (Akshay Sura, Feb 2025) — the definitive SSG/SSR/ISR/CSR breakdown for XM Cloud SEO.
• Optimizing Metadata and SEO in Next.js for Sitecore XM Cloud | Fishtank (David Austin, Oct 2023) — the generateMetadata pipeline in depth.
• Sitecore SEO Best Practices | Fishtank (Marcel, Aug 2018) — the “virtually no SEO functionality” baseline and a lifecycle approach.
• Impact of Sitecore Aliases on SEO | BugDebugZone (Dheer Rajpoot, Jul 2014) — the alias duplicate-content mechanics.
• How to Customize Multilingual Features in Sitecore | kogifi (Jakub Koba, Jun 2025) — language versions, fallback, and hreflangHreflang is an annotation (in HTML, HTTP headers, or XML sitemaps) that tells search engines which language and optional region a page targets, and which alternate versions exist. It only works when every page in the cluster references all the others..
• 10 SEO Tips for Your Sitecore Website | Codehouse (Peter Lambrou, Dec 2022) — practical tips including schema markupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor..

Test yourself: Sitecore SEO

Five quick questions on the Sitecore-specific SEO traps and platform differences. Pick an answer for each, then check.

Sitecore SEO

Sitecore SEO is the set of technical, on-page, and governance practices applied to sites built on Sitecore — an enterprise Digital Experience Platform. Sitecore ships with very little SEO functionality by default; the work happens through SXA's SEO modules (on Sitecore XP) or the Next.js application layer (on XM Cloud headless), plus careful governance of templates, metadata inheritance, aliases, and robots.txt.

Related: Canonicalization, Duplicate Content

Sitecore SEO

Sitecore SEO refers to optimizing websites built on Sitecore, an enterprise Digital Experience Platform (DXP) and CMSA content management system (CMS) is software that lets users create, manage, and publish digital content — like blog posts and pages — without writing raw code. WordPress, Drupal, and Joomla are the most common open-source CMS platforms. used mostly by large enterprises and Fortune 500 companies. Sitecore runs in two very different shapes for SEO: Sitecore XP (the traditional .NET Experience Platform, server-rendered, on-premise or managed cloud) and XM Cloud (the modern headless SaaS, where content is delivered via GraphQL to a Next.js front end built with Sitecore JSS). Which one you’re on changes where SEO is controlled — Sitecore templates and pipelines on XP, the Next.js metadataNext.js SEO is the set of practices and built-in features that make a Next.js site crawlable, indexable, and rankable — rendering mode (SSG/SSR/ISR/Server Components), the App Router Metadata API, sitemap.ts/robots.ts conventions, next/image, and next/link. layer on XM Cloud.

The defining reality is that Sitecore ships with virtually no SEO functionality out of the box. SXA (Sitecore Experience Accelerator) adds the basics — sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing. generation, robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. management in the content tree, and standardized metadata fields — but everything still needs configuration and governance. Without SXA, every metadata field, sitemapA sitemap is a file that lists the pages, images, videos, and other files on your site so search engines can discover them. It helps discovery, but submitting a sitemap doesn't guarantee crawling or indexing., and robots.txtA plain-text file at the root of a host that tells crawlers which URLs they may and may not request. It controls crawling, not indexing — a blocked URL can still be indexed if it's linked from elsewhere. rule must be custom-built.

Several Sitecore-specific traps catch enterprise teams. Its default robots.txt blocks every crawlerA crawler — also called a spider or bot — is an automated program that fetches web pages, extracts their links, and queues new URLs to visit. Search engines use crawlers to discover and download content for their index. if the Settings item’s robots field is left blank (User-agent: * / Disallow: / — empty does not mean permissive). Item aliases return HTTP 200HTTP 200 OK is the standard 2xx success status code, meaning the server received, understood, and fulfilled the request and is returning the resource. It's the code every page you want indexed should return — but a 200 alone doesn't guarantee Google will index the page. on both the original and the alias URL — true duplicate contentThe same or very similar primary content reachable at more than one URL. There's no general duplicate content penalty — the real costs are possible signal dilution, the wrong URL getting chosen, and less-efficient crawling. with no 301, which canonical handling won’t fix automatically. And blank metadata fields do not fall back to Standard Values unless “Reset Blank” is explicitly enabled, because in Sitecore’s field model blank is not the same as NULL — a common source of missing titles and descriptions across thousands of pages.

Related: Canonicalization, Duplicate Content

Changelog