Micro-Frontends & Module Federation: Unifying SSR Head & Schema Ownership
Independent team deployments inside micro-frontends frequently emit conflicting head tags or blank client shells unless unified at SSR.
Dmitry K., Technical SEO Lead · SEO Space
Indexation benchmark targets
- Head owner
- Single edge/shell SSR
- Duplicate <title>
- 0 allowed in DOM
Why Uncoordinated Micro-Frontends Break Crawling & Core Web Vitals
When checkout, catalog, and editorial squads ship separate Webpack Module Federation bundles rendered purely client-side inside an empty host shell, Googlebot receives blank containers or mismatched `<head>` overrides.
Multiple micro-apps independently mutating `document.title` or injecting duplicate `<script type="application/ld+json">` graphs trigger erratic SERP snippets and CLS.
- Assemble public SEO pages via edge SSR composition (or streaming SSR shell) before sending HTML to the wire.
- Assign `<title>`, meta robots, canonical, hreflang, and BreadcrumbList JSON-LD strictly to the outer composition contract.
- Enforce CSS min-height placeholders around lazy client-only sub-widgets to keep CLS below 0.05.
Typed SEO Metadata Contract Between Sub-Apps & Host Shell
Expose a standardized server-side `getSeoHead()` contract from each domain fragment consumed synchronously during host SSR.
Choose server/edge assembly for all organic entry templates while keeping client-only micro-apps inside authenticated portals.
| Pattern | Googlebot Initial HTML | CWV Risk |
|---|---|---|
| Edge SSR Fragment Assembly | 100% complete HTML & Schema | Lowest CLS & fastest LCP |
| Client Module Federation Shell | Empty mounts until JS runs | Severe render delay & CLS |
| Authenticated Dashboard MFE | Not indexed (noindex) | Isolated from public SEO |
export interface MicroAppSeoContract {
title: string;
description: string;
canonicalPath: string;
robots: 'index,follow' | 'noindex,follow';
jsonLd: Record<string, unknown>[];
} Need this indexation setup audited on your domain?
Send your website URL. We check raw HTML parity, log crawl hits, canonical discipline, and sitemap architecture manually within 24 hours.