Updates, support and safe maintenance
POM AI is distributed privately. Updates come from your POM account rather than from the public plugin directory, which means a valid license is what makes an update offer appear at all.
How updates reach the site
POM AI checks for updates against the account service using the stored license key. When a newer version exists and the license permits updates, WordPress shows the update in the usual place under Plugins or Dashboard → Updates.
Two conditions must both hold:
- a license key is stored and its last validation was successful;
- the plugin is in a position to use that key for updates.
On a single-site installation, the second condition is automatic: one key covers services and updates.
On multisite it is not. The update check uses the network license, so POM AI must be network-active or active on the network's main site for automatic updates to work. A subsite's own license authorizes AI services for that subsite; it never drives updates. This is explained in The network license and plugin updates.
Manual downloads
You can always download the current release ZIP from My Account → Licenses & Downloads on account.pom.es and install it by hand. That screen also shows the latest available version, so it is a quick way to confirm whether a site is behind.
Manual downloads are limited: the card shows how many downloads of the current version you have used and how many you have used in the last seven days. The limits exist to prevent redistribution, not to restrict legitimate maintenance. If you are hitting them, you probably want automatic updates working instead.
Before updating
POM AI updates change administration behaviour, not public page output, so the risk profile is low. Even so:
- update on staging first if you have one;
- take a backup you can actually restore;
- avoid updating in the middle of a long-running bulk operation;
- read the changelog shipped with the release.
After the update, confirm that Settings → POM AI → License still shows a valid license and that the credit balance loads. Nothing else needs re-doing: enabled tools, prompt templates and the business description survive updates.
What breaks a working installation
In practice, four things account for most sudden failures.
| Change | Effect | Fix |
|---|---|---|
| The site moved to a new domain | The old host is authorized, the new one is not | Save and validate on the new host; remove the old domain if it is gone |
| WordPress security salts were rotated | The stored key can no longer be decrypted | Paste the key again on the License tab |
| The subscription lapsed | Validation fails and services stop | Renew, then revalidate |
| Outbound HTTPS was blocked | Estimates and validation time out | Restore outbound access to the account host |
A cloned site is the case that surprises people most: the clone inherits the encrypted key but is a different domain, so it needs its own authorization and consumes domain capacity. Plan clones deliberately rather than discovering the limit later.
Uninstalling and moving on
Deactivating POM AI stops the tools and removes their screens. Content that was already generated stays where WordPress put it — posts, terms and attachments are ordinary WordPress records with no dependency on the plugin.
If a site is being retired, unlink its license first, from Settings → POM AI → License → Unlink. That releases the domain so the slot can be used elsewhere. Deleting the site without unlinking leaves the domain authorized and the slot occupied; see Remove an authorized domain.
Getting support
Before contacting support, collect:
- the site URL and whether it is single-site or multisite;
- the POM AI version;
- the tool you were using and the exact screen;
- the time the problem occurred;
- the exact error message or error code, copied rather than paraphrased;
- what you expected instead;
- whether it reproduces consistently.
Never include the license key, an MCP API key, an OAuth token, an authorization code, session cookies or customer data. A support report does not need them, and sending them means rotating those secrets afterwards. Redact screenshots before attaching them.
If the problem is a license or domain error, check its code against Understand license errors first. Many are self-service.
Routine maintenance worth scheduling
- Review the authorized domain list quarterly and remove sites that no longer exist.
- Review the credit usage log for domains you did not expect to see.
- Re-read the short description and structured business-profile sections when the business changes; the relevant saved sections continue shaping future requests until someone updates them.
- Revisit which tools are enabled after a team change, and disable what nobody uses.
- Rotate the license key if you suspect it has been exposed, and update every site afterwards. See Rotate a license key.