Langues

Guide Umbraco SEO

How to faire an Umbraco site rank — ce que the .NET CMS handles out of the box (clean URLs, automatic 301s on rename, HTTPS), ce que nécessite a package (meta fields, XML sitemaps, robots.txt, balise canonicals, noindex), and ce que nécessite custom developer fonctionner (hreflang, données structurées). The package stack — SeoToolkit, SEO Checker by Soeteman Software, URL Tracker — and pourquoi uMarketingSuite (now Umbraco Engage) n’est pas an SEO outil.

Première publication : 27 juin 2026 · Dernière mise à jour : 3 août 2026 · Advanced
Langues
AIRédigé parAI v2

Umbraco is a .NET-based open-source CMS, and its defining SEO trait is que it's developer-led by par défaut: unlike WordPress, où a non-developer installs a plugin, almost every meaningful SEO fonctionnalité in Umbraco nécessite a .NET developer or a package. Think of it in three tiers. Built-in: clean URLs from node noms, automatic 301 redirections quand vous rename a node's URL, HTTPS enforcement, basic 404 handling. Nécessite a package: meta fields, XML sitemaps, robots.txt editing, noindex contrôle, balise canonicals — via SeoToolkit (free, open-source, by patrickdemooij9) or SEO Checker (commercial, by Soeteman Software — pas Jumoo, who faire uSync). Nécessite custom dev: hreflang pour Language Variants, données structurées, avancé canonical logic. uMarketingSuite rebranded to Umbraco Engage in November 2024 and is a CRO/personalization platform, pas a SEO technique outil. As of mid-2026, Umbraco 17 (released November 2025) is the current LTS; Umbraco 13, the previous LTS, is in its Security phase and reaches fin of life in December 2026 — plan an upgrade chemin avant alors. The smart play is building self-serve SEO contrôle into the backoffice avant an SEO team ever touches le site.

TL;DR — Umbraco is a .NET open-source CMS, and its SEO story is developer-led by par défaut. Three tiers: built-in (clean URLs from node noms, automatic 301 on URL rename, HTTPS, 404s, Language Variants); nécessite a package (meta fields, XML sitemap, robots.txt, noindex, canonicals — via SeoToolkit (free) or SEO Checker by Soeteman Software (paid)); nécessite custom dev (hreflang, structured données, avancé canonical logic). SEO Checker is by Soeteman Software, pas Jumoo (who faire uSync). uMarketingSuite became Umbraco Engage in Nov 2024 and is a CRO outil, pas SEO. Umbraco 17 (Nov 2025) is the current LTS; 13, the prior LTS, is in its Security phase and hits fin of life in Dec 2026. The réel craft is building self-serve SEO contrôle into the backoffice avant an SEO team arrives.

Evidence for this claim The article's described umbraco-seo capabilities must be evaluated against the platform's current documentation rather than assumed to be search-engine behavior. Scope: Platform-specific capability documentation. Confidence: high · Verified: Umbraco CMS documentation Evidence for this claim Regardless of platform, Google needs crawlable URLs, accessible rendered content, descriptive metadata, and valid search directives. Scope: Google requirements independent of platform. Confidence: high · Verified: Google Search Central: SEO Starter Guide

Ce que Umbraco is (the 30-second version)

Umbraco is an open-source CMS construit on ASP.NET Core. Vous model content with Document Types (typed content templates), arrange pages in a content tree, and render les with Razor templates. It comes two façons: Umbraco Cloud (managed hosting on Azure with Cloudflare at the edge — automatic TLS, firewalls, point-in-time restore) and self-hosted (votre propre server, complet contrôler). Les deux run the même CMS; the difference is who manages the infrastructure.

The unique la plupart important framing pour le SEO: la plupart SEO configuration in Umbraco exige a .NET developer. Ce is the structural difference from WordPress, où a non-developer peut install a plugin and self-serve. On Umbraco, même basic meta fields are a developer task unless a package has déjà ajouté les.

The three tiers of Umbraco SEO

I trouver it cleanest to sort every SEO fonctionnalité into un of three buckets.

Tier 1 — construit in. Clean URL generation from node noms (an automatic ToUrlSegment() transform produces lowercase, hyphenated slugs), automatic 301 redirections quand a node’s URL changements on rename, HTTPS enforcement, proper 404 code d’états, and Language Variants (the multilingual content model).

