Whose Key Is It Anyway? Keeping Tabs on Elementor Pro Licences Across a UK Client Roster

There's a particular email that lands on a Friday at about ten to five. It reads something like: "Getting a warning in the dashboard — says the licence is invalid?" And nine times out of ten, nobody has done anything wrong. You've simply run out of activations, because the site you built in 2023 is still sitting on a staging subdomain nobody remembered, quietly holding a seat.

Licensing is the least glamorous part of running client builds, and it's the bit that bites hardest during a launch window. So here's the unglamorous fix: a register, a decision made up front, and a deactivation routine that doesn't leave a live site in a strange state.

What a licence actually gives you

Keep this straight and most of the confusion evaporates. An Elementor Pro licence isn't a per-site product key that you buy once and forget — it's a subscription with a cap on how many sites can be activated at the same time. Your tier decides that cap, and the number lives on your Elementor account page under the websites list.

Do yourself a favour and check the figure there rather than trusting a blog post, including this one. Tiers get reshuffled, and the only count that matters is the one on your account.

Two things that catch people out:

• Activation is not installation. You can have the plugin sitting on forty sites. Only activated ones count against the cap.
• An activation is tied to a URL. Not a folder, not a database, not a client. The domain and path. Change either and the licence server sees a new site.

That second point is where UK agencies get their fingers burned, and we'll come back to it.

Where activations quietly go to die

In a typical freelance or small-agency setup, the spread looks like this:

1. The live client site.
2. A staging copy at staging.clientsite.co.uk, or on the host's own staging URL.
3. The dev sandbox where you actually build the thing before it earns a domain.
4. The previous version of the site, still live at the old domain while DNS settles.
5. Something from two years ago that you'd swear you disconnected.

Number five is the killer. It's usually a local dev environment, or a .test domain, or a host's temporary URL like srv123.hostingprovider.co.uk/~client. It doesn't feel like a real site, so it doesn't feel like it's using anything. It is.

The register: six columns and a habit

You don't need software. A shared sheet — Google Sheets, Notion, whatever the team will actually open — with these columns does the job:

A few notes from having run this badly before running it properly:

• Environment should be one of live / staging / dev / parked. If a row is staging and has been for over a month, that's your next deactivation.
• Licence holder is the important one, and it's a business decision, not a technical field.
• Last checked forces you to actually look. Quarterly is enough. The week before a launch, look again.

Bolt a calendar reminder onto the same day as your plugin update sweep. Updates and licences are the same chore, so treat them as one.

Client-owned, or rented from you?

This is worth settling in the contract, not in a support ticket six months later.

The client buys their own key. They pay Elementor directly, they own the renewal, and they can't accuse you of holding their site hostage. The trade-off is that you lose a bit of control: if they let the subscription lapse, Pro updates stop, and you'll get the panicked message about a security warning on a widget they've never heard of. It also means every client needs a small amount of hand-holding at renewal time.

You hold the key and they rent access to it. Cleaner for you, since one renewal covers the whole portfolio and you decide when updates land. But it makes you responsible for continuity, and it makes the offboarding conversation awkward if it isn't written down. If you go this route, put two lines in the agreement: the licence is provided as part of the care plan while the care plan is active, and on termination it will be deactivated and the client will be issued their own.

Whichever way you go, write it in the register next to the site name. Future you will not remember.

When the domain moves

Rebrands are the classic lockout trigger. A UK client decides in February that thistleandco.co.uk is now thistle-studio.co.uk, and suddenly you have a new site as far as the licence server is concerned — plus the old one, still activated, still counting.

A sensible order of operations:

1. Build on the new domain with the licence already active there, if you have a free seat.
2. Deactivate on the old domain the moment the new one is signed off — from inside the old site's WordPress, under Elementor's licence screen.
3. If you can't get into the old site (DNS gone, host cancelled, client changed their mind about paying), go to your Elementor account's website list and remove the entry there. That's the escape hatch, and it's the one people forget exists.

Same logic for a staging site that gets promoted to live. Deactivate on staging first, then activate on live. Doing it the other way round is how you end up one seat short at 4pm on go-live day.

What deactivating actually does

Less than people fear. Deactivating doesn't wipe your content, strip your widgets or turn the site into a pumpkin. The widgets you've already used generally keep rendering. What stops is Pro updates, the template library connection, and anything that phones home for a licence check — so don't be surprised if a Pro feature that fetches templates starts complaining.

Because of that, the rule is simple: never deactivate a live site to free up a seat for another live site. That's not housekeeping, that's a game of musical chairs with someone's business. If you're out of seats on a launch week, the answer is a tier upgrade, not a scramble.

The pre-launch check

Ten minutes, once per project, before the site goes anywhere near a client:

• Count live activations on the account page.
• Compare against the register.
• Deactivate anything marked staging or dev that hasn't been touched this quarter.
• Confirm which key the client is on, and that it matches the contract.
• Screenshot the account's website list and drop it in the project folder.

It's dull. It's also the difference between a launch and a lockout, and dull wins that trade every single time.