Category: User Manual

AuctionX – PrestaShop Auction Module Complete User Manual

The Knowband PrestaShop Auction Module (also called AuctionX) allow store owners to run live auctions on products and on individual product variants. This manual walks store admins through installing the PrestaShop auction extension, setting it up, creating auctions, and handling live bidding through to the winner’s order.

1. Introduction to the PrestaShop Auction Module

The PrestaShop Auction Module is a product bidding system for PrestaShop. With it you can run timed auctions, accept customer bids, keep a bid history, and move the winning bid into a normal order.

It includes a back office auction dashboard, a storefront auction listing, live countdown timers, customer bid history, an optional watchlist, winner selection, and auction email notifications.

How the PrestaShop Bidding System Works

  1. The admin creates an auction for a product or a product combination, sets the bidding rules and dates, and publishes it.
  2. Customers open the auction, place bids while it is running, and track results from their account.
  3. When the auction closes, the module picks the winners automatically, or the admin picks them by hand.
  4. A winner places the order at the winning amount before the set deadline.

2. Key Features of the PrestaShop Auction Addon 

These are the main features of the module. Together they let a merchant run controlled online auctions in PrestaShop, manage who takes part, choose winners, and finish the sale.

Product Auctions and Variant Bidding

Create an auction for any active product and, if needed, for one specific combination. The form covers starting price, bid increment, optional maximum bid, reserve price, waiting time between bids, visibility options, scheduling, and closing rules.

Live Bidding on the Product Page

Logged in customers bid straight from the product page. The module checks the minimum amount, bid increment, maximum bid, bidder status, stock, and the minimum time between bids. The live view updates through polling, shows a countdown, and displays the statistics the admin has chosen.

Auction Scheduling and Auto Extension

An auction can stay in Draft or be published to start at a later time. With Auto Extension on, a bid placed within the trigger period pushes the end time back.

Winner Selection and Order Completion

Winner Selection Mode can be Auto or Manual. In Auto mode the module ranks each bidder by their highest bid, leaves out blocked bidders, applies the reserve price, and settles ties in favor of whoever reached the amount first. In Manual mode the admin chooses winners from Live View once bidding has ended. Each winner gets an order deadline and a private order link under My Bids. 

Watchlists and Auction Announcements

With the watchlist turned on, customers can save auctions to My Watchlist. Watchers can be emailed when other users bid and when an auction starts, as long as the matching email template is enabled.

Dashboard and Email Notifications

The dashboard has configurable KPI widgets, charts, and tables of recent activity. The Email Templates page holds subjects and bodies in several languages for bid confirmations, winning bids, auction announcements, order events, bidder blocks, cancellations, and other events.

3. Installing the PrestaShop Auction Module

Install and activate the module in the PrestaShop back office before you create any auction. Follow these steps in order.

  1. Sign in to the PrestaShop Admin Panel.
  2. Go to Modules > Module Manager.
  3. Choose the upload option and upload the Knowband PrestaShop Auction Module archive.
  4. Install the module and wait for PrestaShop to finish.
  5. Go to Sell > Knowband PrestaShop Auction Module. During installation the module creates its database tables, default settings, email templates, CRON token, hooks, and back office tabs.
  6. Open General Settings, enable the module, and set the storefront options.
  7. Set up the CRON job shown on the General Settings page if you want scheduled status changes, automatic winner processing, and deadline processing to run without anyone visiting a page.

Uninstalling the module only removes its back office menu entries. Auction data, bids, winners, watchlists, email templates, logs, dashboard layouts, and settings stay in place, and they are still there if you reinstall.

4. Opening the Module in the Back Office

After installation, every auction function is under Sell > Knowband PrestaShop Auction Module. The pages are:

  • Dashboard
  • General Settings
  • Customization Settings
  • Email Templates
  • Auctions
  • Winners List
  • Other Modules

General Settings, Customization Settings, and Email Templates are also reachable from the in page Settings menu.

5. Admin Panel Overview

The admin area is split into separate sections, so settings, auction work, notifications, reports, and winner records can each be handled on their own.

Dashboard

Shows auction KPIs, charts, and recent activity for the current shop, so you can check how things are going without opening each auction. Widgets can be turned on or off, reordered, and resized.

General Settings

Turns the bidding system on or off and decides where auction summaries show on the storefront. It also holds the CRON URL and an example server crontab entry.

Customization Settings

Sets the colors used for auction boxes, buttons, progress bars, watchlist controls, body areas, and status badges.

Email Templates

Lists the fixed notification templates with their codes and status. Every template has one translation row for each installed language, with an editor for the subject and a rich text body. These emails keep admins, bidders, watchers, and winners informed during the auction.

Auctions

The place to view the auction list, apply filters, add or edit auctions, open Live View, block bidders, select winners, and run lifecycle actions.

Winners List

A read only history of closed auctions with winner and order details. Auctions that closed without a winner are included.

Other Modules

A catalog of other Knowband extensions. It has no auction settings.

6. PrestaShop Auction Module Configuration

This section covers each configurable area. Check these values before you publish an auction, because they affect bidding rules, what shows on the storefront, notifications, and winner processing.

General Settings

Enable Module. The main switch for the module. Leave it on No while you are still preparing things if you do not want customers to see auctions. Choose Yes to turn on storefront and bidding behavior. Options: Yes or No. Default: No.

Enable Watchlist. Allows logged in customers save auctions and come back to them. Turn this on after enabling the module. Options: Yes or No. Default: No. Customers must be logged in.

Show Recent Auctions on Home Page. Adds a block of recent auctions to the home page for extra exposure. Options: Yes or No. Default: No.

Number of Recent Auctions. Sets how many auctions the home page block lists. Enter a whole number from 1 to 20. It applies only when Show Recent Auctions on Home Page is Yes. Default: 5.

Display auction info on Category page. Adds auction status to product cards on category pages, so shoppers can spot products that are in an auction now or soon. Options: Yes or No. Default: No. The badge appears on category pages only, not on every page that reuses a product list template.

CRON URL. The server calls this URL to run scheduled auction tasks, which matters for auctions that must move forward without page visits. The page shows a generated URL and a crontab line that runs every minute and sends a silent curl request to that URL. Use Copy to copy either one. Regenerate CRON token makes the old URL invalid, so update your server crontab right after using it. The URL contains a secret token, so keep it private.

Customization Settings

These settings allows you match the auction look to your store theme. Every field is a color input, is required, and must be a six digit hex code such as #ffffff.

Setting What it controls Default
Header Background Color Auction header background #2456e7
Header Text Color Text in the auction header #ffffff
Button Color Auction action buttons #2456e7
Button Text Color Text on auction buttons #ffffff
Progress Bar Color Bidding progress bar #2456e7
Add to Watchlist Color Watchlist control #2456e7
Box Body Background Color Auction box body #ffffff
Box Text Color Text in the auction box #1f2430
Live / In Progress Badge Color Live status badge #dc2626
Upcoming Badge Color Upcoming status badge #4f46e5
Ended / Expired Badge Color Ended and expired badges #64748b

Click Save to apply the colors. Blank or wrongly formatted values are rejected.

Managing Auctions

The Auctions section is where you create, set up, publish, watch, and manage each auction from start to finish.

Auction List

The list allow you search, filter, and inspect auctions and run actions on them. Its columns are ID, Reference Number, Auction Title, Product, Status, Starting Price, Start Date, and End Date.

The Status filter offers Draft, Scheduled, Ongoing, Inactive, Completed, Winner Selected, Order Pending, Order Placed, Winner Expired, Reassigned, and Cancelled.

Available actions are Add New Auction, View, Edit, Publish, Duplicate, Pause, Resume, Force Cancel, Delete, and Bulk Delete, depending on the auction’s current status. Ongoing auctions cannot be deleted. Bulk Delete skips ongoing rows and tells you which IDs it skipped.

Basic Information

This part names the auction, links it to a product, sets its starting state, and defines the schedule and storefront behavior.

  • Auction Title. Required, up to 30 characters, and unique across the whole store setup.
  • Reference Number. Required, up to 64 characters, and unique. Use letters, numbers, hyphens, and underscores.
  • Select Product. Pick an active product. You may also pick a combination for variant bidding.
  • Auction Status. Draft or Publish. Publishing gives Scheduled status if the start time is ahead, and Ongoing status if the start time has already come.
  • Hide Product Price. Hides the normal product price while the auction box is shown.
  • Hide Add to Cart Button. Hides the normal Add to Cart button for the auction product.
  • Continue Selling. Decides whether normal selling can go on while the auction is set up.
  • Starting Date/Time and End Date/Time. Enter these in the form’s Asia/Kolkata timezone. The start cannot be in the past. The end must come after the start and, when editing, must be in the future.

Bidding Configuration

These are the money and participation rules that decide which bids are accepted and what bidders can see.

  • Starting Price. Required and above zero. The first bid must reach this amount.
  • Bid Increment. Required and above zero. Each later bid must be at least the current highest bid plus this amount.
  • Maximum Bid. Optional. Must be above the Starting Price. Once it is reached, no more bids are accepted.
  • Minimum Time Between Bids (minutes). Optional whole number. Sets a waiting period between bids from the same customer.
  • Reserve Price. Optional and hidden from bidders. It must be at least the Starting Price and no more than the Maximum Bid. Automatic winner selection only works if the reserve price is met.
  • Show Highest Bid. Allow customers see the current highest bid.
  • Show Bid Rank. Allow a bidder see their own rank.
  • Show Total Bids. Shows the total number of bids.
  • Show Bidder Information. Decides whether bidder details are shown.
  • Show Last Bid Time. Shows when the last bid was placed.

All the visibility switches use Yes and No.

Auction Extension

Auction Extension guards the final stretch of an auction by letting late bids move the end time.

  • Enable Auto Extension. Turns on extension when a bid comes in inside the trigger window.
  • Extension Trigger (minutes). Required and above zero when auto extension is on. This is the window before the scheduled end in which a bid causes an extension.
  • Extension Duration (minutes). Required and above zero when auto extension is on. This is how much time gets added when the trigger is met.

Winner Configuration

This part sets how winners are chosen and how long they have to buy.

  • Winner Selection Mode. Auto ranks bids and creates winners by itself. Manual lets you pick winners from Live View once bidding ends.
  • Number of Winners. Default 1. Must be at least 1 and cannot be more than the available stock. It is hidden or ignored in Manual mode.
  • Winner Order Deadline. Enter a number (default 48) and choose Hours or Days. Winners must order before this deadline.

Dashboard

The Dashboard gives a quick view of auction activity and results through KPIs, charts, and recent activity tables.

Use the period selector to choose Last 7 days, Last 30 days, Last 3 months, Last 6 months, or Last 12 months. Save Layout and Reset Layout are available.

KPI widgets: Total Auctions, Upcoming Auctions, Ongoing Auctions, Completed Auctions, Order Pending Auctions, Orders Placed, Total Bids, and Unique Bidders.

Charts: Auction Status, Auction Statistics, Bid Statistics, and Conversion Statistics.

Tables: Recent Auctions, Recent Bids, Recent Orders, Top Products, and Top Bidders.

Drag widgets to reorder them, switch them on or off in the Widget Library, and set their column span from 1 to 12. KPI values show the current state of the shop. The period selector affects the period based charts and the Top Bidders data.

Email Templates

Email Templates controls which messages go out at key points in an auction. Enable the ones you need and edit the text for each installed language.

The first grid shows ID, Title, Code, and Status, with a Manage Translations option. Status is Disabled or Enabled. All templates start out disabled, so turn on each notification your store should send.

The translation grid shows Language, Subject, Enabled or Disabled status, and Edit. The editor has a Subject, a rich text Body, a placeholder legend, and Save. The subject is required and limited to 255 characters. The body is required.

Built in notifications:

  • Email to Admin on Bid Place
  • Email to Customers on Bid Place by Other Users
  • Email to Watchers on Bid Place by Other Users
  • Email to Watchers on Auction Start
  • Email to Customer on Winning and Place Order
  • Email to Other Customers Who Placed a Bid but Did Not Win
  • Email to Admin on Order Place
  • Email to Admin on Auction Close or No Bid
  • Email to Admin on Auction Close and Winner Selected
  • Cancelled Auction: Notify Users Who Placed a Bid
  • Email to Users on Block/Unblock Bidding on Any Auction
  • Email to Admin on Maximum Bid Reached

Use only the placeholders listed in the editor’s legend. If a translation is missing, the shop default language is used. Each email attempt is saved in the email log. If an email fails, the bid, order, or auction step still goes through.

Winners List

The Winners List is a read only record of closed auctions with their winners and order details. Columns: Auction ID, Reference Number, Product, End Date, Actual End Date, Winner, Winning Bid, Order Status, Order Deadline, and Order Reference. Order Status can be Pending, Placed, Expired, or Reassigned.

An auction with no winner appears with empty winner fields and a no winner label. Use View Auction to open the related auction.

7. Field Types and Options

This summary shows what kind of input each part of the module uses.

  • General Settings: Yes/No switches and one number field.
  • Customization Settings: color inputs.
  • Auction form: text fields, a product and combination picker, status choice, date and time inputs, numeric price and duration fields, and Yes/No switches.
  • Winner Configuration: Auto/Manual choice, numeric winner count, numeric deadline, and an Hours/Days choice.
  • Lists: searchable, filterable tables with status, date, product, and reference filters where offered.
  • Dashboard: draggable widgets, an enable/disable library, a period selector, and column span controls.
  • Email Templates: status toggle, language table, text subject, rich text body, and a Save button.

8. Admin Actions

Admin actions either change an auction’s state or help you manage customers and winners. Which actions you see depends on the auction’s status.

  • Save stores settings, colors, dashboard layouts, or email translations, depending on the page.
  • Publish moves a Draft to Scheduled or Ongoing.
  • Pause moves a Scheduled or Ongoing auction to Inactive. Resume brings an Inactive auction back.
  • Force Cancel cancels an Ongoing auction.
  • Duplicate makes a copy of an auction.
  • Delete removes an eligible auction. Ongoing auctions are protected.
  • Bulk Delete deletes the eligible selected rows and skips Ongoing ones.

In Live View you can Refresh, Block or Unblock a bidder, Pause, Resume, Cancel Auction, Edit Auction, and select manual winners where it applies. In Manual mode, the order in which you select bidders sets their winner rank.

9. Storefront Behavior: What Customers See

This section describes the customer side of the PrestaShop bidding system: bidding, auction listings, account pages, and limits on winning orders.

Product Page Auction Box

The product page can show an auction box for auctions that are scheduled, ongoing, won, lost, no bid, no winner, ended pending, or inactive. For an ongoing auction, depending on your settings, the box can show the countdown, the current or next minimum bid, a progress bar, the bidder count, rank, total bids, last bid time, a bid field, the Place Bid button, a watchlist control, a blocked bidder message, and a maximum bid message.

Bidding Rules for Customers

Customers must be logged in to bid, and guests see a login prompt. A customer cannot right away outbid their own bid, and blocked bidders cannot bid. Stock levels and PrestaShop out of stock rules also affect whether a bid is accepted. The page polls every 10 seconds by default to refresh status, timing, minimum bid, statistics, winner state, and extension notices.

Auction List Page

The public Auction List has tabs for All, Upcoming, In Progress, and Expired. The Expired tab is optional. Ended cards are greyed out and do not link to the product. The home page block and category badges follow their General Settings switches.

Customer Account: My Bids and My Watchlist

The customer account has an Auction entry that opens My Bids. My Bids shows bid history, best bid, result, ranking where allowed, and a Place Your Order or View Order action. When the watchlist is on, My Watchlist lists scheduled and ongoing auctions, and Include past/cancelled shows older watched ones.

Quantity Limit for Winning Orders

Products bought at a winning price are limited to a quantity of 1 in the cart and at checkout. If the module corrects a higher quantity, it shows a notice explaining why.

10. Multi-language, Multi-store, and Currency Behavior

Auction, bid, watchlist, winner, and dashboard data belong to a shop. In single shop context, admin lists show only the current shop. In the All Shops context, nothing is restricted. Auction reference numbers and titles must be unique across all shops.

Email subjects and bodies are stored per language. Languages that exist at install time are seeded, and a missing translation falls back to the shop default language. A language added after installation may not get translation rows automatically.

Auction amounts are stored and compared in the shop default currency. Storefront values are converted to the customer’s chosen currency, while admin notification emails use the shop default currency. The auction form and admin dates use Asia/Kolkata time, and stored dates use UTC.

11. CRON Job and Automated Tasks

The CRON job handles time based work, so scheduled starts, closings, winner selection, and expired winner deadlines are processed even when nobody visits the store or admin pages.

Call the CRON web URL every minute with the token shown on the page. Each run can:

  1. Move due Scheduled auctions to Ongoing and notify watchers.
  2. Close expired Ongoing auctions.
  3. Select winners for Auto auctions.
  4. Process expired winner deadlines and reassign or expire winner slots.

Each run handles at most 200 records. Product views, bids, polls, and the Auctions list also do some limited just in time expiry processing, but CRON is needed for auctions that get no page visits.

12. External Services and API Settings

The module needs no external API connection. The CRON URL is an HTTP endpoint on your own PrestaShop installation, not an outside service. There are no external credentials to enter. Keep the token private, and regenerate it if it may have been exposed.

13. Troubleshooting the PrestaShop Auction Module

If an auction, bid, email, or winner order is not working as expected, check the causes and fixes below. If the problem remains, contact Knowband support.

The auction does not show on the storefront

Possible cause: The module is disabled in PrestaShop, Enable Module is No, or the auction is in Draft, is inactive, or belongs to a different shop or product combination. Fix: Enable the module in PrestaShop and in General Settings, check the auction status and dates, and confirm the selected product or combination.

Customers cannot use the watchlist

Possible cause: Enable Watchlist is No, or the customer is not logged in. Fix: Turn on the setting and test while logged in.

Scheduled auctions or winners are out of date

Possible cause: The CRON URL is not being called, the token was regenerated but the server job was not updated, or the module is disabled. Fix: Copy the current URL from General Settings, update the server crontab, run it every minute, and make sure Enable Module is Yes.

Email notifications are not sent

Possible cause: The template or the language translation is disabled or incomplete. Fix: Enable the template, edit the translation, make sure the Subject and Body are filled in, and look at the email log and PrestaShop logs. Email failures do not block bidding or order processing.

A bid is rejected

Possible cause: The bid is under the starting price or required increment, the maximum bid was reached, the bidder is blocked, the waiting period has not passed, stock rules reject it, or the auction is no longer ongoing. Fix: Review the auction’s bidding settings and status. The customer must be logged in and cannot immediately outbid their own bid.

A winning customer cannot place the order

Possible cause: The winner token or deadline is invalid, the product or combination does not match, the paid amount is different from the winning amount, or the cart quantity is not exactly 1. Fix: Have the customer open My Bids, use the active Place Your Order link before the deadline, pick the right product or combination, and keep the quantity at 1.

Category auction badges are missing or look wrong

Possible cause: The category display switch is off, the auction is not live or upcoming, or a heavily customized theme changes the product card selectors. Fix: Enable Display auction info on Category page, check the auction status, and review the theme’s product list markup if the styling is off.

14. Best Practices for Running PrestaShop Auctions

These tips help you avoid setup mistakes, keep automated tasks running, and give customers a steady auction experience.

  • Keep Enable Module off while you prepare auctions, then test one full auction before opening more.
  • Use unique, clear Reference Numbers and short Auction Titles.
  • Double check start and end times in the Asia/Kolkata admin timezone.
  • Pick a Bid Increment that suits the product’s value, and review Maximum Bid and Reserve Price together.
  • Turn on only the statistics and bidder details you want customers to see.
  • Set up CRON before publishing scheduled auctions.
  • Enable and review each email template in every language your store uses.
  • Treat the CRON URL as a secret and regenerate it if it leaks.
  • Test a winning order with the right product, combination, winning amount, and a quantity of 1.
  • Use Live View to watch for odd bidding, block bidders when needed, and keep a record of manual winner choices.
  • Update the module to the latest Knowband release for security and compatibility.

15. Conclusion

The Knowband PrestaShop Auction Module is a full bidding extension for scheduled product auctions, live bidding, customer bid history, watchlists, winner selection, and winner order handling. General Settings controls activation and storefront placement, Auctions defines each product auction, Customization Settings controls the look, Email Templates controls notifications, and the Dashboard and Winners List help with daily auction management.

 

Prestashop Point of Sale Module User Manual

Knowband PrestaShop Point of Sale Module is an all-in-one PrestaShop Multiple Store POS module that is specially designed for merchants who have one or multiple physical stores in addition to their online store. The Knowband PrestaShop POS module comes in handy for such merchants as it integrates functionalities like store-level sales, stock management, and employee management directly into their PrestaShop back-end, making it a viable PrestaShop POS Module Alternative to other POS systems.

The module is built around Multi-Outlet POS approach. Every physical location, which is called an outlet in admin terms, is configurable on its own using its own unique address, currency, language, and sales regulations, but all outlets will still work under one single PrestaShop website. Thus, the Prestashop Point of sale Addon is appropriate for Multi-Outlet Retail business models including but not limited to boutique chains, franchise counters, pop-ups, and warehouses with retail activity in addition.

Knowband Point of Sale is not a payment method in itself. It records POS sales through its own internal order flow and always uses a fixed internal payment method for POS transactions; the order status applied once a sale is paid is configurable in Settings, and shipping, discounts, and commission are layered on top of that flow.

1.1 What the module includes

The Prestashop Point of Sale Module includes functionalities like dashboard, multi-outlet creation, commission tracking, inventory sync and many more.

  • Sales dashboard module for PrestaShop: a customizable, draggable widget grid for reviewing outlet performance, oversold orders, and sales trends
  • Outlet management: creating, editing, and activating individual outlets, each with its own address, currency, language, and override rules
  • PrestaShop sales agent management: assigning PrestaShop employees to outlets as cashiers, and flagging specific employees as POS managers
  • Commission tracking: recording salesperson commission per sale, with reporting broken down by employee and outlet
  • POS Customer Management for PrestaShop: Searching, creating and configuring guest check-out behavior based on outlet
  • PrestaShop Barcode Scanner Module: Matching the barcodes entered through the scanner with a user configurable barcode field such as EAN13, UPC, ISBN, MPN, and Reference
  • Inventory Synchronization for PrestaShop: Maintaining the correct stock visibility while assigning, selling and returning products in various outlets
  • Offline order module for PrestaShop: queuing sales when the connection drops and syncing them automatically once connectivity returns, using idempotency keys to prevent duplicate orders
  • PrestaShop POS with receipt printing: generating printed receipts through standard browser-based HTML printing, with configurable discount line display
  • Return and refund POS trail: order-level visibility into paid amounts, order status, and oversold flags so that returns and refunds can be traced back to the original outlet and salesperson
  • PWA-style panel access: a public POS panel URL, optionally customised, that can be opened in a browser tab or installed as an app-like shortcut on a desktop device

2.0 Requirements and Compatibility for Prestashop Point Of Sale Addon

2.1 PrestaShop compatibility

The module is compatible for Prestashop 1.7, Prestashop 8.x. and Prestashop 9. x.x. Store owners can use it feel free, in case if you face any issue, our team is always available at supprot@knowband.com

2.2 Module dependencies

The Multi-Outlet POS system creates and relies on its own database tables for outlets, product-to-outlet assignment, stock allocation, discount logs, offline order queues, and commission records, in addition to standard PrestaShop tables for employees, customers, carriers, and orders.

2.3 Required permissions

