WordPress
Shopify Integration for WordPress
HaloSEO publishes to WordPress through the WordPress REST API. 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 create an application password in your WordPress user profile. You paste that password into HaloSEO once. HaloSEO then calls the WordPress REST API over HTTPS to create posts, set categories and tags, add internal links and update published content. No plugin is required. The application password can be revoked from your WordPress profile at any time, and revoking it stops all access immediately.
What permission HaloSEO needs
The application password acts as the user account it was created under. HaloSEO needs an account that can publish posts and edit them, which usually means an Editor or Administrator role. It does not need access to your theme files, your database, your plugins or your server. If you want HaloSEO to publish without review, the account needs publish rights. If you want every post to wait for approval, give it a Contributor account and HaloSEO will submit drafts instead.
What a published post looks like
HaloSEO writes standard WordPress posts. They use your active theme, your templates, your fonts and your layout. Headings, images, lists and links are saved as normal block editor content, so you can open any post and edit it by hand. Nothing is rendered by HaloSEO at runtime and no custom front end is added. If you change your theme later, the posts change with it.
What happens on WordPress that does not happen elsewhere
WordPress gives HaloSEO a direct, structured way to publish. HaloSEO can read your existing categories and tags and reuse them, so new posts land in the right places. It can read your published posts to find internal link targets and add links to them. It can update an existing post in place rather than publishing a duplicate. Scheduled posts use the WordPress cron, so they go live on your site's schedule.
What breaks, and what happens when it does
The connection fails if the application password is revoked, the user is deleted, the password expires, or a security plugin blocks REST API requests. It also fails if your host blocks outgoing or incoming API traffic, or if the site moves to a new domain without updating the address in HaloSEO. When a publish call fails, HaloSEO records the error against that post and retries. The post stays in your HaloSEO queue and is not marked as published. You see the failure in the dashboard with the HTTP status returned by WordPress. Nothing is published twice, because HaloSEO checks for the post before it retries.
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. It is not right for you if you want to approve every word before it goes live and will not use the draft setting. It is not right for you if you run a WordPress.com free plan, which does not allow application passwords. It is not right for you if you want a tool that only writes text and leaves publishing to you.
Related
the platform
the feature
same feature, another platform
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