HuntBee SEO Suite is a complete SEO management solution developed specifically for modern OpenCart 4 stores.
It brings technical SEO, metadata management, structured data, XML sitemaps, indexing controls, SEO URLs, redirects, broken-link monitoring, image SEO, AI-assisted content, product feeds, internal product discovery, and SEO automation together inside one coordinated OpenCart SEO system.
Instead of installing and maintaining many unrelated SEO extensions, HuntBee SEO Suite provides a structured collection of 19+ integrated SEO tools powered by the HuntBee Framework.
The Suite is designed for both beginners and experienced OpenCart administrators. Safe defaults, SEO Health monitoring, bulk tools, automation, queues, and centralized Cron processing help make ongoing SEO maintenance much easier as your catalog grows.
HuntBee SEO Suite does not attempt to replace good SEO strategy or guarantee rankings. Its purpose is to give your OpenCart store a cleaner technical foundation, better machine-readable information, more manageable content workflows, and a practical system for maintaining SEO over time.
SEO becomes difficult to maintain when an OpenCart store grows.
A small catalog may be manageable manually, but stores with hundreds or thousands of products can quickly develop problems such as:
Store owners often try to solve these problems by installing several separate OpenCart SEO extensions.
This can lead to duplicated functionality, overlapping events, inconsistent settings, more maintenance work, and difficulty understanding which extension controls a particular SEO function.
HuntBee SEO Suite solves this by bringing the major SEO workflows into one coordinated OpenCart SEO environment.
HuntBee SEO Suite is suitable for:
You do not need to be an SEO expert to use HuntBee SEO Suite.
The Suite includes safe defaults, diagnostics, guided tools, and practical administration workflows so that normal OpenCart store owners can manage important SEO tasks without needing to understand every technical detail.
HuntBee SEO Suite is designed to provide an ongoing SEO management system for OpenCart, rather than simply adding a collection of SEO settings.
The Suite focuses on four important areas.
Manage how search engines discover, crawl, interpret, and process your OpenCart URLs.
This includes:
Manage important page information associated with products and other OpenCart content.
This includes:
Provide structured information that supported search engines, shopping systems, and other external services can understand more easily.
This includes:
Find problems, process large catalogs, automate repetitive work, and maintain SEO as your OpenCart store changes.
The result is a more manageable SEO environment with less dependence on repetitive manual administration.
SEO Health Dashboard provides a central SEO check-up for your OpenCart store.
It helps administrators identify SEO problems and understand which areas require attention.
SEO Health can help review areas such as:
Instead of randomly changing SEO settings, administrators can use SEO Health to identify problems, open the appropriate HuntBee component, make corrections, and then run the health check again.
Manage metadata for important OpenCart page types.
Features include:
Existing OpenCart metadata can remain authoritative where HuntBee override fields are left empty.
The focus is on useful titles and descriptions rather than outdated Meta Keywords practices.
Generate machine-readable structured data using live OpenCart information.
Supported structured-data areas include:
OpenCart stock statuses can be mapped to appropriate structured-data availability values.
Diagnostics are included to help administrators review public structured-data output.
Structured data can make pages eligible for supported enhanced search experiences, but external search engines determine whether those features are displayed.
Generate scalable XML sitemaps directly from OpenCart data.
Supported content can include:
Additional features include:
Large OpenCart catalogs can be divided into manageable sitemap files automatically.
Help search engines understand the preferred URL when similar OpenCart URLs exist.
Features include:
The component is designed to work with OpenCart's normal canonical behavior rather than unnecessarily replacing it.
Control page-level indexing instructions for common OpenCart page types.
Built-in policy areas include:
Additional functionality includes:
This allows administrators to manage which pages should normally appear in search indexes without incorrectly relying on robots.txt for every indexing decision.
Notify participating search engines when important OpenCart URLs change.
Automatic change tracking can cover:
Features include:
IndexNow helps notify supported services about URL changes more quickly.
Successful submission means the change notification was received. It does not guarantee that a URL will be crawled, indexed, or ranked.
Generate and manage native OpenCart SEO URLs.
Features include:
The recommended workflow is to generate missing URLs first rather than unnecessarily replacing existing URLs that may already have links or search-engine history.
Manage your site's robots.txt file directly from OpenCart administration.
Features include:
Robots.txt controls crawler access and should not be confused with page-level noindex instructions.
The component is intentionally treated as an advanced SEO tool because incorrect crawler rules can block important pages or resources.
Identify and manage real URLs generating not-found responses on your OpenCart store.
Features include:
Broken URLs can result from deleted products, changed URLs, old external links, incorrect links, or outdated indexed pages.
HuntBee helps administrators identify which broken URLs actually deserve a relevant redirect rather than redirecting every 404 to the store home page.
Manage URLs belonging to known OpenCart content that has been disabled or removed from normal storefront availability.
Supported source content includes:
Redirect targets can include:
Administrators can use permanent or temporary redirect types depending on the situation.
This is especially useful for stores where products are regularly discontinued or replaced.
Manage OpenCart catalog image filenames and folder organization.
Features include:
The component uses a conservative workflow because moving or renaming catalog files can affect active storefront image references.
Preview and backup are recommended before large image operations.
Generate WebP image derivatives through the compatible OpenCart image resize workflow.
Features include:
The current recommended quality value is 82.
HuntBee does not replace original catalog images.
Custom themes that bypass the normal OpenCart resize pipeline may use their own image optimization system.
Generate supported OpenCart catalog and SEO content using either AI or deterministic templates.
Supported entity types include:
Depending on the entity, supported fields can include descriptions, metadata, headings, image text, and other SEO-related content.
Features include:
AI generation uses the shared HuntBee Framework AI configuration.
Automatic generation is optional and is recommended only after manually testing output quality.
Publish OpenCart product information in a machine-readable format for supported external workflows.
Features include:
The component can be useful where external systems or merchant programs require machine-readable catalog information.
Publishing an AI Product Feed does not guarantee ingestion, indexing, citation, recommendation, or inclusion by any AI or search platform.
Automatically generate useful OpenCart product tags from existing catalog information.
Possible sources include:
Features include:
Product Tags are intended primarily for OpenCart storefront search and discovery.
They are not the same as HTML Meta Keywords.
Automatically create relevant product relationships using existing catalog information.
Relevance signals can include:
Features include:
Random fallback is disabled by default so the Suite can prioritize relevance rather than filling every related-product position with unrelated items.
Edit important OpenCart SEO and catalog fields from one efficient administration interface.
Supported areas include:
Depending on the entity, editable fields can include:
Additional features include:
This is particularly useful when SEO Health identifies the same type of missing information across many catalog records.
Manage SEO Suite background automation through one central Cron system.
Instead of creating a different hosting Cron command for every SEO component, your server calls one HuntBee Cron URL.
The SEO Suite then determines which enabled jobs are due.
Current scheduled jobs include:
Features include:
For hosting environments that support it, calling the central Cron URL every minute is recommended. Individual HuntBee jobs still run only when their own configured schedule becomes due.
SEO Suite components work together using coordinated OpenCart events.
For example, when a product changes, different SEO features may need to:
Instead of requiring customers to manually configure many separate event integrations, HuntBee Suite installation and repair manage the required HuntBee events automatically.
HuntBee SEO Suite is powered by the free HuntBee Framework.
The Framework provides shared infrastructure including:
The Framework is installed separately and is required before installing HuntBee SEO Suite.
Install the latest HuntBee Framework version supported by your OpenCart installation.
The Framework is free and provides the shared services required by HuntBee Suites.
Open HuntBee Suite Manager and activate your HuntBee SEO Suite licence.
Install the SEO Suite through HuntBee Suite Manager.
The Framework handles component registration, setup, permissions, and required HuntBee events.
Open SEO Health before making large changes.
This gives you a starting overview of your store's technical and content SEO condition.
A typical store should then review:
Enter accurate business information where required.
For example:
Never add information that is not actually true for your store.
Depending on your store, you may also configure:
Add the central HuntBee SEO Cron command to your hosting control panel.
Cron allows queues and recurring SEO maintenance to run automatically.
Test AI generation, image operations, SEO URL generation, feeds, and other large operations on a few records before applying them across the entire catalog.
Use HuntBee SEO Suite as an ongoing maintenance system.
SEO should be reviewed whenever your catalog, OpenCart version, theme, URLs, content, or business information changes significantly.
No OpenCart SEO extension can guarantee search-engine rankings.
Rankings, indexing, rich results, AI citations, traffic, and sales depend on many factors outside the control of an extension.
Correctly configuring and regularly using HuntBee SEO Suite can, however, help achieve:
Most importantly, HuntBee SEO Suite provides a structured system for continuously maintaining the SEO health of an OpenCart store rather than treating SEO as a one-time configuration exercise.
AI functionality is completely optional.
If AI Content is used, configure one supported AI provider through HuntBee Framework.
Supported Framework integrations can include:
Any third-party AI usage charges are billed by the respective AI provider and are not included with the HuntBee SEO Suite licence.
HuntBee SEO Suite is developed specifically for the modern OpenCart 4 architecture.
Development, new features, and ongoing enhancements are focused on newer supported OpenCart releases rather than maintaining indefinite backward compatibility with every older OpenCart 4 generation.
For the best compatibility, security, performance, and access to current HuntBee features, we recommend keeping your OpenCart installation reasonably up to date with a release supported by the current HuntBee Framework and SEO Suite.
Compatibility with older OpenCart 4 versions is not automatically guaranteed unless specifically stated for the HuntBee release being installed.
Standard HuntBee SEO Suite support covers normal installation issues, confirmed HuntBee bugs, supported configuration assistance, and expected Suite behavior in a supported environment.
OpenCart stores can also contain custom themes, modified code, and extensions from other developers.
If an issue is caused by a third-party extension, custom theme, OpenCart modification, or custom development, investigation and compatibility work may require an additional support or development charge.
This allows HuntBee to continue providing standard Suite support while maintaining and continuously improving a much larger integrated SEO platform.
HuntBee SEO Suite turns OpenCart SEO from a collection of disconnected extensions into one maintainable SEO system — helping you identify problems, improve technical SEO, manage catalog information, automate repetitive work, and keep your store prepared for modern search and AI-assisted discovery.
Explore what this extension can do for your store, with practical examples.
Features for OpenCart 4
| Feature | What it does / Real-world example |
|---|---|
| Readable SEO-friendly URLs | Product, category and other supported pages can have meaningful addresses instead of technical route-based links. |
| Separate URLs for each store language | A translated product can have its own language URL, with configurable prefixes such as /fr/ for French. |
| Hreflang tags for translated pages | Optional alternate-language tags help search engines recognize different language versions of the same page. |
| Redirect old URLs to their replacements | When existing SEO URLs are regenerated with protection enabled, old links can redirect permanently to the new address. |
| Send visitors away from missing pages | Configured redirects take shoppers from broken or discontinued URLs to relevant working pages. |
| Preferred canonical links | The store can publish canonical links for supported pages, including configured exceptions to their ordinary preferred address. |
| Keep utility pages out of search indexes | Configured noindex directives can apply to internal search, account, cart and other eligible pages. |
| Relevant titles and descriptions on special pages | Home, search, product-tag, pagination and configured routes can use customized SEO metadata. |
| Product details in search-engine structured data | Supported product pages can publish JSON-LD describing prices, availability, offers and identifiers. |
| Review and variation details in product markup | Where relevant data exists, structured output can describe eligible product ratings and product-option variations. |
| Structured business information | Configured organization, contact details and social profiles can be included in search-engine-readable page data. |
| Breadcrumb and article structured data | Supported storefront pages can describe their navigation hierarchy and eligible articles to search engines. |
| Shipping and returns in structured data | Configured eligible shipping services and return policies can accompany suitable merchant markup. |
| Page metadata for social sharing | Supported Open Graph and social tags supply titles, images and descriptions to services that read them. |
| Descriptive text for product images | Supported product images can use managed alt and title attributes to describe the picture in page markup. |
| WebP storefront images when supported | The suite can serve cached WebP alternatives for resized images when enabled and compatible with the server and theme. |
| Search-engine XML sitemap files | Store-specific and multilingual sitemaps can list eligible pages and optionally their product images. |
| Machine-readable product catalogue | An enabled store can expose a product catalogue and prepare a compressed merchant feed for compatible consumers. |
| Feature | What it does / Real-world example |
|---|---|
| See an SEO health score and top priorities | The SEO Health dashboard highlights critical problems, attention areas and important opportunities for the selected store. |
| Find missing or duplicate SEO content | Identify supported records with missing titles, descriptions or duplicate metadata. |
| Check a focus keyword across page fields | Enter a phrase for a selected item to see how consistently it appears in important SEO areas. |
| Review technical SEO problems | Inspect supported indexing, robots, sitemap and URL configuration checks. |
| Check structured data, images and broken links | Use separate health sections to focus on markup, image issues, and link or redirect problems. |
| Inspect affected pages and export results | Open problem records, navigate to the relevant SEO tool and download supported audit findings as CSV. |
| See which pages are missing SEO URLs | Review URL availability by content type, store and language before generating new links. |
| Generate SEO URLs in batches | Create missing readable URLs for many supported products, categories and other pages rather than editing them individually. |
| Edit or regenerate a page's SEO URL | Choose a particular URL keyword or deliberately regenerate one that needs improving. |
| Control URL naming and character style | Set a product keyword template and choose native characters or Latin transliteration for generated URLs. |
| Manage language prefixes and static route URLs | Set language prefixes and readable keywords for supported routes, synchronized across stores where appropriate. |
| Review SEO URL changes and safe redirects | Check recent URL generation activity and choose whether regenerated links should have permanent redirects. |
| Edit homepage metadata for different languages | Set the store's homepage title and description separately for its supported languages. |
| Create metadata patterns for search and tags | Configure how internal search and product-tag result pages present their SEO titles and descriptions. |
| Customize metadata for later result pages | Apply pagination templates to page 2 onward without replacing page 1's normal metadata. |
| Manage metadata for custom routes | Add, edit, preview or delete route-specific titles and descriptions for pages that need overrides. |
| Edit key SEO fields without opening full edit pages | Update supported products, categories, manufacturers, information pages and articles in a focused workspace. |
| Search for the exact product or page to edit | Find records by supported names, IDs, models, SKUs or other available search terms. |
| Manage store-specific SEO URLs in Quick Editor | Change the URL for one store while preserving shared product and other entity content. |
| Choose AI generation or a non-AI template mode | Generate supported content through a configured Framework AI provider, or use reusable templates without API calls. |
| Generate SEO content for supported page types | Work with product, category, manufacturer, information-page and article fields that the generator supports. |
| Choose which SEO fields are generated | Generate suitable descriptions, meta tags, headings, product tags or image text, depending on the page type. |
| Generate content in selected store languages | Choose which enabled languages to include rather than applying one language to the whole catalogue. |
| Customize writing style, length and instructions | Choose the tone and detail level and provide additional guidance for generated text. |
| Protect existing text or deliberately regenerate it | Target missing content by default, or choose regeneration when an existing field needs replacing. |
| Preview proposed generated content | Inspect new descriptions or metadata before deciding to apply the changes. |
| View generation queues, logs and retries | Inspect pending and completed work, review failures and retry or remove eligible tasks. |
| Choose which structured-data types to use | Configure eligible Product, Organization, Breadcrumb, Article and other supported schema output. |
| Configure product offers, reviews and availability mapping | Choose relevant review limits and supported product availability rules for merchant markup. |
| Enter organization and local business information | Provide business identity, contact, location, social profiles and optional opening-hours details. |
| Describe shipping and returns for structured data | Enter supported shipping costs, destinations, delivery periods and return conditions. |
| Configure image licensing and social sharing metadata | Maintain supported image creator, copyright and license values, plus social metadata defaults. |
| Inspect a public page's structured data | Enter a URL on the selected store to inspect the structured output and possible issues. |
| Choose what appears in XML sitemaps | Enable supported products, categories, articles and other available content types. |
| Provide separate store and language-aware sitemaps | Keep sitemap URLs relevant to each storefront and its enabled languages. |
| Include product images in sitemap files | Add eligible product-image references alongside product URLs. |
| Add extra storefront URLs to the sitemap | Include suitable URLs belonging to the selected store that are not covered automatically. |
| Control sitemap size, cache lifetime and optional hints | Configure URL limits, file caching and optional priority or change-frequency hints. |
| Validate, clear and rebuild sitemap output | Check sitemap XML and URLs for errors, then clear the cache when fresh sitemap files are needed. |
| Control indexing of normal and utility pages | Use built-in policies for public pages, internal search, account, checkout and other supported routes. |
| Control indexed versions of sorted or filtered pages | Apply rules to qualifying query variations so unnecessary page combinations do not all need indexing. |
| Create custom noindex or index exceptions | Define a rule for a specific OpenCart route and optional query parameters. |
| Test indexing rules and store scope | Try a route and its parameters to see the directive the storefront would select for a particular store. |
| Set a preferred canonical URL when necessary | Add an exact custom override when a page needs a different canonical from its automatically chosen URL. |
| Search, edit and delete canonical overrides | Maintain individual or multiple canonical records from the admin without changing template code. |
| See which requested URLs cannot be found | Review missing-page records, request counts and whether a redirect has been assigned. |
| Trace broken links to their referring pages | Inspect saved referrer information to find where visitors may have encountered a bad link. |
| Create manual redirects with suitable status codes | Point an old URL to a replacement using supported permanent or temporary redirect responses. |
| Redirect URLs matching selected keywords | Use configured keywords to send matching missing-page requests to a suitable destination. |
| Repair repeated URL patterns using replacement rules | Replace an obsolete path segment or another matching URL part when a consistent destination pattern exists. |
| Find, filter and update broken links in bulk | Search by URL and other available criteria, then change destinations, types or selected records together. |
| Monitor and clean broken-link storage | Review tracked URL and referrer counts and use retention or cleanup controls to remove unneeded old data. |
| Find disabled store pages needing redirects | Review disabled products, categories, information pages and articles whose existing URLs may need replacements. |
| Choose replacement destinations for disabled items | Point an unavailable item to a suitable category, information page, article or supported custom link. |
| Monitor IndexNow submissions per store | See pending submissions, successful and failed URLs, and recent activity. |
| Create and verify a store-specific IndexNow key | Generate the ownership key file and verify that the store's public domain can serve it. |
| Review and manually submit URLs | Inspect changed URLs awaiting submission and add suitable page URLs manually. |
| Retry failed URLs and choose monitored content types | Retry unsuccessful submissions and select eligible types of page changes that should be queued. |
| See which products are ready for merchant feeds | Review eligible products and identify those missing required information. |
| Scan products for missing or inconsistent feed data | Check prices, image URLs, availability, identifiers and other required product-feed details. |
| Confirm products that genuinely lack identifiers | Record an appropriate no-GTIN or no-MPN situation without inventing product codes. |
| Generate a compressed merchant feed | Build a supported OpenAI merchant CSV.GZ feed from eligible products in batches. |
| Preview and validate generated merchant-feed records | Review product samples and feed validation issues before using an export. |
| Configure, cache and download store-specific feeds | Choose a store and language, manage catalogue publication and download generated feed snapshots. |
| See which catalogue images need attention | Review poor filenames, folder organization, missing image files and images referenced from several records. |
| Generate descriptive filenames for images | Use product, category, manufacturer or other supported values to build useful file names. |
| Organize image files into meaningful folders | Choose category, manufacturer, alphabetical or custom folder structures. |
| Work with supported product and catalogue images | Manage product main and additional images plus category, manufacturer and optionally product-option images. |
| Preview proposed image changes without modifying files | Review destination paths, shared references and conflicts before approving a rename or move. |
| Process selected image changes in controlled batches | Rename or organize only approved image records rather than changing all files at once. |
| Audit image filename quality | Identify generic, overly long or unsuitable filenames and review suggested improvements. |
| Find missing image files and possible repair paths | Locate database references whose image file is absent and inspect supported repair options. |
| Find possibly unused image files without deleting them | Perform an optional read-only scan for unreferenced file candidates. |
| Review history and undo supported image operations | Restore eligible individual renames or a processed batch, and optionally normalize verified JPEG extensions to .jpg. |
| See which products need search tags | Review tag coverage across active products and enabled store languages. |
| Generate useful tags from product information | Choose categories, manufacturers, attributes, filters, names and product codes as available sources. |
| Preview language-specific tags before generation | Compare existing tags and suggestions, with configurable stop words and tag limits. |
| Generate and remove tags without losing merchant tags | Queue missing or updated products and remove HuntBee-generated tags while retaining manual entries. |
| Find products missing related-product recommendations | See product coverage, missing suggestions and queued generation work. |
| Match related products using relevant details | Use category, filters, manufacturer and price similarity when choosing eligible suggestions. |
| Preview and limit the related products selected | Review suggested candidates and choose a maximum target number of related items. |
| Regenerate related products without deleting manual links | Queue bulk updates or remove relationships owned by HuntBee while keeping merchant-created links. |
| Edit the store's robots.txt from OpenCart admin | Maintain crawler access rules without using your hosting file manager. |
| Validate robots.txt and load a recommended starting template | Review warnings and optionally add your sitemap directive before saving. |
| Restore the previous robots.txt file | Undo an unsuitable change using the stored previous version when available. |
| Configure WebP generation and quality | Enable supported resized-image optimization and choose the quality of generated WebP files. |
| Test image conversion and review compatibility | Check server support and whether the active theme already handles its own WebP pipeline. |
| Clear generated WebP cache files and inspect logs | Remove disposable HuntBee derivatives without deleting original pictures or standard OpenCart thumbnails. |
| Manage background SEO jobs in one place | See available scheduled tasks, their enabled state and processing settings. |
| Use one server scheduler for the SEO Suite | Install a single command or authenticated URL rather than a separate hosting cron for every SEO task. |
| Run a background task immediately for testing | Use Run Now to execute an eligible job once without enabling a recurring schedule. |
| Monitor scheduler health, frequency and batch limits | Review last automatic calls and adjust task intervals or work limits for your hosting capacity. |
| Feature | What it does / Real-world example |
|---|---|
| Generate missing SEO URLs after content is saved | When enabled, saving a supported page can create missing SEO keywords for its assigned stores and languages. |
| Protect changed URLs with 301 redirects | Regenerating an existing page keyword can create a permanent redirect from the former address. |
| Add alternate-language information to eligible pages | When enabled, supported multilingual pages can output hreflang links automatically. |
| Apply indexing rules when a page is requested | The storefront resolver checks configured routes and query parameters to choose the relevant robots directive. |
| Apply canonical rules without editing page templates | The runtime uses supported canonical defaults and exact overrides to choose a preferred URL. |
| Use metadata patterns on eligible storefront pages | Configured homepage, search, tag, pagination and route metadata can be applied as supported pages load. |
| Generate enabled structured data from store content | Product, organization and other eligible JSON-LD output is assembled using current page and configured store information. |
| Reuse cached sitemap files and rebuild them when needed | The sitemap component can serve existing output and regenerate it after relevant changes or cache expiry. |
| Mark sitemap information outdated after catalogue updates | Supported events refresh sitemap cache state when eligible store content changes. |
| Queue changed public URLs for IndexNow submission | When the integration is enabled, eligible content changes add addresses to a pending queue. |
| Submit queued IndexNow URLs in manageable batches | The scheduler processes selected stores' pending addresses and records submission results. |
| Retry failed IndexNow requests | Unsuccessful queued URLs can be submitted again instead of being silently discarded. |
| Queue missing SEO content on supported content changes | When configured, new or edited items missing selected fields can be added to the AI content work queue. |
| Generate queued SEO content through Cron Manager | An optional scheduled task processes queued content in bounded batches using a configured AI provider or template mode. |
| Protect merchant-written text according to generation settings | The generator can fill missing values rather than replacing existing descriptions unless regeneration was chosen. |
| Queue product tags after product changes | Enabled automation adds eligible new or edited products to the language-specific tag queue. |
| Preserve manually entered tags during generated updates | Ownership of generated tags is tracked so updating them does not intentionally remove store-owner tags. |
| Refresh generated product tags periodically | An optional scheduled job can queue active items to bring their generated tags up to date. |
| Generate related-product suggestions after product changes | When enabled, new and updated products are placed in the related-product work queue. |
| Exclude unavailable products from automatic suggestions | The generator skips disabled, unavailable and out-of-stock items when choosing candidates. |
| Remove stale generated related-product matches | Optional maintenance rechecks suggested relationships without deleting manually added ones. |
| Process approved image-organization work in the background | Optional work can rename poor image filenames or organize folders in small resumable batches. |
| Schedule image filename and missing-file audits | Optional maintenance reports image quality or missing references without automatically deleting originals. |
| Record image changes for potential rollback | Supported image operations save their history and reference changes so eligible operations can be undone. |
| Generate WebP derivatives on demand | Compatible resized-image requests create and reuse WebP files without converting the full image library in advance. |
| Avoid conflicting with Journal3 image optimization | When a supported Journal3 image pipeline is detected, HuntBee can defer its WebP processing. |
| Mark generated merchant feeds outdated after catalogue changes | Relevant product, category and manufacturer changes flag affected feed snapshots for a future update. |
| Refresh generated merchant feeds through scheduled batches | When enabled, cron refreshes eligible existing feed snapshots without automatically publishing new unused feeds. |
| Record missing-page requests for later review | The Broken Link Manager can capture qualifying 404 URLs with request counts and available referrer information. |
| Clean up old low-value broken-link records | Configured retention rules can reduce accumulated link-tracking records and database storage. |
| Redirect configured disabled catalogue pages | When a supported unavailable page has a replacement assigned, shoppers can be sent to its working destination. |
| Run background tasks according to their schedule and limits | The central scheduler checks task frequency and batch settings rather than processing every SEO task on every call. |
| Record the health and recent status of SEO jobs | Scheduler diagnostics show when automatic calls arrive and help identify missed or failed jobs. |
| OPENCART | |
| Compatibility | 4.1.0.4 |
| SUPPORT | |
| Support Policy | Standard support covers reasonable assistance with installation, configuration and confirmed HuntBee SEO Suite issues. Extensive troubleshooting, repeated store-specific investigation, third-party conflicts and customization may require paid technical support. If SEO Suite itself contains a defect, HuntBee will fix it under standard support. If investigation shows that the issue is caused by a third-party extension, theme, customization, server configuration, or modification outside HuntBee SEO Suite, further investigation or compatibility work may require paid support. |
| VERSION : 4.6.1 | DATE RELEASED: 16 Oct 2026 |
| |
| VERSION : 4.5.18 | DATE RELEASED: 15 Oct 2026 |
| |
| VERSION : 4.5.17 | DATE RELEASED: 09 Sep 2026 |
| |
| VERSION : 4.4.15 | DATE RELEASED: 03 Sep 2026 |
| |
| VERSION : 4.4.14 | DATE RELEASED: 29 Aug 2026 |
| |
| VERSION : 3.14.8 | DATE RELEASED: 14 Aug 2026 |
| |
| VERSION : 2.1.3 | DATE RELEASED: 14 Aug 2026 |
| |
| VERSION : 2.1.1 | DATE RELEASED: 02 Aug 2026 |
| |
| VERSION : 1.0.0 | DATE RELEASED: 02 Aug 2026 |
| |