The administrator installing or configuring the module needs valid PrestaShop back-office access with rights to manage modules, products, carriers, customers, employees, and orders. Outlet management in particular touches products and carriers directly, so an store adins without those permissions will not be able to complete outlet setup.

3.0 Installation and Activation of Prestashop Multi Outlet POS System

3.1 Installing the module

Install Knowband PrestaShop Point of Sale from the PrestaShop module list in the back office, the same way any standard PrestaShop module is installed. 

  • Navigate to Module Manager > Modules
  • Click on the Upload option and upload Knowband Prestashop Point of Sale
  • After installation, click on configure, this will redirect you to the configuration module.

3.2 Activation

Installing the module is not the same as activating it for live sales.  Enable the module from the Enable POS module Tab.

4.0 Module Tabs Structure in POS 

After installation, you will see the module Knowband Prestashop Point of Sale under the PrestaShop SELL menu. 

  • Dashboard
  • Settings
  • Outlets
  • Employees
  • Orders
  • Reports
  • Receipt Settings
  • Other Modules

5.0 Admin Panel Module Configuration in Prestashop POS System

5.1 Dashboard

The Dashboard is the landing page of the sales dashboard module for PrestaShop and gives the administrator an outlet-scoped overview of POS activity as soon as they open the Knowband Prestashop Point Of Sale menu.

5.1.1 Purpose

  • Review recent sales activity and trends across outlets.
  • Check individual outlet performance.
  • See oversold order counts, which relate directly to inventory sync accuracy.
  • Open the POS panel quickly from a single screen.
  • Customise the widget layout to match how the store owner or manager wants to review data.

5.1.2 Fields and controls

  • Outlet selector: switches the dashboard view to a specific outlet or to all accessible outlets, central to multi-outlet management
  • Period selector: changes the reporting period used by the dashboard widgets
  • Widget customise controls: allow enabling, rearranging, and saving the widget layout
  • Oversold orders quick link: opens the Orders screen filtered to orders flagged as oversold

5.1.3 Buttons and actions

  • Open POS: opens the POS panel in a new browser tab
  • Reset dashboard layout: returns the widget arrangement to the default layout
  • Demo mode toggle: switches the dashboard to a demo dataset instead of live data, useful for screenshots or training

5.1.4 Important behavior

  • Widget data loads through AJAX rather than a full page reload.
  • Dashboard content is always outlet-specific once an outlet is selected.
  • The widget layout and demo mode setting are saved per shop, so multi-shop PrestaShop installs keep separate dashboard preferences.

5.2 General Settings

Settings is the main configuration area for the module’s behaviour and is organised into five sub-tabs: General, Product, Customer, Payment, and Shipping.

5.2.1 General

It controls the core operational behaviour of the PrestaShop POS module: whether it is active, how discounts and offline mode work, panel colours, and the public panel URL.

  • Enable POS module: turns the entire module on or off; when disabled, the POS panel becomes unavailable
  • Display voucher input on the cart panel: shows or hides the voucher field in the POS cart
  • Cart panel notice text: optional message shown above the POS cart
  • Allow manual discounts at the till: enables cashier discounting
  • Max discount %: maximum manual discount percentage a cashier may apply
  • Max discount fixed amount: maximum fixed discount amount a cashier may apply
  • Panel accent colour: main colour used by the POS interface
  • Panel gradient colour: secondary colour for the POS background gradient
  • Button fill colour: main colour for action buttons in the POS panel
  • Button hover colour: button hover state colour
  • Enable offline mode: activates the offline order module for PrestaShop, allowing sales to be queued while connectivity is lost and synced automatically once it returns
  • Idempotency retention window (days): number of days to retain de-duplication keys for offline sales, preventing the same offline sale from being recorded twice
  • Custom Sell-page URL path: This option allows the POS panel use a custom public URL path, such as /pos/, and supports PWA-style shortcut installation

Note: Changing the custom panel path can break already-installed desktop app shortcuts, because an installed shortcut points to the URL it was created with.

5.2.2 Product

Controls how products are searched, displayed, assigned, and managed in the POS, and is the main configuration point for both the barcode scanner module for PrestaShop and the inventory sync module for PrestaShop.

  • Maximum characters shown per product name: truncates long product names in the POS interface
  • Low stock alert threshold: flags low stock when allocated stock falls to or below the chosen value
  • Search result cap (products / customers): maximum number of rows returned in product or customer searches
  • Product search fields: selects which product fields are text-matched in POS search, from Name, Reference, EAN, ISBN, UPC, MPN, and Tags
  • Barcode field to match: selects which barcode field the barcode scanner module for PrestaShop uses when scanning or typing a code, from EAN13, UPC, ISBN, MPN, and Reference
  • Auto-drop disabled products from an open cart: removes disabled or de-assigned products from an open cart automatically
  • Flag products that have combinations: marks products with variants so the cashier knows a choice is required before completing the line
  • Enable POS status on new assignment: makes newly assigned products immediately available for POS sale
  • Show original price alongside a discount: displays both original and discounted pricing for price-reduced products
  • Auto-assign new or edited products to outlets: automatically assigns products to active outlets, supporting the inventory sync module for PrestaShop
  • Default/starting category ID: category the POS panel opens to by default; set to 0 to use the shop root category
  • Show product image thumbnails in search results and cart: displays small product images
  • Show available quantity in search rows: displays outlet stock in product search results
  • Show SKU/reference in search rows: shows product reference text under the product name

5.2.3 Customer

Handles the global portion of PrestaShop POS customer management. Most customer-related configuration now lives at the outlet level rather than here.

  • Let cashiers pick customer groups on creation: shows a customer group selection box when a cashier creates a customer from the panel

5.2.4 Payment

Controls the payment status applied to POS sales and the salesperson commission rules that drive commission tracking.

  • How POS sales are paid: a display-only field explaining that all POS sales use one fixed internal payment method
  • Status applied once paid: the order status assigned once a sale is marked paid
  • Enable salesperson commission tracking: turns commission calculation on or off for commission tracking
  • Commission rate (% of order total): percentage of each sale total used for salesperson commission

5.2.5 Shipping

Controls shipping behaviour for POS orders, including which carriers a cashier can offer.

  • Allow shipping a POS sale to the customer: enables shipping at the POS
  • Carriers available at the till: multi-select list of all carriers a cashier may choose from
  • Pre-selected carrier: default carrier chosen when a cashier enters shipping mode

5.3 How to add Multi Outlets in Prestashop Point of Sale

Outlets are the core of Multi-Outlet Retail configuration. This section covers the outlet listing, the add and edit outlet form, and the outlet products panel used for inventory sync.

5.3.1 Outlets listing

Lists every outlet configured for the current shop and is the entry point for outlet management.

Listing columns: ID, Store/outlet label, Post code, Country, Override Payment, Override Shipping, Status

  • Edit: opens the outlet configuration form
  • Status toggle: enables or disables the outlet
  • Open POS: opens the POS panel for that context in a new tab
  • Add new outlet: creates a new outlet record

5.3.2 How to Add an Outlet using PrestaShop Point of Sale System

Creates or edits a single outlet, defining its physical profile plus its local payment, shipping, and guest checkout rules.

Core fields: Outlet is active, Store/outlet label, Address Line 1, Address Line 2, City, Postal code, Country, State, Contact phone number, Currencies accepted at this outlet, Pre-selected currency at the till, Languages available at this outlet, Pre-selected language at the till

5.3.3 Payment override group

  • Override Payment Settings: turns the outlet payment override on or off
  • Status applied once paid: order status assigned to paid POS sales at this outlet
  • Enable salesperson commission tracking: enables commission tracking at the outlet level
  • Commission rate (% of order total): commission percentage specific to this outlet

5.3.4 Shipping override group

  • Override Shipping Settings: turns the outlet shipping override on or off
  • Allow shipping a POS sale to the customer: enables shipping at this outlet
  • Carriers available at the till: allowed carriers for this outlet
  • Pre-selected carrier: default shipping carrier for this outlet

5.3.5 Guest checkout group

This group is the outlet-level half of PrestaShop POS customer management.

  • Allow sales without a registered customer: enables guest sales at this outlet
  • Guest customer handling: selects whether guests use an existing customer record or a new guest customer created per sale
  • Guest checkout customer email: email of the existing customer used for guest sales
  • Ask for the customer’s name: shows name fields on the guest form
  • Ask for the customer’s address: shows address fields on the guest form

5.3.6 How to Assign Products to Outlet 

Appears when editing an existing outlet and is the working screen for the inventory sync module for PrestaShop at outlet level.

  • Assign product to outlet
  • Assign all products to outlet
  • Manage quantity for assigned products
  • Remove a product from this outlet

5.4 Employees

The Employees screen is the PrestaShop sales agent management view, listing every PrestaShop employee assigned to a POS outlet.

Listing columns: Employee ID, Cashier name, Email, Outlet assigned, Status, Manager

  • Edit: opens the employee record in the standard PrestaShop employee editor

The Employee tab provides functionality for the creation of employee accounts and configuring of permissions and outlets that employees will have access to.

  • First Name: Provide the first name of the employee.
  • Last Name: Provide the last name of the employee.
  • Avatar: Upload the avatar image of the employee.
  • Enable Gravatar: Specify whether you want to use the employee’s Gravatar image (Yes/No).
  • Email Address: Provide the employee’s email address. This email can be used as a login and account information exchange channel.
  • Password: Provide a password of at least 8 characters for the employee.
  • Language: Provide the language used by the employee in the administration panel.

Access and Permissions

  • Active: Select Yes if you want to give the employee access to the Admin panel; otherwise select No.
  • Role: Choose the role of the employee. Based on the chosen role, the employee gets permission and access to functions.
  • Default Page: Choose the page that should be opened right after logging in by the employee.

POS Access

  • POS Outlet Assigned To: Choose the POS outlet that belongs to the employee.

If this field is left blank/uninitialized, the employee is not considered a cashier and hence does not get POS access.

  • Employee Image: Choose the photo/image of the employee. It could help in recognizing the employee in the system. Once all the necessary data is entered, save the employee’s record.

5.5 How to sync orders in POS 

The Orders screen lists all POS-originated orders and is the primary place to review sales history and the starting point for any return and refund POS trail investigation.

Listing columns: ID, Reference, Customer, Outlet, Salesperson, Commission Amount, Status, Total, Paid, Oversold, Date

Filters: Outlet filter, Salesperson filter, Date filter

View: opens the detailed order view for that sale, including outlet, salesperson, and payment detail useful for tracing a return

CSV export is available through the standard PrestaShop helper list export mechanism, which makes it straightforward to pull a return and refund POS trail or a reconciliation file for accounting.

5.6 How to Analyse Reports 

The Reports parent tab groups the two reporting screens used for commission tracking and discount oversight.

5.6.1 Discount Report

Summarises discount activity by employee and outlet, helping administrators identify cashiers who discount heavily or frequently.

Listing columns: Employee ID, First name, Last name, Outlet, Times discounted, Total discounted, Per-item discounts, Per-item total, Whole-cart discounts, Whole-cart total, Last discount

Filters: Employee name filters, Outlet filter, Last discount date range

This is a read-only report. It is based on discount activity logged by the module and does not include voucher-related discount rows.

5.6.2 Commission Report

The primary screen for commission tracking, summarising commission earned by a salesperson at each outlet.

Listing columns: Employee ID, First name, Last name, Outlet, Sales with commission, Total sales value, Total commission, Average per sale, Last commission

Filters: Outlet filter, Last commission date range

View orders: opens the Orders page filtered to the related salesperson and outlet

Note: This report is grouped by salesperson and outlet, which matters when a single employee works across multiple outlets under Multi-Outlet POS operations.

5.7 Receipt Settings

Controls how PrestaShop POS with receipt printing displays discounts and whether new customers receive a welcome email.

  • Print each line’s own discount: prints a separate discount line for each discounted product on the receipt
  • Print the whole-cart discount total: prints a separate total line for cart-level discounts
  • Email new customers a welcome message: sends a welcome email when a cashier creates a new customer from the POS.

6.0 Conclusion

Knowband PrestaShop Point of Sale also called as PrestaShop Multi-Outlet Point of Sale (POS) module for stores that need genuine multi-outlet management inside PrestaShop rather than a bolted-on third-party system. It gives admins the tools to create outlets, assign employees through sales agent management. Also, this module keep stock accurate with the inventory sync module for PrestaShop, scan products with the barcode scanner module for PrestaShop, take sales while offline through the offline order module for PrestaShop, configure shipping and payment behavior, print receipts, and monitor discount and commission trends from a single sales dashboard module for PrestaShop. If you find any issue with the module, please feel free to contact us at support@knowband.com

Watch the video tutorials below to learn how to configure and use the PrestaShop Point of Sale Module step by step.

OpenCart SEO Audit Manager User Manual

1. Introduction

Having an OpenCart website requires much more than just adding your products and completing orders. Search engines need to know what is on the web page, customers require faster-loading pages, and there are also broken links that have to be detected before they start bringing losses to you. An OpenCart SEO Audit Manager developed by Knowband provides all these functions from one dashboard instead of using different add-ons, Excel sheets, and manual checks. An OpenCart SEO Audit Extension indeed does all these things at once.

The fundamental principle behind the operation of the OpenCart SEO Audit Extension is to rate products, product categories, informational pages, manufacturers, and blogs that are compatible with OpenCart. Every single page will get its own quality rating, taking into account such aspects as meta tags, readability, keyword inclusion, linking, and more. For those store owners who do not know much about SEO, this is a good checklist.

Apart from scoring, the Extension includes functionalities such as OpenCart Google Analytics 4 Analysis, OpenCart Google Search Console, and OpenCart PageSpeed Insights for traffic analysis, search analysis, and page speed information to be found in one dashboard. In addition, it takes care of redirect management using the OpenCart URL Redirect Extension. This extension also identifies any 404 URL that might ruin users’ experience and detects duplicate SEO URLs.

This module acts as an OpenCart Technical SEO plugin, which allows you to edit your robots.txt file using OpenCart Robots.txt Editor and creates XML and HTML sitemaps using OpenCart Sitemap Generator. With the optional OpenCart AI Content Generator based on ChatGPT, it drafts such important elements as meta titles, meta descriptions, product descriptions, and social media tags.

This manual describes the functionality of the Knowband OpenCart SEO Audit Extension on the basis of its actual navigation, features, and performance. This document does not give any guarantees concerning the ranking of the page in search results, since no on-page service can control the search engine ranking of a page. It gives an explanation of each feature’s function, usage, and relevance. The manual is written for those OpenCart store owners who have the knowledge of OpenCart but do not know how to perform an OpenCart SEO audit.

2. Key Features of OpenCart SEO Audit Manager

OpenCart SEO Audit Manager, a complete OpenCart SEO audit extension for OpenCart stores, combines several distinct capabilities under one module. Together, they cover most of the recurring SEO maintenance tasks an OpenCart store needs:

  • SEO and readability scoring for products, categories, information pages, manufacturers, and supported blog content
  • Score history with trend charts, snapshots, and comparisons over time
  • Issues grouped by rule, so administrators can fix one problem across many pages at once
  • OpenCart Google Analytics 4 integration with sessions, users, eCommerce, and behavior reporting
  • OpenCart Google Search Console integration covering performance, sitemap submission, and URL indexing checks
  • PageSpeed Insights integration with mobile and desktop testing, plus historical trend tracking
  • An OpenCart Redirect Manager supporting OpenCart 301 Redirects plus 302 and 303 redirect types, including bulk CSV import
  • 404 URL detection that records missing storefront requests for review
  • Duplicate URL checking, effectively an OpenCart SEO Checker for SEO keywords assigned to more than one page
  • XML and HTML sitemap generation through the module’s OpenCart Sitemap Generator, along with RSS feed support
  • robots.txt management via the built-in Robots.txt Editor, directly from the admin panel
  • An OpenCart AI Content Generator (ChatGPT-assisted) for meta titles, descriptions, product copy, and social metadata
  • Import/export for bulk SEO data backup, restore, and AI-assisted enhancement
  • Social Cards for Open Graph and X (Twitter) card metadata, plus structured data support

Each of these areas is documented in detail in the sections that follow, using the exact tab names and fields found in the OpenCart SEO Audit Module.

3. Installation of the Extension

Step 1: Download the module. Download the OpenCart SEO Audit Manager, an OpenCart SEO plugin developed and extract it on your local machine.

Step 2: Copy the files to your server. Upload the contents of the files’ upload (admin, system, catalogue) directory into your store, keeping the existing folder structure intact.

Step 3: Install or refresh the OCMOD modification. The module includes an OCMOD modification that adds the Knowband SEO group to the admin sidebar. In OpenCart, go to Extensions > Modifications and refresh the modification list so the OpenCart SEO Extension appears correctly. If the sidebar entry does not appear immediately, the extension also includes an event-based fallback that adds the menu automatically once the extension is installed.

Step 4: Install the extension. Open the OpenCart administration panel, go to Extensions, locate Knowband SEO, and install it.

Step 5: Confirm user permissions. Installation grants the installing user group access and modification permission for the module’s routes. If other administrator groups also need to use the module, add their access and modify permissions manually under System > Users > User Groups.

4. Admin Overview of OpenCart SEO Audit Extension

The OpenCart SEO Audit Extension organises its tools under a dedicated admin menu. The navigation includes Dashboard, Analytics (includes GA, GSC & PageSpeed Insight dashboards), Score History, URL Optimisation, Sitemap XML, and HTML. This extension also includes updating products in bulk using import/export settings. Also allow you to edit sitemap.xml, sitemap.html, and robots.txt.

4.1 Dashboard 

 

The dashboard is the summary view of your store’s overall SEO condition. It is usually the first place to check when reviewing how your catalog is performing from a content and metadata POV. 

You can view the current and previous overall SEO scores, review several breakdown charts, run a bulk analysis of pages that have not yet been scored, and jump straight into Score History.

  • Current website score / Previous score: The overall SEO score of the store as of its latest audit, presented in relation to the previous period’s score to track if there was an improvement or decline.
  • Trend of the overall SEO score: A graph showing the performance of your website over time that will help understand whether the improvements made had any lasting impact or just an initial positive response.
  • Index/Follow ratio: The ratio of pages marked for indexing and following versus those marked noindex and nofollow, will allow to detect the pages that were mistakenly blocked from search engines’ crawling.
  • Pages by scores distribution: A chart reflecting the number of pages with strong, moderate, and poor SEO scores.
  • Readability: a chart summarizing readability scores across analyzed content, separate from the SEO score.
  • Meta settings completed: a chart showing how many pages have complete metadata (title, description, and similar fields) versus how many are missing it.
  • SEO checklist: a list of store-wide technical items, including SEO URLs enabled, SSL enabled, XML sitemap enabled, robots.txt existence, maintenance mode status, webmaster verification, URL redirects, RSS, and blog detection where relevant. Each row shows whether the item is in place and may include an edit or external link to fix it directly.
  • Score History (header action): a shortcut that opens the Score History tab without using the main menu.
  • Analyze missing pages (header action): opens the bulk analysis tool described below, used to score pages that have not yet been analyzed.

4.2 Analytics

Analytics contains the tabs, including Analytic Dashboard, Settings, GA4 Analytics, Search Console, and PageSpeed.

4.2.1 Analytics Dashboard of the OpenCart SEO Audit Manager

This is a customizable widget dashboard that pulls together GA4, Search Console, and PageSpeed data in one place, so you do not need to open each integration separately for a quick check. These widgets are included from Google Analytics 4, Google Search Console and PageSpee

  • Period selector: The Store owner can set the reporting window for every widget on the page, with choices of Last 7 days, Last 28 days, Last 30 days, or Last 90 days.
  • Sessions: Select GA4 sessions recorded in the selected period.
  • Users: total Unique users recorded in the selected period.
  • Page views: Total page views recorded in the selected period.
  • Realtime users: The number of users currently active on the storefront, updated close to live.
  • Sessions trend / Users trend: Line charts showing how sessions and users changed day by day across the selected period.
  • Sessions by country: A breakdown of sessions by visitor country.
  • Sessions by device: A breakdown of sessions by device category, such as desktop, mobile, or tablet.
  • Top traffic sources: The channels or sources sending the most sessions to the store.
  • Clicks: total Search Console clicks in the selected period.
  • Impressions: total times your pages appeared in Google search results.
  • CTR: click-through rate, calculated as clicks divided by impressions.
  • Avg position: the average ranking position of your pages in Google search results for the period.
  • Clicks vs Impressions: a combined chart plotting clicks and impressions together so you can see how they move relative to each other.
  • Top search queries: the search terms generating the most clicks or impressions.
  • Top landing pages: the pages receiving the most traffic from search.
  • PageSpeed performance: a widget summarizing your most recent PageSpeed test scores.
  • Refresh: reloads the data for all currently displayed widgets.
  • Customize: opens the widget library so you can add, remove, or reorder widgets.
  • Save layout: stores your current widget selection and arrangement for this store.
  • Cancel: closes the customization view without saving changes.
  • Reset layout: restores the default widget selection and order.

4.2.2 Settings of GA4, GSC and PageSpeed

 This includes holds every configuration value the Analytics area needs, organized into General, Credentials, Properties, Access, PageSpeed Cron, and Notifications sections.

General

  • Analytics Status: turns Analytics data collection and dashboards on or off for this store.
  • Default Period (days): the reporting window used by dashboard widgets when no other period has been chosen.
  • API Cache TTL (minutes): how long API responses are cached before the Extensionrequests fresh data from Google, which reduces API usage but delays how quickly new data appears.
  • Search Console Data Lag (days): the number of most recent days excluded from Search Console reporting, since Google typically finalizes that data a few days after it occurs.
  • History Retention (days): how long PageSpeed test history is kept before older records are removed.

Credentials

  • PageSpeed API Key: your Google PageSpeed Insights API key, required to run performance tests.
  • Google OAuth Client ID: the Client ID from the Web application OAuth client you created in Google Cloud.
  • Google OAuth Client Secret: the matching Client Secret; leaving this field blank when editing keeps the value already stored.
  • Connect with Google: starts the OAuth authorization flow using the Client ID and Secret above.
  • Disconnect Google: removes the stored Google connection for this store.
  • Refresh: reloads the list of available Google properties after a successful connection.

Properties

  • Search Console Property: the specific Search Console property this store’s data should be pulled from.
  • GA4 Property: the specific GA4 property ID this store’s data should be pulled from.
  • PageSpeed Test URL: the default URL used when running a PageSpeed test without specifying a custom one.
  • Custom Test URL: an optional alternate URL available when a custom PageSpeed target is selected instead of the default.

PageSpeed Cron

  • Enable Scheduled Checks: turns on automatic, recurring PageSpeed tests.
  • Pages To Test: which page targets are included in the scheduled checks.
  • Cron URL: the unique URL your server scheduler should call to trigger scheduled PageSpeed checks.
  • Last Run: the date and time the scheduled check last executed.
  • Regenerate: creates a new security token for the Cron URL; any existing scheduled job still using the old URL will stop working until it is updated.
  • Run now: triggers a scheduled check manually, without waiting for the next scheduled time.

Notifications

  • Enable Email Alerts: turns on email notifications for score or performance changes.
  • Alert Recipient: the email address that receives alerts.
  • Alert Threshold (points): the score-change amount that triggers an alert.
  • Also Notify On Recovery: sends an additional alert when a score that previously dropped recovers.
  • Notify When Core Web Vitals Fail: sends an alert specifically when Core Web Vitals metrics fail their thresholds.
  • Send test email: sends a sample alert to the configured recipient so you can confirm delivery is working.

