Table of contents8
A client once called me on a Friday evening and asked, “David, we paid for this plugin last year. Can we just put it on our three other websites? It’s the same company.” I froze. I had been building WordPress sites for years, and I honestly did not know the answer. I told her I would check and call back. That silence told me something uncomfortable: I was selling websites built on tools whose rules I had never actually read. I am David Mwangi, and I have been building WordPress sites for clients across three continents for over a decade. That Friday call sent me down a rabbit hole of license pages, and what I found changed how I buy, use, and hand over every plugin.
Here is the fear I want to name for you: most of us buy a plugin license without reading a single line of what it allows. We either pay for more than we need, or we quietly break rules we never agreed to understand. Neither feels good. In this guide, I will teach you one practical skill: how to read any WordPress plugin license in about ten minutes, so you always know exactly what you paid for, what happens if you don’t pay again, and who should actually own the thing. Whether you run one small blog or you are a freelancer buying licenses for clients, this is the method I wish someone had taught me before I learned it the embarrassing way.

Now, a quick trust note before we start: I am not a lawyer, and this is not legal advice. Licenses are legal documents, and if something involves real money or real risk, talk to a professional. What I am giving you is the practical literacy that took me years to build — the same literacy that now saves me from stupid purchases and awkward client conversations. Everything in this guide comes from reading the actual terms of real plugins and the GPL license that WordPress itself uses.
Here is what this guide covers:
- What a license key actually controls (and what it can’t)
- The four freedoms you already own (GPL in plain words)
- The 6 clauses worth reading before you pay a cent
- What really happens when your license expires
- Who should own the license (the bus-factor rule)
- Red flags in license terms
- Frequently Asked Questions
- Final Thoughts
Ready? Let’s decode some licenses.
What a License Key Actually Controls Here’s the deal: the biggest lie we all believed is that a plugin license is permission to run the software. It is not. Once you understand this one split, everything else about plugin licenses clicks into place, and it comes from a simple article by Gaurav Tiwari about what a license key can and can’t enforce.
A license key controls exactly two things: your update feed and your support access. That is it. When you paste that key into the plugin’s settings, you are switching on the pipeline that delivers new versions to your dashboard and opening a door to the developer’s support team. The key does not control whether the plugin works. The plugin keeps running with or without a key, because of how WordPress licensing works — and I will explain that in the next section.
I learned this the hard way with a client who had an expired license on a form plugin. She panicked: “Did our forms stop working?” No. They were working perfectly. She just hadn’t received an update in eight months. That distinction matters enormously, because it reframes what you are actually buying. You are not buying install permission. You are buying a year of updates plus a support slot. Say it out loud next time you are on a checkout page, and the price suddenly reads very differently.
Here is the flip side that nobody tells you: an unlicensed plugin copy that never updates stops being worth running within about a year. WordPress moves fast. Core releases new versions several times a year, and plugins that stop updating slowly rot — they develop conflicts, they miss security fixes, and one day they break your site after a routine update. I saw a membership plugin last year that had not been updated in fourteen months break two client checkouts in one week. Nobody had touched it. WordPress had simply moved on without it.
So here is your first practical rule: think of every license purchase as renting a seat on the update train, not buying the train. That one mental shift will change every buying decision you make. And if you have ever wondered whether to leave auto-updates on or take control yourself, my walkthrough of the WordPress auto-updates guide lays out the risk tiers so you can decide site by site.
The Four Freedoms You Already Own Now comes the part that surprised me most, and it is written on the WordPress.org license page itself: almost every WordPress plugin is released under the GPL license, and the GPL gives YOU four specific freedoms that no license key can take away. Let me explain them the way I would explain them to my ten-year-old niece.
Freedom one: you can run the program for any purpose. Your plugin does not get to tell you what kind of site you may use it on. You bought a booking plugin? You can use it for your dentist site, your band’s site, and your cousin’s wedding site. The code does not care, and it does not check.
Freedom two: you can study how it works and change it. The code is open. A developer can read it, learn from it, and modify it to fit your site. This is why WordPress developers can fix a plugin’s bug themselves instead of waiting for the developer to wake up in another time zone.
Freedom three: you can share copies with anyone. You can literally send the plugin’s zip file to a friend. That is not piracy under the GPL. That is the license working as intended.
Freedom four: you can share your modified version. If your developer improves a plugin, they can distribute that improved version too.
Here is where it gets interesting — and where the confusion lives. These four freedoms mean the plugin’s code is free as in freedom. But the developer’s update feed and support desk are a service they sell. The GPL protects the code. The license key protects the service. Both exist at the same time, and they do not contradict each other. This is the exact distinction that the enforce-versus-rights article makes so clearly, and it is the single most useful sentence in this whole guide: the site limit is a service limit, not a freedom limit.
So what does that mean for the question my client asked me — “can we use this plugin on three sites when we bought a one-site license?” Honestly, yes, the code will run on all three sites, because the GPL allows it. But here is what I actually told her, and what I stand by: you will be paying for the privilege of being dishonest with a developer whose work you depend on, and you will only get updates and support for one of those three sites. The other two will silently rot. In my experience, that is a terrible trade. I would rather pay for the right tier once than spend a year nursing three half-maintained sites. Keep this honest-answer spirit in your pocket — we will need it again in the FAQ.
The 6 Clauses Worth Reading Before You Pay Here is the practical heart of this guide: the ten-minute license reading method I use before every purchase. You do not need to read forty pages of legal text. Every plugin’s terms page contains the same six clauses that actually affect your wallet and your site. Here they are, in the order I check them.
Clause 1: What does the site limit actually count? Most licenses say something like “5 sites” or “unlimited sites,” but the definition of a “site” varies wildly. The cleanest explanation I have seen comes from the MC4WP team’s license-choosing guide, which spells out how they count installations — and the examples apply to the whole industry. The question you must answer: is a site counted per domain, per WordPress installation, or per network? Get this wrong and you will either overpay for a tier you do not need or run short mid-year with no budget left.
Clause 2: How are multisite and staging counted? This is where I have seen the most surprise charges. Some developers count a multisite network as one site. Others count every subsite. Some let you run the plugin on staging and local development copies for free; others count those against your limit too. PublishPress has an unusually clear multisite license key guide that shows how one real vendor defines it — use it as your template for the questions to ask any vendor. My rule: if the terms do not clearly say “staging copies are free,” assume they are not, and ask.
Clause 3: Renewal price versus first-year price. Read the pricing page twice. Many plugins discount the first year heavily, then renew at the full price. That is not a scam — it is standard — but it means the price you paid on day one is not your real annual cost. I once bought a plugin at what I thought was thirty dollars a year and was billed fifty-nine at renewal. The terms said so, plainly. I just had not read them. Now I write the renewal price on a sticky note before I click buy.
Clause 4: What does “lifetime” actually mean? Lifetime deals sound wonderful until you read the fine print. “Lifetime” usually means the lifetime of the product, not your lifetime — if the developer sells the company, discontinues the plugin, or rewrites it as a new product, your lifetime deal may quietly end. I am not against lifetime deals, but I treat them as a bet on the developer’s longevity, not a contract.
Clause 5: The refund policy. Most reputable plugins offer a refund window — fourteen or thirty days is common — but the conditions vary. Some refund only if support could not solve your problem. Some exclude renewal payments from refunds entirely. Before you pay, find the refund section and read it twice. It is the cheapest insurance you will ever buy, and it takes ninety seconds.
Clause 6: Support terms. “One year of support” sounds simple, but read what it covers: how many tickets, what response time, and whether it includes help with conflicts caused by OTHER plugins. When a plugin fights with your theme at 9 PM before a launch — and if you want to be ready for that night, my plugin conflict troubleshooting guide has your back — the difference between “we will help” and “we will help, but only with our own code” becomes very expensive.
Note: I use those real-vendor guides as neutral examples of how tiers are shaped, not as recommendations. The skill is the same regardless of whose checkout page you are staring at: find these six clauses, read them, and you will never again be surprised by a license.
What Really Happens When Your License Expires This section exists because the expired-license panic is the single most common license question I get from clients, and the answer is almost always calmer than they expect.
When your license expires, three things happen, and none of them are dramatic. First, your update feed stops. New versions no longer appear in your dashboard. Second, your support access closes. Tickets you open go unanswered, or the developer politely points at the renewal link. Third, nothing else changes. The plugin keeps running exactly as it did the day before. Your forms still submit. Your sliders still slide. The site does not break, the sky does not fall, and WordPress does not come to take your website away.
That is the honest, technical truth. But here is the honest, practical truth too: the rot begins silently. WordPress releases major updates several times a year. Each one changes something under the hood. A plugin that has not been updated for six months is a plugin that has not been tested against the last two versions of WordPress — and if you are not sure whether that matters for you, the major versus minor updates guide explains exactly which releases break things. So the real expiry consequence is a countdown, not a cliff. You are not punished on day one. You are slowly abandoned.
I tell clients to treat an expired license like an expired car insurance policy: the car still drives, but every mile is now your personal risk. My practical system is simple. I keep a spreadsheet — one line per client site, one column per licensed plugin, with the renewal date. Once a month I scan it. Anything expiring within sixty days gets a decision: renew, replace, or retire. Renew if the plugin is still earning its keep. Replace if a better option exists — and before activating anything new, I run my pre-activation checks because a fresh plugin on a live site deserves caution. Retire if the feature is no longer needed. Three options, sixty-day horizon, no panic.
And if a plugin updates badly after you renew? That happens more than anyone admits, which is why I never update blind. My safe update checklist is the routine I run every single time, and when an update does go wrong, the rollback guide gets you back to safety. The license keeps the updates flowing; these routines keep the updates from hurting you.
Who Should Own the License This is the section that saves people real money and real heartbreak, and it comes straight from a principle I learned from Lockedown SEO’s ownership rule for plugin licenses: the business should own the license. Always. Never let your site depend on a freelancer’s or an agency’s license key. Let me tell you why with a story I still feel bad about.
Three years ago, I built a site for a small restaurant and bought the plugins under my own developer license — one of those “unlimited sites” tiers I was paying for anyway. It felt generous. It saved the client money. And it worked beautifully for exactly eighteen months, until the client and I had a disagreement about a redesign quote. Suddenly I was in the ridiculous position of holding the keys to software running their business. I handed everything over — I am not a hostage-taker — but the transfer took two weeks of support tickets, re-purchases, and downtime on one form that lost its license mid-transfer. We were both embarrassed. Neither of us will do it that way again.
This is called the bus-factor problem: if the license owner gets hit by a bus — or just changes their email, or stops paying, or stops answering — the business is stuck. The business pays for the site. The business suffers when it breaks. The business must own the keys. It really is that simple.
Here is the workflow I now use on every project, and I teach it to every freelancer who asks me. During the project, the freelancer may use their own license for testing and staging — that is normal and fine. At handoff, the client buys their own license under their own account, with their own email and their own payment method. The freelancer installs the client’s key, verifies updates flow, and walks away. No shared accounts. No “I will renew it for you each year.” Clean ownership, clean conscience.
If you are the client reading this: when your developer says “don’t worry, I have got the licenses covered,” that is your cue to ask exactly what they mean, politely but firmly. Covering the cost is generous. Owning the account in their name is a trap — usually an accidental one, but a trap. And if you are a freelancer, build this into your contracts. My article on freelancer contract clauses that protect you covers exactly this kind of term, and if you sell ongoing care, knowing how to price maintenance plans means license renewals become a line item, not a favor.
One more thing: when the handoff happens, licenses go on the transfer list alongside hosting, domain, and admin accounts. My client handoff guide has the full checklist. Licenses are assets. Treat them like assets.

