Configure a single WordPress site

On an ordinary, non-multisite WordPress installation the licensing model is as simple as it gets: one key, saved once, covering everything POM AI does on that site.

This page describes that case completely, so you can skip the multisite chapters entirely.

What one key covers

A single key saved under Settings → POM AI → License authorizes:

• AI service requests from this site;
• the credits those requests consume, drawn from the owning account;
• private plugin updates for this installation.

There is no second key, no separate updates credential and no network scope to think about. The stored entry lives in this site's own options, alongside any other POM product licenses the site uses.

The one-time setup

1. Install and activate POM AI.
2. Open Settings → POM AI → License.
3. Paste the key from My Account → Licenses & Downloads and select Save and validate.
4. Confirm the panel shows a masked key, a valid status and your public host on the Domain line.
5. Confirm the credit balance loads.

That is the whole licensing task. Activate a POM AI license covers each control in detail.

Which host gets authorized

The domain that gets authorized is the host of the site's own URL, as WordPress reports it. Two details are worth knowing:

• www is ignored for matching. example.com and www.example.com are treated as the same site and occupy one slot.
• The host is normalized before comparison. Case and a trailing dot make no difference; an internationalized domain is converted to its ASCII form.

If your site is reachable on more than one hostname — an old domain still resolving, a marketing alias — only the one WordPress considers canonical is authorized by saving the key. Authorize the others deliberately if they genuinely serve the site; see Authorize a domain to use POM AI.

Staging and development copies

A staging copy is a different host, so it needs its own authorization and it consumes a slot from the same plan. Whether it can be authorized at all depends on the plan:

• a staging host, detected from names containing staging, stage, dev, test, pre or sandbox, counts like any other domain;
• a local or development host — .local, .test, localhost, a hostname without a dot, or an IP address — is only accepted when the plan allows local domains.

Plan a staging site into your domain budget rather than discovering the limit when you need it. See Understand domain authorization limits.

Moving the site to a new domain

A domain change is the most common reason a working site stops working.

1. Before the move, unlink the license on the old domain, from Settings → POM AI → License → Unlink. This releases the slot.
2. Complete the migration.
3. On the new domain, paste the key and select Save and validate.

If you have already moved without unlinking, save the key on the new host anyway. If the plan has a spare slot the new domain activates immediately; if it does not, remove the old domain from My Account → Licenses & Downloads first. Remove an authorized domain covers both paths.

Cloning a site

A clone inherits the encrypted key from the database copy, but it is a different domain, so it is not authorized. The clone's License tab will show the stored key with a status that reflects the unauthorized host.

Decide deliberately which of the two sites should hold the authorization, and unlink on the other. Never leave both running against the same plan slot expecting both to work.

If the clone was made after the WordPress salts changed, the clone will additionally ask you to paste the key again, because the stored copy is no longer decryptable there.

Handing the site to a new owner

When a site changes hands, the license should change with it:

1. Unlink the license on the site. This deactivates the domain on your account and clears the local key.
2. The new owner saves their own key on the same site.

Do not leave your key on a site you no longer control. Whoever administers that site can spend credits from your account for as long as the domain stays authorized. If you cannot reach the site to unlink it, remove the domain from My Account instead, or rotate the key if you believe it was exposed — see Rotate a license key safely.

Routine checks

• After any migration, confirm the Domain line still matches reality.
• After changing the WordPress salts, expect to paste the key again.
• After renewing a subscription, use Revalidate so the panel shows the new expiry.
• Review the authorized domain list on the account periodically and remove sites that no longer exist.