Steps to Create Google Client ID & Secret ID 

  1. Enable the required APIs. Inside that project, turn on the Google Analytics Admin API, Google Search Console API, and PageSpeed Insights API.
  2. Configure the OAuth consent screen. Google requires this before it will let your project request access to Analytics and Search Console data.
  3. Create an OAuth 2.0 Client ID. Choose “Web application” as the type.
  4. Add the redirect URI. Copy the exact redirect URI shown by the module and paste it into the OAuth Client’s settings.
  5. Save the Client ID and Client Secret. Copy both values from Google Cloud and paste them into the matching fields here.
  6. Click Connect with Google. This starts the authorization process using the credentials you just saved.
  7. Click Refresh. This loads the list of Google properties available to your account.
  8. Select the correct properties. Choose the right Search Console property and GA4 property for this store.
  9. Create a PageSpeed Insights API key. Generate this in the same Google Cloud project.
  10. Paste the key into the PageSpeed API Key field. This connects PageSpeed testing to the module.

4.2.3 GA4 Analytics

  • This is inclusive of visualization of your Google Analytics 4 metrics including traffic, engagement, and eCommerce activities.
  • Period Selector: Last 2 days, Last 7 days, Last 28 days, Last 30 days, or Custom that shows Date start, Date end, and an Apply button for a particular period.
  • Compare to previous period: this will add a second line to your charts and cards in order to indicate the corresponding period SEO score of fStore, this way you can tell whether there has been an improvement.
  • Overall SEO score trend: This is a graph of website score trend overtime, and it will help in knowing whether the changes that you have made recently are working or not.
  • Index/Follow ratio: This will show the number of pages that are marked as index and followed against the number of pages that are noindexed and nofollowed. This way you can know the pages hidden from the search engines
  • Page audit: a chart showing how many pages fall into strong, fair, and weak score bands, giving a quick sense of catalog-wide health.
  • Total users: everyone who visited the store in the period.
  • Active users: users counted by GA4 as actively engaged during the period.
  • New users: first-time visitors in the period.
  • Sessions: total sessions recorded in the period.
  • Engaged sessions: sessions that met GA4’s engagement criteria, such as lasting a minimum duration or including a conversion event.
  • Views: total page or screen views.
  • Views per session: average number of views per session.
  • Avg. session duration: average length of a session.
  • Engagement rate: the share of sessions that were engaged sessions.
  • Bounce rate: the share of sessions that were not engaged.
  • Events: total events recorded, such as clicks or scroll triggers configured in GA4.
  • Realtime panel: shows active users from the last 30 minutes, broken down by country, device, or page.
  • Traffic over time: a chart of sessions, users, and views across the selected period, with a previous-period comparison line when enabled.
  • Sessions by hour of day: a chart showing which hours typically bring the most sessions.
  • Revenue: total eCommerce revenue recorded by GA4.
  • Purchases: total completed purchase events.
  • Transactions: total recorded transactions.
  • Average order value: revenue divided by the number of orders.
  • Items purchased: total quantity of items sold.
  • Purchase funnel: a step-by-step view of Add to cart, Begin checkout, and Purchase, plus the conversion rates between them (Cart to checkout, Checkout to purchase, and Cart to purchase).
  • Top items: the best-selling products by revenue or quantity in the period.

4.2.4 Search Console

This Google Search Console Integrations in OpenCart includes performance and sitemap & URL check options. Together they show how your store appears in Google search results and whether Google has indexed your pages correctly.

Available Options

  • Clicks: how many times a search result led to a click on your site.
  • Impressions: how many times your pages appeared in search results, whether clicked or not.
  • CTR: click-through rate, clicks divided by impressions.
  • Average position: the average ranking position of your pages for the queries measured.
  • Comparison toggle: adds a previous-period series alongside the current data.
  • Period / date range selector: sets the reporting window for the Performance data.
  • Search type filters: narrows results to Web, Image, Video, or News search.
  • Queries table: search terms, with Clicks, Impressions, CTR, Position, Previous, and Change columns.
  • Pages table: individual URLs, with the same metric columns as Queries.
  • Countries table: performance broken down by visitor country.
  • Devices table: performance broken down by device type.
  • Search appearance table: performance broken down by the type of search result shown (for example, a normal listing versus a rich result).
  • Clicks vs impressions chart: plots both metrics together over time so you can see whether visibility and clicks are moving in the same direction.

Sitemaps & URL Check

  • Sitemap: the submitted sitemap’s URL.
  • Last submitted / Last downloaded: when the sitemap was last submitted to Google and when Google last downloaded it.
  • Status: Google’s current processing status for the sitemap.
  • Warnings / Errors: counts of issues Google found while processing the sitemap.
  • Submitted URLs: how many URLs the sitemap contains.
  • Submit/Delete sitemap: actions to add a new sitemap to Search Console or remove one that is no longer needed.
  • Google Index Checker: URL filter: enter a specific URL to check its indexing status.
  • Google Index Checker: Indexed filter: narrows results to indexed or not-indexed URLs.
  • Details: opens the full inspection result for a checked URL, which can show Indexed by Google, Not indexed, Listed in a submitted sitemap, or Not found in any submitted sitemap.
  • Check new URL: runs a fresh indexing check on a URL and stores the result in history for future reference.
  • Open in Search Console to request indexing: opens Google’s own URL Inspection tool, since Google does not provide an API for requesting indexing of ordinary pages.

Submit your XML sitemap here after configuring the Sitemap tab, and revisit the Sitemaps table periodically to check for warnings or errors rather than assuming a one-time submission is enough.

4.2.5 PageSpeed 

 PageSpeed brings Google PageSpeed Insights testing into the admin, with Run Test, Results, and History areas.

Run Test

  • Home page: runs the test against the storefront’s home page.
  • Category page: runs the test against a selected category page.
  • Product page: runs the test against a selected product page.
  • Custom URL: runs the test against any URL you specify.
  • Mobile / Desktop: every test runs on both device types, since performance often differs between them; a full test can take up to 90 seconds.

Results

  • Field data: real-world performance measured from actual Chrome users, when enough data exists in the Chrome User Experience Report.
  • Lab data: performance measured in a controlled, simulated test environment, useful when field data is unavailable.
  • Lighthouse scores: the overall category scores Google’s Lighthouse tool assigns.
  • Metrics: individual timing measurements such as load and rendering speed.
  • Insights: guidance describing what is affecting performance.
  • Diagnostics: additional technical detail about performance issues.
  • Passed audits: checks the page already satisfies.
  • Failed audits: checks the page does not satisfy, each with an explanation of the issue.

History

  • Target: filters history by which page type was tested (Home page, Category page, Product page, Custom URL).
  • Device: filters history by Mobile or Desktop.
  • From / To: date range filters for the history list.
  • Date: the date a specific test was run.
  • URL: the exact URL that was tested.
  • LCP: Largest Contentful Paint, a Core Web Vitals loading metric.
  • INP: Interaction to Next Paint, a Core Web Vitals responsiveness metric.
  • CLS: Cumulative Layout Shift, a Core Web Vitals visual stability metric.
  • Source: whether the test was run Manually or by a Scheduled check.
  • Export CSV: downloads the filtered history as a CSV file.

4.3 Score History

Score History in OpenCart SEO Audit Extension tracks how your store’s overall SEO score, and individual entity scores, change over time. This is where you confirm whether your SEO efforts are actually moving the needle..

Use Create snapshot to capture the store’s current state manually, for example before a large content update. To compare two points in time, select one snapshot as Snapshot A and another as Snapshot B, then click Compare snapshots; the two selections must be different from each other.

Best practice is to enable automatic snapshots and configure a retention policy in General Setting so that history builds up on its own, rather than depending on manual snapshots that are easy to forget.

4.5 URL Optimisation in Prestashop

This OpenCart SEO Audit Extension includes features like a redirection feature, 404 URL fixing and Duplicate URL detection.

A 301 redirect signals a permanent move and is generally the right choice when a page has been renamed or merged and the old URL should never be used again, this is the most common use case for OpenCart 301 Redirects. A 302 redirect signals a temporary move, useful for short-term changes such as a seasonal category being swapped out and back. A 303 redirect is typically used to point a request elsewhere after an action, such as a form submission, and is less commonly needed for straightforward catalogue URL changes.

Import CSV: this includes adding a bunch of URLs directly at once from a sheet.

Add Redirect: Type in a redirect’s name, its source URL, or its target URL, and click Filter to narrow the list down, handy once you’ve got more than a handful of redirects saved.

Redirect entry type: Individual for a single redirect, or Bulk for a CSV upload; Bulk mode is available only when adding, not editing.

Redirect name: an optional label to help you identify the redirect later, such as “mens-tshirts.”

Source URL: the old address to redirect from; this can be an SEO path (for example, old-category/old-product), an OpenCart route such as information/contact, or a path without the domain. This field is required.

Target URL: the destination address, entered as a relative path or a full http(s) URL. This field is required, and unsafe schemes such as javascript: or data: are rejected.

Redirect type: 301, 302, 303, or 404; new individual forms default to 301.

Active: Enabled or Disabled; new individual forms default to Enabled.

Save: stores the redirect and returns to the list with a success message.

The file must stay under 2 MB and 2,000 rows. Invalid rows are skipped, and the import result reports how many rows were imported and how many were skipped.

Editing and managing redirects. Use Search redirects to locate an entry by name, source, or target, then use Edit or Delete from the row actions. Bulk mode is available only when adding redirects, not when editing an existing one.

Avoiding mistakes. Redirects do not run on the storefront unless both the module’s master Status and Enable URL redirects are turned on in General Setting. Base redirect decisions on an actual URL change, such as a renamed product or a restructured category, rather than redirecting pages speculatively. A chain of redirects pointing to other redirects should generally be avoided; point each source directly to its final destination where possible.

Example. If a product URL changes from /product/old-name to /product/new-name after a rename, add a 301 redirect from the old path to the new one so that existing links and bookmarks continue to work.

10. 404 URL Detection

A 404 URL is a storefront request for a page that no longer exists or never existed at that address. Left unaddressed, these broken links frustrate visitors and waste any traffic or link value the old page had earned.

This module detects the 404 URLs and allow the store owners to redirect the 404 URL by following redirect feature.

4.6 Robots.TXT

Robots.txt is a plain text file at your store’s root address that tells well-behaved search engine crawlers which parts of the site they should avoid crawling.

A misconfigured robots.txt file can accidentally block important pages from being crawled, while a well-configured one keeps crawlers away from admin and system directories that offer no value in search results.

The OpenCart Robots.txt Editor includes:

  • File path: the server location of the robots.txt file, for reference.
  • Exists: shows Enabled when a robots.txt file is already present, or Disabled when it is not.
  • robots.txt content: an editable text area containing the file’s directives. If no file exists yet, this area is pre-filled with a starting version that disallows the /admin/ and /system/ directories.
  • Save: writes the edited content to the file.

4.7. XML Sitemap

An XML sitemap is a structured list of your store’s URLs that helps search engines discover and prioritize pages for crawling.

The module’s OpenCart XML Sitemap tool, part of its broader OpenCart Sitemap Generator, allows you to configure the following under Sitemap > XML Sitemap:

  • Enable XML sitemap: turns on the public XML sitemap endpoint.
  • Sitemap page URL: displays the public URL once the sitemap is enabled.
  • Per-language sitemap URLs: shown for each enabled storefront language, since each language can have its own sitemap address.
  • Enable RSS: turns on the RSS feed endpoint alongside the sitemap.
  • Include in sitemap: checkboxes for Product, Category, Information, and Manufacturer, controlling which content types are listed in the sitemap.
  • Product limit: the maximum number of products included; the Extension recommends a positive value of 5,000 or lower, and treats zero or a blank value as a safe maximum.
  • Priority (per content type): a value from 1.0 down to 0.0 indicating relative importance within your own site; saved values are clamped to this range.
  • Change frequency (per content type): Always, Hourly, Daily, Weekly, Monthly, Yearly, or Never, describing how often that page type typically changes; invalid values are normalized to Weekly.
  • Save: stores the configuration.

