Launch WordPress Campaign Microsites Fast, Without New Hosting Each Time

Every campaign has the same infrastructure problem hiding behind it. The creative is ready, the copy is signed off, and then someone has to stand up a place for it to live. For a marketing agency running launches back to back, that “place to live” quietly becomes a recurring tax: a new hosting account, a fresh WordPress install, another set of credentials to track, and a deployment process to babysit.

There is a faster pattern. Build a campaign microsite once as a reusable template, then clone it per launch and route it to a domain or a path. This guide walks through that workflow using GrabWP Tenancy and GrabWP Tenancy Pro, where every campaign is a tenant on one WordPress installation.

The per-campaign hosting tax

When each campaign gets its own hosting account, the cost is not just the monthly bill. It is the setup time, the WordPress install, the theme and plugin stack you rebuild from scratch, and the onboarding of yet another dashboard into your password manager. Multiply that by every product drop, seasonal push, and event landing page across every client, and the overhead grows faster than the work does.

The goal is to decouple “we are launching a campaign” from “we are provisioning infrastructure.” You want the second part to be near-instant and repeatable, so your team spends its time on the campaign, not the plumbing.

Build a campaign template tenant once

Instead of starting blank each time, invest an hour building a single template tenant that captures how your agency ships campaign sites:

1. Create a tenant in GrabWP → Tenants and name it something like campaign-template.
2. Install the theme and the plugin stack you use for landing pages (page builder, forms, analytics, consent banner).
3. Build the reusable structure: a hero section, a lead-capture block, a thank-you page, and your standard tracking setup.
4. Set the per-tenant Performance and Security defaults you want every campaign to inherit. GrabWP Tenancy exposes a per-tenant Performance and Security tab that can apply settings like disabling WP-Cron, turning XML-RPC off, capping post revisions, setting how quickly trash empties, and blocking outbound HTTP except to an allowlist of hosts.

This template is the master you never launch from directly. It exists to be copied.

Clone it per launch

When a new campaign lands, clone the template rather than rebuilding it. GrabWP Tenancy Pro ships a full AJAX-driven clone workflow that copies the tenant database tables and the uploads, and runs a comprehensive URL search-replace across the cloned database, including serialized data, so internal links and settings point at the new site instead of the template.

1. Open the clone workflow from the tenant list and pick campaign-template as the source.
2. Name the new tenant for the campaign, for example spring-launch.
3. Choose the database option for this tenant. Pro lets you pick shared MySQL with table prefixes, a dedicated MySQL database, or SQLite per tenant.
4. Run the clone and let the AJAX progress UI copy the database and uploads and rewrite the URLs.

You now have a working campaign microsite that is a faithful copy of your template, with none of the manual rebuild.

Route it: custom domain or /site/ path

A cloned tenant needs an address. GrabWP Tenancy gives you two routing styles:

• Custom domain per tenant. Point the campaign’s own domain (or a subdomain you control) at the tenant. This is the clean choice for a client-facing launch that needs its own brand on the URL.
• Path-based routing. Serve the campaign from a subdirectory of an existing site, like example.com/site/spring-launch. The path prefix defaults to site and is configurable via GRABWP_TENANCY_PATH_PREFIX, and path aliases 301-redirect to the alias URL so you can hand out a clean link.

Path routing is handy for quick internal or short-lived campaigns where a dedicated domain would be overkill, while custom domains suit flagship client launches. Either way, no DNS-to-hosting-account setup dance is required beyond pointing the address.

Tear down or archive after the campaign

Campaigns end. When one wraps, you do not want a pile of half-live microsites lingering on the install. The clean exit is backup, then delete:

1. Run a tenant backup. Pro’s backup workflow is a multi-step AJAX process with a progress UI, and finished backups can be listed, downloaded, deleted, or restored later. Auto-offload can push the backup to S3-compatible storage after completion.
2. Confirm the backup is on disk (or offloaded to S3) so you have an archive point.
3. Delete the tenant to reclaim resources on the install.

If the client revives the campaign next season, restore the tenant from its backup instead of rebuilding. That turns a finished campaign into a reusable asset rather than dead weight.

Where this fits

This clone-and-route pattern is one piece of running an agency on a single install. If you manage several brands from that same WordPress, see how to keep them cleanly separated in Run a Multi-Brand Client Portfolio From One WordPress Install, and if clients ask how their data is handled, read Give Marketing Clients a Clean Data-Privacy Story With Per-Client Isolation.

Ready to stop paying a hosting tax per launch? GrabWP Tenancy Pro is $9.99/month (or $99.99/year, or $499.99 lifetime) for unlimited tenants on one install. See the full agency breakdown on the marketing agencies page.