WordPress
Squarespace Integration for WordPress
HaloSEO publishes to WordPress through the WordPress REST API. This page explains how the connection works, what a published post looks like, and what to expect when something fails.
How HaloSEO connects to WordPress
You add your site in HaloSEO and create an application password in your WordPress user profile. HaloSEO stores that credential and uses it to call the WordPress REST API over HTTPS. The permission it needs is the ability to create and edit posts, plus read access to your categories and tags. It does not need file access, plugin install rights or your admin password. You can revoke the application password at any time from WordPress, and the connection stops immediately.
What the published post looks like
HaloSEO sends the post as standard WordPress content. It uses your theme's templates, so the header, footer, sidebar and typography are the ones your site already uses. The post appears in your normal post list with its categories, tags, featured image and author set. Internal links point to pages on your site. Nothing is rendered in a separate template or an iframe, and there is no HaloSEO branding on the page.
What happens on WordPress that does not happen elsewhere
WordPress gives HaloSEO a full publishing API, so posts can be created as drafts or published directly, scheduled, and updated later without a person touching the editor. HaloSEO can read your existing categories and tags and reuse them, which keeps the new post inside the structure your site already has. It can also set the featured image and the excerpt. On platforms without an open API, the same work needs a manual export and upload step.
What breaks, and what happens when it does
The most common failure is an expired or revoked application password. HaloSEO then cannot authenticate, the publish attempt fails, and the post stays in your HaloSEO queue. You get a notice in the dashboard with the error WordPress returned. Other failures include a security plugin blocking REST API requests, a host blocking outgoing or incoming requests, and a theme or plugin that strips content on save. In each case the post is not marked as published, so nothing is silently lost. Fix the cause, reconnect, and the post can be sent again.
Who this is not right for
This is not right for you if your WordPress site blocks the REST API and you cannot change that, or if every post must pass a legal or medical review before it goes live. It is also not right for you if you want to approve each sentence as it is written. HaloSEO is a publishing system, and it works best when you set the rules up front and let it run.
Related
the platform
the feature
How it runs, once it is connected
You do the first step. HaloSEO does the other six, on its own, every week.
- 01
Connect your website
- 02
HaloSEO researches keywords
- 03
Writes blog posts
- 04
Publishes automatically
- 05
Creates internal links
- 06
Builds backlinks
- 07
Improves rankings on Google and AI search engines