NextlerAI licences are product-specific and bind an installation identity to a normalised domain and environment. This protects purchased website capacity while allowing the plugin to remain readable when runtime access is unavailable.

Where the key is located

For direct purchases, sign in at My Account and open My Products. Copy the key from the exact Assistant or Publisher product card.

Inside WordPress, paste it only into that product’s License screen. The full key is stored encrypted; administration shows a masked suffix.

Choose the environment correctly

• Production: public/live business website; consumes production-site capacity according to the selected plan.
• Staging: non-public pre-production copy used for testing.
• Development: local or development installation.

Do not label a live customer site as staging to avoid capacity limits. The licence server can reject environments not allowed by the entitlement.

Activation and verification

Activation sends the product identifier, licence key, normalised domain, installation UUID and selected environment server-to-server to nextlerai.com.

The plugin checks status roughly every 12 hours and displays last/next verification, runtime access and update access. Responses are cryptographically verified.

Possible states include Active, Grace period, Not activated, Deactivated, Suspended, Expired, Domain mismatch, Invalid licence, Server unavailable and Verification required.

An eligible temporary server/network failure after a successful validation can use a grace period (default maximum seven days unless the signed entitlement specifies otherwise). Invalid key, product mismatch, domain/instance mismatch, not activated, activation-limit and disallowed-environment responses are immediate and do not use grace.

What happens without runtime access

Assistant hides the public assistant and makes its admin read-only. Publisher stops generation/publication runtime and keeps administration readable. Existing settings, indexes, topics, posts, jobs and stored data are preserved so access can be restored after the licence problem is corrected.

Move a licence to another domain

1. Back up both sites.
2. On the old site, open the product’s License screen.
3. Choose Deactivate licence and confirm.
4. Verify the old site no longer consumes the activation in My Products.
5. Install the same product on the new site.
6. Activate with the correct environment.
7. Refresh status and test providers/indexes/jobs.

If the old site is unavailable, use the account’s site-management control if provided or contact support with the order number, product, old/new domain and masked key ending.

Domain-change cases

• HTTP to HTTPS: normally the domain stays the same, but refresh status and caches.
• www to non-www: normalisation may treat the canonical host consistently; verify the displayed activated domain.
• temporary migration URL: use Staging/Development when appropriate; do not activate as Production unless it is genuinely the live destination.
• cloned database: the installation UUID and saved state are copied. Deactivate/re-activate deliberately so the licence server sees the intended installation.
• multisite: confirm how the plugin is installed and how the purchased website capacity applies before network-wide activation.

Common errors

• Invalid licence: recopy the product-specific key; remove whitespace and confirm the order entitlement.
• Product mismatch: an Assistant key is being used for Publisher or vice versa.
• Domain mismatch: deactivate the old domain or correct the canonical domain.
• Activation limit reached: free a retired production activation or upgrade capacity.
• Environment not allowed: select the real allowed environment.
• Server unavailable: verify outbound HTTPS/DNS/firewall and use Refresh status; an eligible prior state may enter grace.
• Expired/suspended: review the plan/order/account state and contact support if it is unexpected.

Safe support evidence

Provide order number, product/version, domain, environment, installation status, last verification time, error code/message and masked key ending. Do not send the full key or diagnostic files containing customer data unless support specifically requests a secure, minimised transfer.