TL;DR: Elementor Pro does not count staging subdomains as separate license activations. Domains like
staging.example.com,dev.example.com, and any*.localor*.testTLD are exempt — you can run Elementor Pro on a staging site alongside your live site without buying an extra license seat.
Elementor Pro users have a set number of license seats for connecting to WordPress websites. When you create a staging site for testing and development, you do not need an extra seat — as long as the staging domain matches one of Elementor’s exempt patterns.
Which Domains Count as an Elementor Pro License Activation?
The table below covers the most common domain patterns. A "No" means the domain does not consume an Elementor Pro license seat.
| Domain example | Pattern | Counts as activation? |
|---|---|---|
example.com |
Production domain | Yes |
example2.com |
Second production domain | Yes |
production.example.com |
Non-exempt subdomain | Yes |
staging.example.com |
staging.* subdomain |
No |
dev.example.com |
dev.* subdomain |
No |
example.staging |
*.staging TLD |
No |
example.local |
*.local TLD |
No |
example.test |
*.test TLD |
No |
Exempt TLDs and Subdomains
The following domain patterns are not counted as active Elementor Pro license activations.
TLDs (Top-Level Domains) that are not considered an active site:
*.dev(example:example.dev)*.local(example:example.local)*.staging(example:example.staging)*.test(example:example.test)*.example(example:example.example)*.invalid(example:example.invalid)
Subdomains that are not considered an active site:
dev.*(example:dev.example.com)local.*(example:local.example.com)test.*(example:test.example.com)staging.*(example:staging.example.com)wp.*(example:wp.example.com)m.*(example:m.example.com)beta.*(example:beta.example.com)support.*(example:support.example.com)webmaster.*(example:webmaster.example.com)portal.*(example:portal.example.com)cdn.*(example:cdn.example.com)cache.*(example:cache.example.com)media.*(example:media.example.com)static.*(example:static.example.com)
A one-site Elementor Pro license activates on one production domain. Any staging, development, or system domain that matches one of the exempt patterns above does not consume a seat, so a one-site license covers your live site and as many exempt staging environments as you need.
Setting Up Elementor Pro with WP Staging Pro
When you clone a WordPress site using WP Staging Pro, Elementor Pro is copied to the staging environment together with the rest of your site’s files and database. Because the staging subdomain matches an exempt pattern (for example, staging.example.com), Elementor Pro’s license validation does not prompt for re-activation.
In our testing with WP Staging, cloning a site that has Elementor Pro installed automatically carries the plugin to the staging subdomain — Elementor’s license validation treats the staging.* domain as exempt and does not prompt for re-activation.
Step 1: Clone your live site to staging
In your WordPress admin, go to WP Staging → Staging Sites → Create New Staging Site. Select the live site as the source. WP Staging Pro copies the database, all files, and every installed plugin — including Elementor Pro — to the staging environment.
Step 2: Open the staging site and check the Elementor license
Open the staging site’s WordPress admin and navigate to Elementor → License. Because the staging domain matches the staging.* exempt pattern, the license status should show as connected without consuming an additional seat.
Step 3: Confirm the activation count has not changed
To verify that the staging environment has not consumed a license seat, check your Elementor account’s connected-sites list. Only your production domain should appear as an active activation.
What If Elementor Shows a License Error on Staging?
If Elementor Pro displays a license error or requests activation on your staging site, these are the most common causes and fixes.
The staging domain is not in the exempt list. Check the domain against the TLD and subdomain tables above. Elementor also exempts patterns not shown here — including stage.*, numbered variants such as staging1.*, and host-specific staging domains (Kinsta, WP Engine, Pantheon) — so if your domain uses an unusual prefix, confirm it against Elementor’s published exempt-pattern list.
The license was activated under a non-exempt domain and the staging copy carries the old activation record. If you migrated a site from a non-exempt domain to an exempt one, the stored record may still count the old domain as a seat. To fix this:
- Log in to your Elementor account and deactivate the staging domain from the connected-sites list.
- Return to the staging site’s WordPress admin.
- Go to Elementor → License and reconnect.
If you have an existing site activation and need to adjust your activation count, disconnect and reconnect the license. This refreshes the domain registration against the current exempt-domain rules.
You have reached the seat limit on non-exempt production sites. If all license seats are in use by production domains, Elementor Pro will reject any new activation — including activations on exempt-pattern domains. Upgrade your Elementor Pro plan, or deactivate one production domain before retrying on the staging site.