Tier 2 — nécessite a package. Meta title/description fields, XML sitemaps, robots.txt editing, noindex contrôle, and balise canonicals. Ces tout come pre-built in SeoToolkit (free) or SEO Checker (paid).

Tier 3 — nécessite custom dev. hreflang pour Language Variants, données structurées, and avancé canonical logic. Même with a package, ces souvent besoin template code or careful per-culture configuration.

The auto-301 on rename — Umbraco’s quiet win

Ce is the built-in fonctionnalité la plupart guides miss, and it’s genuinely bon. Umbraco’s official URL tracking docs put it plainly: “Whenever a document is publié and causes changements to its URL (and quelconque of its descendants’ URLs), Umbraco rend a remarque of the old URLs. Whenever an incoming requête is served and the par défaut content finders ne peut pas trouver a matching publié document, Umbraco checks si l’URL matches un of ces enregistré URLs. Si a match is trouvé, Umbraco renvoie a 301 Redirection réponse pointing to the nouveau URL of the document.”

En pratique: rename une page, modifier its slug, and the old URL garde working with a 301 automatically. Aucun plugin (WordPress nécessite Yoast Premium or Redirection pour the equivalent), aucun developer ticket. Ce alone empêche a lot of the broken-link and lost-equity damage que routine content editing causes elsewhere. Don’t over-read it, though: ce is publication-triggered tracking of a document’s propre URL changements — it ne fait pas cover arbitrary rewrite rules, or the plus complex culture-and-hostname changements vous hit during a migration. Nom votre hosting or middleware couche pour ceux, pas Umbraco core.

Worth knowing alongside it: Umbraco has several reserved routing property aliases, and they’re facile to mix up parce que leur noms sound similaire but leur behavior isn’t interchangeable. umbracoUrlName changements l’URL chemin suffix a node generates — définir a valeur and it overrides the auto-generated slug, pendant que the backoffice node nom stays whatever vous comme. umbracoUrlAlias is différent à nouveau: a comma-separated liste of alternate complet paths que resolve to the même node, masking the réel URL in le navigateur’s adresse bar plutôt que redirecting to it. umbracoRedirect sends a 302 (temporary) redirection to un autre node, picked via a content picker property — it’s a visible redirection, pas silent. umbracoInternalRedirectId is the un que fait the silent internal rewrite: the target page’s content is served transparently, with aucun redirection visible to le navigateur. Treat ces four as distinct outils, pas variations on un “redirect” concept, and confirmer réel behavior in votre propre version’s docs avant wiring un into a migration. Pour avancé contrôler, a developer peut aussi implement IUrlSegmentProvider to pull slugs from a dedicated field au lieu de the node nom. Un plus gap: trailing-slash and www/non-www consistency n’est pas handled natively — it nécessite ASP.NET Core middleware or IIS rewrite rules.

Metadata — the developer workflow

Parce que Umbraco ships aucun meta fields, the standard pattern is:

  1. Ajouter a “SEO” tab/groupe to votre Document Types — or, meilleur, a composition vous pouvez reuse à travers types.

  2. Ajouter properties: metaTitle, metaDescription, a noIndex toggle, optional canonicalUrl, and Ouvrir Graph fields (ogTitle, ogDescription, ogImage).

  3. Render les in the master template with Razor:

    <title>@Model.Value("metaTitle")</title>
<meta name="description" content="@Model.Value("metaDescription")" />
<link rel="canonical" href="@Model.Url(mode: UrlMode.Absolute)" />

  4. Add fallback logic so an empty metaTitle defaults to the node name.

Or install a package que adds ce composition pour vous. That’s the whole choice in Umbraco SEO, over and over: construire it, or install a package que construit it.

Un chose worth internalizing ici: a Document Type seulement defines ce que fields exist — a field having a valeur in the backoffice proves nothing à propos de ce que ends up in the deployed HTML. Output is owned by the template. Umbraco’s current templating supports master-template inheritance with named sections, so a child template peut placer its metaTitle/metaDescription/canonical markup into the master’s <head> — but que signifie every template que inherits from the master (and every fallback chemin quand a section is left vide) nécessite to be vérifié individually. Don’t assume un Document Type’s rendering behavior generalizes to every page type on le site; vérifier the rendered HTML per template.