The HTML Sitemap sub-tab works alongside the XML version, publishing a customer-facing sitemap page instead of a machine-readable file. Its fields are:

  • Enable HTML sitemap: publishes the customer-facing sitemap page.
  • Sitemap page URL: shown only once the HTML sitemap is enabled.
  • Per-language HTML sitemap URLs: shown for each enabled storefront language.
  • Include in HTML sitemap: checkboxes for Home page, Product, Category, Information, Manufacturer, and Specials (Price Drop).
  • Custom URLs: an optional table of additional links, each with a Title and a URL (an absolute https:// address or a store path such as contact).
  • Add URL: adds a new blank row to the Custom URLs table.
  • Remove: deletes a row from the Custom URLs table.
  • Save: stores the configuration; the extension returns to the HTML tab if it was the active tab when you saved.

The HTML sitemap’s product list reuses the Product limit set on the XML Sitemap tab.

4.8 Settings

4.8.1 General Setting

 General Setting is the module’s central configuration page, and Status here is the master switch that everything else depends on. This is also where the extension functions as an OpenCart Metadata Manager, letting you define default meta title and description templates for products and categories.

Master and analysis controls

  • Status: the master switch for the entire module; storefront metadata, redirects, panels, and score columns only work when this is enabled. Default: Disabled.
  • Enable Page audit: shows SEO score cards, the Page audit tab in catalog forms, and SEO Score columns in catalog lists. Default: Disabled.
  • Enable readability analysis: shows readability score cards and lists alongside the SEO scores. Default: Disabled.
  • Enable auto analysis on edit: reruns analysis automatically while a page is being edited; scores are also saved when the catalog form is saved. Default: Disabled.
  • Record 404 requests: records missing storefront URL requests for the 404 URLs report. Default: Disabled.
  • Enable URL redirects: applies active redirects on the storefront. Default: Enabled, though the master Status must also be enabled for redirects to actually run.
  • Enable XML sitemap: turns on XML sitemap functionality store-wide. Default: Disabled.
  • Enable RSS: turns on RSS functionality store-wide. Default: Disabled.

Search and metadata defaults

  • Title separator: the character or text used between parts of a generated title, such as -; referenced by the {title_separator} shortcode. Default: -.
  • Show products in search by default: whether new products appear in the storefront search index by default. Default: Enabled.
  • Show categories in search by default: whether new categories appear in the storefront search index by default. Default: Enabled.
  • Show manufacturers in search by default: whether new manufacturers appear in the storefront search index by default. Default: Enabled.
  • Show information pages in search by default: whether new information pages appear in the storefront search index by default. Default: Enabled.
  • Product meta title template: the default meta title pattern for products, using shortcodes. Default: {product_name} {title_separator} {shop_name}.
  • Product meta description template: the default meta description pattern for products. Default: blank.
  • Force product meta templates: when enabled, the template is applied even if a product already has its own meta title or description. Default: Disabled.
  • Category meta title template: the default meta title pattern for categories. Default: {category_name} {title_separator} {shop_name}.
  • Category meta description template: the default meta description pattern for categories. Default: blank.
  • Force category meta templates: when enabled, the template is applied even if a category already has its own meta title or description. Default: Disabled.

Supported shortcodes across these templates include {product_name}, {category_name}, {shop_name}, {title_separator}, {brand}, {og_meta_title}, and {og_meta_description}.

Cron and verification

  • Cron secure token: the secret value used in the module’s cron URL to authenticate scheduled requests; a token is generated by default.
  • Google verification code: the content value from Google Search Console’s HTML-tag verification method; it can be left blank if verification is already completed another way.
  • Bing verification code: the content value from Bing Webmaster Tools verification; it can also be left blank if verification is already completed another way.

Score History

  • Enable SEO score history: turns on score tracking and snapshots. Default: Enabled.
  • History retention: Keep all history (default), Delete older than X days, Keep only daily snapshots, or Keep only weekly snapshots.
  • Retain history for (days): the number of days to keep when the day-based retention option is selected. Default: 365.
  • Automatic snapshot schedule: Manual only, Daily (midnight) (default), Weekly, or Monthly; automatic snapshots also require a scheduled request to the module’s cron URL.

4.8.2 Social Cards

 Social Cards controls the Open Graph and X (Twitter) card metadata added to storefront pages, along with basic structured data settings.

  • Enable Facebook Open Graph: turns Open Graph metadata on or off. Default: Enabled.
  • Enable X Card: turns X (Twitter) card metadata on or off. Default: Enabled.
  • X card type: summary or summary_large_image, controlling how a shared link’s preview card is laid out. Default: summary_large_image.
  • Site type: Organization, WebSite, or LocalBusiness, used in the structured data describing your store. Default: Organization.
  • Site name: the name used in site-level metadata.
  • Breadcrumbs: turns breadcrumb structured data on or off. Default: Enabled.
  • Facebook: your store’s Facebook profile URL.
  • Twitter: your store’s Twitter/X profile URL.
  • Instagram: your store’s Instagram profile URL.
  • LinkedIn: your store’s LinkedIn profile URL.
  • YouTube: your store’s YouTube channel URL.
  • Pinterest: your store’s Pinterest profile URL.
  • Save: stores the settings.

4.8.3 ChatGPT Content Generator

Knowband OpenCart SEO Audit Extension also includes the feature of an AI Content Generator as an additional tab inside product and category SEO panels, and as a bulk tool within Import/Export.

  • Enable ChatGPT: turns the assistant on or off across the module. Default: Disabled.
  • ChatGPT model: GPT-4o, GPT-4o mini, GPT-4 Turbo, GPT-4, or GPT-3.5 Turbo; the controller falls back to gpt-4o-mini and the installation default is gpt-3.5-turbo.
  • ChatGPT API token: your OpenAI secret key, which must begin with sk-.
  • Test API key: sends a live validation request to OpenAI to confirm the token works.

Single-page fields (SEO panel > ChatGPT tab).

  • Prompt templates: a set of ready-made prompts you can select instead of writing your own.
  • Your prompt: a free-text box for a custom prompt, supporting shortcodes such as {product_name}, {brand}, {category_name}, {meta_title}, and {meta_description}.
  • Generate: sends the prompt to ChatGPT and returns a draft.
  • Generated content: displays the draft returned by ChatGPT for review.
  • Apply: places the generated content into the relevant field (the catalog form must still be saved afterward for the change to take effect).
  • Apply to: chooses which field the generated content should be applied to.
  • Clear history: clears the recent generation history for this page.
  • Recent history: a list of previous prompts and results for this page.

Bulk fields (Import/Export > ChatGPT enhance).

  • Field checkboxes: choose which fields to generate, from Meta title, Meta description, Meta keywords, Social title, Social description, Product tags, SEO URL, Primary keyword, Supporting keywords, and Product description (readability).
  • Select all / Select none: quickly selects or clears every field checkbox.
  • Process all products: generates content for the entire catalog.
  • Max products: an alternative to Process all products, capping the run at a specific number, up to 5,000 distinct catalog products across all languages for each product.
  • Products per API call: how many products are sent together in a single request, from 1 to 5; the Extension forces this to 1 whenever Product description (readability) is selected.
  • Start / progress indicator: begins the enhancement run and shows live progress.
  • Maximise SEO & readability scores (download JSON): the action that runs the enhancement and produces a downloadable file; it does not save directly to the catalog.

That downloaded file must then be brought back in through the Import panel described below; the bulk ChatGPT tool never writes to the catalog on its own.

4.9. Import/Export

Import/Export handles product SEO data as a JSON file: meta title, description, keywords, and tags; the SEO URL, primary and supporting keywords, robots and canonical settings, social title, description, and image; SEO and readability scores and analysis data; and rating markup fields. This is used in updating multiple product in bulk.

Supported format. The exported file uses JSON format at version 1.2 and includes an export timestamp and field list along with the product data.

Export fields.

  • Export: the single action button that generates and downloads the current product SEO data as a JSON backup file, versioned 1.2 and including an export timestamp, field list, and product data. This same file can also serve as a baseline before running the ChatGPT enhancement tool described in Section 14.

Import fields.

  • Choose file: selects the .json file to import; the extension must be .json, the content must be valid JSON, it must contain a products array, and it must stay under 5 MB with no more than 5,000 rows.
  • Import: runs the import; product and language IDs in the file must be positive numbers matching the current store. Successful imports report the number of updated product and language rows.

 Other Modules is a shared Knowband catalogue page reachable from the Knowband SEO menu. It lists other Knowband extensions available for OpenCart rather than SEO configuration options specific to this module.

5. SEO Audit and Scoring

The scoring system is the foundation of Knowband’s OpenCart SEO Audit Extension. Every product, category, information page, manufacturer page, and supported blog entity can receive an SEO score and a separate readability score once the relevant analysis settings are enabled in General Setting , the core of what makes this an effective OpenCart SEO Analyzer.

Supported page types. Scoring covers Products, Categories, Information pages, and Manufacturers by default. Blog posts, Blog categories, Blog tags, and Blog authors are included only when a supported Knowband Blog integration is connected to the store.

What the score measures. Running this OpenCart SEO Audit means the rule library evaluates content length, sentence and readability quality, heading structure, internal links, image alt attributes, title and description length, and the placement and density of your primary and supporting keywords in the page’s content and URL slug. Any rule that scores below 7 is logged as an issue and grouped under the Issues tab.

What the score means. A high score indicates that a page has covered the fundamentals: a reasonably descriptive title and description, readable content, sensible heading structure, and keyword usage that matches the page’s stated focus. A low score does not mean a page is invisible to search engines; it means specific, correctable gaps exist. Since the Extensioncannot see how Google actually ranks a page, the score should be read as a content quality checklist rather than a ranking prediction.

Why the score matters. Search engines reward pages that clearly answer a search intent with well-structured, readable content. A low score often points to the same weaknesses that make a page harder for a human shopper to read, so fixing them tends to help both audiences.

What to do about a low score. Open the page from the catalog list, review its Page audit panel, and check the specific rules it failed. Alternatively, open the Issues tab, filter by the relevant entity type, and work through rules that affect multiple pages at once. After making changes, save the page (or rely on Enable auto analysis on edit) so the score updates. This ongoing review is the heart of OpenCart SEO Optimization within the module.

How to improve a page. Set a clear primary keyword and, where relevant, supporting keywords that reflect what a shopper would actually search for. Write a meta title and description that describe the page honestly rather than stuffing keywords. Break long content into sections with headings, add descriptive alt text to images, and link to related products or categories where it makes sense for the shopper, not purely for the score.

Throughout this process, remember that an OpenCart SEO Audit is only useful when it leads to real edits. The module’s role is to surface what needs attention; the administrator’s role is to decide how to phrase and structure the fix, using the OpenCart SEO Audit Extensionas a guide rather than a final authority.

5. Frequently Asked Questions

I found several 404 URLs. How can I redirect them? Open URL Optimization > 404 URLs, review the list ordered by visit count, and click Redirect next to the entry you want to fix. This opens the redirect form with the old URL already filled in as the Source URL; enter the correct destination as the Target URL, choose the redirect type, and save. Only redirect to a page that is genuinely relevant to the original content.

How should I handle a URL that is no longer available? If a replacement page exists, add a 301 redirect from the old URL to the new one through URL Optimization > URL Redirects. If no relevant replacement exists, it is reasonable to leave the URL as a 404 rather than redirecting visitors somewhere unrelated.

How can I improve a page with a low SEO score? Open the page’s Page audit panel, or open Issues and filter by entity type, to see exactly which rules the page failed. Address specific gaps, such as a missing meta description, thin content, or missing image alt text, then save the page so the score updates. Score History will then show whether the change moved the page’s score in the right direction.

Can I use the Extensionto generate meta titles and descriptions? Yes. Enable and configure ChatGPT under Settings > ChatGPT, then use the ChatGPT tab inside a product or category’s SEO panel to generate a meta title or description from a prompt. Review the result, click Apply, and save the catalog form. For many products at once, use the bulk ChatGPT tool inside Import/Export instead.

How can I check duplicate URLs? Open URL Optimization > Duplicate URLs to see which SEO keywords are assigned to more than one page in the same store and language. Click Update on a conflicting row, edit each keyword so it becomes unique, and save.

How can I check my XML sitemap? Open Sitemap > XML Sitemap, confirm Enable XML sitemap is turned on, and open the displayed public sitemap URL to verify it loads. Submit that same URL under Analytics > Search Console > Sitemaps & URL Check to confirm Google has received it and to monitor for warnings or errors afterward.

Can I connect Google Search Console? Yes. Set up a Google Cloud project with the Search Console API enabled, configure OAuth credentials under Analytics > Settings, click Connect with Google, and select the correct Search Console property for the store. Once connected, the Search Console tab shows Performance data and lets you manage sitemap submissions and URL indexing checks.

Can I view Google Analytics data inside the module? Yes. After connecting Google and selecting the correct GA4 property in Analytics Settings, the GA4 Analytics tab displays sessions, users, engagement, eCommerce, and breakdown data directly in the admin panel, without needing to open Google Analytics separately.

How can I identify SEO issues on product or category pages? Use the Dashboard’s Page audit by type chart to see which content type has the most low-scoring pages, then open Issues and filter by entity type to review specific rules affecting those pages. Alternatively, open an individual product or category and review its Page audit panel directly.

Does the Extensionguarantee better search rankings? No. The OpenCart SEO Audit Manager measures on-page content quality, technical configuration, and available Google data, all of which support good SEO practice. It does not control, and cannot guarantee, how any search engine ranks a specific page.

Is a blog required to use the module? No. Blog-specific scoring, trends, and entity types appear only when a supported Knowband Blog integration is connected to the store. Every other feature works fully without a blog installed.

Do I need Google or OpenAI accounts to use the core module? No. Analytics, Search Console, PageSpeed, and ChatGPT are optional integrations that require their own external credentials. The scoring system, redirects, 404 detection, duplicate URL checking, sitemap generation, and robots.txt management all work independently of those connections.

Prestashop SEO Audit Module: Complete User Manual

1. Introduction

Prestashop SEO Audit Manager is the SEO Audit module that allows prestashop store owners to conduct a SEO audit from scratch to the product, category, CMS and manufacturer. Rather than using separate modules or plugins to check pages for meta tags, redirects, sitemap, and analytical data, this module gathers all scoring, technical checks.

The module is designed for PrestaShop store administrators with no professional SEO experience. The result and target of each audit are shown in layman’s terms so that a person immediately understands why the description is 24 words long when the target is 300 words.

Technically, the module allows spotting thin content, lack of or duplicate meta title and description, broken internal links causing 404 errors, colliding URLs creating duplicate slugs, problems with configuring sitemap and robots.txt files, as well as slow loading time. Once the problem is spotted, there is usually a solution to fix the issue right within the module – editing the redirect, making the new meta description via ChatGPT, or fixing the sitemap options.

Prestashop SEO Audit Module also integrates with Google Analytics 4, Google Search Console, and PageSpeed Insights to let audit scores be analysed along with real traffic numbers, real search performance and page speed metrics, rather than in isolation. This is how a PrestaShop SEO audit changes from being a mere checklist into a live workspace.

2. Key Features of Prestashop SEO Audit Module

  • Page-level SEO audit and readability audit with a 0 to 10 score
  • Dashboard summarising store-wide SEO health, meta completeness, and index status
  • Score History with trend charts and snapshot comparison
  • URL Optimisation tools: Pretty URLs, 404 monitoring, duplicate URL detection, URL redirects
  • XML Sitemap and HTML Sitemap management, plus RSS output
  • Social Cards for Open Graph and Twitter metadata
  • Built-in ChatGPT integration for meta titles, meta descriptions, and other SEO fields
  • Robots.txt editor tied to the live file
  • Google Analytics 4, Google Search Console, and PageSpeed Insights reports

3. How to Install the Prestashop SEO Audit Module

  1. Install the Prestashop SEO Audit Module and from the PrestaShop Admin Panel, go to Modules -> Module Manager to install the module. This module builds its own database for SEO, History, Redirects, 404 Monitoring, ChatGPT, and Sitemap
  2. A new Prestashop SEO Audit Module entry appears in the left menu, under Sell. This master switch determines if the module will affect the storefront at all.
  3. Turn on features that you will be using: SEO analysis, Readability analysis, Record 404s, URL redirects, XML sitemap, RSS.
  4. In case you will be using Google integration or ChatGPT, go to Analytics > Settings and ChatGPT, where you should provide the necessary credentials. It can be done later.
  5. Open any product, category, CMS page, manufacturer or supplier, where you should find the SEO Audit tab in the edit form; here SEO work will be done.
  6. As the module modifies metadata of storefront, redirects and generates public robots.txt and sitemap files, staged installation, starting with analysis and readability score generation, followed by redirects and sitemap generation once you gain confidence in generated data, is recommended rather than full activation from the very beginning.

4. Admin Overview of PrestaShop On-Page SEO checklist

Tabs included in the Prestashop SEO Audit Module Sidebar: Dashboard, Analytics, Score History, URL Optimisation (Pretty URLs, 404 URLs, Duplicate URLs, URL Redirects), Sitemap (XML Sitemap, HTML Sitemap), Social Cards, ChatGPT, Robots.txt, Import / Export, Settings and Others Modules. All tabs have been described field-wise below such that every setting which is visible to users is explained separately.

4.1 Dashboard

The Dashboard provides an overview of your store’s current SEO health.

Top Actions

  • History button: Will immediately redirect you to the page of historical trends
  • Analyse missing pages button: Prestashop SEO Audit Module performs the batch analysis for all products, categories, information pages, manufacturers, suppliers, which do not yet have the stored SEO score.

Panel of Overall SEO score trend

  • Store SEO score: The current overall score of the store (for instance, 46), which is derived by the score of each analysed page. This is the one figure to follow every week.
  • Label improving/declining/no change: Appears right beside the Store SEO score (for instance, “Improving (+1)”). It will instantly show you the direction of the change of the SEO of your store.
  • Score of previous scan: The score of the store from the last snapshot.
  • Trend graph: The line graph showing Store SEO score by recent snapshots.

Page analysis cards

  • Excellent SEO: Count of analysed pages that pass nearly all audit rules. A rising number here means more of the catalogue is fully optimised.
  • Acceptable SEO (Needs improvement): Count of pages that are functional but have room to improve; this is usually the largest bucket in a growing catalogue.
  • Not good SEO: Count of pages failing most audit rules and needing priority attention.
  • No analysis (Pending analysis): Count of pages that have never been scored. A non-zero number here is a signal to run Analyse missing pages.
  • Meta complete/missing: How many pages have both a meta title and meta description filled in, and how many are still missing one or both. Missing metadata is one of the fastest, highest-value fixes available.
  • Index / No index: How many analysed pages are set to be indexed by search engines versus deliberately excluded. A high No index count on pages that should be visible is worth investigating.

Donut charts

  • Index/Follow ratio: Shows the proportion of analysed pages set to Index versus No index, so you can confirm important pages are not accidentally hidden from search engines.
  • Page analysis: Breaks the same Excellent/Acceptable/Not good/No analysis buckets down as percentages of the total analysed catalogue.
  • Readability: Shows the same breakdown for the Readability score specifically, separate from the SEO Audit score.
  • Meta settings completed: Shows what percentage of pages have finished meta title and description setup versus still needing attention.

Page analysis by type

The above pattern, repeated for each entity type (Products, Categories, Information, Manufacturers, Suppliers), with each displaying the number of pages belonging to this category and their respective Page Analysis (Excellent/Acceptable/Not good/No analysis) and Readability (Excellent/Acceptable/Not good) statistics. For example, the above illustrates the relatively poor performance of Categories compared to Products in terms of readability.

SEO checklist

A list of ten store-level requirements, each shown as Completed or Not completed with an action button:

  • SEO URLs enabled: Confirms PrestaShop’s own friendly URL setting is active, a prerequisite for clean, readable page addresses.
  • SSL enabled: Confirms the storefront is served over HTTPS, which search engines treat as a baseline trust signal.
  • XML sitemap enabled: Confirms the module’s XML sitemap output is switched on.
  • Robots.txt exists: Confirms a robots.txt file is present and reachable at the storefront.
  • Maintenance mode is off: Confirms the store is not accidentally left in maintenance mode, which would block all crawling and all visitors.
  • Webmaster verification configured: Confirms a Google or Bing verification code has been entered under Settings
  • URL redirects enabled: Confirms the redirect engine is active, so any redirects you create actually take effect on the storefront.
  • RSS enabled: Confirms the RSS feed output is switched on.
  • Knowband Blog: Indicates whether the companion Knowband Blog module is installed; shown with a Buy button when it is not, since blog SEO features only appear once that module is present.
  • LLMs.txt available: Indicates whether an llms.txt file, used to describe the site to AI crawlers, is available

4.2 Analytics

The Analytics section connects Prestashop SEO Audit Module to Google Analytics 4, Google Search Console, and PageSpeed Insights, and is organized into an overview page, three data-source reports, and a Settings page.

4.2.1 Analytics overview (Google Insights Overview) in Prestashop SEO Audit Module

  • Period selector (for example, Last 28 days): Sets the reporting window used across all the summary cards and charts on this page.
  • Refresh button: Reloads the widgets with the latest data from Google without leaving the page.
  • Customise button: Opens the widget library so you can control which cards appear.
  • Connection status panel: Shows four indicators at a glance: Google OAuth (Connected or not), GA4 Property (the connected property ID), GSC Site (the connected Search Console property URL), and PageSpeed API (Configured or not). This is the fastest way to confirm the integration is actually working before trusting any numbers below it.
  • GA4 Sessions card: Total GA4 sessions for the period, with a percentage change versus the prior period.
  • GA4 Users card: Total GA4 users for the period, with a percentage change.
  • GSC Clicks card: Total Search Console clicks for the period.
  • GSC Impressions card: Total Search Console impressions for the period, with a percentage change.
  • PageSpeed performance card: The most recent PageSpeed performance score.
  • GA4 Realtime users card: Users active on the storefront in the last 30 minutes.
  • Trend lines for GA4 Sessions / Trend line for GA4 Users charts: Daily line graphs for GA4’s top metrics.
  • Chart for GSC Clicks vs Impressions: Shows both clicks and impressions on the same chart to see if there is conversion of the impression numbers into clicks.
  • Sessions by Country chart: Bar graph of sessions by visitor country, helpful in seeing if traffic is matching up with target market.
  • Table for Top Search Queries: List of Search Console queries that generate traffic, with Clicks, Impressions, CTR, and Position columns.
  • Trend line for PageSpeed Score history chart: Graph that tracks the history of PageSpeed scores – easy to see the impact of a theme or content change in a regression.

4.2.2 How to check GA4 report  for Prestashops store

  • Period dropdown: Chooses the reporting window (for example, Last 28 days).
  • Compare to previous period checkbox: Check to compare the current data to that of the previous period
  • Total users / Active users / New users: Default GA4 audience measures – reach, active visitors and new visitors, respectively.
  • Sessions: Total number of visits.
  • Engaged sessions: Number of sessions that passed GA4’s engagement criterion (interaction beyond immediate bounce).
  • Views: Total number of page views during the period.
  • Views / Session: Average pages viewed per session, i.e. how deep the visitor is exploring the site.
  • Avg. session duration: Average time spent per visit.
  • Engagement rate / Bounce rate: % of engaged sessions / % of bounces (these two are in inverse correlation and should be watched together).
  • Events: Total number of tracked GA4 events during the period.
  • Realtime panel (Active users, By country, By device, By page): Who is on the website right now and where are they from, helpful for validating traffic driven by campaigns/promotions.
  • Traffic over time graph (Sessions/Users/Views checkboxes): Combined graph that allows to show/hide sessions/users/views.
  • Sessions by hour of day graph: Sessions distribution by hour of the day, allowing to determine most active hours, good for scheduling promotions or maintenance.
  • Dimension tabs (Pages, Landing pages, Channels, Source/medium, Campaigns, Countries, Cities, Devices, Browsers, Operating systems, Languages, New vs returning, Events, Key events): Tabs with Sessions, Users, and Views data segmented by the corresponding dimension, allows to ask very specific questions such as “which landing page performs better” or “which traffic channel performs better”.

4.2.3 How to Analyse the Google Search Console report

  • Period dropdown: Sets reporting period (e.g. 28 days).
  • Search Type dropdown (Web, Image, Video, News, Discover, googleNews): Allows filtering the report to specific type of Google search result.
  • Compare checkbox: Allows comparing the current data with the previous period when checked.
  • Clicks card: Total number of clicks to your storefront from Google search results.
  • Impressions card: Total number of impressions in Google search results, including unclicked results.
  • CTR card: Click-through rate, % of impressions that converted into clicks.
  • Average position card: The average ranking position of your pages for the queries that triggered them; a lower number is better.
  • Comparison of clicks and impressions graph: Displays the relationship between these two measures to determine if the rate of visibility is rising or falling in comparison to clicks.
  • Queries/Pages/Countries/Devices/Search Appearance tabs: All these allow you to break down the Clicks, Impressions, CTR, and Positions by these parameters to determine, for instance, what query results in the largest number of clicks or what country has the highest impressions.
  • Sitemaps sub-tab: Manages sitemap URLs without leaving Search Console/

4.2.4 PageSpeed report

  • Run button: Starts a new PageSpeed test against the selected target.
  • Target dropdown (Home page, Category, Product, Custom URL): Chooses which page type to test.
  • Device dropdown (Mobile, Desktop): Chooses which device profile to filter the history table by; a full Run tests both automatically.
  • From / To date fields: Restrict the history table to a specific date range.
  • Apply Button: Applies the applied filters to the History Table that follows.
  • Export to CSV Button: This exports the filtered history data in CSV format so that it can be analyzed later on
  • Score Trend Graph (Performance, Accessibility, Best Practices, SEO): This is the graph where all the four PageSpeed scores will be plotted throughout time, and this will help you to know whether there are any improvements or deterioration in the PageSpeed score since the latest modifications.
  • History Table Fields: Date (Test date), Target (Type of web page tested), URL (URL tested), Device (Mobile/Desktop), Performance/Accessibility/Best Practices/SEO (PageSpeed Score), LCP/INP/CLS (Core Web Vitals field/lab), and Source (Manual/Cron).4.2.5 Analytics Settings (Analytics Settings)

General Setting Configuration

  • Analytics Status: Enables or disables Analytics data collection and dashboards store-wide. Nothing in the Analytics section works until this is Enabled.
  • Default Period (days): The default reporting window, in days, used by dashboard widgets when no other period is selected (for example, 28).
  • API Cache TTL (minutes): How long API responses are cached before the module requests fresh data again. A higher value reduces API usage but delays how quickly new data appears; a lower value shows fresher data but calls the Google APIs more often.
  • Search Console Data Lag (days): Search Console data is delayed by Google itself, so this setting tells the module to skip the most recent N days when querying, avoiding incomplete or misleading recent-day figures.
  • History Retention (days): How many days of PageSpeed history to keep before older rows are automatically pruned, keeping the history table from growing indefinitely.

How to create Google Client Secret ID and Client ID for Google Analytics 4

  • PageSpeed API Key: Your Google PageSpeed Insights API key from Google Cloud, required for the PageSpeed report and scheduled checks to run at all.
  • Google OAuth Client ID: The OAuth 2.0 Client ID from your Google Cloud credentials, used to authorize the module to read GA4 and Search Console data on your behalf.
  • Google OAuth Client Secret: The matching OAuth 2.0 Client Secret. Both this and the Client ID must be saved before the Connect with Google button becomes usable.
  • Connected indicator and Disconnect Google button: Shows whether the module currently has an active Google connection, and lets you revoke stored access, refresh, and expiry tokens if you need to reconnect or switch Google accounts.

Properties (Store)

  • Search Console Property: The Search Console property URL used for this specific store; select one from the loaded list or enter it manually if the list fails to load. A refresh icon reloads the list of properties your connected Google account has access to.
  • GA4 Property: The GA4 property ID used for this store, selected from the loaded list or entered manually, with the same refresh option.
  • PageSpeed Test URL: The default URL tested when no other target is specified; if left blank, the store’s home URL is used instead.
  • Custom Test URL: An optional additional URL, used only when Custom URL is selected as a PageSpeed Cron target.

PageSpeed Cron

  • Enable Scheduled Checks: Turns on automatic, scheduled PageSpeed testing rather than relying on manual Run clicks.
  • Pages To Test (Home page, Category page, Product page, Custom URL checkboxes): Chooses which page types the scheduled job actually tests each time it runs.
  • Cron URL, Copy button, Regenerate button, Run now button: A unique, tokenized URL to paste into your server’s scheduled task system so PageSpeed tests run automatically on a timer. Copy grabs the URL, Regenerate invalidates the old token and issues a new one (useful if the URL was ever exposed), and Run now triggers the configured job immediately for testing.
  • Last Run: Shows the timestamp of the most recent scheduled run, or “Never” if the cron has not fired yet, which is a quick way to confirm your server scheduler is actually calling the URL.

Notifications

  • Enable Email Alerts: Turns on email notifications when PageSpeed scores drop or Core Web Vitals fail.
  • Alert Recipient: The email address that receives these alerts.
  • Alert Threshold (points): The minimum score drop, in points, required before an alert is triggered, preventing alerts from firing on minor, normal fluctuation.
  • Also Notify On Recovery checkbox: When enabled, sends a follow-up notification once a previously dropped score recovers.
  • Notify When Core Web Vitals Fail checkbox: Controls whether Core Web Vitals status changes specifically trigger their own alert.
  • Send test email button: Sends a sample alert to the configured recipient so you can confirm delivery before relying on real alerts.

4.3 Score History

  • Date from / Date to fields: Set the custom date range for every chart and table on the page.
  • Entity type dropdown (All, Products, Categories, and so on): Restricts the history shown to a single page type, useful for isolating whether one part of the catalog is improving or declining.
  • Filter button: Applies the selected date range and entity type.
  • Store SEO score card: The current store-wide score with its trend label (Improving, Declining, or No change).
  • Previous scan card: The score from the prior snapshot, for direct comparison.
  • Excellent / Acceptable / Not good cards: Counts of analyzed pages in each quality band for the selected filters.
  • Total issues card (with new/resolved counts): The total number of failing audit rules across all analyzed pages, plus how many are new and how many were resolved within the selected window (for example, over the last 7 days).
  • Overall SEO score trend chart and Date/Score/Change table: A visual and tabular record of every stored snapshot, showing exactly how the store score has moved over time.
  • SEO issues trend chart (New issues, Resolved issues, Open issues): Tracks how the total number of failing rules is changing, separate from the single score number, which can hide a rising issue count even while the overall score looks stable.
  • Product SEO score trend / Category SEO score trend charts: The same trend view scoped specifically to products and to categories.
  • Top improved entities / Top declined entities panels: Lists the specific pages that moved the most in either direction between snapshots, so you can investigate what changed on a page that suddenly improved or dropped.
  • Snapshot A / Snapshot B dropdowns and Compare snapshots button: Pick any two stored snapshots and generate a direct comparison table (ID, Date, Score, Change, Entities, Source, Version), useful for measuring the exact effect of a specific batch of changes, such as a redirect cleanup or a ChatGPT content pass.

4.4 URL Optimisation in Prestashop

4.4.1 Pretty URLs

  • Settings / Structure sub-tabs: Settings holds the on/off switch described below; Structure defines the actual URL patterns applied when Pretty URLs is enabled.
  • Enable Pretty URLs dropdown: Turns the feature on or off. When enabled, the module rewrites default PrestaShop URL patterns into cleaner, more readable versions.
  • Reset to PrestaShop defaults button: Restores the store’s original URL routing, useful if you want to fully undo Pretty URLs rather than simply disabling the toggle.
  • Save button: Applies changes made on this page.
  • The page’s own notes clarify that patterns which include an ID use PrestaShop’s own SEO routes, ID-less patterns use the module’s router, disabling the feature restores previous SEO routes from backup when one exists, and automatic redirects for Pretty URL changes only apply while the separate Redirects feature is also enabled.

4.4.2 How to fix 404 URLs in Prestashop

  • ID column: The internal record number for the 404 hit.
  • URL column: The exact storefront path that returned a 404.
  • Referer column: The page or external site the visitor came from before hitting the broken URL, useful for tracing where a bad link lives.
  • Visits column: How many times that specific URL has been hit, letting you prioritize the most frequently broken links first.
  • Last visited column: The timestamp of the most recent hit, useful for telling a stale one-off request apart from an ongoing problem.
  • Delete button (per row): Removes that recorded hit from the monitor once it has been reviewed or resolved.
  • Search filters (ID, URL, Referer, date range) and Search button: Narrow the list down to a specific URL pattern or time window.
  • Bulk actions button: Applies an action to multiple selected rows at once rather than one at a time.

4.4.3 How to detect Duplicate URLs (Duplicate SEO URLs) in Prestashop

  • Slug column: The specific friendly URL segment that is colliding across more than one page.
  • Entities column: Lists which pages (products, categories, CMS pages, manufacturers) share that slug.
  • Matches column: The number of pages involved in that particular collision.
  • Update action: Opens the group so you can change the friendly URL on the pages that need to become unique, then save to apply the fix.
  • When the store has no collisions, the page simply shows “No records found.”

4.4.4 How to add 301, 302, 303 redirects to URLs in Prestashop using Prestashop SEO Audit Module

  • Add redirect button: Opens a blank form to create a new redirect.

  • Import CSV button: Uploads many redirects at once from a CSV file instead of adding them individually.
  • Redirect count badge: Shows the total number of redirects currently stored for the shop.
  • ID column: The internal record number.
  • Name column: A label you assign for your own reference; it does not affect redirect behavior.
  • Source URL column: The old or broken URL that visitors and crawlers currently request.
  • Target URL column: The URL they are sent to instead.
  • Type column: The redirect type in use (301, 302, 303, or 404).
  • Active column: Whether the redirect is currently enforced on the storefront.
  • Edit button (per row): Opens the redirect for editing.
  • Search filters (ID, Name, Source URL, Target URL, Type, Active) and Search button: Narrow the list down when it grows large.
  • Individual redirect form fields: Name (your internal label), Source URL (required; the old path), Target URL (required; must be a relative path or a full http/https URL), Redirect type (301 for a permanent move, 302 for a temporary one, 303 for specific post-form-submission cases, or 404 to explicitly mark a URL as not redirected), and Status (active or inactive, active by default).

4.5 How to Edit Sitemap.xml in Prestashop

4.5.1 XML Sitemap

  • Enable XML sitemap dropdown: Turns the XML sitemap output on or off.
  • Sitemap URL display: Shows the live, public sitemap URL once enabled, ready to copy into Search Console.
  • Language sitemap URLs list: For stores with more than one active language, shows a separate sitemap URL per language, each of which should be submitted individually.
  • Enable RSS dropdown: Turns the RSS feed output on or off, independent of the sitemap.
  • RSS URL display: Shows the live RSS feed URL once enabled.
  • Include in sitemap checkboxes (Products, Categories, Information, Manufacturers, Suppliers): Chooses which entity types are listed in the sitemap; all five are checked by default.
  • Product limit (0 = all) field: Caps how many products are included in the sitemap; set to 0 to include every product regardless of catalog size.
  • Priority dropdowns (per entity type, for example Product Priority 0.8, Category Priority 0.7): A relative-importance hint passed to crawlers for that page type. As the page itself notes, this is a hint, not a ranking guarantee.
  • Change frequency dropdowns (per entity type, defaulting to Daily): Tells crawlers how often that page type typically changes, helping them plan how often to revisit it.
  • Save button: Applies all sitemap settings on this page.
  • An info banner also explains the recommended cron setup: submit the sitemap URL (or each language URL) in Google Search Console and Bing Webmaster Tools, then schedule the shown cron URL once a day at midnight so Google is automatically pinged after catalog changes.

4.5.2 HTML Sitemap

  • Enable HTML sitemap dropdown: Turns on a storefront page that lists important links for human visitors, separate from the XML sitemap built for crawlers.
  • Sitemap page URL display: Shows the live URL of that visitor-facing page once enabled.
  • Include pages checkboxes (Home page, Product pages, Categories, Information, Brands, New products, Special (Price drop), Best sellers, Popular): Chooses which page groups are linked from the HTML sitemap.
  • Custom URLs (Label and URL fields, delete icon, Add custom URL button): Lets you manually add extra links, such as an off-catalog landing page, that would not otherwise appear in the automatic groups.
  • Save button: Applies the HTML sitemap configuration.

4.6  How to edit Social OpenGraph Tags on Source Page 

  • Facebook Open Graph toggle: Enables Open Graph metadata (used by Facebook and many other platforms) on storefront pages so shared links show a proper title, description, and image.
  • Twitter cards toggle: Enables Twitter-specific card metadata on storefront pages.
  • Twitter card type dropdown (default summary_large_image): Chooses the visual layout used when a page is shared on Twitter/X.
  • Site name field: The name shown alongside shared links, typically your store’s brand name.
  • Site type dropdown (default Organization): Describes the nature of the site in structured data terms.
  • Facebook URL, Twitter URL, Instagram URL, LinkedIn URL, YouTube URL, Pinterest URL fields: Your store’s profile links on each platform, used to connect your storefront to your official social presence in structured data.
  • Save button: Applies all Social Cards settings.

4.7 How ChatGPT helps in Generating Content in Prestashop 

  • Enable ChatGPT toggle (default Disabled): Turns the AI content assistant on for the product and category SEO panels and for the Import/Export bulk workflow.
  • ChatGPT model dropdown (options include GPT-4o, GPT-4o mini, GPT-4 Turbo, GPT-4, and GPT-3.5 Turbo, default GPT-3.5 Turbo): Chooses which OpenAI model generates content; more capable models generally produce stronger output at a higher cost per request.
  • ChatGPT API token field: Your OpenAI API key, which the module needs to make generation requests on your behalf.
  • Save button: Stores the enabled state, model choice, and token.
  • Test API key button: Calls OpenAI directly to confirm the token and model actually work, before you rely on them inside a product panel.
  • A promotional banner on this and related pages also points to a separate Knowband add-on, the Knowband AI Content Generator (supporting Gemini and ChatGPT for product content and translation), which is a distinct product from this built-in ChatGPT tab and is outside the scope of this manual.

4.8 What is Robots.txt and How to edit it using Knowband’s Prestashop robots.txt editor

  • Public URL display: Shows the live, public web address of the robots.txt file, useful for confirming what crawlers actually see after saving.
  • File path display: Shows the exact server file path being written to, useful for troubleshooting with your hosting provider if saves fail.
  • Writable warning: Appears automatically if the server file cannot currently be written to, telling you to fix permissions on the shop root, or create a writable robots.txt file, before your changes will take effect.
  • Robots content textarea: The actual directives that will be published, defaulting to a permissive configuration:

 User-agent: *

  Allow: /

  • Save button: Publishes the entered directives to the live, public robots.txt file immediately.

4.9 How to Update the content of the Products in Bulk

  • Goal info box: Summarizes the intended three-step workflow: export as an optional backup, enhance selected fields with ChatGPT, then import the result.
  • Row count display (for example, “114 product/language row(s) available”): Shows exactly how many rows will be included in an export before you run it.
  • Exported fields list: Documents every field the export will contain: product, language, and store identifiers, name, meta title, meta description, meta keywords, tags, SEO URL, description and excerpt, focus keyphrase, minor keyphrases, allow search and allow follow link directives, advanced robots meta, canonical URL, SEO score, readability score, score analysis, content analysis, social title, social description, social image, and rating snippet fields (enable, average rating, best rating, worst rating, rating count).
  • Export button: Downloads the full JSON file described above.
  • Choose file control (Import panel): Selects a JSON file from your computer to upload.
  • Import button: Applies the selected file’s SEO fields, keyphrases, social data, and rating data to the matching products; only .json files are accepted.
  • ChatGPT enhance (SEO + readability) field checkboxes (Meta title, Meta description, Meta keywords, Focus keyphrase, Minor keyphrases, SEO URL, Social title, Social description, Tags, Description): Chooses exactly which fields the bulk ChatGPT pass should regenerate.
  • All products option / Max products field: Either processes the entire catalog, or limits the run to a specific whole number of products, useful for testing quality on a small batch first.
  • This panel stays disabled, with a message and a ChatGPT settings link, until ChatGPT is enabled and a token is saved under the ChatGPT tab.

4.10 General Settings for all the configuration in Prestashop SEO Audit Manager

General

  • Status toggle: The master switch for the entire module’s storefront behavior, including meta output, redirects, panels, and list scores. Nothing else works while this is off.
  • Enable SEO analysis toggle: Turns on SEO score cards, the SEO Audit sub-tab, and SEO columns on catalog list pages.
  • Enable readability analysis toggle: Turns on the readability scoring shown alongside the SEO score.
  • Enable auto analysis on edit toggle: When enabled, pages are automatically re-analyzed whenever they are saved, so scores stay current without a manual re-run.
  • Record 404 requests toggle: Turns on the 404 Monitor’s data collection.
  • Enable URL redirects toggle: Turns on redirect matching for storefront visitors; without this, entries in URL Redirects are stored but not actually applied.
  • Enable XML sitemap toggle: Turns on the XML sitemap output described in Section 4.5.
  • Enable RSS toggle: Turns on the RSS feed output.
  • Title separator field (default ” – “): The character or characters inserted between parts of a generated meta title, such as between the product name and the shop name.
  • Show products / categories / manufacturers / suppliers / CMS pages in search by default toggles: Sets the default index behavior for each entity type when an individual page has no override of its own; enabled by default for all five.

Meta templates

  • Product / Category / CMS / Brand / Supplier meta title template fields: The pattern used to build a meta title automatically when a page’s own meta title is empty, or when Force template is enabled for that type. Each supports shortcodes such as {product_name}, {category_name}, {cms_title}, {brand}, {supplier_name}, {shop_name}, and {title_separator}.
  • Product / Category / CMS / Brand / Supplier meta description template fields: The same idea applied to meta descriptions; these are blank by default, so no automatic description is generated unless you fill one in.
  • Force product / category / CMS / brand / supplier meta templates toggles: When enabled, the template is applied even if the page already has its own meta value, effectively overwriting it. When disabled (the default), the template only fills in genuinely empty values.

Cron and score history

  • Cron secure token field: A unique token used in the module’s cron URL; calling that URL with the correct token triggers a Store SEO score snapshot when score history is enabled. Leaving the field blank regenerates the token.
  • Enable SEO score history toggle: Turns on the snapshot system that powers the Score History page.
  • History retention dropdown (default Keep all history): Chooses whether old snapshots are kept indefinitely or pruned after a set period.
  • Retain history for (days) field (default 365): When retention is limited rather than set to keep everything, this sets how many days of history are preserved.
  • Automatic snapshot schedule dropdown (default Daily, midnight): Sets how often a new snapshot is taken automatically via the cron URL.

Search engine verification

  • Google verification code field: Paste your Google Search Console verification content value here if your site is not already verified another way, letting the module output it in the page header.
  • Bing verification code field: The same idea for Bing Webmaster Tools.

Save button: Applies every setting on the page in a single action.

5. Steps to Analyse On Page SEO for Product and Catogies Pages

Store owners can easily see the score of readability and SEO within Product , Categories and Brand Pages listing.

  • SEO Audit score circle (0 to 10): The page’s on-page SEO score, color-coded from red (low) through orange to green (strong) will be visible on the product listing pages using Prestashop SEO Audit Module
  • Readability score circle (0 to 10): The page’s readability score, scored and colored the same way but based on writing-style checks instead of structural checks.

  • Language selector: Switches the entire panel, including scores and every field below, to a different active store language, since each language is scored and edited independently.
  • AI Content Generator banner: Promotes the separate Knowband AI Content Generator add-on described in Section 4.7; it is not part of the scoring engine documented here.

Keyword & SERP sub-tab

  • Primary keyword field: The single main keyword this page is being optimized for; most of the primary-keyword checks in the SEO audit sub-tab read directly from this field, and several of them show “Not set” until it is filled in.

  • Supporting keywords field: A comma-separated list of additional, secondary phrases the page should also reflect where natural.
  • Search result preview panel: Simulates how the page’s title, URL, and meta description are likely to appear in a search result.
  • Desktop / Mobile toggle: Switches the preview between how it typically renders on a desktop search results page versus a mobile one, since mobile often truncates titles and descriptions more aggressively.
  • Title character count: Shown against a target of 60 characters, the general point at which titles start getting cut off in search results.
  • Description character count: Shown against a target of 160 characters, the equivalent limit for meta descriptions.

SEO audit sub-tab

Two columns, Page audit and Readability, each listing individual rules grouped under a Strong or Needs work heading. Every rule shows a numeric score, the rule name, a Result (what the page currently has), a Target (what it should have), and, for failing rules, a short tip. The verified rules visible in the panel are:

Page audit checks: Single H1; Image alt attributes; Supporting keyword in title, in description, in content, in subheading, in meta description, and in slug; Supporting keyword density (target 0.3 to 1.5 percent); Supporting keyword length (target up to 4 words); External links (target 1 to 3); Internal links; Text length (target at least 300 words); Primary keyword length (target up to 4 words); Primary keyword in meta title; Primary keyword in page title; Primary keyword in introduction (target: present in the opening roughly 150 characters); Primary keyword density (target 0.5 to 2.5 percent); SEO title width (target 30 to 60 characters); Meta description length (target 120 to 160 characters); Primary keyword in meta description; and Primary keyword in URL slug.

Readability checks: Sentence length (target 20 words or fewer per sentence); Flesch reading ease (target 60 or higher); Consecutive sentences; Passive voice (target roughly 10 percent or less of sentences); Minimum content length (target at least 300 words); Paragraph length (target at least 3 paragraphs); Subheading distribution (target at least 2 subheadings); and Transition words (target roughly 20 percent or more of sentences using connector words).

 

Indexing controls sub-tab

Covers whether the page is set to show in search results and whether links on the page should be followed by crawlers, along with any advanced robots directive or canonical URL override for that specific page and language.

Share preview sub-tab

Shows how the page will look when shared on social platforms, reflecting the Social Cards settings from Section 4.6 combined with any page-specific social title, description, and image you set here.

Star rating markup sub-tab

Available on products and categories, this controls whether a star rating snippet is generated for the page and, if so, the average rating and rating count values used to build it.

Score timeline sub-tab

Repeats the Current, Previous, Change, Highest, Lowest, Average, Trend, and Last analyzed figures, plus a history chart and table, that appear on the store-wide Score History page (Section 4.3), but scoped to this individual page only.

6. How to do a Complete SEO Audit in Prestashop 

Prestashop SEO Audit Module can run a PrestaShop SEO audit on products, categories, CMS pages, manufacturers, and suppliers, producing two separate 0 to 10 scores per page: an SEO Audit score covering structural checks such as keyword placement, meta length, alt text, and linking, and a Readability score covering sentence length, paragraph structure, passive voice, and transition words. A page can score well on one and poorly on the other.

A low score points to a specific, fixable gap rather than a vague quality problem, because every rule pairs a Result with a Target, as detailed field by field in Section 5. To act on it, open the page’s SEO Audit panel, work through Needs work items, and prioritize content quality (text length, primary keyword placement) before smaller technical checks like linking counts, which need editorial judgment rather than mechanical fixing.

None of these checks claim to be a direct Google ranking signal by themselves. They represent established on-page SEO and content-quality practices, things search engines and readers both respond well to, rather than guarantees of a specific ranking outcome.

7. Frequently Asked Questions

Question 1: I found several 404 URLs. How can I redirect them?
Open URL Optimisation> 404 URLs in the Knowband Prestatshop SEO Audit Module, find the entry, and use its Redirect action, which opens the URL Redirects form with the source URL prefilled. Add the target URL, choose a type (301 for a permanent change), and save. Only redirect when a genuinely relevant destination exists.

Question 2: How should I handle a URL that is no longer available?
If the content moved, add a 301 redirect from the old URL to the new one under URL Optimisation> URL Redirects. If nothing relevant replaces it, leaving it as a 404 is acceptable rather than forcing a redirect to an unrelated page.

Question 3: How can I improve a page with a low SEO score?
Open the page’s SEO Audit panel in Knowband’s Prestashop SEO Audit Manager and its SEO audit sub-tab, then work through the rules listed under Needs work using the Result and Target shown for each one.

Question 4: How to use ChatGPT to generate meta titles and descriptions?
You can use ChatGPT to generate meta title, description, social graph tags using the PrestaShop Complete SEO Module. Click on ChatGPT Tab, save a valid OpenAI token, then use the ChatGPT sub-tab inside a product or category SEO panel to generate, review, apply, and save.

Question 5: How can I check duplicate URLs?
 Open URL Optimisation in the PrestaShop SEO Audit Addon and click on duplicate URLs. Colliding friendly URL slugs appear grouped by slug with affected entities listed, and each page’s URL can be updated to a unique value.

Question 6: How can I check my XML sitemap?
By using Knowband’s Prestashop Sitemap XML Editor, you can make changes in sitemap and submit it inside Google Search Console’s Sitemaps tool.

Question 7: Can I connect Google Search Console for my Prestashop website?
Now you can Google OAuth Client ID and Secret, click Connect with Google, then select your Search Console Property or enter its URL manually.

Question 8: Can I view Google Analytics data inside the module?
Yes. Once GA4 is connected and a property is selected, the Analytics section shows sessions, users, views, engagement, traffic trends, and dimension breakdowns without opening Google Analytics separately.

Question 9: How can I identify SEO issues on product or category pages?
Review Score History’s issue trends or open the page directly and check its SEO Audit panel, which surfaces the specific rules failing along with the target value needed to pass.

Question 10: Does the redirect tool support bulk changes?
Yes. Knowband’s Prestashop Redirection Module allow to import CSV on the URL Redirects page to add many redirects in one upload instead of creating them individually.

Question 11: Is ChatGPT-generated content published automatically?
No. Generated content is written into the selected field for review, and the administrator must check it and save the host form for it to take effect.

Question 12: What does the Search Console Data Lag setting actually do?
This setting tells the module to skip the most recent few days when pulling Search Console data, since Google itself delays that data; without this adjustment, the newest days in a report could appear artificially low.

Question 13: Why does my Cron URL matter if I never open it manually?
 The Cron URL is meant to be called automatically by your server’s scheduled task system, not opened by hand. It is what actually triggers daily score snapshots, sitemap pings to Google, and scheduled PageSpeed checks, so it needs to be added to your server scheduler to keep those features running without manual effort.

The Prestashop SEO Audit Module integrates scoring, technical maintenance, and Google reporting in one module, making an SEO audit of PrestaShop not require the use of different modules for different processes. If you have faced any issue with this module, feel free to contact us at support@knowband.com.

OpenCart Backup and Restore Extension: Complete User Manual

Ask any OpenCart store owner when they last backed up their database, and most will hesitate before answering. It’s not that people don’t care about their data. It’s just that backups sit at the bottom of the to-do list, right under “get to it eventually.” Then one bad update, one failed plugin install, or one hosting glitch happens, and suddenly there’s no way back. That’s exactly the gap this OpenCart backup and restore Extension is built to close.

Instead of relying on you to remember, this backup extension by Knowband is one of the best OpenCart backup extensions that turns automatic store backup into something that just happens in the background, quietly, on a schedule, without you lifting a finger once it’s set up. Think of it as insurance for your catalogue, your orders, your customer records, and everything else sitting in your OpenCart database.

This isn’t just a database tool either. It works as a full OpenCart store backup Extension, meaning it can grab your files, your images, your database, or all of it together, depending on what you need at that moment. On top of that, it comes with a proper restore engine and a standalone restore script, so even if your admin panel becomes unreachable for some reason, you still have a way back in. That combination, backup plus a reliable restore path, is really what disaster recovery for eCommerce is supposed to look like.

The rest of this manual walks through every screen, every setting, and every button in Knowband’s OpenCart backup and restore Extension, so you can set it up correctly the first time and troubleshoot with confidence if something looks off later.

Quick tip before you start: Read the General Settings section first. The CRON token and the restore password you set up there are needed for every scheduled backup and every restore you’ll ever run through this OpenCart restore Extension. Skipping that step now just means backtracking later.

2. Getting Familiar with the Admin Panel of Backup and Restore Plugin

Once installed through Extensions in your OpenCart admin, the module adds its own dashboard and a handful of tabs. We’ll go through each one, starting with the Dashboard, since that’s the screen you’ll actually look at most often.

2.1 Dashboard 

The Dashboard exists to answer one question the moment you open it: is my store’s data actually protected right now, or not? You shouldn’t have to dig through logs to find out, so everything important is summarized right here.

Last Backup: Tells you whether the most recent backup job succeeded, failed, or is still running, along with the date, time, and how long it took.

Last Restore: Same idea, but for restores. This matters more than people think. You want to know a restore genuinely completed before you trust it, not just assume it worked.

Storage Used: Shows how much space your stored backups are eating up across every connected storage platform. Useful when you’re deciding whether it’s time to clean up old archives.

Platform Health: A quick status check across whatever storage destinations you’ve connected, local folder, FTP or SFTP, S3-compatible storage, or an OAuth-based cloud service. Each one is flagged as healthy or unreachable so problems don’t sit hidden until backup day.

Backup Activity: A simple view of how many backups ran over a given period, day by day, along with any that failed. Handy for spotting a pattern, like backups quietly failing every Sunday because of a server maintenance window.

Storage by Platform: Breaks down exactly how much space each connected storage destination is using. If your local server storage is filling up faster than expected, this is where you’d notice.

Latest Backup Composition: Shows what’s actually inside your most recent archive, database, images, other files, and roughly how big each piece is.

Recent Jobs: Lists your latest backup runs with quick Restore or Retry buttons right there, so if something failed overnight, you can act on it immediately instead of hunting through menus.

Restoration History: A snapshot of recent restore attempts, their outcome, and timing, so you can confirm at a glance whether a restore genuinely finished properly.

Connection and Error Feed: Live status and error messages as they happen. This alone often saves you a trip to the Logs tab, since you get the exact cause of a failure right there on the dashboard.

3. General Settings of the OpenCart backup and restore Extension

This is really the control center of the whole OpenCart backup Plugin. It decides whether the module runs at all, how your standalone restore script is protected, and what CRON command your host (or an external scheduler) needs to trigger scheduled runs.

Enable Module: A simple on/off switch. Turn it off and scheduled CRON jobs stop firing, though you can still run manual backups and restores from inside the admin panel whenever you like.

Restore Password: This protects the standalone restore script from being used by anyone who shouldn’t have access to it. It’s stored as a hashed value, never in plain text, and you’ll need it any time you restore your shop outside the normal admin interface.

CRON Secure Token: A unique token baked into every scheduled backup URL and command line trigger. Here’s the thing though, if you regenerate this token, every existing CRON job tied to the old one stops working. So the moment you regenerate it, go update every scheduler entry that references it. Don’t put that off.

Standalone Restore Script: This gives you the direct URL and server file path for restoring your shop even when the OpenCart back office itself won’t load. As long as you know your restore password, you can restore your shop from this script alone, without needing to log into admin at all.

Scheduled Backup (CRON): Ready-made commands, web URL, PHP CLI, or shell script, that you copy straight into your hosting panel’s CRON manager or any external scheduler. One trigger runs every enabled backup profile in a single pass.

4. Backups Tab in Knowband’s OpenCart backup Manager

This is where you run a one-off backup outside your regular schedule, and where you review every archive the OpenCart database backup Extension has generated so far. Pick a profile from the dropdown, hit Run, and watch progress update live on the same screen, no page reload needed.

4.1 What You’ll See in the Backups Table

ID: An internal identifier used to link a restore action back to the exact archive it came from.

Filename: The actual file saved to disk, usually timestamped so backups never overwrite each other by accident (and it’ll carry a .crypt suffix if you’ve turned on encryption).

Type: Tells you whether it’s a database-only dump, a files-only backup, or a complete backup covering both, matching whatever the profile was set to do.

Size: The compressed size of the finished file.

Profile / Platform: Which saved profile created this backup, and which storage destination is currently holding it.

Encrypted: A simple Yes or No showing whether AES-256 encryption was applied before the archive was stored.

Locations: Shows the from and to file paths, which is genuinely useful for confirming a copy actually made it to your remote destination and isn’t just sitting in a local staging folder.

Date: When the backup finished, used for sorting and for whatever retention rules you’ve set on that storage platform.

5. Profiles

A profile is basically a saved recipe for how you want backups done. It stores what gets backed up, where it goes, and who gets notified when it’s done. You can build as many profiles as your store needs, one for a quick daily database snapshot, another for a full weekly files and database backup, whatever fits your workflow.

5.1 Setting Up a Profile

Profile Name: Whatever name helps you recognise this profile later, in the dashboard, the backups list, or the restore history.

Backup Type: Choose whether this profile grabs both database and files, database tables only, or just files and folders with no data at all.

Database Tables: You can back up every table in your OpenCart database, or pick specific ones if you only need, say, orders and customers, and don’t care about log tables cluttering the archive.

Files & Folders: Same idea. Back up everything, or select specific folders. There’s also an exclude list below for skipping things like cache directories or temp files that just add bulk without adding value.

Exclude These Files or Folders: List anything you want skipped, one entry per line, things like system/storage/cache/ or image/cache/. These get skipped even when “all files” is selected above.

File Extensions to Include: If you only want certain file types backed up (php, js, css, whatever), list them here. Leave it blank and every file type gets included.

Tick Budget (seconds): Big backups take time, so the process runs in short bursts called ticks. This setting controls how long each burst runs, somewhere between 5 and 300 seconds. Lower it on shared hosting that tends to time out scripts.

Status: Enable a profile so it runs automatically during CRON jobs, or disable it so it only runs when you manually trigger it. Either way, you can always start it by hand.

5.2 Destination

Pick a storage platform here. You will need to create the destination first under the Platforms tab before it shows up as an option in a profile.

5.3 Email Notifications

Email on Completion / Email on Error: Decide independently whether successful jobs, failed jobs, or both trigger a notification email.

Send To: A comma-separated list of recipients. Leave it blank and it defaults to your store’s admin email address automatically.

Attach Restore Script: Turn this on and the standalone restore.php file gets attached to the completion email. That way, even if your server disappears entirely, you’ve still got a copy of the restore script sitting safely in your inbox.

5.4 Advanced Settings

Backup Filename: Customize naming using placeholders like {date}, {time}, {datetime}, {type}, and {version}. Leave it blank for the default naming pattern. One thing worth noting: a fixed filename without {datetime} in it will overwrite the previous backup instead of creating a fresh one, so be careful there.

Compression: Choose Auto (it picks between bz2, gz, or none automatically) or lock it to a fixed format. This determines whether your final archive ends up as .tar.gz, .tar.bz2, or plain .tar.

Max Part Size (MB): Split large archives into smaller chunks of a set size. Set it to 0 and splitting is disabled entirely.

Product Images: Choose whether product and source images are included in the backup or left out.

Encrypt Archive: This is where the OpenCart cloud backup Extension really earns its keep. Turn this on and AES-256 encryption gets applied to the archive before it’s stored locally or shipped off to a remote platform.

Encryption Key: The key needed to decrypt and restore that specific backup. There’s genuinely no recovery option if you lose it, so store it somewhere safe, and definitely somewhere other than on the same server.

Build File Map: Records a per-file size breakdown, which powers a detailed file map view later, handy for auditing exactly what ended up in a given archive.

Dump Values Per Line: Controls how many rows get batched into each INSERT statement when the SQL dump is written.

Dump Rows Per Select: Sets the maximum number of rows pulled per SELECT during the dump, using cursor paging (default is 25000). Lower this on memory-constrained hosting if you’ve got some seriously large tables.

6. Platforms

Platforms decide where your finished backups actually land. Local storage is fine as a starting point, but the real value of this OpenCart cloud backup Extension shows up once you connect something off-server, FTP or SFTP, an S3-compatible service (MinIO, Wasabi, Backblaze, Scaleway, take your pick), Google Cloud Storage, or an OAuth cloud provider like Google Drive, Dropbox, OneDrive, or Yandex.

Here’s the honest truth: keeping a copy away from your origin server is the single change that turns “I have backups” into actual disaster recovery for eCommerce. A backup sitting on the same server that just went down doesn’t help you much.

Platform Name: A friendly label used everywhere this platform gets referenced, in profiles, the backups table, and the dashboard’s health card.

Storage Type: Local folder, FTP/SFTP, an S3-compatible service, Google Cloud Storage, or an OAuth-based cloud provider.

Remote / Local Directory: The destination path for stored archives. It defaults to something like system/storage/backup/ if you leave it blank. Note that this field locks once the platform is created, so if you need a different path down the line, just set up a new platform rather than trying to edit this one.

Keep Remote Copies: The maximum number of archives this platform will retain. Set it to 0 and it keeps everything forever, which is convenient, but keep an eye on your available storage if you go that route.

7. Restore History

Every restore attempt gets logged here, successful or not, which matters most in the exact moment you’re actually trying to restore your shop under pressure. You shouldn’t have to trust that a restore “probably went fine.” This tab gives you a timestamped, per-file record instead.

ID / Filename / Type: Identifies the restore record and the exact archive that was restored, along with its type (Complete, Database, or Files only).

Source: Where the restore was triggered from. Usually it’s from inside the module itself, though the standalone restore script logs its attempts here too.

Status: Complete or Failed, showing the outcome of that particular attempt.

Launched By: The admin user who kicked off the restore. Useful for accountability on stores where multiple people have back-office access.

Started / Finished: Timestamps marking the operation from start to end, so you can work out exactly how long it took.

Message: The exact system message tied to that attempt, a permissions error on a specific folder if it failed, or a plain confirmation if everything went through fine.

8. Logs 

Whenever the Dashboard’s Connection and Error Feed doesn’t give you quite enough detail, this is the tab to check next. Every backup, every restore, and every connection test writes a row here, and you can filter by date, platform, type, and severity.

Date: The exact timestamp of the event.

Platform: Which storage platform this entry relates to, where applicable. It’ll be blank for events happening before a platform comes into play.

Type: The category of the underlying operation, local, ftp, or whatever connector type was involved.

Context: What action was actually being performed, backup, restore, or test_connection.

Level: Success or Error. Filtering by this alone clears out most of the noise when you’re scanning for a specific problem.

Message: The full, unfiltered system message, file paths, permission codes, network errors, whatever it is. Usually enough to figure out what went wrong without needing to escalate further.

9. Frequently Asked Questions

1. Does this replace my hosting provider’s backups?
Hosting-level backups are useful, but having your own Knowband’s OpenCart database backup Extension means you control the schedule, the retention, and where copies actually go, rather than relying entirely on your host’s policy.

2. Can I restore my shop if the admin panel won’t load? 
In the OpenCart backup and Restore Extension as long as you have the restore password, you can restore your shop directly through restore.php without ever touching the admin panel.

3. What happens if I lose my encryption key?
There’s no way around it, unfortunately. If a backup was encrypted and the key is gone, that archive can’t be decrypted. Store the key somewhere separate from your server; a password manager works well.

4. How often should scheduled database backup run in OpenCart?
It really depends on how often your store changes. A high-order-volume store might want daily or even more frequent database backups, while a smaller catalogue-based store might be fine with weekly. The scheduling is flexible enough to handle either.

5. Is cloud storage necessary, or is local storage enough?
Local storage is better than nothing, but cloud backup for OpenCart gives you real protection if the server itself fails, gets hacked, or becomes inaccessible. For genuine OpenCart data protection, an off-server copy is worth setting up.

10. Conclusion

This manual has walked through every tab in Knowband’s OpenCart backup and restore Extension, from the Dashboard all the way through to Logs, and it’s worth bookmarking for whenever you’re setting up a new profile or troubleshooting a restore later on.

If you ever hit a scenario this manual doesn’t quite cover- an unusual storage provider, a permissions quirk specific to your host, or a restore that isn’t behaving the way you expect- checking the Logs tab first will usually get you most of the way to an answer before you need to reach out for further support.

In short, treat scheduled backups and off-server copies as routine maintenance, not an emergency scramble. Once that’s part of your normal workflow, OpenCart data protection stops being something you worry about and just becomes something that quietly runs in the background, exactly the way it should

PrestaShop Blog Manager – AI Content & SEO Optimisation | Complete User Manual

Prestashop Blog Manager is a complete PrestaShop Blog Module developed for e-merchants who want to add blogs to their stores. Instead of relying on a separate blogging platform, you can publish articles, guides, and news directly inside prestashop store, then link that content back to your products for stronger SEO and better engagement. In other words, this Prestashop Blog Module works as both a publishing tool and a PrestaShop Content Marketing Module, so your writing effort translates into real commercial value.

As a comprehensive PrestaShop Blog Module, this gives you:

  • Blogs management with rich text, gallery images, video or audio embeds, SEO fields, and related products links.
  • Integration of categories, flexible tags, and author profiles individually, keep your content well organized while improving search engine visibility and user navigation.
  • Reader comments with moderation, replies, star ratings, emoji reactions, likes, and bookmarks, all of which work together as a PrestaShop Blog Engagement Addons suite.
  • Built-in AI content generation and translations through ChatGPT or Google Gemini, which speeds up writing without compromising the blog content quality.
  • Bulk import from WordPress exports and RSS or Atom feeds, so migrating an existing blog takes minutes rather than days.
  • An XML sitemap, RSS feed, friendly URLs, and GDPR-ready hooks that keep your blog compliant and easy for search engines to crawl.
  • Full multistore and multilanguage support, since every setting can be scoped per shop and per language.

Altogether, these capabilities make Prestashop Blog Manager one of the most complete PrestaShop Blog Addons available on Prestashop Addons, whether your goal is search visibility, community building, or simply keeping customers on your site longer.

2. Installation and Uninstallation

  1. Upload the zipped file from the Upload Option in the module manager.
  2. In the Back Office, go to Modules > Module Manager, search for “KB Blog,” and click Install.
  3. Once installation is complete, you will see the configuration button on the page.
  4. Click on Configure; now you will be redirected to the general setting page of the Prestashop Blog Module

NOTE: Important: If the Clean Database on Uninstall setting (found under General Settings, then Maintenance) is set to Yes, all blog data, including posts, categories, and comments, will be permanently deleted. Therefore, leave this set to No if you plan to reinstall the module later and want to keep your content.

3. Admin Panel Overview of the Blog Manager Module

In this section, you are going to learn how to create blog, manage content on your website. This module also helps your website to rank higher.

Once installed, a dedicated Knowband Blog Module sections appears in the PrestaShop Back Office sidebar. This is the control centre for your PrestaShop Blog Module, and it includes the following sub-sections:

Dashboard – shows KPI summary and sample-data generator
General Settings – includes all global configuration for the module
Posts –Using posts, you will create and manage blog articles
Categories– Manage nested post categories for the listed blogs
Tags– Manage flat tag taxonomy per blogs
Authors – Manage author profiles for the blogs
Image Type – Define named image-size presets for blogs
Comments – Moderate reader comments
Sliders – Manage home-page slider slides
Banners – Manage zone-targeted promotional banners

SEO and Sitemap – Handles Sitemap and RSS settings, plus URL structure
AI – Configure AI content-generation providers
Import – Import from WordPress or RSS feeds

4. DASHBOARD

 

The Dashboard is the first screen you see when you open this PrestaShop Blog Manager Module, and it gives you a quick snapshot of how your blog is performing.

KPI Cards

Six KPI cards summarise your content at a glance. The Posts card shows the total number of posts, broken down into Published, Draft, and Scheduled sub-badges. The Categories card shows your total category count, and the Tags card shows your total tag count. The Authors card totals your author profiles, while the Image Types card totals your configured image-size presets. Finally, the Pending Comments card shows how many comments are still waiting for moderation, and it highlights in red whenever that number is greater than zero, so nothing slips through unnoticed.

Quick Action Buttons

Each KPI card includes a direct link button, such as Manage Posts or Manage Categories, so you can move from overview straight to action in a single click, without hunting through menus.

Sample Data Generator

If the Posts, Sliders, or Banners sections are still empty, a Create Sample Data button appears. Use this feature whenever you want to explore the module before writing real content. Clicking it automatically generates one sample author named Jane Doe, complete with a bio, three sample categories called News and Updates, Tips and Tutorials, and Product Highlights, and six sample tags: PrestaShop, E-Commerce, Marketing, SEO, Design, and Tutorial.

5. GENERAL SETTINGS

To configure the PrestaShop Blog Manager Module, navigate to KB Blog > General Settings.

Keep in mind that changes only take effect after you click the Save button at the bottom of the page. All General Settings fields are part of a single form, so even if you switch tabs before saving, clicking Save on any tab will save the changes made across all tabs.

Module Status
When disabled, the blog is completely hidden from the storefront, which is useful during setup, testing, or maintenance windows. Enable it to see the functionality of the module.

5.1 Listing and Display

This part of the settings shapes how your PrestaShop Responsive Blog Addons layout looks and behaves for visitors.

Posts per Page sets how many posts show on each listing page, and the value must fall between one and two hundred, with ten used as the default.

Blog Grid Layout Type controls the visual layout of the post listing, and you can choose between a clean Grid, a simple List, or a magazine-style Masonry layout, with Grid selected by default.

Enable Previous/Next Navigation adds Prev and Next links on individual post pages, so readers can keep browsing without returning to the listing, and this is on by default.

Display Read More Button shows a Read More button on post cards in listings, which tends to improve click-through rate, and it is also on by default.

Show Post View Count displays how many times a post has been viewed, adding a layer of social proof for popular articles, and Show Reading Time displays an estimated reading time so readers can decide whether to dive in now or bookmark the article for later; both are enabled by default.

Sort Posts By sets the default sorting order for every post listing, offering Newest First, Oldest First, Most Viewed, Title A to Z, or Title Z to A, with Newest First as the default.

Finally, Date Format determines how dates are formatted on the storefront, and you can choose from eight PHP date presets, with d/m/Y used as the default format.

5.3 Feature Toggles

The blog module of prestashop allow the store owner to activate the engagement with users using blogs features available on the frontend.

  • Enable Image Zoom : Allow visitors to zoom into the featured image on the post detail page. : a click/hover triggers a zoom overlay. 
  • Enable Post Like : Shows a like/heart button on posts, which readers click to register a like without leaving a comment. 
  • Display Like on Hover Only : Keeps the like button hidden until a visitor hovers over the post card. Please note that this feature requires Post Like to already to be enabled; the button is rendered but visually hidden until hover. 
  • Enable Emoji Reactions : Adds emoji reaction buttons to posts.
  • Reaction Set : As you enable the emoji reaction, these emoji reactions appear. The type of reaction set includes Love, Haha, Wow, Sad, Angry. 
  • Enable Bookmarks : Allow readers to save posts for later. Now store owner can add a bookmark feature to the post so that reader can save the blog and read later. 
  • Enable Authors : Shows author information on posts and generates author listing pages. 
  • Use Font Awesome Icons : This feature loads the Font Awesome icon library, which ensures icons render consistently across the blog UI. 
  • Enable Social Share Buttons : Adds share buttons for Facebook, X/Twitter, LinkedIn, WhatsApp, and Email. 
  • Show Blog Posts on Product Pages : Displays a linked blog posts block on product pages. This shows posts explicitly linked to that product via the post editor’s Products section. This can help in increasing ranking of the product pages.

5.4 Comments

This tab turns the module into a fully moderated comment system, giving you control over how, when, and by whom comments are posted on your website.

  • Enable Comments: Allows readers to leave comments on posts as part of your website comment system. When switched off, the comment form and the entire comment thread are hidden from the storefront, effectively letting you turn off comments on your website.
  • Allow Guest Comments: Permits visitors who are not logged in to comment, removing the login requirement from the comment form and enabling anonymous commenting. This lowers friction and increases engagement by letting people comment without login.
  • Auto-Accept Comments: Determines whether comments are published immediately or held for review in the comment moderation queue. When turned off, every new comment enters the moderation queue, so pre-moderation and comment approval stay active until this setting is changed.
  • Enable Comment Replies: Allows one level of threaded replies (nested comments), so readers and admins can respond directly under an existing comment using the reply to comments feature.
  • Enable Star Rating: Adds a 1-5 star rating field to the comment form, turning it into a simple comment rating system where the rating is captured alongside the comment text.
  • Enable reCAPTCHA: Protects the comment form with Google reCAPTCHA v2 for spam protection on your comment form. This requires a Site Key and a Secret Key to function, and the reCAPTCHA widget is embedded directly in the form to help prevent comment spam.
  • Site Key / Secret Key: Authenticate the reCAPTCHA widget against Google’s service as part of your reCAPTCHA v2 setup, and are entered once reCAPTCHA is enabled. Without both keys, reCAPTCHA cannot function.
  • Admin Email Notification on New Comment: Sends an email notification for new comments to the admin whenever a new comment is submitted.
  • Notification Email Address: Specifies the address used for comment notification settings and receives comment notifications, falling back to the shop’s default email if left empty.
  • Comment System: Determines which comment plugin powers storefront comments, swapping the rendered comment widget accordingly. Available options are Native, Disqus, Facebook Comments, and Disabled, with Native set as the default, letting you choose the best comment system for your website.
    • Disqus Shortname: Required when Comment System is set to Disqus; identifies your Disqus site as part of your Disqus shortname setup.
    • Facebook App ID: Required when Comment System is set to Facebook Comments; authenticates the Facebook comments plugin widget.
    • Facebook Comment Count: Sets how many comments display initially when using Facebook Comments, with a minimum of 1. Default number of comment has been set 5.
    • Facebook Colour Scheme: Sets the visual theme of the Facebook widget, with Light or Dark mode as the available values and Light as the default.

5.5 URLs and SEO Meta

This URLs and SEO Meta controls how blog URLs and meta tags appear to search engines and is the heart of the module’s on-page SEO configuration.

  • Main Blog URL: Sets the base URL slug for the blog. For example, entering “blog” produces yourdomain.com/blog. Only letters, numbers, and hyphens are accepted. Default value: blog.
  • Use .html URL Suffix: Appends .html to every blog URL. This rewrites generated URLs to end in .html for a traditional SEO style.
  • Blog URL Pattern: Determines how individual post URLs are built by selecting the rewrite pattern applied to new URLs. Available values: /blog/{slug}, /blog/{category}/{slug}, and /blog/{year}/{month}/{slug}. The default is the simple slug pattern.
  • Main Meta Title / Main Meta Description / Main Meta Keywords: These fields set the meta tags for the main blog listing page. Each is available per language and is rendered in the page’s <head> section, influencing how the blog listing appears in search results.
  • Main Page Description: A rich-text introduction to your content strategy, displayed on the main blog listing page for both readers and search engines.
  • Listing Meta Title / Listing Meta Description / Listing Meta Keywords: These apply the same meta concept specifically to category, tag, and author listing pages. Each is available per language and reused consistently across all listing-type pages.

5.6 Display and Author

This tab controls page layout and author presentation, giving you full control over how your PrestaShop blog module content appears to visitors.

  • Sidebar Position: Sets where the widget sidebar appears. Values: Right, Left, None. Default: Right.
  • Author Name Display Format: Controls how author names are displayed across your blog manager. Values: Full Name, First Name Only, Last then First, Username. Default: Full Name.
  • Show Category on Post: Displays the post’s category on cards and detail pages, helping readers and search engines understand your content structure.
  • Show Category Image: Shows the category thumbnail on listing pages for a more visual, professional blog layout.
  • Show Category Description: Shows the category’s description text to give visitors more context before they click through.
  • Show No-Image Placeholder: Shows a placeholder graphic when a post or category has no image, preventing a broken-image icon from appearing on the storefront.
  • Default Author Avatar: Sets a fallback avatar image used when an author has no personal avatar. Accepted formats: JPG, PNG, GIF, or WEBP, up to 2 MB.

5.7 Images and Thumbnails

This tab controls which image-size presets are used where, and lets you regenerate thumbnail files across your PrestaShop blog module.

  • Detail Page Image Size: Chooses the preset applied to the featured image on post detail pages. Populated automatically from your active Image Types (Section 10).
  • Listing Page Image Size: Chooses the preset applied to post cards in listings.
  • Thumbnail Image Size: Chooses the preset applied to small thumbnails in widgets and related posts.
  • Delete Old Thumbnails (button): Deletes all previously regenerated thumbnail files (JPG, PNG, WEBP) from the posts, categories, and authors image directories. Use this before regenerating thumbnails with new sizes, so no stale files remain in your blog manager.

Tip: After creating or changing Image Types and selecting new sizes here, use Regenerate Thumbnails in the Image Types section (Section 10) to rebuild every thumbnail accordingly.

5.8 Responsive Columns and Spacing

This tab fine-tunes how many post cards appear per row at each screen size, along with the spacing between them, ensuring your blog module looks polished on any device.

  • Desktop Large (≥1200px): Columns default 4, Spacing default 20px.
  • Desktop (992–1199px): Columns default 3, Spacing default 20px.
  • Tablet (768–991px): Columns default 2, Spacing default 15px.
  • Mobile (<768px): Columns default 1, Spacing default 10px.

Each breakpoint has its own independent column and spacing value, applied via CSS grid rules on the storefront. The minimum number of columns per row at any breakpoint is 1, and spacing values can never be negative. As a result, the post grid re-flows automatically as the visitor’s screen size changes, keeping your responsive blog layout consistent across devices.

5.9 Post Detail Settings

This tab controls two related feature groups shown on individual post pages: the Table of Contents and Related Posts, both designed to improve readability and engagement on your blog.

5.9.1 Table of Contents

  • Generate Table of Contents: Automatically builds a linked table of contents from heading tags (h2, h3) in the post content. Recommended for long-form guides to improve readability and keep readers on the page longer.
  • TOC Position: Sets where the table of contents is inserted. Values: Top, Left, Right. Default: Top.
  • Sticky TOC: Keeps the table of contents fixed in place as the reader scrolls. Values: On/Off.
  • Minimum Headings for TOC: Sets the minimum number of headings a post must contain before a TOC is generated, preventing short posts from being cluttered with an unnecessary outline. Default: 3.

5.9.2 Related Posts

  • Enable Related Posts: Shows a grid of related posts at the bottom of each post detail page, keeping visitors engaged and reducing bounce rate.
  • Related Posts Match By: Determines how related posts are selected. Values: Category only, Tags only, or Category and Tags combined. Default: combined.
  • Related Posts Count: Sets the total number of related posts displayed. Default: 3.
  • Related Posts per Row: Sets how many related posts appear per row. Default: 3.
  • Carousel Mode: Makes related posts scroll as a carousel instead of a static grid, adding a more dynamic feel to your PrestaShop blog module.

5.10 Widgets

This tab configures the sidebar and other widget-area building blocks of your PrestaShop Blog Widget Module. Each widget can be enabled or disabled, titled, and shown or hidden per device where relevant.

  • Recent Posts Widget: Lists the most recent posts. Fields include an Enabled toggle, a Title, a Number of posts field, and Devices (Desktop, Tablet, Mobile), each independently toggleable.
  • Categories Widget: Lists blog categories. Fields include a Title and a Maximum categories shown field, where entering 0 shows all categories.
  • Tags Widget: Displays a tag cloud. Fields include a Title and a Number of tags shown field.
  • Popular Posts Widget: Lists the most-viewed articles. Fields include a Title and a Number listed field.
  • Archives Widget: Lists monthly archive links in a dropdown. Fields include a Title and a Number of months listed field.
  • Search Widget: Shows or hides a blog search box in the sidebar. Fields include a Title.
  • Footer Blog Block: Shows a compact list of recent blog links in the storefront footer, giving your latest articles extra site-wide visibility.
  • Home Page Blog Block: Shows a recent-posts section on the storefront home page. Fields include a Title and a Display count. This block respects the same Desktop, Tablet, and Mobile device settings as other widgets.

5.11 Home Slider Settings

This tab controls the behavior of the home-page image slider, one of the standout visual features among the PrestaShop Blog Addons bundled with this module. The actual slide content itself is managed separately in the Sliders section (Section 12).

  • Enable Home Slider: Activates the slider on the storefront home page.
  • Autoplay Slides: Advances slides automatically without visitor interaction. Values are On or Off.
  • Autoplay Interval: Sets the time between slide transitions, measured in milliseconds. The minimum accepted value is 1000ms.
  • Show Dot Navigation: Displays clickable dot indicators below the slider.
  • Show Arrow Navigation: Displays left and right arrow buttons.
  • Pause on Hover: Stops autoplay while the cursor hovers over the slider, giving readers time to read a slide before it advances.
  • Transition Effect: Sets the animation used when switching slides. Values are Slide or Fade.
  • Thumbnail Navigation: Shows small thumbnail previews below the slider for quick navigation.
  • Slider Theme: Sets the overall visual skin of the slider. Values include Default, Dark, and Boxed.

5.12 Banners

This tab contains the master toggle for zone banners. Individual banner content is managed separately in the Banners section (Section 13).

  • Enable Zone Banners: Turns every promotional banner placed across blog zones on or off at once. This acts as a master switch layered above each individual banner’s own Enabled toggle.

5.13 Appearance and Extras

This tab covers general visual theming and optional extra widgets.

  • Dark Mode: Sets the blog’s colour theme. Values include Off, On, and Auto ( according to system) and a Toggle button in which the user can change the mode. 
  • Blog Layout Theme: Sets the visual theme preset for blog pages. Values include Classic, Magazine, Minimal, and Full-width.
  • Enable Social Feed Widget: Shows a sidebar widget embedding social media content. Fields once enabled include a Facebook Page URL and a Twitter/X Handle, entered without the @ symbol.
  • Enable Newsletter Widget: Shows a newsletter sign-up widget. Fields once enabled include a Newsletter Widget Title and Newsletter Widget Text.
  • Enable Post Star Rating: Shows a star-rating widget on post detail pages, separate from comment ratings.
  • Use Store Theme Font: Makes the blog use your PrestaShop theme’s font instead of the Google Fonts below. When Off, two font pickers become active.
  • Heading Font: Chooses the font used for headings when Use Store Theme Font is Off, with 8 options available.
  • Body Font: Chooses the font used for body text when Use Store Theme Font is Off, with 8 options available.
  • Custom CSS: A textarea for injecting custom CSS rules across all blog pages. <style> and <script> tags are stripped automatically for security.

5.14 Maintenance

This tab covers admin convenience and data-retention behavior.

  • Show KB Blog Tab Menu at Top of Pages: Displays the horizontal quick-navigation bar at the top of every KB Blog admin page.
  • Clean Database on Uninstall: Drops every KB Blog database table the moment the module is uninstalled. This permanently deletes all blog data, including posts, categories, and comments, on uninstall. Treat this setting with real caution and set it to Off if you intend to reinstall later and keep your content.

Once every field above has been reviewed, click Save to apply all settings on the General Settings page.

6. How to create a blog in PrestaShop

To create a blog in PrestaShop, navigate to Prestashop Blog Manager Module by Knowband, click on the Posts. Now you will have the options to create blog by clicking on Add, then proceed to add the informations like Post title, URL, Content, meta details etc. This section will walk you through all the feature available in Posts .

6.1 Creating or Editing a Post

Post creation is divided into five sections in Prestashop Blog Module.

6.1 Content

  • Title: The post headline, required in the default language and limited to 255 characters.
  • URL Slug: A Regenerate URL from Title button allow you to refresh it anytime.
  • Excerpt: A summary shown on listing pages and in the Related Posts section. 
  • Content: The full post body, written through a rich-text editor. Once AI is configured (Section 15), buttons appear inside this field to generate content, generate an excerpt, or translate the post.
  • Author: Store owners can assign a post to an author from your Authors list, or leave it as None if no author should be shown.
  • Categories: Assigns the post to one or more categories via a nested picker. At least one category must be ticked.
  • Default Category: Chooses the primary category used for URL generation. This is only relevant when the category-based URL pattern is selected (Section 5.5).
  • Tags: Here you can add the tags for the blog post, which will differentiate your post within the website using posts.
  • Series: Groups a post into a named content series such as “Fashion Basics” helping readers read the blog post in a series, in this way this module also work as PrestaShop Content Marketing Module strategy.

6.2.2 How to improve blog SEO in Prestashop

  • Meta Title: The post’s search-result title, available per language, with an AI Generate button.
  • Meta Description: The post’s search-result summary, available per language, with an AI Generate button.
  • Meta Keywords: Target keywords for the post, available per language, with an AI Generate button.

6.2.3 Media

  • Post Type: Determines the media format of the post. Values include Standard, Video, Audio, and Gallery.
  • Featured Image: The main image for the post, required for the Standard type. Accepted formats include JPG, JPEG, PNG, GIF, and WEBP.
  • Cover Image ALT Text: It is recommended to add the alt text fo the cover image as, it also helps in ranking the blog post.
  • Video URL: Appears only when Post Type is Video and holds the source URL for the embedded video.
  • Audio URL: Appears only when Post Type is Audio and holds the source URL for the embedded audio.
  • Gallery: Appears when Post Type is Gallery and lets you upload multiple images, drag them into any order, delete individual images, and set one image as the cover. The gallery displays in a lightbox on the post detail page.

6.2.4 Products

  • Related Products: This Prestashop blog Manager is best blog module which also helps in marketing and cross selling. This module allow you to attach PrestaShop products to the post, one of the most valuable PrestaShop Related Products Blog Addons for driving cross-sell traffic.

6.2.5 Publish

  • Status: Sets the post’s publication state. Values include Draft, Published, and Scheduled.
  • Publish Date: Records when a Published post went live.
  • Scheduled Date: Sets the future date and time a Scheduled post auto-publishes. This is required whenever Status is Scheduled.
  • Featured: Pins or highlights the post.
  • Sticky: Pins the post to the top of the listing.
  • Allow Comments: Enables or disables comments for this specific post, overriding the module’s global Comments setting.
  • Show on Post Detail Page: When Off, hides the post from its own detail URL, though it may still appear in listings.
  • Save as Draft / Publish (buttons): Quick actions that save the post and set the respective status in a single click.

7. How to manage blog categories

Navigate to Knowband Prestashop Blog Manager> Categories to organize your content. This section covers everything on how to add categories in a blog and manage them at scale.

7.1 Browsing the Categories List

The list shows each category’s internal ID and Name with bulk actions which let you Enable Selected, Disable Selected, or Delete Selected. A category cannot be deleted while it still has child categories, so remove the children first.

7.2 Creating or Editing a Category

If you’re wondering how to add categories in a blog using this module, this user guide covers every field you’ll need:

  • Name: The category’s display name.
  • URL Slug: The category’s URL-friendly identifier, validated as a link-rewrite.
  • Description: Rich-text content shown on the category listing page.
  • Meta Title / Meta Description / Meta Keywords: The SEO fields for the category’s listing page.
  • Enabled: Controls storefront visibility for new categories.
  • Cover Image: A category thumbnail. Accepted formats include JPG, JPEG, PNG, GIF, and WEBP.
  • Parent Category: Sets the category’s place in the hierarchy. Circular references, where a category becomes its own ancestor, are automatically blocked.
  • Group Access: Selects which customer groups can view posts in this category.

8. Tags

Navigate to Knowband Blogs > Tags to manage the tags taxonomy using these PrestaShop Blog Tags Addons.

8.1 Browsing the Tags List

The list shows each tag’s internal ID, Name, and a Posts column counting how many posts carry that tag. 

8.2 Creating or Editing a Tag
From here, you can add the tag with details like tag title, meta description, meta title and meta keywords. Furthermore, you can also add the tags from the Post Creation. There you will find an option to add tags. After the tag addition, these tags will display individually here.

 

9. Authors

Navigate to PrestaShop Blog> Authors to add multi-author profiles with social links using this PrestaShop Multi-Author Blog Module.

9.1 Browsing the Authors List

The list shows each author’s internal ID, a small Avatar thumbnail, Name, an Enabled toggle, and the Created date. Bulk actions allow you to Enable Selected, Disable Selected, or Delete Selected authors.

9.2 How to add Author in a Blog

As a core piece of the PrestaShop Blog Module, this module supports full author profiles, which helps in SEO as well.

  • Name: The author’s display name, required in the default language.
  • Bio: The author’s biography, shown on the author page and optionally on posts. Supports rich text.
  • Avatar: The author’s profile photo. Accepted formats include JPG, JPEG, PNG, GIF, and WEBP, up to 2 MB.
  • Facebook URL / Twitter/X URL / Instagram URL / LinkedIn URL / Website URL: Each links out to the corresponding social profile.
  • Meta Title / Meta Description / Meta Keywords: The SEO fields for the author’s listing page.
  • Enabled: Controls whether the author appears on the storefront at all.

10. Image Types

Navigate to Knowband Blog Manager > Image Type to control image quality and performance across the blog. Image types define named size presets used to generate thumbnails for posts, categories, and authors.

10.1 Browsing the Image Types List

Each entry shows its internal ID, preset Name (such as blog_large), target Width and Height in pixels, the Entity it applies to (Post, Category, or Author), and an Enabled toggle. A single bulk action, Delete Selected, is available. Out of the box the module ships with three presets. blog_large is sized 800×600 for Posts, blog_medium is sized 400×300 for Posts, and blog_thumb is sized 150×150 for Posts.

10.2 Creating or Editing an Image Type

  • Name: A unique identifier for the preset, limited to 64 characters. Spaces are not recommended.
  • Width / Height: Define the target dimensions in pixels. Both are required positive integers.
  • Applies To: Determines which entity uses this size. Values include Post, Category, and Author.
  • Enabled: Controls whether this size appears in the Image Size dropdowns under Settings.

10.3 Regenerating Thumbnails

  • Regenerate Thumbnails (button): Triggers a background process that loops through every post, category, and author image, generating a resized copy for each active image type matching the corresponding entity. Use this whenever you add new image types or change existing sizes, so images stay sharp and properly sized across the blog.

11. How to Enable Blog Comments

Navigate to Knowband PrestaShop Blogs> Comments to moderate reader comments with this PrestaShop Blog Comment Module. Comments are submitted by readers or users on the frontend, so this section is strictly for moderation. You cannot create a comment directly from the Back Office.

11.1 Browsing the Comments List

Each row shows the comment’s internal ID, the Post it belongs to (filterable), the commenter’s Author name and Email (filterable), and a Comment preview that reveals the full text on hover. Status appears as Pending, Approved, or Spam, with inline quick-action buttons. A Rating column shows the star rating given, if enabled; a Reply column flags admin replies, and a Date column records submission time. Store owner can filter by post, email, or status. Bulk actions let you Approve Selected, Mark as Pending, Mark as Spam, or Delete Selected. Row-level actions include View, Reply, and Delete.

11.1 Replying to a Comment

Clicking Reply opens a form with a single required Reply textarea. Submitting it creates a new comment entry marked as an admin reply, displayed differently on the storefront. If the original commenter left a valid email address, they receive a notification email containing your reply.

12. Sliders

Navigate to Knowband PrestaShop Blog> Sliders to manage the home-page slider with this PrestaShop Blog Slider Module. The slider appears on the storefront home page once Enable Home Slider is turned on under General Settings (Section 5.11).

12.1 Browsing the Sliders List

Each slide shows its internal ID, a Title with a small thumbnail preview, a drag-and-drop Position column, and an Enabled toggle. Bulk actions let you Enable Selected, Disable Selected, or Delete Selected.

12.2 Creating or Editing a Slide

  • Title: The slide’s headline, shown as an overlay and required in the default language.
  • Subtitle: Adds a secondary line of text below the title.
  • Button Text: Sets the label for the call-to-action button, such as “Read More.”
  • Link URL: Sets the destination when the slide or button is clicked.
  • Position: Sets the numeric sort order within the slider.
  • Enabled: Controls whether the slide appears at all.
  • Slide Source: Determines how the slide’s content is populated. Values include Custom, where you enter data manually, Blog Post, which auto-fills from a chosen post’s title, image, and URL, and Blog Category, which auto-fills from a chosen category. Choosing Blog Post or Blog Category reveals a corresponding selection field and lets you promote existing content without duplicating work.
  • Slide Image: Uploads a custom slide image. The recommended size is 1920×600px, and accepted formats include JPG, JPEG, PNG, GIF, and WEBP.

13. Banners

Navigate to KB Blog > Banners to configure promotional banners shown in defined zones on blog pages using these PrestaShop Blog Banner Addons. Banners only display once Enable Zone Banners is turned on under General Settings (Section 5.12).

Five zones are available. Blog Top sits above the main blog listing, Blog Bottom sits below it, Sidebar sits inside the blog sidebar, and Post Top and Post Bottom sit above and below the post content on detail pages.

13.1 Browsing the Banners List

Each banner shows its internal ID, a Title and Image with a small thumbnail, the Zone it occupies, a drag-and-drop Position within that zone, and an Enabled toggle. Bulk actions let you Enable Selected, Disable Selected, or Delete Selected.

13.2 Creating or Editing a Banner

  • Title: An internal label for the banner, not shown to visitors.
  • Image Alt Text: Accessibility alt text for the banner image.
  • Zone: Determines the display location and is required. Values include Blog Top, Blog Bottom, Sidebar, Post Top, and Post Bottom.
  • Link URL: Sets where the banner points when clicked.
  • Position: Sets the sort order within the selected zone.
  • Enabled: Controls whether the banner is active.
  • Start Date / End Date: Optionally let a banner appear only within a defined window, useful for time-limited promotions.
  • Banner Image: The actual graphic. Accepted formats include JPG, JPEG, PNG, GIF, and WEBP.

Tip: Placing a banner in the Post Bottom zone can direct engaged readers straight toward a relevant product or promotion, another example of these PrestaShop Blog Banner Addons working double duty for conversions.

14. SEO and Sitemap

Move to Knowband Prestashop Blog> SEO and Sitemap to fine-tune search-engine indexing settings as part of this PrestaShop SEO Blog Addons suite.

14.1 Sitemap Settings

  • Enable Sitemap: Includes the blogs in XML sitemap for search engines.
  • Include Posts / Include Categories / Include Tags / Include Authors / Include Archives: Store owners are allowed to choose or control whether that content type is added to the sitemap.
  • Change Frequency: Signals how often the sitemap indicates content changes. Values include Always, Hourly, Daily, Weekly, Monthly, Yearly, and Never.
  • Priority: Sets the sitemap priority value, on a scale from 0 to 1.

14.2 RSS Feed Settings

  • Enable RSS Feed: Generates a standard RSS 2.0 feed for the blog, letting subscribers and content aggregators follow new posts automatically.

Click Save to apply the settings above.

14.3 Information Panel

After saving, a read-only panel displays:

  • Sitemap URLs: One per installed language, following a pattern like yourdomain.com/blog/sitemap?lang=en.
  • RSS Feed URLs: One per installed language.
  • Content Counts: Published Posts, Active Categories, Tags, Active Authors, Archive Months.
  • Ping Bing (button): Sends a sitemap ping directly to Bing’s search engine. Google retired direct sitemap pinging in 2023, so submit your sitemap through Google Search Console instead. This makes the PrestaShop SEO Blog Addons here especially useful for merchants managing multi-engine indexing.

15. How to use AI for blog writing

Navigate to Knowband Prestashop Blog  > AI to connect the blog to OpenAI’s ChatGPT or Google Gemini as part of this PrestaShop AI Blog Module, helping you write post content, excerpts, metadata, ALT text, tags, and translations directly from the post editor.

15.1 Configuration

  • Enable AI: The master toggle for all AI features. AI buttons only appear in the Post editor once this is On and a valid API key has been saved.
  • AI Provider: Chooses which AI service powers generation, either ChatGPT (OpenAI) or Google Gemini.
  • ChatGPT API Key / Gemini API Key: Store your provider credentials securely. Neither is ever displayed in plaintext after saving, and a Test Key button lets you verify each one.
  • ChatGPT Model: Picks which OpenAI model to use, populated from your account’s available models, with options such as GPT-4o Mini, GPT-4o, GPT-4.1 Mini, and GPT-4.1.
  • Gemini Model: Picks which Gemini model to use, with options such as Gemini 2.5 Flash, Gemini 2.5 Pro, and Gemini Flash Lite.
  • Temperature: Controls creativity versus focus in AI outputs, on a scale from 0 (fully deterministic) to 2 (very creative).
  • Max Tokens: Sets the maximum length of AI responses, on a scale from 1 to 8192.
  • Default Language: Sets the language AI-generated content is produced in, following your shop’s default language unless changed.
  • Enable Usage Logging: Records every AI call, including provider, action, token count, employee, and success or fail status, in a log table. No prompt text or API keys are ever stored in that log.

Click Save to apply these settings.

15.2 Where AI Features Appear in the Post Editor

Once AI is enabled and a valid key is saved, these buttons appear directly in the post form as part of the PrestaShop AI Content Addons toolkit:

  • Generate Post Content (Content field): Builds a full blog post body using the title and excerpt as context.
  • Generate Excerpt (Content field): Summarizes the existing content into a short excerpt.
  • Translate To (Content field, with language selector): Translates the current content into another language.
  • Suggest Tags (Tags field): Suggests relevant tags based on the post content.
  • Generate Meta Title / Generate Meta Description / Generate Meta Keywords (SEO section): Write SEO-optimized versions of each field.
  • Generate ALT Text (Featured Image): Writes descriptive alt text for the cover image automatically.

These PrestaShop AI Content Addons features save significant time for merchants publishing content at scale.

15.3 Recent AI Usage Log

A table at the bottom of the AI page lists the most recent AI calls, showing Date, Employee, Provider, Action, Tokens consumed, and Status (OK or Failed).

16. Import

Navigate to Knowband Prestashop Blog > Import to bring existing content into the module.

16.1 How to Import a WordPress Blog

Use this to migrate content from an existing WordPress site.

  1. In WordPress, go to Tools > Export and export All Content, producing a .xml file in WXR format.
  2. In KB Blog, under Import > WordPress Import, choose that exported file. The maximum file size is 20 MB.
  3. Select Default Status for Imported Posts: Sets the status assigned to imported posts. You can use the status from the export file itself, force everything to Draft, or force everything to Published.
  4. Click Import. Progress and results display live as the migration runs.

Items already imported previously are skipped automatically, since they are tracked in an internal import log.

16.2 RSS Import

Sets up automated content import from any RSS or Atom feed.

  • Enable Scheduled RSS Import: Gates the cron endpoint responsible for automated imports.
  • Feed URL: The full http or https address of the RSS or Atom feed to import from.
  • Frequency: Sets how often the cron job runs an import. Values include Hourly, Daily, and Weekly.
  • Default Author: Assigns every imported post to a specific author.
  • Default Category: Assigns every imported post to a specific category.
  • Default Status: Sets whether imported posts land as Draft or Published.
  • Max Items per Run: Caps how many feed items import during a single cron run, on a scale from 1 to 100.

After saving, three tools become available:

  • Run Now: Immediately imports up to the configured Max Items from the feed via AJAX, with no page reload.
  • Test Feed: Fetches and parses the feed without importing anything, then reports the item count and feed title.
  • Cron URL: A link to copy into your server’s cron or task scheduler, such as cPanel Cron Jobs or a Linux crontab entry. It includes a built-in security token and respects your configured Frequency, so calling it more often than scheduled simply does nothing.

16.3 Field Mapping for WordPress

This mapping is saved as JSON inside the module configuration. Select None for any field you would rather not import. Store owners are allowed to map the parameters like title, categories, authors slug etc. This module really helps owners in blog management.

16.4 Field Mapping for RSS

This mapping is saved as JSON inside the module configuration. Store owners are allowed to map the parameters from RSS Feed blogs like title, categories,cover image, content, excerpt, tags authors,slug etc

16.5 Recent Import Log

This log shows the last 100 import operations. Columns include Date, Source (WordPress or RSS), resulting Status (Imported, Skipped, Failed), and a Message with further details or an error description.

Final Thoughts

From writing your first article to configuring AI-assisted content and multi-author profiles, Knowband Prestashop Blog  gives PrestaShop merchants a genuinely complete PrestaShop Blog Module, covering SEO, reader engagement (likes, reactions, comments), and traffic-driving links back to product pages. Whether you’re running it as a standalone PrestaShop Content Marketing Module or layering it on top of an existing storefront, it’s built to scale with your content strategy. For technical support, contact Knowband at support@knowband.com

👉Explore the Module with Our Video Guide

 

OpenCart WhatsApp CRM and Order Notification Extension – Complete User Guide

1.0 Introduction

Order confirmation emails have a deliverability problem that most store owners do not think about until a customer complains. WhatsApp messages achieve open rates of 95 to 98 percent against email’s 20 to 25 percent, a difference that shows up directly in how many customers actually see the updates you send them. An OpenCart WhatsApp CRM Extension takes the manual work out of it, and alerts go to the customer at the right moment without your team needing to do anything.

The Knowband OpenCart WhatsApp CRM and Order Notification Extension ties your store to the WhatsApp Business API. New order confirmations and status change alerts are sent automatically. Your support team can chat with customers in real time from within the OpenCart admin. Promotional messages can also be sent to a segmented contact list at whatever time you schedule. A chat icon on your storefront puts your agents within reach of any visitor.

This guide documents every tab and field in the extension. Every setting is described exactly as it appears in the admin panel, whether you are doing a fresh setup or working through a specific configuration.

1.1 Who Is This OpenCart WhatsApp CRM Extension For

This extension suits:

  • Store owners who want WhatsApp order alerts to be sent automatically without needing a developer to set it up.
  • Support staff who need an OpenCart WhatsApp Live Chat Extension so they can reply to customer messages from the OpenCart backend.
  • Merchants who want an OpenCart WhatsApp Integration Extension that covers both automated notifications and outbound marketing campaigns in one place.
  • Agencies that are building OpenCart stores for clients who have asked for a WhatsApp Business API connected to their shop.

2.0 Installation Guide of the OpenCart WhatsApp Live Chat Extension

Step 1: Download the Extension

After purchasing, download the videomate.ocmod.zip file, which contains the complete video plugin for OpenCart.

1. Unzip the downloaded file; this will contain the videomate.ocmod.zip and necessary folders.
2. Go to the upload folder and locate the admin and catalog files.

3. Copy these files into the root directory of your OpenCart store

Step 2: Upload via Extension Installer

  1. Go to Extensions > Extension Installer in your OpenCart admin panel.
  2. Upload the videomate.ocmod.zip file.
  3. Once installed, go to Extensions > Modifications, and click Refresh to apply changes.

Step 3: Assign User Permissions

Navigate to System > Users > User Groups, then edit your group and enable permissions for extension/module/videomate.

Step 4: Enable the Module

Navigate to Extensions > Extension Installer in your OpenCart admin dashboard.

2.3 Common Installation Issues

Upload fails: Your host is probably blocking the file size. Have them increase upload_max_filesize and post_max_size in the PHP settings to at least 32 MB.

Emails not going out: Go to System, then Settings, then the Mail tab. The extension uses the store’s default mail configuration unless you have set a different one at the form level.

Page looks wrong: Do a browser cache clear. Then reset the OpenCart theme cache using the blue cog icon on the Dashboard refresh panel.

3.0 Admin Panel Overview

The OpenCart WhatsApp CRM Extension adds its own section to the OpenCart admin sidebar after installation. Each tab in that section has a specific job:

  • Module/API Settings: This is where your WhatsApp Business API credentials go, along with the webhook configuration.
  • Templates: Where you write and submit templates to WhatsApp for review.
  • Order Settings: Decides which order-based WhatsApp alerts are active and when they are sent.
  • Order Status Trigger: Links each order status to the template that gets sent for it.
  • CRM: The live chat panel for two-way conversations with customers.
  • Contacts: Your full contact database, with import and export built in.
  • Lists: Groups of contacts that promotions get sent to.
  • Promotions: Builds and schedules outbound campaigns to your contact lists.
  • Agents: The support agents your visitors see in the storefront chat pop-up.
  • Chatbox Settings: Settings that control the floating WhatsApp icon on your storefront.
  • Message Logs: A timestamped record of all messages sent and received through the extension.

4.0 Module/API Settings of the OpenCart WhatsApp CRM Module

Nothing in the OpenCart WhatsApp Business API Extension works until this tab is filled in. Four credentials are required, and all four must be correct before the extension can send or receive anything.

4.1 WhatsApp API Settings

Enable Extension: You can easily enable/disable the plugin with this toggle. Turn it off, and the extension stops sending messages, and the storefront chatbox is removed.

Facebook App ID: Pull this from the Meta Developer Console. It identifies which Meta app the API request is coming from.

Facebook Access Token: This needs to be a permanent token, not the short-lived one shown in the API Setup tab. Head to Meta Business Settings, add a System User, give it full control over your app and WABA, then generate a token. The three permissions you need are whatsapp_business_messaging, whatsapp_business_management, and business_management. That token goes here.

WhatsApp Business Account ID (WABA ID): Your WABA ID lives in the Meta Developer Console, inside the WhatsApp section of your app. Copy it from there.

Phone Number: The registered WhatsApp Business number you want all messages to come from. Pick it from the dropdown.

Save the form once all four fields are filled. Any field left empty or entered incorrectly shows a validation error right away. An expired access token does the same.

4.2 Webhook Setup

Below the credential fields, the Configuration Information section shows a Webhook URL and a Verify Token that are specific to your store. These go into the Meta Developer Console.

In your Meta app, go to WhatsApp, then Configuration, and paste the two values into the webhook setup fields. After that, the extension picks up incoming messages and template status updates on its own.

The webhook is not strictly required to get started. If it is not set up yet, you can click Sync Templates inside the Message Templates tab at any time to manually pull the latest approval status from WhatsApp.

5.0 Order Settings

The Order Settings tab is where you control when the OpenCart WhatsApp Order Notification Extension sends messages and which templates it uses for them.

5.1 WhatsApp Order Settings

Enable New Order Message: When this is on, a WhatsApp message goes out to the customer every time a new order lands in your store.

Enable Order Status Message: When this is on, customers get a WhatsApp update each time their order status changes. Turning this on also adds a WhatsApp number field to the customer address form so shoppers can put in the number where they want to receive those updates.

5.2 New Order Message Templates

This section lists your store languages. For each one, pick the approved Utility template that sends when a new order is placed. The dropdown only pulls in Utility templates that WhatsApp has already approved.

If the dropdown has nothing in it, your templates are either sitting in the queue waiting on WhatsApp review, or they were categorised as Marketing instead of Utility. Create a Utility template in the Message Templates tab, wait for approval, then come back here and save your selection.

6.0 Message Templates

Templates used anywhere in the OpenCart WhatsApp CRM Extension are created and submitted here. WhatsApp has to approve a template before it can be assigned to any message flow. Both submission and status checking happen inside this tab.

 

6.1 Templates List

Every template tied to your WhatsApp Business Account shows up in this table. The columns cover Template ID, Name, Use Case, Category, Language, Status, and the date the template was created. Status can be Pending, Approved, or Rejected.

The Sync Templates button pulls the latest status data from WhatsApp whenever you need it. Search fields at the top let you filter by template name, category, language, or a date range.

6.2 Creating a New Template

Name: Use lowercase letters and underscores only. Spaces and special characters are not accepted.

Use Case: Pick the use case that fits: For Orders, For Marketing, or For Customers.

Category: Utility or Marketing. Any template assigned to order notifications has to be in the Utility category. WhatsApp reviews the body text and may move a template to Marketing if it reads like a promotion.

Language: Choose the language the template is written in. If your store serves customers in multiple languages, you will need a separate template for each one.

Header Type: Not required. You can leave it as No Header or add a Text, Image, Video, or Document header if the message needs one.

Message Body: The message itself. Bold, italic, and strikethrough options are in the editor toolbar. Use Insert Variable to drop in things like the customer’s name, their order ID, or the order total. The Body Preview below the editor shows you how the finished message reads as you build it.

Footer: An optional line of smaller text that sits below the main body.

Enable CTA Button: Switch this on to attach a CTA button to the message. You will need to fill in the Button Text and the URL it points to.

Hit Save when the template is ready. WhatsApp gets it for review right away. Straightforward templates are usually clear in a few minutes. More complex ones can take a few hours. Once it is approved, it shows up in Order Settings, Order Status Templates, and the CRM template list.

7.0 Order Status Triggers

Each order status in OpenCart can be paired with a Utility template in this tab. When an order hits a status that has a template assigned, the extension sends that message to the customer as an automated WhatsApp update.

Every status your store uses is listed in the table: Awaiting check payment, Payment accepted, Processing in progress, Shipped, Delivered, Canceled, Refunded, and the rest. Each row shows whether notifications are on or off and which template is currently mapped to that status.

Hit Edit on any row to change it. Toggle Enable WhatsApp Notification on, pick a Utility template for each store language from the dropdown, and save. The row reflects the change straight away.

8.0 CRM: Live Two-Way Chat in Best WhatsApp CRM Extension

The CRM tab is the live chat section of this OpenCart WhatsApp Live Chat Extension. Your contact threads sit in a sidebar on the left. Click on any one of them to bring up the full conversation on the right.

Two tabs are at the bottom of the chat window: Message and Template. The message is for free-text replies, though this only works during the 24-hour window that opens when a customer sends you something first. After that window closes, swap to the Template tab. Approved Marketing templates can go out from there at any time.

Automated order alerts sent by the extension also show up inside the relevant contact thread. That way, your support team always has the full picture of what the customer received before they start a reply.

9.0 Promotions

The Promotions tab is for outbound WhatsApp campaigns. You pick the list of contacts, choose the template, set when it goes out, and the extension takes it from there.

9.1 Creating a Promotion

Name: An internal name so you can tell this campaign apart from others. It is not included in the message the customer receives.

Contact List: Choose which WhatsApp List this campaign targets. Every contact on that list will get the message.

Template: Pick an approved Marketing template from the dropdown. Marketing category templates are the only ones that appear here.

Schedule at: The date and time you want the campaign to go out. It has to be in the future. If you leave this blank, the campaign runs on the next CRON trigger instead.

Save it. The campaign will sit in the list with a scheduled status. The CRON command at the top of the Promotions page needs to be added to your server if you want campaigns to send automatically. It checks for pending campaigns every minute.

After a campaign runs, the Sent and Failed numbers fill in. The WhatsApp Business API bills you per message, so it is worth sending to a small group of 10 to 20 contacts first, just to see what the actual cost looks like before you go to the full list.

10.0 WhatsApp Contacts

Every phone number the extension can message is stored here. A contact needs a phone number and a name at a minimum. Linking to an OpenCart customer account is optional.

10.1 Adding a Contact Manually

Phone Number: Start with the country code, no leading zero, no spaces or dashes. An Indian number, for example, would be entered as 919310436362.

Name: Whatever name you want displayed for this contact in the extension.

Click Save when done.

10.2 Importing Contacts in Bulk

Click Download Template to get the CSV file in the right format. Add your contact data to it, come back to WhatsApp Contacts, and click Import Contacts to upload the file. Numbers that are already in the extension get their records updated. Numbers that are not in there yet get added as new contacts. Export to Excel and Export to CSV are both available if you need to pull the whole contact list out.

11.0 WhatsApp Lists

A WhatsApp List is just a named group of contacts. Promotions target one list at a time. To create one, click Add new list, type a name, and save it. If you mark a list as Default, new contacts get added to it automatically.

You assign contacts to lists from the WhatsApp Contacts tab. One contact can be in more than one list at the same time.

12.0 Chatbox Settings

This tab is for the floating WhatsApp icon on your storefront. When a visitor clicks it, a pop-up appears listing the agents you have set up. They tap Chat next to whoever they want to speak with, and it opens a WhatsApp conversation on their phone.

Enable Chatbox: Switch this on to show the icon on the storefront, or off to hide it.

Icon Position: Where the icon sits on the screen. Options include Bottom Right and Bottom Left.

Theme Color: The main color used for the icon background and the pop-up header. It defaults to WhatsApp green, which is #25D366.

Header Title: The text shown at the top of the chat pop-up. The placeholder example is “Chat with us”; enter whatever heading you want your visitors to see when the popup opens.

Sub Title: A short line shown below the header title. Use this to set response time expectations or any brief supporting text.

Greeting Message: The opening message displayed to visitors inside the chat pop-up before they select an agent. Accepts plain text. A WhatsApp emoji picker and formatting options are available in the bottom right of the text area.

Online Text: The label shown on agent cards when the agent is available. Defaults to “Online.”

Offline Text: The label shown on agent cards when the agent is not available. Defaults to “Offline.”

Hit Save Settings once you have made your changes.

13.0 WhatsApp Agents

Agents are the people your storefront visitors see in the chat pop-up. Each agent card has a name, a department or role, and a Chat button. When a visitor taps that button, it opens a WhatsApp conversation with that agent’s number on their device.

Active: Controls whether this agent is visible in the storefront popup.

Agent Name: The name shown on the agent card. Capped at 50 characters.

Contact Number: The agent’s WhatsApp number, country code included (for example, +919876543210). If you use the same number as the one in the API Settings, conversations from this agent also appear inside the CRM tab.

Department: The team name or role shown under the agent’s name. Up to 50 characters, and it can be set differently per language.

Display Order: A number that controls where this agent appears in the pop-up. The lower the number, the higher up the agent shows.

Avatar Type: Pick a Predefined Avatar from the available options, or upload an image of your own.

14.0 Message Logs

The Message Logs tab keeps a record of every message that has passed through the OpenCart WhatsApp Messaging Extension, both sent and received. Each row tells you the Direction, the phone number it involved, the template used if any, a preview of the message text, the WhatsApp Message ID, the delivery status, and the timestamp.

Order alerts, CRM replies, and campaign messages all end up in this list. A success status means the WhatsApp API received and accepted the message. The date range, phone number, and template filters make it easy to find a specific message. When something is not delivering the way it should, this tab is the right place to start looking.

15.0 Frequently Asked Questions

Q: What is the OpenCart WhatsApp CRM Extension, and what does it do?

The Knowband OpenCart WhatsApp CRM and Order Notification Extension connects your OpenCart store to the WhatsApp Business API. Order confirmations and status change alerts go to customers on WhatsApp automatically. Your team handles live customer conversations from inside the OpenCart admin through the CRM tab. You can run scheduled WhatsApp campaigns to contact lists through the Promotions tab. A storefront chatbox lets visitors tap through to your support agents on WhatsApp directly.

Q: Does the OpenCart WhatsApp Messaging Extension require a WhatsApp Business Account?

Yes, it does. The OpenCart WhatsApp CRM Extension needs a WhatsApp Business Account, a phone number registered as a WhatsApp Business number, and a Meta Developer App that has WhatsApp Business API access set up. All three are needed before the API Settings tab can be completed and before the extension can send anything.

Q: How does the OpenCart WhatsApp Order Notification Extension send alerts when a new order is placed?

When Enable New Order Message is switched on in Order Settings, the OpenCart WhatsApp Order Status Extension sends an approved Utility template to the customer each time an order goes through. For status updates, turn on Enable Order Status Message as well. That puts a WhatsApp number field on the customer address form. Once a customer fills it in and their order moves to a status that has a template mapped in Order Status Templates, the message goes out to that number straight away.

Q: Why are no templates showing in the Order Settings dropdown of the OpenCart WhatsApp CRM Extension?

Order Settings only lists Utility templates that have been approved by WhatsApp. An empty dropdown usually means templates are still in the review queue or sitting in the Marketing category by mistake. Head to Message Templates, build a Utility template, wait for the approval to land, then go back to Order Settings. The Sync Templates button is there if you want to pull the latest approval status without waiting for the webhook.

Q: How does the live chat work inside the OpenCart WhatsApp Live Chat Extension?

The CRM tab in the OpenCart WhatsApp Messaging Extension shows all contact threads on the left side. Click a contact to open the conversation. Use the Message tab to type a reply while the 24-hour window from the customer’s last message is still open. Once that closes, the Template tab is the way to reach them; any approved Marketing template can be sent from there, regardless of when the customer last wrote. Automated order alerts from the extension appear in the thread too, so your team always has context.

Q: Can I run WhatsApp marketing promotions through the OpenCart WhatsApp CRM Extension?

Yes, through the Promotions tab. Go there, click Add new promotion, give it a name, pick a Target List, choose a Marketing template, and set a time in the future for it to go out. The CRON command on the Promotions page needs to be on your server for campaigns to send automatically; it checks every minute for anything due. Before sending to your whole list, send it at a small group of 10 to 20 contacts first to see what the API costs look like.

Q: How does the OpenCart WhatsApp Business API Extension connect to WhatsApp?

The OpenCart WhatsApp Order Status Extension also available on Opencart Marketplace with Price $49.99, connects through four fields in the Module/API Settings tab: your Facebook App ID, a permanent Access Token, your WhatsApp Business Account ID (WABA ID), and your registered phone number. On top of that, you paste the Webhook URL and Verify Token shown in the Configuration Information panel into your Meta Developer Console. With those two steps done, the OpenCart WhatsApp Business API Extension handles message sending, template approval tracking, and incoming messages without any further manual input.

Q: Can I bring existing contacts into the OpenCart WhatsApp Order Status Extension from a spreadsheet?

Yes. Open the WhatsApp Contacts tab and click Download Template to get the CSV in the right layout. Put your contact data into it, then upload it using Import Contacts. If a phone number is already in the extension, that contact’s record gets updated. Anything new gets added. Once the contacts are in, you can assign them to WhatsApp Lists and target them in your next promotion.

Q: A template was rejected inside the OpenCart WhatsApp CRM Extension. What now?

Go to Message Templates and look at what the rejected template says. WhatsApp will reject templates that put sales or promotional language inside a Utility template, contain anything inaccurate, or go against its commerce policies. Delete the rejected one, fix whatever the issue was in the body text, and submit a fresh template. If the tone was the problem, write the body more like a factual update and less like a sales message.

Q: Which versions of OpenCart work with the Knowband WhatsApp CRM Extension?

The Knowband OpenCart WhatsApp CRM Extension runs on OpenCart 3.x. If you need compatibility details for versions released after this guide was written, the extension product page on the Knowband website will have the most current information. You can also contact the Knowband support team directly.

16.0 Conclusion

The Knowband OpenCart WhatsApp CRM Extension, also known as the OpenCart WhatsApp CRM and Order Notification Extension, is a full OpenCart WhatsApp Integration Extension. Order alerts go out on their own. Live support runs through the CRM tab. Campaigns reach targeted contact lists on a schedule you define.

The only thing that happens outside the extension is pulling your API credentials from the Meta Developer Console. After that, templates, order mappings, contact lists, agent profiles, and promotions are all handled from inside OpenCart.

For help getting set up or questions about any feature, the Knowband support team is at support@knowband.com. There are also documentation pages and setup videos on the Knowband website.

OpenCart SocialAI Pro Extension Complete User Manual

Running a busy OpenCart store usually means someone has to sit down, look at the catalogue, and write captions for Facebook, LinkedIn, and X every single time a product launches or comes back into stock. The Opencart AI Social Media Post Generator Extension, also known as the OpenCart SocialAI Pro Extension, removes that issue by linking your frontend catalogue straight to an AI writing engine and to your connected social accounts, so posts can be written and published without anyone typing a single line of copy.

Three tasks happen inside this one extension automatically: the AI writes the caption, a rule decides when that caption goes out and to which network, and a history log keeps a record of everything that was ever generated, whether it was published, held as a draft, or scheduled for later.

1. 0 Installation of the Opencart Social Media Automation Extension

The setup below installs the Opencart Social Media Automation Extension the same way as any other OpenCart module. From the OpenCart admin, go to Extensions and open the Installer screen. Upload the ocmod.zip file exactly as it was downloaded after purchase.

Open the FTP, copy the files under the upload folder to the site root file.

Go to the modification, refresh and clear the cache.

2.0 Admin Panel Overview

Once configuration opens for the first time, three tabs are visible across the top: General Settings, Rules, and Post History. Each one handles a different part of the workflow, and together they make up the entire Opencart AI Social Media Post Generator Extension experience.

General Settings is where the AI provider gets connected, where API keys live, and where each social account gets authorised through OAuth.

Rules are the automation layer; this is where a store owner decides which products qualify, what has to happen for a post to fire, which platforms receive it, and what tone the AI should write in.

Every post the extension has ever produced shows up here with its status, the platform it targeted, which AI engine wrote it, and whether a rule triggered it or a human did. A post can also be started from scratch directly inside this tab, without involving a rule at all.

3.0 General Setting of Opencart AI Social Media Post Generator

Enable Module: Enable or disable the functionality on the frontend using the toggle.

Choosing an AI Provider: Three engines are available from a single dropdown, and a store can only run one of them at a time:

OpenAI: The OpenAI ChatGPT choices include GPT-5, GPT-5 Mini, GPT-5 Nano, GPT-4.1, GPT-4.1 Mini, and GPT-4o.
Google Gemini: Gemini 3 Pro, Gemini 2.5 Pro, Gemini 3.5 Flash, and Gemini 2.5 Flash are all selectable for stores that would rather stay inside Google’s ecosystem.
Anthropic Claude: Claude Opus 4.8, Claude Sonnet 4.6, and Claude Haiku 4.5 are offered for anyone who already has Claude API access or simply prefers its writing style.

Switching providers takes effect on the very next post generated; it doesn’t touch anything already sitting in Post History from before the change.


Entering the API Key: Store admins must paste the key for whichever provider was chosen above into this field. It needs to be a real, currently active key with either prepaid credit or billing turned on. A key that’s expired or been revoked will only show its error the first time the extension actually tries to generate something. The key itself stays in your store’s own database and is sent directly from your server to the provider, with nothing routed through a third party.


Temperature Slider: Store administrators can use the Temperature Slider to control the creativity and variation of AI-generated social media content. Lower values generate more consistent and predictable marketing copy, while higher values produce more creative, engaging, and diverse social media posts.


Token Ceiling: This shows how many tokens a single generation request is allowed to use, somewhere between 100 and 2,000.


Handles for X: Two optional fields sit here: one for the store’s own X handle, one for whoever is credited as the content’s author. Neither has any bearing on whether a post actually goes out; leave both blank if there’s no X presence to reference.


Linking Each Social Account: All three networks get connected from this same General Settings tab, and the Opencart Auto Publish Facebook LinkedIn Extension functionality handles each one through its own dedicated authorization flow.


Facebook: Click the Facebook connect button and a popup opens asking for posting permission on a Page. If more than one Page is managed under that account, a picker shows up so the right one can be chosen. As soon as that’s confirmed, the settings screen updates to show which Page is now linked: this is the Opencart Facebook Auto Post Extension side of the setup, and it’s usually the fastest of the three to finish.


LinkedIn: Open the LinkedIn Developer Portal first and find the app that was registered there. The Auth tab on that app holds the Client ID and Client Secret: copy both into the matching fields here. Before clicking the Connect button on this end, take the redirect URL shown in the extension and add it to the authorised redirect list inside the LinkedIn app, save that, and only then come back and finish authorising. This is the piece marketed as the Opencart LinkedIn Product Post Extension capability, and it’s the one most likely to need a second look if posts aren’t appearing: a mismatched redirect URL is the usual culprit.


X (Twitter): Inside the X Developer Portal, open Keys and Tokens for the registered app and copy the Client ID and Client Secret across into the extension. The redirect URL needs to be added to that app’s callback list too, the same way it does for LinkedIn. One thing that trips people up: the X app must have write permission turned on, not just read, or the whole Opencart Twitter Auto Post Extension connection attempt will fail at the authorisation step.


Instagram: Instagram posting isn’t part of this release. An Opencart Instagram Auto Post Extension capability is on the roadmap for a future update, but for now the extension only authorises and publishes to Facebook, LinkedIn, and X.

3.0 How to Create Rules To Generate Social Media Posts 

Rule Name
Store administrators can use this setting to assign a unique and descriptive rule name for easy identification and tracking within the OpenCart AI Social Media Automation Extension.

Products / Categories / Manufacturer
This feature allows merchants to define the product scope for automated social media content generation based on specific products, categories, or manufacturers.

Trigger
Store administrators can configure trigger events that automatically initiate AI-powered social media post generation and publishing workflows.

New Product
Automatically generates and publishes social media content when a new product is added to the OpenCart store.

Back in Stock
Automatically creates promotional social media posts when an out-of-stock product becomes available again.

Manual
Allows administrators to generate social media content manually without relying on automated trigger conditions.

Platforms
Merchants can select one or more connected social media platforms, including Facebook, LinkedIn, and X (Twitter), for content distribution.

Publish Mode
This feature allows administrators to define how and when generated social media content is published across selected platforms.

Immediate
Publishes AI-generated social media posts instantly after content generation without requiring manual review.

Manual (Draft)
Saves generated content as a draft, allowing administrators to review, edit, and approve posts before publication.

Scheduled
Automatically schedules social media posts within a defined time range to maintain consistent content distribution and engagement.

Scheduled Delay Window
Administrators can define a minimum and maximum publishing delay to automatically distribute social media content over a specified period.

Brand Name

This setting allows merchants to specify their brand name, enabling AI-generated content to maintain consistent brand messaging.

Industry

Store administrators can define their business industry to help the AI generate relevant and industry-specific social media content.

Tone of Voice

This feature enables merchants to customize the writing style of AI-generated posts to align with their brand communication strategy.

Emoji Usage

Administrators can control emoji usage within generated content to ensure consistency with brand and platform requirements.

Hashtag Groups

Merchants can define predefined hashtag groups to improve social media visibility, discoverability, and audience engagement.

Word Blacklist

This feature allows administrators to restrict specific words, phrases, competitor names, or sensitive terms from appearing in generated content.

Per-Platform CTA

Store owners can configure platform-specific call-to-action messages to improve engagement and conversion rates across social media channels.

Custom Instructions

Administrators can provide additional content-generation guidelines to ensure AI-generated posts align with specific marketing objectives.

Max Posts Per Cron Run / Per Day / Per Product Per Day

This feature enables merchants to control social media publishing frequency and prevent excessive or duplicate content generation.

Saving and Testing Rules

Save Rule

Store administrators can save automation rules to activate AI-driven social media content generation based on configured triggers and publishing conditions.

Generate / Run Now

This feature allows merchants to test and execute a rule instantly, generating social media content for all eligible products and selected platforms.

4.0 Post History Log in Opencart AI Social Media Post Generator Extension

Post History Overview

Store administrators can use the Post History Log to monitor, review, and manage all AI-generated social media content from a centralised dashboard.

What’s Recorded

The system records essential details including post ID, generation date, platform, product, publication status, AI provider, and associated automation rule.

Create Post

Merchants can manually generate AI-powered social media content for selected products without creating an automation rule.

Manual Post Generation

This feature enables administrators to create, review, edit, schedule, or publish custom social media content directly from the Post History section.

5.0 Steps to Generate the API Key for Opencart SocialAI Pro Plugin

For Claude API: 

  1. Visit Anthropic’s website, and click “Start Building”.
  2. Create an account, access your Dashboard, generate an API key, and save it securely.

For Gemini API:

  1. To access the API,  visit the Google AI Studio website.
  2.  Click “Get API key,” accept the terms of service, create your key, and paste it into the module’s configuration settings.

For ChatGPT API: 

  1. Obtain an OpenAI API key and configure it within the module settings.
  2. Click on your profile (top-right) → “View API keys” → “Create a new secret key”.
  3. Copy the key immediately and store it safely. 

Conclusion

The Opencart AI Social Media Post Generator Extension covers the entire path from product data to a published post without requiring anyone to write captions by hand. As a complete Opencart Social Media Automation Extension, it handles the writing through AI, the timing and platform targeting through rules, and the record-keeping through its history log, all from inside the same OpenCart admin panel store owners already use daily.


Whether it’s running as an Opencart Auto Publish Facebook LinkedIn Extension pushing posts out the moment they’re generated, or as an Opencart Social Media Auto Scheduler Extension spacing a large batch out naturally over several days, editorial control never leaves the store owner’s hands: drafts can always be checked, edited, or held back before anything goes public.

 For anyone evaluating it specifically as an Opencart Social Media Marketing Automation Extension, the short version is this: one AI engine writes on-brand copy, one rules engine decides when and where it goes, and one history log keeps track of all of it, which together cover the bulk of a catalogue’s day-to-day social presence without ongoing manual effort.

Opencart SocialAI Pro Extension is also available on Opencart Marketplace – https://www.opencart.com/index.php?route=marketplace/extension/info&member_token=a82287f721dce288db62f253df7a972b&extension_id=48624

 Support questions, setup help, or configuration requests can go to support@knowband.com. Release notes and further documentation are maintained on the Knowband website.