Connect a WordPress site with the SEOAsist Connector plugin

If your site runs WordPress, you can connect it to the panel with the free SEOAsist Connector plugin. Once connected, your enabled Pixel rules (title, meta description, canonical, robots, Open Graph, JSON-LD, hreflang, image alt text, H1 and 301/302 redirects) are applied server-side while WordPress renders the HTML. Posts from the content studio can also go straight to WordPress.

#Prerequisites

• WordPress 5.8 or later and PHP 7.4 or later.
• Permission to install plugins in WordPress admin (an administrator account).
• The site's REST API must be reachable (the plugin uses /wp-json/seoasist/v1/).
• For AI-bot reporting, create a Pixel key (px_…) on the site's Pixel tab first.

#Create a connection token

1. Open the site from Sites and switch to the Fix channels tab.
2. In the WordPress card, enter the site's final address in WordPress address (no redirects, e.g. https://www.site.com).
3. Click Create connection. The Installation steps and a Connection token starting with wp_ appear.
4. Copy the token. It is shown only now; after that it is stored encrypted and masked.

#Install the plugin

1. Download the zip with the seoasist-connector.zip button in the Download plugin step.
2. In WordPress admin go to Plugins → Add New → Upload Plugin, upload the zip and activate it.
3. Open Settings → SEOAsist. Paste the token from the panel into the connection token field and your px_… key into the Pixel key field.
4. Optionally tick the Pixel script box, which adds the Pixel script to your pages. AI-bot reporting is on by default.
5. Save the settings.

#Test the connection and push rules

1. Back in the panel, click Test connection in the same card.
2. When the status shows Connected, the Site information section fills in: plugin, WordPress and PHP versions, theme, post and page counts, permalink setting and the number of rules on the site.
3. In Rule sync, click Push rules to send your enabled Pixel rules to the plugin.

From then on, rules are re-pushed to the connected site automatically whenever a rule changes. If there are no enabled rules, an empty list is sent and the rules on the site are removed.

#Publish content

In the Content studio, pick WordPress as the Channel, choose WordPress draft or Publish live, and click Publish. The featured image, tags, meta description and JSON-LD go with the post. For page updates, the plugin finds the post by URL, replaces its content and keeps the previous 5 versions as backups in WordPress. Roll back in the studio writes the original content back to WordPress.

#Verification

• The card's status badge reads Connected and the "Last seen" date is recent.
• In WordPress, the status table on Settings → SEOAsist shows a recent panel connection.
• After Push rules, a "Last push" date appears, and the page source contains the rules' title and meta tags.

#FAQ

#The test says "plugin not found (is SEOAsist Connector active?)". Why?

The plugin's REST endpoint returned 404. Make sure the plugin is activated and that WordPress address points to the site where it is installed.

#I get a "redirect to …" error. What should I do?

The address you entered redirects somewhere else, for example from the non-www address to the www one. Remove the connection and create it again with the final address the redirect lands on.

#What do "Invalid token" and "non-JSON response" mean?

"Invalid token" means the token in the plugin does not match the panel's; paste it again or generate a new one with Reset. "non-JSON response" means an HTML page came back instead of the REST API; a security plugin or server rule may be blocking /wp-json/.

#Does removing the connection delete the rules on my site?

No. Remove connection deletes the connection record and token; the plugin stays on the site but can no longer reach the panel. Rules on the site stay as they are until you remove the plugin or make a new connection.

#Is the Pixel key required?

Not for the connection or rule sync. It is required for AI-bot reporting, which covers visits from crawlers such as GPTBot, ClaudeBot and PerplexityBot.