Clariti works with self-hosted WordPress sites. When you sign up, Clariti runs a quick compatibility check on your site before you create an account. This article covers what Clariti needs and how to fix the most common reasons the check fails.
What Clariti Needs from Your Site
A WordPress site. Clariti only works with WordPress. Sites on Squarespace, Wix, Blogger, or other platforms are not compatible.
A live site with published content. Clariti needs at least some published posts or pages to check. A site that has not launched yet cannot run through the check.
A reachable WordPress REST API. Clariti reads your posts and pages through the WordPress REST API, the same public data your site already shares. Firewalls and security tools sometimes block it.
10,000 posts and pages or fewer. Clariti supports up to 10,000 content items per site, counting posts and pages together.
The Clariti WordPress plugin. You install it during signup to verify that you own the site, and it needs to stay installed so Clariti hears about new and updated posts. See How to Install and Connect the Clariti WordPress Plugin.
Is My Site Big Enough for Clariti?
There is no minimum number of posts. Clariti tends to save the most time once your archive is big enough that keeping track of it in a spreadsheet gets painful, like a food blog with a few hundred recipes that need new photos, updated SEO, and fixed links. Plenty of bloggers with smaller sites join early, too, so they can build good habits for keeping older posts fresh as their site grows.
Fixing a Failed Compatibility Check
If the check fails, you will see a message under the Site URL box that starts with "Site check:". Here is what the most common ones mean.
"Request to WordPress was blocked"
Something in front of WordPress turned Clariti away. This is usually a firewall at your host, a security plugin like Wordfence, or Cloudflare. The message sometimes names the tool, for example "blocked by cloudflare."
To fix it, allow Clariti's IP address, 35.192.123.62, in each tool that could be blocking it, then run the check again. If you use Cloudflare, follow How to Set Up Cloudflare to Work with Clariti. If you are not sure where the block is coming from, your host can usually help.
"Unable to find WordPress REST API"
Clariti could not find the REST API at its usual address. Either the site is not built on WordPress, or the REST API has been turned off or moved by a plugin or custom setup. Check any performance or security plugin that has a setting to disable the REST API, and make sure it is turned on. If your REST API lives at a custom address, contact us and we will see whether we can accommodate your site.
"Unable to find any WordPress content"
Clariti reached your site but could not see any published posts or pages. A firewall or security plugin may be hiding them, so try allowing 35.192.123.62 as described above. This can also happen when a site publishes everything as a custom post type. Contact us, because we may still be able to set up your site. See Does Clariti Support Custom Post Types?.
"Site has too many content items"
Your site has more than 10,000 posts and pages combined. Contact us, as we may still be able to accommodate your site.
Frequently Asked Questions
I already signed up. Can a firewall still cause problems?
Yes. If a firewall or security setting changes later, Clariti can lose its connection to your site. See Troubleshooting the Clariti Plugin Connection.
Does Clariti support custom post types?
Yes, with a little setup from our team. See Does Clariti Support Custom Post Types?.
Still Have Questions?
Reach out anytime and we will help you sort it out. Email us at [email protected].