Works with SEOPress

RankHive works with SEOPress.
Approved titles land in SEOPress’s own fields.

SEOPress keeps your title and description templates under Titles & Metas, and SEOPress PRO can show each post’s Search Console clicks, impressions, click-through rate and position right in the posts list. RankHive acts on those numbers: each week it picks the posts with room to improve, drafts a new title, description or other fix, and after you approve, writes it into the same SEOPress fields you would fill in by hand. Here is where those fields live, how SEOPress’s templates, PRO modules and importer sit next to RankHive, and what to check when something looks off.

Find my SEO fixes See pricing

What RankHive writes into SEOPress

Three values per post or page: the SEO title, the meta description and the canonical URL. They are the post’s own values in the SEO metabox, which SEOPress’s guide describes as bypassing your global settings, so SEOPress prints a title RankHive wrote exactly as it prints one you typed.

Field	Where you see it in SEOPress	When the field is empty
SEO title	SEO metabox → Titles settings → Title	The title template for that post type, under SEO → Titles & Metas → Post Types
Meta description	SEO metabox → Titles settings → Meta description	The description template for that post type, in the same place
Canonical URL	SEO metabox → Advanced → Canonical URL	SEOPress sets the canonical automatically

RankHive does not write target keywords, the social titles and images, the noindex and nofollow settings on the Advanced tab, or the per-post Redirection tab.

Page edits, alt text, schema, redirects and robots.txt rules never pass through SEOPress. The integrations page shows where each one goes.

For developers: the SEOPress meta keys

SEOPress reads these keys; the RankHive plugin writes them with update_post_meta(). Changing one re-sends the other two as they stood just before the write, and a blank value deletes the key so the Titles & Metas template applies. Note the canonical sits under a robots key. Schema goes in _seoagent_schema_jsonld, which SEOPress does not read.

SEO title: _seopress_titles_title
Meta description: _seopress_titles_desc
Canonical URL: _seopress_robots_canonical

Where to see a RankHive change in SEOPress

Open the post in the block editor or the classic editor and scroll to the SEO metabox. Its Titles settings tab holds the title and meta description, with a Google preview that switches between mobile and desktop and flags text likely to be cut off. A title or description RankHive wrote after your approval is in those fields.

The canonical URL is on the metabox’s Advanced tab, next to the noindex and nofollow settings. SEOPress handles canonicals automatically, so the field is usually empty; if RankHive set a canonical for that post, it is there.

SEOPress 9.8 rebuilt the metabox, so screenshots in older guides may not match what you see. On pages built with a page builder, the Universal SEO metabox shows the same fields. Either way, the preview is a length check, not a promise: judge a change by its clicks and impressions in Search Console.

Titles & Metas templates and RankHive’s per-post values

SEOPress sets a default title and meta description for each post type under SEO → Titles & Metas → Post Types, built from dynamic variables such as %%post_title%% (or %%title%%), %%sitetitle%% (or %%sitename%%) and %%sep%%, the separator you choose in SEOPress’s settings. A %%_cf_ variable pulls in a custom field, which some sites use to build titles from product or listing data.

SEOPress’s guide is explicit about precedence: a value set on the post bypasses the global settings, and the global settings never override it. RankHive writes that per-post value, and its drafts are finished text rather than patterns of variables. So an approved title replaces the template for that post, including any custom-field part, and later template changes don’t reach it. Posts RankHive has not touched keep following the template.

If your template appends the site name or a custom field, check whether a draft includes what you want and edit it before approving. SEOPress PRO’s AI buttons in the metabox write the same two fields, so if you use them on a post RankHive has a draft for, whichever is applied last wins.

SEOPress features that overlap with RankHive

Several SEOPress features, mostly in PRO, do jobs RankHive can also do. The rule for each is the same: one owner per job.

