WordPress
WordPress Integration for WordPress
HaloSEO connects to your WordPress site and publishes posts into it. This page explains the connection, the permission it needs, and what happens when something breaks.
How HaloSEO connects to WordPress
You add your site in HaloSEO and approve the connection from inside your WordPress admin. HaloSEO uses the WordPress REST API with an application password tied to a user account you choose. That account needs the ability to create and edit posts, upload media and set categories and tags. It does not need administrator rights, and HaloSEO does not ask for them. You can revoke the application password at any time from the WordPress users screen, which cuts the connection immediately.
What the published post looks like
HaloSEO writes into the standard WordPress post editor fields. The post uses your theme. Headings, paragraphs, lists, images and internal links are stored as normal WordPress content, so your templates, fonts, colours and plugins apply without changes. Featured images are uploaded to your media library. Categories and tags are set from the ones that already exist on your site. Nothing is rendered by HaloSEO on the front end, so there is no extra script or block on your pages.
What happens on WordPress that does not happen elsewhere
WordPress gives HaloSEO a live view of your site structure. It reads your existing posts, pages, categories and permalinks, so internal links point at URLs that exist. It can schedule posts through the normal WordPress scheduler, so a post goes live at the time you set even if HaloSEO is not running. Drafts land in your posts list where your editors already work, and your existing roles and review process apply to them like any other post.
What breaks, and what happens when it does
The connection can fail if the application password is revoked, the user is deleted, the REST API is blocked by a security plugin, or the site moves to a new domain. When a publish attempt fails, HaloSEO marks the item as failed and keeps the draft. It does not retry blindly and it does not publish twice. You see the error in the HaloSEO dashboard with the reason WordPress returned. Fix the cause, then retry from the dashboard. If your site is down, scheduled posts wait in WordPress and go live when it returns.
Who this is not right for
This is not right for you if your WordPress site does not allow application passwords, if a plugin blocks the REST API and you cannot change that, or if every post must pass a manual editorial review before it can exist as a draft. It is also not right for sites hosted on WordPress.com plans that do not permit the REST API or plugin access. In those cases HaloSEO cannot connect, and we would rather say so here than during setup.
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