[00] Subset PersonaMark, User guide
Getting started
Install Subset PersonaMark, connect it to your PersonaMark site with a site API key, and read the latest audit's score and to-dos in wp-admin.
Subset PersonaMark connects your WordPress site to PersonaMark, which audits your site. Once it’s connected, you see the latest audit’s to-dos in wp-admin and apply PersonaMark’s title and meta description rewrites from the block editor. This page takes you from install to your first audit in wp-admin.
Before you start
The plugin is free, and it does nothing until you connect it to a site in PersonaMark. PersonaMark (opens in a new tab) is a separate paid service that audits your site for search problems and speed, sends AI personas to try real tasks on it, and writes new titles and meta descriptions for your pages.
You need:
- A PersonaMark account, with your site added to it. Find out more at personamark.app (opens in a new tab).
- A site API key. An owner of the site in PersonaMark makes it in the site’s Settings → API tab. PersonaMark’s API docs (opens in a new tab) explain how.
- WordPress 6.5 or later and PHP 8.1 or later.
Install
- Download the free Subset PersonaMark zip from subsetwp.com/download/personamark.
- In WordPress, go to Plugins → Add New → Upload Plugin, choose the zip and click Install Now.
- Click Activate.
Connect your site
- In PersonaMark, open your site’s Settings → API tab and make a key. It starts with
pm_. - In WordPress, go to Subset → PersonaMark → Settings.
- Paste the key into API key and choose Connect.
Connecting does three things:
- It asks PersonaMark which of your PersonaMark sites the key belongs to, and shows its domain.
- It adds PersonaMark’s verification meta tag to the
<head>of your site’s pages. - It asks PersonaMark to check your ownership, which PersonaMark does by loading your homepage and finding the tag.
If PersonaMark doesn’t accept the key, nothing is kept, and a key you’d saved before stays in place. If the ownership check doesn’t find the tag, the site is still connected: clear any page cache, then choose Check connection. Troubleshooting covers each message.
The key is stored encrypted and never shown in full again. Disconnect forgets the key and removes the meta tag.
Keep the key in wp-config.php
To keep the key out of the database, add it to wp-config.php instead:
define( 'SUBSET_PERSONAMARK_API_KEY', 'pm_your-site-api-key' );
The key field then shows as set in wp-config.php and can’t be changed on the screen. Choose Connect once to add the meta tag and verify the site. Disconnect removes the tag but leaves the key, until you remove the line.
Read the latest audit
The Overview tab under Subset → PersonaMark shows:
- the latest audit’s score out of 100 and its date, with links to that audit and to all your audits in PersonaMark;
- its to-dos, in PersonaMark’s order, each with its severity, the pages it affects and a link to it in PersonaMark.
Answers from PersonaMark are cached for five minutes. If PersonaMark can’t be reached, the tab shows the last results it sent, with the date they’re from.
To start a new audit, choose Run audit. An audit usually takes a few minutes. Reload the tab to see when it’s done. If an audit of the site is already running in PersonaMark, the tab follows that one instead.
The audit’s details, and everything else PersonaMark keeps about it, stay in PersonaMark. The links in the tab open them there.
Who can do what
Connecting, checking the connection and running an audit need the manage_options capability, which administrators have. Applying a rewrite needs permission to edit that post, so authors and editors can apply rewrites to the posts they can edit. See the editor panel.
Watch Site Health
Subset PersonaMark adds one check to Tools → Site Health: whether the site is connected to PersonaMark and whether PersonaMark has verified that you own it. It reads what the plugin stored at the last connection check, so opening Site Health sends nothing to PersonaMark.
What’s sent to PersonaMark
Nothing is sent until you choose Connect. After that, your site calls PersonaMark’s API from your server, never from the browser, with the key in each request:
- to read the site’s details and its latest audit, when you open the Overview tab or check the connection;
- to ask PersonaMark to verify the site, when you connect or check the connection;
- to start an audit and follow its progress, when you choose Run audit;
- to find a post’s page in the latest audit, when you open the PersonaMark panel on a published post or apply a rewrite. This sends the post’s public address.
Post content isn’t sent. PersonaMark reads your published pages from the web when it audits them, and loads your homepage to find the verification tag.
Multisite
Each site in a network connects to its own PersonaMark site with its own key, and each site’s administrators manage it. Network activation doesn’t connect anything. The keys are kept on the network’s main site, each under the ID of its site, and deleting a site from the network deletes its key.
SUBSET_PERSONAMARK_API_KEY in wp-config.php applies to every site in the network, so use it only when every site connects to the same PersonaMark site.
Removing the plugin
Deleting the plugin from Plugins deletes its settings, the stored keys and the cached answers from PersonaMark, on every site of a network, and the meta tag goes with it. Titles and descriptions you applied stay, because they’re part of your posts now, and so do the revisions saved with them. Deactivating the plugin deletes nothing.
What to read next
- The editor panel covers reviewing and applying rewrites.
- Troubleshooting explains each connection message.
- The developer reference lists the constants, the filter, the WP-CLI commands and the stored data.