Search Console (PRO). Since version 6.2, SEOPress PRO can show clicks, impressions, click-through rate and position as columns in your post lists, over the last three months by default. Version 10.3 added the same metrics in the metabox and a 12-month chart on the dashboard. That is the data RankHive reads. SEOPress shows it; RankHive picks the posts, drafts the fix with the numbers beside it, and writes it after you approve. RankHive connects to Search Console on its own, with read-only access, so it doesn’t need SEOPress’s connection.
Redirects. The free plugin has a Redirection tab on each post for 301, 302 and 307 redirects. PRO adds a redirect manager with 410 and 451, regex, CSV import and 404 monitoring, and recent versions warn in the editor when a URL is already redirected. That warning only knows SEOPress’s redirects: the ones you approve in RankHive sit in the RankHive plugin’s own list, which SEOPress doesn’t read. RankHive never changes a slug, so it never prompts SEOPress’s redirect notice for one. Keep one rule per URL.
robots.txt (PRO). SEOPress PRO serves a virtual robots.txt once you turn on Enable robots.txt virtual file under SEO → PRO → robots.txt. A real robots.txt file on the server overrides it, SEOPress warns you about that, and its guide notes some hosts create one. RankHive’s approved lines also go into the virtual file, so a real file hides them as well.
Schema. The free plugin outputs Knowledge Graph markup for a person or organization, set under SEO → Social Networks. PRO adds manual schemas on a post and automatic schemas applied to a post type with conditions, under SEO → Schemas. RankHive’s schema is a separate JSON-LD block, so a RankHive fix that repeats a type an automatic schema already prints, such as Article, leaves the post with two.
Instant Indexing. SEOPress’s free Instant Indexing can submit a URL to IndexNow when a post is published, updated or deleted. RankHive does not submit URLs to IndexNow itself, and SEOPress’s docs don’t say whether a field changed outside the editor counts as an update, so don’t assume RankHive’s changes are submitted.
Sitemaps. SEOPress’s XML and HTML sitemaps, under SEO → XML - HTML Sitemap, are untouched. RankHive does not generate or edit a sitemap.

Bulk editing in SEOPress, and where RankHive fits

SEOPress can add columns to your post lists, chosen under SEO → Advanced → Appearance → Columns: the title tag, meta description, canonical, target keyword, noindex and nofollow, and with PRO, Search Console data. Its productivity page says you can quick edit the title and description from the posts list. PRO adds bulk actions, including AI-written titles, descriptions and alt text, and a CSV import under SEO → Tools with an option to update only empty values.

With PRO, that makes a workable manual routine: sort by impressions, read the click-through rate, rewrite the weak titles inline. RankHive does the picking and the drafting for you, shows the query and position beside each draft, writes nothing until you approve, and logs every change so you can revert it. Approved values land in the same fields, so they show in the title and description columns like any other.

One caution if you edit in both places: RankHive’s Change Log only knows RankHive’s own changes. If you rewrite a title in the posts list after RankHive changed it, then revert RankHive’s change, the revert puts back the title from before RankHive’s change, over yours.

Switching to or from SEOPress

Moving to SEOPress: its importer, under SEO → Tools, reads Yoast SEO, Rank Math, AIOSEO and The SEO Framework, bringing over titles, descriptions, social data, robots settings, canonicals, focus keywords and redirect URLs. It overwrites SEOPress’s post meta and leaves the old plugin’s data in place.

Two things follow. First, run the import before you approve anything in RankHive, and don’t run it again afterwards: a second import would overwrite the titles RankHive wrote with the old plugin’s values. Second, deactivate the old plugin. The RankHive plugin checks for Yoast SEO, Rank Math and AIOSEO before SEOPress, so while one of them is active, approved titles are written for that plugin, not into SEOPress.

Leaving SEOPress: Rank Math’s importer reads SEOPress’s fields, RankHive’s values included. Yoast’s import list doesn’t include SEOPress. A revert in the Change Log writes to whichever plugin is active at the time, so a title reverted after the move lands in the new plugin’s field.

Who does what on a SEOPress site

Job	SEOPress	RankHive
Default titles and descriptions	Templates under Titles & Metas	Nothing
Showing Search Console numbers	PRO columns, metabox metrics and dashboard chart	The numbers beside each draft
Choosing which posts to rewrite	You	The weekly audit
Per-post titles and descriptions	You, in the metabox, quick edit or PRO’s AI tools	Drafted, then written into the same fields when you approve
Structured data	Knowledge Graph free; manual and automatic schemas in PRO	An extra JSON-LD block, when you approve a schema fix
Redirects	Per-post redirects free; the full manager in PRO	Its own list, for the redirects you approve
robots.txt	The PRO virtual file, or WordPress’s default	Lines you approve, added to the virtual file
XML sitemap	SEOPress	Nothing

