Title: BlazeHive Connect
Author: yassineblazehive
Published: Agẹmọ 22, 2026
Last modified: Ògún 21, 2026
---
Ṣàwárí àwọn plugin
# BlazeHive Connect
Láti ọwọ́ [yassineblazehive](https://profiles.wordpress.org/yassineblazehive/)
[Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/blazehive-connect.2.6.2.zip)
* [Àwọn àlàyé](https://yor.wordpress.org/plugins/blazehive-connect/#description)
* [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/blazehive-connect/#reviews)
* [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/blazehive-connect/#installation)
* [Ìdàgbàsókè](https://yor.wordpress.org/plugins/blazehive-connect/#developers)
[Ìrànlọ́wọ́](https://wordpress.org/support/plugin/blazehive-connect/)
## Àpèjúwe
**BlazeHive Connect** links your WordPress site to [BlazeHive](https://www.blazehive.io),
an SEO content service that researches keywords and writes conversion-focused SEO
pages for your product or service. Once connected, finished pages are published
to your site automatically — you never copy-paste HTML or fight your page builder.
Landing pages are published as a **standalone, theme-independent layout**: a keyword-
specific hero, alternating image-and-text sections, a plain-English explainer, an
FAQ, and repeated calls to action — the bottom-of-funnel structure that ranks and
converts. The plugin renders each page from structured data stored in post meta,
so the design is consistent on **every** WordPress theme and can be restyled later
from a single stylesheet without touching your content.
#### What it does
* **Publishes automatically** — BlazeHive pushes finished pages to your site through
a secure REST endpoint. No manual export/import.
* **Full side-by-side layout** — hero, alternating image splits, dividers, FAQ,
and CTAs, rendered pixel-for-pixel the same on any theme (the plugin loads its
own self-contained stylesheet and steps out of your themeÌtumọ̀ Yorùbá: ’s way
on landing pages only).
* **Its own URL space** — landing pages live under `/solutions/` (a post-type archive
that lists them all, plus automatic inclusion in your WordPress sitemap). If
your site already uses `/solutions/`, the plugin picks a free path automatically
and tells you which one.
* **Clean SEO head** — per-page ``, meta description, Open Graph, and Twitter
tags; canonical and robots handled by WordPress core.
* **Zero layout shift** — every image ships with intrinsic width/height, so pages
score well on Core Web Vitals.
* **Never breaks your site** — if anything is malformed, the page renders a safe
fallback (heading + description + call to action) rather than a blank screen.
Your other post types are completely untouched.
#### Use your own post types
By default each content type publishes into its own BlazeHive post type, and that
post type decides the URL root. If your site already has its own structure — a Resources
post type at `/resources/`, Guides at `/guides/`, or plain pages — open **BlazeHive
Advanced** and point any content type at it. Those pages then live under your URL
structure and are rendered by your theme like any other post of that type. Pages
already published keep their post type and URL; only new ones follow the change.
#### Other BlazeHive page types
The plugin also registers post types for BlazeHiveÌtumọ̀ Yorùbá: ’s other formats—
alternatives, “vs” pages, comparisons, and listicles — published as standard WordPress
content.
#### External service
This plugin is a connector for the **BlazeHive** service and requires a BlazeHive
account to do anything. It does not generate content on your server.
* **What the service is:** BlazeHive ([https://www.blazehive.io](https://www.blazehive.io))
researches keywords and generates SEO pages and articles.
* **What is sent to BlazeHive:** when you connect, you paste the pluginÌtumọ̀ Yorùbá:’
s generated API key and your site URL into BlazeHive. BlazeHive then calls your
siteÌtumọ̀ Yorùbá: ’s REST endpoint to create/update posts; the content it sends(
copy, image URLs, metadata) originates from BlazeHive and is written into your
posts. The plugin itself does not transmit your visitors’ data.
* **When it happens:** only when you connect the site in BlazeHive and when BlazeHive
publishes a page you approved.
* Terms of Service: [https://www.blazehive.io/terms-of-service/](https://www.blazehive.io/terms-of-service/)
* Privacy Policy: [https://www.blazehive.io/privacy-policy/](https://www.blazehive.io/privacy-policy/)
## Àwọn àwòrán ìbòjú
[⌊A complete landing page published to WordPress — keyword hero, alternating image
sections, SEO explainer, and FAQ, all theme-independent.⌉⌊A complete landing page
published to WordPress — keyword hero, alternating image sections, SEO explainer,
and FAQ, all theme-independent.⌉[
A complete landing page published to WordPress — keyword hero, alternating image
sections, SEO explainer, and FAQ, all theme-independent.
[⌊A landing page for a SaaS product (AI meeting notes), with a keyword-specific
hero and product mockup.⌉⌊A landing page for a SaaS product (AI meeting notes),
with a keyword-specific hero and product mockup.⌉[
A landing page for a SaaS product (AI meeting notes), with a keyword-specific hero
and product mockup.
[⌊A landing page for a local service (mobile car detailing).⌉⌊A landing page for
a local service (mobile car detailing).⌉[
A landing page for a local service (mobile car detailing).
[⌊A landing page for a professional service (freelance bookkeeping).⌉⌊A landing
page for a professional service (freelance bookkeeping).⌉[
A landing page for a professional service (freelance bookkeeping).
[⌊A landing page for a consumer app (sleep coaching).⌉⌊A landing page for a consumer
app (sleep coaching).⌉[
A landing page for a consumer app (sleep coaching).
## Ìgbéwọlẹ̀
1. In WordPress, go to **Plugins Add New Upload Plugin**, choose `blazehive-connect.
zip`, and click **Install Now**, then **Activate** (or install directly from the
WordPress.org directory).
2. Go to **BlazeHive** in your admin sidebar and copy your **Site URL** and **API
Key**.
3. In [BlazeHive](https://www.blazehive.io) **Integrations WordPress**, paste both
values and click **Test connection**.
4. ThatÌtumọ̀ Yorùbá: ’s it. Pages you approve in BlazeHive publish to your site automatically,
at `https://yoursite.com/solutions/<slug>/`.
## FAQ
### Do I need a BlazeHive account?
Yes. The plugin is a connector — it publishes and renders content from BlazeHive.
Without an account it registers the post types but has nothing to publish.
### Will these pages look different from my theme?
Landing pages are intentionally rendered as a standalone, theme-independent layout
so they look identical on every site and stay on-brand across your whole landing
set. All your other content and post types use your theme normally.
### What URL do landing pages use?
/solutions// by default, with a `/solutions/` archive listing them all. If another
plugin or page already owns `/solutions/`, BlazeHive Connect automatically uses
the next free path (offerings, products, uses, or features) and shows you which
one in the connection screen.
### Does it slow down my site?
No. Live pages render from data stored in your database — no external calls on the
visitorÌtumọ̀ Yorùbá: ’s request. Images are served with explicit dimensions to
avoid layout shift.
### What happens if something goes wrong with a page?
The plugin renders a safe fallback (heading, description, and call to action) instead
of a blank page, and it never affects your theme or other posts.
### How do I update the plugin?
Through WordPress as usual — **Dashboard Updates**, or the **Update** link on the
Plugins screen. BlazeHive will also nudge you from your dashboard when a new version
is available.
## Àwọn àgbéyẹ̀wò
Kò sí àwọn àgbéyẹ̀wò fún plugin yìí.
## Àwọn Olùkópa & Olùgbéejáde
“BlazeHive Connect” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe
ìkópa sí plugin yìí.
Àwọn Olùkópa
* [ yassineblazehive ](https://profiles.wordpress.org/yassineblazehive/)
[Túmọ̀ “BlazeHive Connect” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/blazehive-connect)
### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè?
[Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/blazehive-connect/), ṣàyẹ̀wò
[ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/blazehive-connect/), tàbí ṣe
àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/blazehive-connect/)
nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/blazehive-connect/?limit=100&mode=stop_on_copy&format=rss).
## Àkọsílẹ̀ àwọn àyípadà
#### 2.6.2
* Article headings now keep a little space above them, so a page whose heading
follows an image no longer looks glued to it.
#### 2.6.1
* Removed a leftover style rule that tried to hide your themeÌtumọ̀ Yorùbá: ’s
post title on BlazeHive pages. It did nothing on the pages BlazeHive renders
itself, and on themed pages it risked hiding the only heading on the page. Your
themeÌtumọ̀ Yorùbá: ’s heading is now always left alone.
#### 2.6.0
* **New: publish into your own post types.** Under BlazeHive Advanced, point any
content type at a post type you already use, so pages land under your existing
URL structure and your theme renders them. Applies to pages published from then
on; anything already live keeps its post type and URL. “Reset config” puts every
content type back to its BlazeHive default without touching a single published
page.
* BlazeHive never overwrites your content: when a page it publishes would collide
with a post of yours that has the same slug, WordPress gives the new page a unique
slug instead. Your post is left exactly as it was.
* Every BlazeHive URL root now steps aside if your site already uses it. Alternatives,
comparisons, and listicles got the automatic fallback that landing and FAQ pages
already had, so the plugin can no longer collide with an existing page or another
pluginÌtumọ̀ Yorùbá: ’s post type.
* Sites that already publish under the default roots keep them — your live URLs
never change on update.
* “{Your product} vs Competitor” pages now publish as comparisons, under `/comparisons/`,
instead of their own `/vs/` root. One less URL root to manage, and both page
styles live in one archive. Any existing page of that kind is moved automatically
and its old address redirects.
* Fixed: images inside article pages could overflow their container on themes that
do not constrain images. Every image now ships with a maximum width, so it fits
whatever layout renders it.
* The FAQ hub at /faq/ lists every question, including ones published into one
of your own post types.
#### 2.5.0
* BlazeHive pages now render your siteÌtumọ̀ Yorùbá: ’s own header and footer.
Previously landing, FAQ, and article pages were standalone documents with no
navigation — a visitor arriving from Google had no way back into the rest of
your site, and the pages were poorly linked internally.
* Works with both classic themes and block (full site editing) themes.
* Fixed: pages could ship two tags when an SEO plugin such as Yoast or Rank Math
was active. The title is now left entirely to WordPress and your SEO plugin,
so there is exactly one.
* Your themeÌtumọ̀ Yorùbá: ’s stylesheet now loads on these pages so the header
and footer look like they do everywhere else. BlazeHiveÌtumọ̀ Yorùbá: ’s own
styles remain scoped to its content and cannot restyle your theme.
#### 2.4.0
* New contextual-linking endpoints: your connected BlazeHive account can now list
your published posts and place a hyperlink on a phrase that already exists in
your content (used by BlazeHiveÌtumọ̀ Yorùbá: ’s contextual link features, which
you opt into from your BlazeHive dashboard).
* Linking never writes or rewords anything — one link is wrapped around one existing
phrase, in body paragraphs and list items only, at most one link per target site
per post. Block markup and special characters are preserved exactly.
* All new endpoints require your siteÌtumọ̀ Yorùbá: ’s own API key, like every
other plugin endpoint. No publishing behavior changed.
#### 2.3.0
* Article pages (alternatives, vs, comparison, listicle) now render with the same
clean, theme-independent styling as landing and FAQ pages: consistent typography,
spacing, tables, images, and code blocks on every theme.
* Article pages get a proper H1 (the post title) and social preview (Open Graph/
Twitter) tags, using the first body image when available.
#### 2.2.0
* Post type keys renamed from the generic `bh_` prefix to the distinctive `blaz_`
prefix (`blaz_landing`, `blaz_faq`, …), per WordPress.org plugin review.
* Existing content is migrated automatically on upgrade — every page keeps its
URL, status, and content.
* The publish API still accepts the old post type names, so no BlazeHive-side change
is needed.
#### 2.1.0
* New: FAQ pages. BlazeHive can now publish one-question-one-answer pages, each
rendered as a clean, theme-independent page with a breadcrumb back to the FAQ
hub.
* New: automatic `/faq/` archive — a styled hub listing every published question
as a card grid, ordered alphabetically (falls back to `/faqs/` if your site already
uses `/faq/`).
* FAQ pages get the same per-page SEO head (title, meta description) as other BlazeHive
content.
* New: social preview (Open Graph/Twitter) tags on FAQ pages and the FAQ archive.
* Fix: on block themes, landing pages (and the new FAQ pages) no longer output
a duplicate tag.
#### 2.0.6
* All admin and front-end CSS/JS now loads through the WordPress enqueue system(
no inline style/script tags).
* JSON-LD output hardened: script-safe encoding so stored markup can never break
out of the tag.
* Rendered-page cache now sets an explicit expiration.
* Removed an unnecessary core file include; admin menu moved to a standard position.
* Internal functions and constants renamed to the full blazehive prefix.
* Refined landing page spacing and image framing.
#### 2.0.5
* Landing pages render as a full, theme-independent side-by-side layout (hero,
image splits, results, FAQ, CTA) from structured post meta.
* Automatic `/solutions/` archive as an internal-link hub, with slug-collision
fallback if the path is already taken.
* Per-page SEO head (title, meta description, Open Graph, Twitter) and zero-CLS
images.
* Safe fallback rendering so a malformed page never white-screens.
* Fix: block data containing quotation marks is now stored and rendered correctly.
* Distributed and updated through WordPress.org.
## Àkójọpọ̀ Meta
* Ẹ̀yà **2.6.2**
* Ìgbàgbọ́hùn tó kẹ́yìn **ọ̀sẹ̀ 2 sẹ́yìn**
* Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10**
* Ẹ̀yà WordPress ** 5.8 tàbí ju bẹ́ẹ̀ lọ **
* Dánwò dé **7.0.4**
* Ẹ̀yà PHP ** 7.4 tàbí ju bẹ́ẹ̀ lọ **
* Èdè
* [English (US)](https://wordpress.org/plugins/blazehive-connect/)
* Àwọn àmì
* [automation](https://yor.wordpress.org/plugins/tags/automation/)[content](https://yor.wordpress.org/plugins/tags/content/)
[landing pages](https://yor.wordpress.org/plugins/tags/landing-pages/)[publishing](https://yor.wordpress.org/plugins/tags/publishing/)
[seo](https://yor.wordpress.org/plugins/tags/seo/)
* [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/blazehive-connect/advanced/)
## Àwọn ìbò
Kò sí ìwádìí tí a tíì fi ránṣẹ́.
[Your review](https://wordpress.org/support/plugin/blazehive-connect/reviews/#new-post)
[Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/blazehive-connect/reviews/)
## Àwọn Olùkópa
* [ yassineblazehive ](https://profiles.wordpress.org/yassineblazehive/)
## Ìrànlọ́wọ́
Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́?
[Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/blazehive-connect/)