Red Flags in License Terms After reading dozens of license pages, I have developed a nose for the ones that smell wrong. Here are the five red flags that make me close the tab, in the order of how often I see them.
Red flag 1: No terms page at all. If a plugin charges real money but has no license terms, refund policy, or pricing page you can actually find, walk away. A legitimate developer is proud of their terms. Hidden terms mean hidden surprises.
Red flag 2: “Unlimited everything” with no definitions. Unlimited sites, unlimited support, unlimited updates — with no page anywhere defining what a site is or what support covers. Unlimited is a marketing word, not a license term. Real terms have numbers.
Red flag 3: The license activates by sending your data somewhere shady. A normal license check phones home to the developer’s server with your key and domain. That is standard. But if the plugin demands your WordPress admin credentials, FTP access, or a scan of your whole site to “validate” a license, that is not validation. That is a security incident waiting to happen.
Red flag 4: No changelog, no recent updates. Before I buy any plugin, I check when it was last updated. A plugin whose last release was eighteen months ago is a plugin you are inheriting security risk from — the license is a ticket to a train that has already stopped running. I check the changelog date before I check the price, every single time.
Red flag 5: Reviews that only talk about features, never support. Scroll past the five-star reviews and read the one- and two-star ones. If the complaints repeat — “support never answered,” “refund refused,” “broke my site and they blamed my theme” — believe the pattern, not the average. A license is a relationship with a developer. The reviews tell you what that relationship is like.
And one honest counterpoint, because I promised honesty: sometimes a plugin with rough edges is still the right choice if nothing else solves your specific problem. Red flags are warnings, not commandments. But warnings exist to be read before you pay, not discovered after.

