AI SEO blog for WordPress
Blogent prepares articles and the connector publishes them as ordinary WordPress posts. Connect the plugin once to load the site’s primary language, blog categories and their real URLs into Blogent. Choose image folders in WordPress for articles that use your own covers.
How to connect Blogent to WordPress
WordPress plugin
Download the current Blogent Connector ZIP here and install it in WordPress. Requires WordPress 4.7+ and PHP 7.4+.
Plugin setup
- Open Plugins → Add New → Upload Plugin, upload the ZIP and activate it. When updating, replace the existing Blogent Connector.
- Open Settings → Blogent Connector. Languages are read from WordPress, WPML, Polylang or WP Multilang.
- Choose the existing blog section from the category selector. Its child categories and native URLs are loaded automatically.
- For your own covers, under Images choose a folder for each category by browsing from the site root. You can also select images in the Media Library. Save the settings.
- Copy the complete Webhook URL, including the token. In the Blogent creation assistant select WordPress, paste it and click Load from website. For an existing project, save it under Integrations.
- Blogent saves the primary language, publication categories and image categories. Check the category → folder list in project settings. After changing the plugin settings, click Load from website again.
- Run Test connection in Blogent. It creates a real test article and then updates that same article.
How the plugin selects images
- The publication category controls where the post appears. The image category controls its cover. Blogent chooses these independently from the categories returned by WordPress.
- Folders are tied to native category IDs. Select the exact folder, such as
/smmix_blog_photo/aromadiffusers. The plugin uses images directly in that folder. To use a subfolder, select it explicitly. - A selected folder takes priority over that category’s Media Library selection. If it is missing or empty, publication fails with a clear error.
- If Blogent supplies a generated or stock image URL, the plugin downloads that image instead.
- Updating an existing article keeps its current cover.
Actions and stable identities
- Shopify, HubSpot, Webflow and Framer use the connected native publisher. WordPress, OpenCart, Strapi and Lovable use the installed Blogent connector; v0 and Replit adapt it to the existing app. Wix, Make, n8n and custom endpoints implement the synchronous contract; Zapier, Albato and ApiX-Drive use completion callbacks.
inventory: sendcursor: nullandlimit; return{articles: [snapshot], next_cursor: string|null}. Repeat the returned cursor until null.read: sendtargetand/orcontent_id; return{article_snapshot: snapshot}. Explicit nativetargetis authoritative. Blogent’s logicalcontent_idmay differ from the native identity.- Each snapshot contains
identity, title, alias, date, article, target, revision, urlsand optional image/author metadata.articlemaps locales to full title, alias, HTML, preview and SEO fields. Unknown original dates may be null and unavailable URLs may be an empty map. create: send the article payload, a uniqueoperation_id, logicalcontent_id, empty target and null expected revision. Return{posted:true,target,revision,urls}after complete publication.update: send existing native target IDs and the latestexpected_revision. Preserve original IDs, URLs/aliases, publication date, author and assets. Compare the revision atomically before applying changes.
Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.
Webhook tester
Run inventory, create, read and update on one real test article. Queued integrations wait for their completion callbacks.
What you get after connecting WordPress
- Articles use your WordPress theme, permalinks, feed and sitemap.
- WordPress, WPML, Polylang and WP Multilang supply the native languages and category URLs. The project uses the primary site language.
- The selected blog section and its child categories appear in the creation assistant and are saved with the integration.
- Choose an image folder for each category by browsing from the WordPress root. Media Library selections are also supported.
- The publication category and cover category are chosen independently. A post can appear in Blog while its cover comes from a product category’s folder.
- Article updates preserve existing IDs, URLs, publication dates, authors and images. Publishing failures include an error message.
Requirements and compatibility
- Platform
- WordPress 4.7 or later, PHP 7.4 or later, and permission to install plugins.
- Plugin
- Download the current Blogent Connector ZIP using the button in this guide.
- Connection
- Copy the full Webhook URL, including its token, from Settings → Blogent Connector into the Blogent assistant or integration settings.
- Languages
- The primary site language is imported from WordPress or its active multilingual plugin.
- Verification
- The connection test inventories existing content, creates one real article, reads its authenticated snapshot and updates the same native IDs. No public-page crawl is required.
Frequently asked questions about the WordPress integration
Do I have to write or edit anything myself?
Blogent prepares and publishes articles automatically. In WordPress, select the blog section and configure the image folders. The assistant loads the available categories. You can refresh them later in project settings.
Will published articles match my theme?
Yes. They are regular WordPress posts, so your active theme renders them. The HTML uses h2–h4, lists, tables and details/summary, which inherit your existing styles.
Can I use my own images instead of generated covers?
Yes. Under Settings → Blogent Connector → Images, choose a folder for each category from the site root, or select images in the Media Library. Save, then reload the categories in Blogent. The binding uses the WordPress category ID, so you do not have to copy slugs or folder keys.
What happens if my site is temporarily down?
The plugin returns an error to Blogent and the reason is recorded in the plugin error log, so you can see exactly which article failed and why.