AI SEO blog for OpenCart
The connector gives an OpenCart store a working blog without a third-party blog module. Articles are published as native Information pages with native SEO URLs, covers are stored inside your own image directory, and a rubric-filtered blog index is added for customers to browse.
How to connect Blogent to OpenCart
OpenCart connector
Install the package for your OpenCart branch. The connector publishes multilingual articles as native Information pages, creates native SEO URLs, stores covers locally, and adds a rubric-filtered blog index.
Download for your OpenCart version
Connector setup
- In OpenCart admin open Extensions → Installer and upload the package for your exact branch.
- Open Extensions → Extensions → Modules, install Blogent Connector, then edit and enable it.
- If needed, map Blogent language codes to installed OpenCart codes, for example
en=en-gbanduk=uk-ua. - For custom covers, map each
image_categoryor rubric key to explicit paths inside the OpenCart image directory. - Copy the generated Webhook URL into the Blogent SEO Blog settings.
- Optionally add the generated public blog URL to the store navigation. Published articles also appear as native Information pages with SEO URLs.
Use the package matching the installed OpenCart branch. Packages are separate because extension paths, templates, admin tokens, and the OpenCart 4 namespace system are not cross-compatible.
This integration receives the standard Blogent JSON payload. Review the full contract — fields, HTML tags, response format — and try the live webhook tester.
Webhook tester
Send a test article to your endpoint and check how the CMS processes the data. Edit the JSON if needed.
What you get after connecting OpenCart
- Articles become native Information pages, so they use your store template, your SEO URL rules and your existing indexing setup.
- A rubric-filtered blog index page is generated and can be linked straight from the store navigation.
- Covers are saved into the OpenCart image directory instead of being hotlinked from a temporary URL.
- Blogent language codes are mapped to the installed OpenCart codes (for example
en=en-gb,uk=uk-ua). - Custom covers can be pinned per
image_categoryor rubric key to explicit paths in your image directory.
Requirements and compatibility
- OpenCart version
- Separate packages for 2.0–2.2, 2.3, 3.x and 4.x. Install the one matching your branch.
- Why separate packages
- Extension paths, templates, admin tokens and the OpenCart 4 namespace system are not cross-compatible between branches.
- Access
- Admin access to Extensions → Installer and Extensions → Extensions → Modules.
- Connection
- The webhook URL generated by the module, pasted into the Blogent SEO Blog settings.
- Verification
- The connection test publishes a real article you can open on your own storefront before launch.
Frequently asked questions about the OpenCart integration
Which package do I download?
The one that matches your installed branch exactly — 2.0–2.2, 2.3, 3.x or 4.x. A package from another branch will not work, because paths, templates, admin tokens and the OpenCart 4 namespaces differ.
Does my store need a separate blog module?
No. The connector publishes into OpenCart Information pages and adds its own rubric-filtered blog index, so no third-party blog extension is involved.
Do articles get proper SEO URLs?
Yes. The connector creates native OpenCart SEO URLs for each published article, per language.
Where are cover images stored?
Inside your OpenCart image directory. You can also map an image_category or rubric key to explicit paths if you want to control which covers are used.
