Quick answer: A microsite is a small website with its own URL and usually a narrow purpose: a campaign, product line, event or partner offer. Build one when the story, design or audience truly does not fit your main site, and you can maintain it. Prefer a strong landing page on the primary domain when you only need a focused layout for ads. Microsites add hosting, SEO and governance cost; use them deliberately.
Microsite vs landing page vs subdomain
People mix terms.
- Landing page: A focused page, often on your main domain (
example.com/campaign/), built to convert ad or email traffic. See landing page optimization and landing page vs homepage. - Subdomain:
campaign.example.commay still feel like part of the brand but is technically a separate site property for many SEO purposes. - Microsite: Often a distinct domain or subdomain with its own navigation and content set, sometimes a temporary campaign home.
If your goal is paid traffic conversion, a landing page on the main domain is usually enough. If your goal is a standalone brand experience, partnership co-brand or a product that must not share main-site chrome, a microsite can be justified.
Good reasons to build a microsite
- Separate brand or product that would confuse main-site navigation
- Partner or co-marketing where shared URL politics matter
- Event or film-style experience with heavy creative that would bloat the main CMS templates
- Regulatory or regional needs that demand isolated content and hosting
- Acquisition brand kept distinct until a planned merge
Also consider one page website patterns when the story is short and self-contained.
Weak reasons (prefer main site)
- “The agency wants a new playground”
- Slightly different visual style for one ad campaign
- Avoiding CMS limits you could fix with a better template
- Chasing a keyword on a throwaway domain without a maintenance plan
- Splitting authority across domains without linking strategy
Thin campaign domains that die after six weeks often waste SEO equity and create redirect debt.
SEO implications
Google treats domains and many subdomain setups as separate strengths. A new microsite starts with little authority. You will need content quality, links and time if organic search matters. Paid traffic microsites can ignore organic for a while, but unpaid discovery will lag the main site.
If the microsite must rank, plan:
- Clear unique content (not a duplicate of the main site)
- Sensible internal links from the main site where relevant
- Search Console property and analytics from day one
- A retirement redirect plan to the main domain
Canonical tags and duplicate offers across main site and microsite confuse crawlers. Pick a primary URL for each piece of content.
Design and tech choices
Microsites are a chance to go light: static hosting, a minimal CMS or a focused WordPress install. Avoid copying the entire plugin stack from the corporate site “just in case.” Fast load matters for campaigns; see speed habits in website speed test thinking.
Governance questions:
- Who renews the domain?
- Who holds hosting credentials? (See website development cost planning and clear handoff habits when agencies are involved.)
- Who updates SSL and dependencies?
- When does content freeze?
Brand and UX consistency
Even separate sites should feel related: logo usage, colour hints, privacy policy links and cookie notices. Users who hop from ad to microsite to main site should not feel tricked. Include an obvious path to the main corporate site when trust matters (checkout, healthcare, finance).
Measurement
Give each microsite its own analytics view (or clear filters) and UTM discipline. Compare cost per lead against landing pages on the main domain. If the microsite never beats a simpler page, do not repeat the pattern.
Call tracking and form goals should be configured before launch, not a week after spend starts.
Retirement and redirects
Every microsite needs an end-of-life plan:
- Date or metric that triggers retirement
- 301 map to the best main-site URLs
- Update ads and QR codes
- Cancel unused tooling
- Archive creative for legal/records
Leaving live abandoned microsites with old offers and unpatched CMS installs is a security and reputation risk.
Alternatives that often win
- Landing page templates in the main CMS
- Subfolders with campaign templates
- Personalised sections on existing product pages
- PDF or video content distributed from the main domain
These keep authority consolidated and reduce orphan tech.
Budgeting honestly
Cost a microsite like a small product: discovery, design, build, QA, hosting, analytics, ongoing content and takedown. Compare that total to building two landing page templates on the main site. Many “cheap microsites” grow expensive when legal asks for updates on five forgotten domains.
Include creative production (video, illustration) in the same budget so launch day is not blocked on assets.
Team ownership models
Name a product owner for the microsite with authority to retire it. Agencies can build, but an internal owner must decide when the story ends. Without that, zombie sites linger past the campaign and past plugin security updates.
Accessibility and legal pages
Campaign teams sometimes forget accessibility, cookie notices and privacy links on microsites. Those obligations still apply. Reuse approved legal pages via links to the main domain when possible so counsel updates one place.
Content ops
Who publishes updates when pricing changes mid-campaign? If the answer is “email the developer,” you will ship wrong prices. Prefer a CMS role for marketers with guardrails, or freeze prices in creative and push changes only through a ticketed process.
Extra practical notes
Take a day to write down your current process before changing tools or structures. The written process reveals which steps are real and which are habit. Share the draft with the people who do the work daily; they will correct assumptions faster than any vendor demo.
After you ship a change, schedule a two-week check: did the metric you cared about move, and did any new failure mode appear? Keep a short changelog so future you knows what was attempted.
Hosting isolation vs convenience
Some teams host microsites on the same account as the main site for billing simplicity. That is fine if access controls still limit who can edit production. Others isolate campaign sites so a plugin experiment cannot take down corporate pages. Isolation costs more operational overhead; shared hosting costs more blast-radius risk. Pick deliberately and write it down.
DNS TTLs should be lowered before launch and before retirement so cutovers and redirects propagate quickly.
FAQ
Is a subdomain always better than a new domain?
Often yes for brand recognition, but SEO separation can still apply. A subfolder is usually strongest for organic continuity.
How long should a campaign microsite live?
As long as the campaign plus a redirect period. Decide the date when you launch.
Can microsites share a CMS?
Yes. Multisite or multiple installs under one host can work. Keep permissions tight.
Do microsites help SEO by targeting extra keywords?
Rarely better than investing in the main site. Extra domains dilute effort more often than they multiply reach.
Split only when the story needs it
A microsite is a tool, not a status symbol. Use it when focus and separation are real requirements, and prefer landing pages on your primary site for ordinary campaigns. If you want campaign sites built cleanly with a plan for what happens next, see our Turn visitors into customers service.
