Microsite vs. Translating Your WordPress Site: When to Build a Separate Campaign Site

Start with the decision trigger

The decision trigger is simple: does this campaign need its own home, or can it live inside the home you already have?

A microsite is a separate website, usually on its own domain or subdomain, built for one campaign. Translating the main WordPress site creates language versions of pages you already own. Both can reach a multilingual audience. They do it in different places, with different costs and different long-term effects.

The real question is not Can we translate? It is Should the campaign live on its own site or inside our existing site?

Choose a microsite if the campaign has a different name, offer, audience, or visual identity from your main brand, or if you need technical isolation. Choose on-site translation if you need speed, existing SEO authority, and minimal maintenance. Conditional recommendation: for a short promotion, translate the main site. For a standalone brand or a long-term market test, build the microsite.

When a microsite is the better choice

Choose a microsite when the campaign needs to feel separate, not just sound different in another language.

• You need a distinct brand experience. A music festival, a new product line, a co-branded partnership, or a one-off event often needs its own visual identity. A translated page on the main site still looks like your main brand.
• You want a separate domain for search or ads. A microsite gives you a fresh domain you can use for specific campaign keywords or paid traffic without changing the main site. Remember that a new domain starts with zero authority; you have to build trust from scratch.
• Your main site cannot support the language stack you need. Some WordPress setups have custom themes, plugins, or forms that break when a translation layer is added. If you cannot fix that quickly, a separate site may be more reliable.
• The campaign has a fixed end date. A microsite can be archived or deleted when the campaign ends, leaving the main site untouched.

When translating the main WordPress site is better

Translate the main site when speed, budget, and existing SEO authority matter more than a separate brand world.

• You need to launch fast. There is no domain setup, no new hosting, and no new theme to build. You turn on translation for the pages you already have.
• You want the campaign to inherit your existing SEO. Translated pages live on your current domain, so they can use your site’s authority and internal links. Add hreflang tags so search engines understand which language version to show.
• You want one place to maintain. One WordPress install means one set of plugins, one content team, and one analytics view. A microsite adds a second property to update, secure, and back up.
• The campaign is temporary and small. If it is a promotion running for a few weeks, you do not need a whole new site. You need translated versions of a few landing pages.

Tools like SEATEXT fit this route well. They translate WordPress pages automatically and keep new posts and products translated in the background.

A readiness checklist before you choose

Work through these questions before you commit to either option.

• Does the campaign have its own name and visual identity? If yes, a microsite may be worth it. If it is just a promotion, translate on the main site.
• How long will the campaign run? More than a few months? A microsite can become a permanent orphan. Less than a month? Translation is usually enough.
• Which languages do you actually need? If it is one or two, translation is simple. If it is many, check that your main site can handle them all without slowing down.
• Who will update the campaign content? If it is the same team, keep it on the same site. If it is a separate team, a microsite gives them independent access.
• Can your current theme and plugins handle a translation layer? Check for conflicts before you decide.
• Do you need the campaign to rank on its own? If yes, a microsite gives you a clean slate. If you need quick wins, main-site translation wins.
• What does a second site actually cost? Hosting, domain, design, and maintenance add up. Translation on the existing site avoids most of that.

Signs to wait, and the exception

Sometimes the right answer is “not yet.” Wait if:

• You have not defined the campaign audience or the exact languages.
• You do not know how long the campaign will run.
• No one is responsible for updating content after launch.
• You have not checked whether your WordPress theme and plugins support translation.
• Legal or compliance questions are still open, such as data privacy or regional offers.

The exception is a hybrid: you may need a microsite for one market and translated pages on the main site for another. That is not a mistake. It is a portfolio decision. Start with the option that serves the largest or most valuable audience first.

Common mistakes that turn either option into a mess

• Translating every page instead of only campaign pages. You waste effort and create unnecessary language versions.
• Skipping hreflang tags. Without them, search engines may treat translated pages as duplicates.
• Forgetting to remove temporary pages. When the campaign ends, archive or noindex the language versions so they do not linger.
• Building a microsite with no owner. A separate site needs someone to maintain it, update it, and eventually take it down.
• Assuming automatic translation is final. Automatic is fast, but you should still review key pages before launch.

Key facts about translating a WordPress campaign

This article compares two ways to run a multilingual campaign on WordPress: a separate microsite or translated pages on the main site. It does not cover full permanent localization strategy.

Limitations and when this advice does not apply

This advice assumes you are comparing two reasonable options. It does not apply when:

• You need a legally separate entity. A microsite on a different domain may be required for compliance or brand safety.
• The main site is technically broken. If it cannot handle a translation plugin without slowing down, a separate site may be simpler.
• The campaign is really a new business. A permanent brand deserves a proper site of its own, not just a translation of the old one.
• You need to build trust from zero. A microsite can create a clean narrative, but it will not inherit existing reviews, backlinks, or history.

Automatic translation does not replace human review. It helps you move fast, but someone should check the pages that actually convert.

FAQ

1. What is a microsite in WordPress? A microsite is a separate WordPress site, usually on its own domain or subdomain, built for one campaign or audience. It can share the same design system or look completely different.
2. Does translating the main WordPress site hurt SEO? Not if you do it properly. Use hreflang tags, keep one URL structure, and avoid duplicates. Translated pages can inherit the main site’s authority.
3. When should I create a microsite instead? When the campaign needs its own brand, a fresh domain, or technical isolation from the main site. If none of those apply, translate the main site.
4. How long should a campaign microsite stay live? As long as it serves a clear purpose. Set an end date, plan the archive, and remember to redirect or remove it when the campaign is over.
5. What should I check before using automatic WordPress translation? Check plugin conflicts, page speed, hreflang output, and whether you can edit the translations. Review the pages that matter most.
6. Can I do both? Yes. Some campaigns use a microsite for one market and translated pages on the main site for another. Treat it as a portfolio decision, not a failure.

If the checklist points you to on-site translation, the next step is to see how it works on your existing WordPress site before you commit to any campaign deadline.