Frequently Asked Questions Can I legally use a plugin on more sites than my license allows?
Under the GPL, yes — the code is licensed to you with the four freedoms, so the plugin will install and run on any number of sites. But the honest answer is that the site limit is a service limit: only the licensed number of sites get updates and support. The rest quietly rot without updates, and you are using a developer’s paid service without paying. I tell my clients the law allows it and my conscience does not recommend it.
Do staging sites count against my site limit?
It depends entirely on the developer’s terms, and this is one of the six clauses I told you to check. Many developers explicitly allow staging, local, and development copies for free — but many do not say so clearly. If the terms are silent, email support and ask before you buy. Get the answer in writing. It takes five minutes and saves an awkward surprise later.
What happens if I don’t renew my license?
The plugin keeps working. You stop receiving updates, and you lose support access. The real consequence is slow: your plugin falls behind WordPress releases, misses security fixes, and becomes more likely to conflict with other updated software. I treat non-renewal as a decision that needs a plan — either renew, replace the plugin, or remove it — not as something you just let happen.
Can I get a refund if the plugin doesn’t work for me?
Usually yes, within the developer’s stated refund window — commonly fourteen to thirty days. Read the refund clause before you buy, because conditions vary: some developers refund only if their support team could not fix your issue, and renewals are often non-refundable. Keep your purchase receipt and your support ticket numbers. They are your evidence if you ever need them.
Should my developer buy the license for me?
They can buy it during the project for convenience, but the license account should end up in your name, under your email, paid with your payment method. This is the ownership rule from the previous section. A developer who insists on keeping licenses under their own account — even with good intentions — is creating a dependency that will hurt you both eventually. Put the transfer in writing as part of the project handoff.

Final Thoughts When I started building WordPress sites, a plugin license was a mystery box: money went in, a key came out, and I never asked what I had actually bought. That Friday evening call from my client changed that. I went and read the terms. I learned the difference between permission and service, between the code’s freedoms and the key’s limits. And slowly, buying licenses stopped feeling like gambling and started feeling like shopping — informed, deliberate, calm.
That is what I want for you. Not expertise in licensing law, just literacy. The ability to open any plugin’s terms page, find the six clauses that matter, and know exactly what your money buys. Ten minutes of reading before a purchase will save you from the two worst outcomes: paying for something you do not understand, and quietly depending on something you do not own.
You just did the hard part — you learned the skill. Now use it. The next time a checkout page asks for your money, slow down, find the terms, and read like someone who knows what a license key actually controls. Because now you do.
I would love to hear your own license stories — the surprise renewal, the staging-site argument, the handoff that went sideways. Drop them in the comments. The best lessons in this field never came from a terms page. They came from people like you who learned them the hard way and were generous enough to share.


1 comment