How to Create a Microsite in Umbraco

The cleanest way to create a microsite in Umbraco is usually to treat it as a small, governed website inside the same CMS architecture. You create a new root node, assign a domain or subdomain, reuse approved document types and templates, control who can edit it, add forms and tracking, then plan what happens after the campaign, event, or product launch ends.

This approach is different from spinning up a disposable website. A microsite may be small, but it still needs SEO, accessibility, privacy, redirects, analytics, brand control, content ownership, and a support plan. If it will live for only a few months, those controls matter even more because the team will be tempted to skip them.

Umbraco's official multisite tutorial says multiple sites can be hosted from one Umbraco project or installation by creating multiple root nodes, with each root acting as a separate website. It also notes tradeoffs: shared-project multisite can increase resource usage, affect editor workflows, and limit schema-change flexibility. On Umbraco Cloud, the documentation recommends Baselines for multisite solutions where stability and separation matter.

Step 1: Choose the Microsite Architecture

Start by deciding whether the microsite should be a section of the main site, a separate root inside the existing Umbraco project, or a separate Umbraco Cloud project based on a Baseline.

For most campaign or event microsites, a new root node is the practical default. Use a separate project when the microsite is not just a small campaign but a different product, region, client, brand, or operational model.

Step 2: Define the Content Model

Umbraco content starts with document types. The documentation describes document types as the blueprint for content: they define what can be created, what fields editors see, which editors are used, and where content is allowed in the tree. For a microsite, that means you should model only the pages and reusable pieces the campaign genuinely needs.

A lean microsite model often includes:

• Microsite Home: the root document type with SEO, campaign settings, navigation, global calls to action, tracking options, and footer content.
• Landing Page: a flexible page for campaign sections, hero content, forms, social proof, FAQs, and conversion blocks.
• Content Page: a simpler page for terms, event details, speaker profiles, product information, or campaign articles.
• Reusable Blocks: element types or block-list items for hero sections, feature grids, testimonials, FAQs, pricing notes, downloads, and CTAs.
• Shared Compositions: SEO fields, open graph image, canonical controls, noindex toggle, analytics IDs, and accessibility metadata.

Do not create a new document type for every visual variation. If your main Umbraco site already has a strong block model, reuse it. New document types should represent new content responsibilities, not one-off design requests.

Step 3: Create the Microsite Root Node

In the Settings section, make sure the chosen home document type is allowed at root. Then go to the Content section, create a new root node for the microsite, and name it clearly, such as 2026 Product Launch, Partner Portal, or Conference Microsite. This root becomes the homepage for the microsite.

Populate the root with launch-critical fields first: page title, meta description, hero message, primary CTA, footer links, privacy link, contact route, campaign owner, and expiry date. Then create child pages underneath the root using the allowed document types.

Step 4: Map the Domain or Subdomain

Umbraco's multisite tutorial maps hostnames to individual root nodes through Culture and Hostnames. In the Content section, use the menu next to the microsite root node, select Culture and Hostnames, add the domain, select the language, and save. Repeat for each domain or language variant as needed.

On Umbraco Cloud, hostnames also need to be added to the project in the Cloud portal before they are mapped to individual websites. The Cloud documentation says this helps ensure the hostname is secured with TLS. For a microsite, confirm DNS, TLS, www and non-www handling, and whether the default umbraco.io URL should be hidden or redirected.

Step 5: Wire Templates and Navigation

Umbraco renders content through templates. The basic website tutorial shows the relationship between document types, templates, and content nodes. For a microsite, create or reuse Razor templates that can render the chosen document types, then keep navigation scoped to the microsite root.

The main implementation detail is context. Header navigation, footer links, breadcrumbs, sitemap logic, search, and related content should not accidentally pull in the main website unless that is intentional. Use the microsite root as the boundary for menus and internal links.

Step 6: Add Forms and Integrations

Most microsites need a conversion action: enquiry, registration, download, quote request, waitlist, newsletter, or contact. Umbraco Forms can be used to build forms and control what happens after submission through workflows. If the form should create a CRM lead, send a notification, post to an external system, or show a confirmation page, define that workflow before launch.

Do not leave form handling as an afterthought. Test validation, spam protection, consent text, notification emails, CRM fields, campaign source values, thank-you pages, and analytics events. If the microsite has a hard campaign end date, decide whether the form should close automatically or route to a different page after launch.

Step 7: Set Users, Permissions, and Workflow

Umbraco user groups control what editors can access and do in the backoffice. The users documentation describes default groups such as Administrators, Editors, Writers, Translators, and Sensitive Data, plus granular permissions for specific content nodes and document properties. For a microsite, create a permission model that gives campaign editors access to the microsite content and media they need, without exposing unrelated website areas.

A useful setup is: developers own document types and templates; campaign editors own page content; legal or brand reviewers approve sensitive copy; administrators manage hostnames, forms, and publish rights. If the microsite needs formal approval, consider Umbraco Workflow rather than relying only on informal review.

Step 8: Prepare Launch, Redirects, and SEO

Before publishing, crawl the staging version or preview routes, check page titles, meta descriptions, canonical URLs, noindex rules, forms, analytics, internal links, accessibility basics, and mobile layout. Umbraco supports scheduled publishing and unpublishing on content documents, which is useful for campaign launches and end dates.

Redirects matter if the microsite replaces an old campaign URL, moves content from another location, or uses temporary launch paths. Umbraco's URL Redirect Management automatically tracks URLs when published content is moved or renamed and can return 301 redirects from old URLs to new ones. Google Search Central recommends preparing URL mappings, using server-side permanent redirects where possible, avoiding irrelevant redirects, checking canonicals and robots rules after launch, and updating sitemaps.

Step 9: Monitor and Sunset the Microsite

After launch, monitor form submissions, conversion events, search indexing, page speed, 404s, CRM attribution, and content questions from sales or support teams. When the microsite is no longer active, do not simply delete it. Export leads, capture performance reporting, unpublish or archive the content, redirect valuable URLs, remove stale campaign CTAs, and document the final owner.

Sources Checked

• Umbraco Documentation: Multisite Setup
• Umbraco Documentation: Creating a Basic Website
• Umbraco Documentation: Creating websites with Umbraco
• Umbraco Documentation: Defining Content
• Umbraco Documentation: Document Blueprints
• Umbraco Documentation: Users
• Umbraco Documentation: Scheduled Publishing
• Umbraco Cloud Documentation: Manage Hostnames
• Umbraco Documentation: URL Redirect Management
• Umbraco Forms Documentation
• Google Search Central: Site moves and migrations

Common Mistakes to Avoid

Recommended Default Setup

For a typical Umbraco campaign microsite, the sensible default is a new root node inside the existing Umbraco project, a shared layout with microsite-specific navigation, reusable block-based landing pages, a mapped subdomain, a dedicated media folder, a campaign editor user group, Umbraco Forms for enquiry capture, scheduled launch, and a redirect plan for expiry.

Move to a separate Cloud Baseline or project when the microsite needs independent release timing, a different code path, agency ownership, heavier traffic, separate compliance controls, or a brand model that should not share the main website schema.