Connect your site
PageSoar publishes the fixes you approve to your site and confirms each one saved.
Pick what your site is built with
Not sure which is yours? Sign in, give PageSoar your address, and it suggests the one that fits.
WordPress
Install the plugin on a test site and paste a one-time code. PageSoar confirms the connection. No password is shared.
You need: A WordPress admin login, or the person who has one.
About 10 minutes.
Ghost
Add a custom integration in Ghost Admin and paste its Admin API key into PageSoar.
You need: A Ghost staff login that can add an integration (Owner or Administrator).
About 3 minutes.
Files in a git repository
Add PageSoar's deploy key to the repository. Approved changes are committed and go live when the site deploys.
You need: The repository's git address and access to its settings.
About 5 minutes.
A Python app
The same deploy key, for pages made by code. Approved titles and descriptions go into the source.
You need: The git address of the source code and access to its settings.
About 5 minutes.
Shopify
Give PageSoar a Shopify access token. Approved changes are published, checked on the live page and can be undone.
You need: A Shopify access token and your store's .myshopify.com address.
About 10 minutes.
Webflow
Give PageSoar a Webflow access token. Approved changes are published, checked on the live page and can be undone.
You need: A Webflow site token and your site's Webflow ID.
About 5 minutes.
Wix
Give PageSoar a Wix access token. Approved changes are published, checked on the live page and can be undone.
You need: A Wix API key and your site's Wix ID.
About 5 minutes.
Squarespace and others
PageSoar cannot publish here yet. It audits every page and writes up each fix, plus the redirects to paste in on Squarespace.
You need: Nothing to connect: start with the free website check.
WordPress: four steps, test site first
Whoever looks after your WordPress does this once for each site.
- 1
Download the PageSoar Connector
One zip file, from PageSoar. Its version is shown beside the link.
WordPress, through PageSoar ConnectorNot connectedDownload the PageSoar Connector (.zip)pagesoar-connector-2.2.0.zip - 2
Install and activate it on your test site
Plugins › Add New Plugin › Upload Plugin, choose the zip, then Install Now and Activate. It opens Settings › PageSoar by itself.
Add PluginsUpload Pluginpagesoar-connector-2.2.0.zipInstall NowPlugin installed successfully.Activate Plugin - 3
Paste the connection code
Make a code on PageSoar's Connect screen, one per site. Paste it into Settings › PageSoar and press Connect. It works once, within 24 hours.
Connection codePaste the code from PageSoar's Connect screen.7Q4K-M2XDConnect - 4
PageSoar confirms by itself
The plugin makes a key only PageSoar holds, so no password is shared. The Connect screen turns green; then repeat on your live site.
WordPress, through PageSoar ConnectorNot connectedConnectedTest siteWaitingConnectedLive siteNot yetPageSoar checked the connection itself. No password was made or shared.
Needs WordPress 5.8 or later and PHP 7.4.
What the WordPress Connector can and cannot do
It writes only what you approve in PageSoar, and every change can be undone.
What it can change
- Search titles, descriptions and the hide-from-Google setting of pages and posts
- Page text and headings, saved as a WordPress revision you can compare and restore
- Image alt text
- Labels Google reads for FAQs and breadcrumbs, and any awards you confirm
- Redirects for pages that are gone, in Safe Redirect Manager or Rank Math if you run one
- PageSoar's heat map script on your public pages, once you turn heat maps on
What it can never do
- Publish a draft, or delete anything but a redirect it made itself
- Change users, plugins, themes or site settings
- Add any other script, or unfiltered HTML
- Save over a page somebody has open in the editor
Before you install
Check your download
Your developer can confirm this is the file PageSoar published:
8286fdac839977a042451137e305b091f579a266bb3b8e952366cb5d32b5ab25Run shasum -a 256 pagesoar-connector-2.2.0.zip and compare.
If your host has no plugin upload
On WordPress VIP or any git-deployed site: commit the pagesoar-connector folder, deploy to staging and production, and pair each with its own code. Pair staging again after cloning production into it.
WordPress: if it does not connect
What you might see, why, and the fix. Still stuck? Write to hello@pagesoar.com with your site's address.
There is no Settings › PageSoar in WordPress
Why: The plugin was uploaded but not activated.
Fix: In WordPress, open Plugins, find PageSoar Connector and press Activate.
PageSoar says it could not reach the site, or the site stays on waiting
Why: A security plugin or firewall such as Wordfence, Solid Security, Cloudflare WAF or Sucuri is turning PageSoar away.
Fix: In that tool, allow requests to /wp-json/pagesoar/v1/, then press Connect in WordPress again with the same code.
The test site asks for a password before WordPress opens
Why: Password protection from the host or a plugin also stops PageSoar's check.
Fix: Leave /wp-json/pagesoar/v1/ out of the password protection, or switch it off while you connect.
WordPress says the site could not reach PageSoar
Why: The host blocks outgoing calls from the web server.
Fix: Send your host or IT team the lines below, then press Connect again with the same code.
Please allow outgoing HTTPS from our WordPress server to PageSoar: Host: pagesoar.com Port: 443 Path: /connector/
Opening your site's /wp-json/ address shows a page not found
Why: Permalinks are set to Plain, which hides the address PageSoar uses.
Fix: In WordPress, open Settings › Permalinks, choose any option except Plain (Post name is the usual one) and save.
PageSoar says the site did not answer
Why: The site was down or slow, or the address in PageSoar is not the site's.
Fix: Open the site in a browser to check it loads, check its address in Workspace settings, then press Check again.
Use PageSoar on a sample company
Try the audit, the approvals and the results yourself.
The demo needs no account or card.