Usually they hurt, though not fatally. A microsite on its own domain splits your entity across two places, so authority accumulates in one and your main site gets none of it. They remain justified for campaigns and paid traffic, but the cost is real and most firms never count it.
The short version
- A separate domain is a separate entity unless you explicitly connect them.
- Authority earned by the microsite mostly does not benefit the main brand.
- Your best thought leadership often ends up on the domain with the least authority.
- Subfolder beats subdomain, and subdomain beats a separate domain.
- Campaign and paid-traffic microsites can still be the right call. Count the cost knowingly.
Why the split costs more than expected
The usual reason for a microsite is sound: the main site is slow to change, a campaign needs flexibility, and standing something up separately is faster than negotiating with the CMS. Nobody decides to fragment their entity. It happens as a by-product of moving quickly.
But AI citation is built on accumulated, corroborated authority attached to an identifiable entity, and a separate domain starts that accumulation from zero. Links earned by the microsite point at the microsite. Citations it earns name the microsite. None of it lifts the main brand unless you deliberately connect them, and most firms never do.
The version that hurts most is the common one: over time, the microsite becomes where the newest and best thought leadership lives, because it is easier to publish there. Your strongest content ends up on your weakest domain, and the main site, which is where buyers eventually land, looks thinner than the organisation actually is.
There is a second, subtler cost. If both properties describe the organisation slightly differently, you have introduced exactly the inconsistency that makes a model hedge about who you are.
When a microsite is still right
- Paid campaign landing pages, where flexibility and speed genuinely matter and organic performance is not the goal.
- Genuinely separate propositions that are not the same entity in any meaningful sense.
- Time-boxed campaigns with a defined end.
- Cases where the main CMS makes the work impossible rather than merely inconvenient. Be honest about which one applies.
The test: is this content you want associated with your brand’s authority? If yes, it belongs on the main domain. If it is a campaign mechanic, a microsite is fine.
How to check it yourself
- Ask an assistant about your organisation and see whether it mentions the microsite, the main site, or treats them as unrelated.
- Compare inbound links to each property. If the microsite is winning, your authority is accumulating in the wrong place.
- Check organic traffic to the microsite. Very little, despite good content, usually confirms the split.
- Compare the descriptions of your organisation on both. Differences are entity noise.
- Ask where your best recent content sits. The answer is often uncomfortable.
What to do about it
- Prefer a subfolder.
/insights/on the main domain beats a subdomain, which beats a separate domain, by a wide margin for authority consolidation. - Migrate high-value microsite content back to the main domain with redirects, where the microsite has become a content home rather than a campaign.
- Connect them explicitly where migration is not possible: consistent organisation details on
both, mutual links, and
sameAsmarkup tying both to one entity. - Keep descriptions identical across both properties.
- Set an end date for campaign microsites at the point you create them, so they do not quietly become permanent content homes.