[00] Subset PersonaMark, User guide
Troubleshooting
What Subset PersonaMark's connection, verification and editor panel messages mean, and what to do about each one.
This page lists the messages Subset PersonaMark shows when something stops it reaching PersonaMark, and what to do about each one.
The key isn’t accepted
That isn’t a PersonaMark site API key. A key starts with pm_ and is 46 characters long. Copy it again from the site’s Settings → API tab in PersonaMark, and check that nothing was cut off or added.
PersonaMark didn’t accept the API key. The key has the right shape, but PersonaMark refused it. It may have been revoked, or it belongs to another PersonaMark account. Make a new key in PersonaMark and connect with that. When a key is refused, the plugin keeps the key it had before, if any.
The saved key can’t be read any more. Keys are encrypted with your site’s security keys and salts in wp-config.php. If those change, paste the key again and choose Connect.
The site isn’t verified
PersonaMark didn’t find the verification tag on its homepage. The site is connected, and the tag is on your pages, but PersonaMark didn’t see it. Check these, then choose Check connection under Subset → PersonaMark → Settings:
- The domain shown under Site is this site’s domain. A key from another PersonaMark site connects to that site instead.
- A page cache or CDN isn’t serving a copy of the homepage from before you connected. Clear it.
- Your theme calls
wp_head(). The tag is printed there.
PersonaMark couldn’t load its homepage. The site may be behind a password, a maintenance page or a firewall that blocks PersonaMark. Choose Check connection once the homepage is publicly reachable.
Site Health shows the same state under Tools → Site Health, from the last check.
PersonaMark can’t be reached
Couldn’t reach PersonaMark. Your server’s request didn’t get an answer within 10 seconds. Try again in a moment. If it keeps happening, your host may block outgoing requests: ask them to allow work.personamark.app.
PersonaMark had a problem answering. PersonaMark answered with an error. Try again later.
PersonaMark has had too many requests from this key. Wait a while, then try again.
While PersonaMark can’t be reached, the Overview tab shows the last results it sent, with the date they’re from.
PersonaMark sent an answer this plugin doesn’t understand. PersonaMark’s API may have changed. Check for an update to Subset PersonaMark.
Running an audit
The audit didn’t start. The message after it is PersonaMark’s reason. PersonaMark runs audits only for a verified site, so verify the site first if that’s the reason.
An audit of this site is already running in PersonaMark. The Overview tab follows that audit instead of starting another. Reload it to see when it’s done.
PersonaMark hasn’t picked it up yet. The audit is queued in PersonaMark but hasn’t started. The tab stops following an audit an hour after it started. After that, check the site’s audits in PersonaMark.
The editor panel
Connect this site to PersonaMark. The site isn’t connected. Administrators see a link to the settings. Other users are asked to contact one.
Publish this post to see PersonaMark results. PersonaMark audits published pages, so a draft has nothing to show.
The latest PersonaMark audit found nothing to fix on this page. Either the page had no issues, or the audit didn’t reach it. Check the page’s address against the audit in PersonaMark.
PersonaMark no longer has that rewrite for this page. The rewrite changed, or was marked ignored or wrong in PersonaMark, after the panel loaded. Nothing was applied. Reload the editor to see the current rewrites.
The applied text went back after saving. With Yoast SEO or Rank Math, reload the editor after applying, before you save the post. Their fields in the editor still hold the old value until you reload.
The API address
SUBSET_PERSONAMARK_API_URL in wp-config.php points the plugin at another PersonaMark, for development or staging. If it’s set to a plain http:// address on another machine, the plugin refuses to send the key there and says so. Use an https:// address, or remove the constant to go back to PersonaMark itself. The developer reference has the details.