Where both have a row, keep one owner per job: one redirect rule per URL, one source of each schema type.

Troubleshooting RankHive on a SEOPress site

The title tag doesn’t match the SEOPress field

SEOPress’s guide traces this to themes without WordPress title-tag support, often ones that still call wp_title() in the header. Add title-tag support and remove that call, and SEOPress’s title, including RankHive’s, is printed.

Google shows a different title or description

Google sometimes rewrites results; SEOPress has a guide on why. Give a change a few weeks, compare clicks for the query, and revert it from the Change Log if it did worse.

You can’t find the fields after an update

SEOPress 9.8 rebuilt the metabox. The title and description are still on Titles settings and the canonical on Advanced. On page-builder pages, open the Universal SEO metabox, which shows the same fields.

RankHive’s robots.txt lines are missing

A real robots.txt file is on the server, which SEOPress PRO also warns about. Copy its rules into SEOPress’s virtual file, delete the real one, and both SEOPress’s rules and RankHive’s lines are served. If your host recreates the file, ask it how to stop.

SEOPress shows no warning for a RankHive redirect

Its redirect warning only checks SEOPress’s own redirects. The ones you approved in RankHive are in the RankHive plugin’s list and in RankHive’s Change Log.

Approved titles don’t appear in SEOPress

Another SEO plugin is still active: RankHive checks Yoast SEO, Rank Math and AIOSEO before SEOPress. With Yoast or Rank Math active, the titles went into their fields; with AIOSEO, they show nowhere. Deactivate the old plugin.

Titles RankHive wrote reverted to old ones

Usually an import run again under SEO → Tools, which overwrites SEOPress’s post meta with the old plugin’s values. Don’t re-run it once RankHive has made changes.

Two Article items in the Rich Results Test

A PRO automatic schema and a RankHive schema fix both describe the post. Keep one: revert the schema change in the Change Log, or narrow the automatic schema’s conditions.

Setup, approval and price

None of this differs on a SEOPress site, so it is covered once on the integrations page: installing the free RankHive plugin and connecting Search Console (read-only), what an approval writes, what a revert checks before it runs, what the RankHive plugin prints itself, and what stays if you cancel. For the loop from Search Console data to an approved change, see how RankHive works. RankHive costs $49.99 a month for one site; see pricing.

SEOPress and RankHive: questions

Does RankHive replace SEOPress?

No. SEOPress keeps doing what it does: templates, sitemaps, structured data, breadcrumbs and its analysis in the editor. RankHive picks posts from your Search Console data each week, drafts fixes, and writes the ones you approve into SEOPress’s fields.

Do I need SEOPress PRO?

Not for RankHive. It writes the same metabox fields with the free plugin as with PRO. PRO adds Search Console columns, the redirect manager, the robots.txt editor and schemas; whether you need them is a separate decision.

SEOPress PRO already shows my Search Console data. What does RankHive add?

SEOPress shows the numbers. RankHive acts on them: it finds the posts where impressions are high and clicks or position lag, drafts the new title, description or other fix with the numbers beside it, writes it into SEOPress when you approve, and logs it so you can revert it.

Will RankHive’s titles show in SEOPress’s columns?

Yes, if you have the title and description columns switched on under SEO → Advanced → Appearance. They are the post’s own SEOPress values.

I am moving to SEOPress from another plugin. Anything to watch?

Run SEOPress’s import first and only once, then deactivate the old plugin before approving anything. RankHive checks Yoast SEO, Rank Math and AIOSEO before SEOPress, and a second import would overwrite RankHive’s titles.

Can I undo a title RankHive wrote into SEOPress?

Yes, from the Change Log. The old title goes back into the metabox; if there was none, the field is emptied and your Titles & Metas template applies again. If you edited the title after RankHive did, the revert replaces your edit too, so check the field first.

What happens to my SEOPress titles if I cancel RankHive?

Nothing. They are SEOPress’s own post meta, so they stay in the metabox and the columns, and SEOPress keeps printing them.

Sources

SEOPress details on this page come from SEOPress’s guides, feature pages and release notes, as of October 2026. Menus and plan features change, so check the current page before you rely on one.

Keep SEOPress. Add the weekly fixes.

Connect Search Console and WordPress, and your first audit starts when you subscribe. Nothing reaches SEOPress until you approve it.