The package stack (and un to pas confuse)

SeoToolkit (by patrickdemooij9) — free, open-source, on NuGet. Ships a dedicated package release aligned to chaque Umbraco major (currently up via Umbraco 18, released mid-2026); it’s actively maintained, but confirmer votre Umbraco version maps to the correct package version avant installing. Meta-field management, dynamic sitemap generation (per-domain sitemaps plus a sitemap index), a backoffice robots.txt editor with validation, script manager, redirection management, and canonical prise en charge. Le sitemap automatically adds itself to robots.txt. Ce is the par défaut starting point pour la plupart builds. From its README: “SeoToolkit creates a /sitemap.xml pour chaque domain and aussi a sitemap index with tout votre sitemaps listed dans. Tout sitemaps generated have a valid syntax, so Google va have aucun problem with indexation it.”

SEO Checker (by Soeteman Software) — commercial (free trial on localhost; license pour production). Aussi tracks Umbraco’s major-version cadence with its propre releases (v18.0,1 was current as of mid-2026, supporting Umbraco 18+) — vérifier the release notes pour the version que matches votre CMS. Adds SERP snippet previews and social previews in the backoffice pendant que editing, automated problème detection (manquant meta tags, broken liens, canonical problèmes), redirection management, automatic robots.txt and sitemap.xml, and — importantly — multilingual prise en charge que renders per-culture metadata notamment hreflang tags. Critical attribution remarque: SEO Checker is made by Soeteman Software, pas Jumoo. Jumoo rend uSync (a content deployment/sync outil), qui is a différent chose entirely. Ce mix-up is courant; don’t repeat it.

URL Tracker — a redirect-management package (404/302 monitoring, redirection creation, recommendations fondé on similaire URLs, query-string matching). Worth installing from day un pour migrations and restructures, so an SEO team peut manage redirections sans developer tickets.

uMarketingSuite → Umbraco Engage — Umbraco acquired uMarketingSuite and rebranded it Umbraco Engage in November 2024. It’s a CRO/personalization platform: server-side first-party analytics, A/B testing, persona targeting, visitor profiling. It n’est pas a SEO technique package — it won’t manage meta tags, sitemaps, robots.txt, or schema. It complements SEO (engagement signals, testing variants); it doesn’t replace SeoToolkit or SEO Checker. Don’t recommend it as votre SEO package.

Multilingual SEO — Language Variants and hreflang

Language Variants are a réel Umbraco strength. Vous define languages by ISO code in Settings → Languages, assign chaque language to un or plus hostnames (so vous pouvez do /en/, /de/, or separate domains), and editors translate content dans the même node by switching language tabs. Chaque variant peut have its propre URL slug (/about-us in English, /acerca-de in Spanish), and fallback rules prevent blank pages quand a translation is manquant.

But the SEO catch: hreflang n’est pas automatic. Language Variants manage the content; ils don’t emit hreflang tags. Vous implement ceux in Razor by iterating over cultures:

@foreach (var lang in Umbraco.LocalizationService.GetAllLanguages())
{
    <link rel="alternate" hreflang="@lang.IsoCode"
          href="@Model.Url(culture: lang.IsoCode, mode: UrlMode.Absolute)" />
}
<link rel="alternate" hreflang="x-default"
      href="@Model.Url(culture: defaultCulture, mode: UrlMode.Absolute)" />

— or utiliser SEO Checker, qui renders per-culture metadata notamment hreflang. Pair ce with self-referencing canonicals per language variant so the variants don’t fight chaque autre pour indexation. (How Google en réalité picks among variants is in Canonicalization.)

Données structurées

Umbraco officially documents three façons to implement schema, tout needing a developer:

  1. Field-based — ajouter a text-area property où editors paste JSON-LD; render it in <head>.
  2. Template-driven with editor input — the developer builds schema selectors in the backoffice; editors fill fields; the template generates JSON-LD from les.
  3. Automatic — schema is generated in the template from document properties, aucun editor input (meilleur pour blog posts and autre templated types).

