CatCode SEO Pack — SEO Module for OpenCart 2.3, 3.x and 4.x

CatCode SEO Pack for OpenCart 2.3, 3.x and 4.x — all of a shop’s SEO in one module: an XML sitemap, structured data for Google, a canonical on filters, meta tag templates, redirects with a 404 log, bulk SEO-URL generation by transliteration, and a catalogue audit.

XML sitemap

An index plus separate files by type, with product images, and hreflang alternates for multilingual shops as well (on OpenCart 3 and 2.3 since version 2.2.0, when the language is part of the page address). Rows are read page by page, and the sitemap is split into separate part files, so a catalogue of 100,000 items doesn’t assemble a 30-megabyte string in memory. Only what the shopper can see goes into the map: enabled items in the current shop, once their availability date has arrived.

Structured data for Google

JSON-LD with Product and Offer — name, SKU, brand, image, and exactly the price the shopper sees: with any promotion applied, in the storefront currency, with stock availability. AggregateRating is only added when there are approved reviews: a made-up rating is the fastest way to lose a rich snippet. Plus BreadcrumbList, Organization with social profiles, and WebSite with a search box on the homepage.

Redirects and the 404 log (Pro)

Every address that isn’t found lands in the log along with the referrer and a hit counter — rules are written from facts, not guesswork. A log row turns into a redirect with one click, and wildcard masks for a whole branch (blog/*) are supported. The response is returned before the shop even starts building a page, so the rule also works for addresses that no longer exist in the catalogue.

SEO URLs by transliteration (Pro)

Bulk generation of clean URLs using the Ukrainian KMU 55/2010 transliteration standard, separately for each language: the Ukrainian page gets a Ukrainian link, the English one an English link. OpenCart 2.3 stores one keyword per product for all languages, so there the link is shared. On OpenCart 4, the run also creates the missing route rows for languages that lack them — those missing rows are usually exactly why a clean URL on a second language silently returns the home page.

Catalogue audit (Pro)

Duplicate titles and descriptions, empty and overly long descriptions, products with no clean URL, no image, or a too-short description — each issue comes with a count and the first ten pages that need fixing.

Three builds: OpenCart 2.3, 3 and 4

Each OpenCart version gets its own build, not a “compatible” compromise. The functionality is the same; the difference is only where the platform differs: in stock OpenCart 3 and 2.3 the language is stored in the session, not the address, so all language versions of a page share one address and the sitemap is single-language. When the language is in the address (on OpenCart 3, ocStore SEO Pro or a language-prefix extension such as /ru/; on OpenCart 2.3, a language-prefix extension), the module detects it since version 2.2.0 and adds hreflang with x-default to the sitemap and to the page <head>. The clean URL keyword must be unique within the shop rather than the language in OpenCart 3, and in OpenCart 2.3 there is one keyword for all languages. Redirects in OpenCart 3 and 2.3 are wired through the generic controller event, because the pre-actions of these versions provide no events.

Meta tag templates

Meta tags are described with a formula using placeholders — product name, category, manufacturer, model, SKU, price, an attribute or option value, shop name, year, page number. In Pro, rules can be narrowed by category, manufacturer and language with a managed priority. Generation runs in batches with a progress bar (up to 200 rows per run without a key); in Pro every run is stored in history and rolls back with one click.

Why a shop needs this

SEO for OpenCart is usually pieced together from four or five separate modules: a sitemap from one author, structured data from another, redirects from a third. They fight over the same spots in the template, and half of it breaks after a shop update.

Here it’s all gathered into one module with a single settings screen — and, crucially, a single point of responsibility for compatibility.

How it works, step by step

1. You turn on the blocks you need: sitemap, structured data, redirects, meta tag templates, URL transliteration.

2. You set title and description templates from product variables — for the whole catalogue at once.

3. You run a catalogue audit (Pro): the module shows empty, overly long and duplicate meta tags, and products with no clean URL, no image or a too-short description.

4. You fix what was found, and keep an eye on the 404 log (Pro) afterwards to set redirects for real traffic losses.

Under the hood

The module doesn’t patch the core — everything runs through OpenCart’s standard events, so a shop update doesn’t wipe out its changes, and removing it leaves no trace in the files.

The sitemap is generated on the fly on every request, rather than a static file you’d have to rebuild by hand after every catalogue change.

How to install

1. Upload the archive via “Extensions → Installer” and install the module.

2. Turn on the blocks you need — not necessarily all at once.

3. Run a catalogue audit and look at the list of issues.

4. Add the sitemap to Search Console.