Pour .NET developers, the Schema.NET library (a NuGet package, pas an Umbraco package) donne strongly-typed C# classes pour Schema.org types, so vous construire JSON-LD from objects au lieu de concatenating strings, alors render with ToHtmlEscapedString(). JSON-LD is Google’s preferred format; validate with the Résultats enrichis Tester. Ce is où Umbraco’s typed Document Types en réalité become an advantage — it’s easier to generate accurate, consistent schema from modeled fields que from WordPress’s freeform editor content.

Performances and Core Web Vitals

The .NET baseline is lean: the Kestrel web server is fast, and Umbraco doesn’t carry the plugin overhead a heavy WordPress install accumulates. Umbraco Cloud adds Cloudflare edge mise en cache and Azure infrastructure pour free; self-hosted (souvent Windows/IIS) nécessite plus manual performances fonctionner. Pour Core Web Vitals: utiliser Umbraco’s built-in Image Cropper (it peut output dimensions, qui helps CLS) plus the Slimsy package pour responsive WebP/AVIF with lazy chargement; reserve space pour media to éviter layout shift; and remember CSS/JS bundling/minification is pas construit in — utiliser .NET bundling middleware or a front-end construire step.

Version landscape: LTS, STS, and the 13→14 backoffice rewrite

Umbraco ships on a fixed cadence with two release tracks: LTS (Long-Term Prise en charge, 18 months of active prise en charge) and STS (Standard-Term Prise en charge, roughly 3 months). As of mid-2026, Umbraco 17 (released November 2025, on .NET 10 LTS) is the current LTS. Umbraco 13 — the LTS la plupart enterprise sites are encore running — is past its Prise en charge phase and now in Security-only patching, reaching fin of life in December 2026. Si you’re encore on 13, that’s votre upgrade deadline, pas a someday item. Umbraco aussi runs shorter STS releases entre LTS majors (16 and 18 shipped in 2025 and mid-2026 respectively) pour teams que track the latest fonctionnalités plutôt que the prise en charge window.

The version-history detail que encore matters pour le SEO tooling: Umbraco 14 introduced a rebuilt backoffice — déplacé from the old AngularJS UI to TypeScript/Web Components (Lit). Que rewrite meant SEO packages had to be mis à jour to render leur UIs correctement, qui is pourquoi package compatibility is tied to spécifique Umbraco majors plutôt que a blanket “v8+” claim. Vérifier the package’s propre release notes contre votre Umbraco version avant quelconque upgrade — don’t assume dernier year’s compatibility remarque encore holds.

Un plus wrinkle: Umbraco 12+ ships a Content Delivery API, enabling headless/decoupled builds. Que changements the SEO calculus — metadata and schema doit be injected by the front-end framework (with the usual SSR-vs-CSR rendering concerns), pas by Razor templates. (Background: JavaScript SEO.)

The réel craft: faire le site SEO-agency-friendly

The recurring pain point on Umbraco isn’t capability — it’s the constant stream of developer tickets from SEO teams who can’t self-serve. Tim Payne put the fix bien in Skrift Magazine: “Fonctionner smart, and modify votre back office so que the SEO guys peut do la plupart of the fonctionner themselves.” Concretely, construire ce avant handoff:

  • A global SEO settings node with fields pour HEAD scripts and CORPS commencer/fin scripts (kills the endless GTM-snippet requêtes).
  • An SEO tab on every page Document Type — meta title, description, canonical, noindex/nofollow — so editors self-serve.
  • URL Tracker installed from day un pour redirection management.
  • An XML sitemap auto-generated from day un.
  • robots.txt served from day un, referencing le sitemap.

Do que and Umbraco goes from “developer bottleneck” to a perfectly capable SEO platform. Skip it and you’ll feel the friction every week.

Umbraco vs WordPress, briefly

Umbraco’s structured Document Types give content built-in context, qui rend systematic schema and metadata consistency easier at scale — as the 24 Days in Umbraco community put it, “WordPress n’est pas great at SEO out of the box; la plupart of le contenu n’est pas semantic or modeled. Umbraco’s structured document types provide built-in context.” The trade-off is ease of utiliser: WordPress + Yoast lets a non-technical utilisateur manage la plupart SEO alone, où Umbraco nécessite a developer pour même simple changements. Pour grand, multilingual, heavily-modeled enterprise sites, Umbraco’s structure souvent wins; pour a petit team que veut to self-serve, WordPress is gentler.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.