JSONLD, GEO, AEO structured data

An extension for Store Builder and Multi-Vendor that enriches your store with Schema.org structured data in JSON-LD format and builds an llms.txt file for AI bots. As a result, your store becomes readable both for Google (rich results and merchant listings) and for AI-powered search engines such as ChatGPT, Claude, Perplexity and Gemini.

A standard CS-Cart installation does not publish the full Schema.org schemas that Google and AI assistants expect today. This add-on fills that gap without touching your templates: it injects ready markup on every page, links the store entities into one coherent graph, keeps everything aligned with Google requirements for 2026, and gives you the tools to confirm that your store data is complete.

Key Features

- Automatic Schema.org structured data (JSON-LD) on every page: OnlineStore, WebSite, Product, category, blog and CMS page, linked into a single entity graph, with no manual template work.

- Product data pulled straight from CS-Cart features: brand and, separately, manufacturer, GTIN/EAN, MPN number, OEM approvals and technical specifications, plus a shared ProductGroup for variants.

- A full return policy aligned with Google 2026 requirements: standard return, buyer's remorse withdrawal and statutory warranty, with a soft integration with the Withdrawal from Contract add-on.

- A store mode that matches your catalogue: physical products shipped by courier, digital products delivered by email, and a brick-and-mortar location described as a Store with its address data.

- Authorship and freshness signals that Google values: the blog article author as a person (Person, an E-E-A-T signal) and the last modification date of pages and posts.

- An llms.txt file for AI bots, a built-in JSON-LD validator, a diagnostic dashboard and a first-steps guide tailored to your store theme.

You begin the setup with company data and the store type. In one place you decide whether you sell physical products shipped by courier or digital ones delivered by email, and the add-on selects the matching markup for you. This is also where the company description, the logo with its dimensions, the email address, opening hours and the tax number belong, the last one published in the structured data as the company tax identifier:

Screenshot 1: company data, store type and tax ID

The second part of the company data covers contact details and online presence. The email address, opening hours split by weekday, currency, social media profile links, contact point data (areas served and languages) and the founding date feed the OnlineStore schema. Google uses them in the Knowledge Panel, and AI assistants use them when answering questions about how to reach the store:

Screenshot 2: contact details, social profiles and contact point

If you also sell from a physical location, the add-on describes the company additionally as a Store and adds geographic coordinates. You simply enable the brick-and-mortar option and provide the latitude and longitude. The same tab holds a note about the company data duplicate coming from the UniTheme2 theme, together with instructions on how to remove it so that only one Organization entity remains in the page source:

Screenshot 3: brick-and-mortar store (Store) with geo coordinates

Stores with a digital catalogue get a dedicated tab. In digital mode the markup adapts to email delivery and the absence of a physical return, and you choose the product subtype (software, e-book, document or media). For software you provide the application category and operating system, and for e-books the author feature, so that Google classifies the digital product correctly:

Screenshot 4: the digital products tab

In this section you connect CS-Cart product features with Schema.org data. You point to the feature that holds the brand and to the one that holds the manufacturer (kept separate from the trade brand), as well as the GTIN/EAN code, the MPN number, OEM approvals and technical specifications. The add-on copies these values into the product markup, and when the manufacturer feature is empty it falls back to a default value or to the brand:

Screenshot 5: mapping product features, brand and manufacturer

Here you decide what exactly the add-on renders on products and the blog. You disable the duplicate Product block from the SEO add-on, turn on the BreadcrumbList path, the Article markup on blog posts and the last modification date on pages. The variant linking option joins products into a ProductGroup, and the blog author fields switch the content author from the company to a specific person, a stronger E-E-A-T signal for Google:

Screenshot 6: rendering options, ProductGroup variants and blog author

Shipping parameters feed the OfferShippingDetails block: delivery cost, handling time, transit time and the number of days allowed for returns. You can also set a free shipping threshold, above which the cost in the structured data drops to zero. This way the offer in Google results reflects the real delivery terms:

Screenshot 7: shipping parameters for the OfferShippingDetails block

A full return policy laid out according to Google requirements for 2026. You describe separately the standard return, the buyer's remorse withdrawal (14 days under Polish law) and the return of a defective product under the statutory warranty. This complete set of fields clearly improves the chance of showing the product in Google merchant listings:

Screenshot 8: MerchantReturnPolicy aligned with Google 2026

Configuration of the llms.txt file, a store map prepared for AI bots. You turn on generation, choose the addresses of supporting pages and the number of blog articles, and create the file with a single click. The panel shows the public address of the file and a ready CRON command for daily updates:

Screenshot 9: llms.txt file generation settings

An optional semantic validation powered by artificial intelligence. After you provide an API key and pick a Claude or OpenAI model, the validator goes beyond the structure check and also judges whether the data makes sense, for example whether the product description matches its name and features:

Screenshot 10: AI validation with a Claude or OpenAI model

The built-in validator fetches any store address, extracts the JSON-LD blocks and checks their compliance with Schema.org and Google requirements. On a product page you immediately see the complete set of detected schemas: OnlineStore, WebSite, MerchantReturnPolicy, Product and BreadcrumbList, each with its own status and a list of any remarks:

Screenshot 11: validator report for a product page

The diagnostic dashboard gathers the add-on status into three cards: errors, warnings and notices. At a glance you can tell whether the configuration is complete and what is worth improving to increase the chance of rich results. The whole report can be exported to JSON or CSV:

Screenshot 12: diagnostic dashboard, add-on status overview

Right after installation the add-on tells you where to start. The first-steps guide recognizes the active store theme and shows only the tasks that actually apply to your setup, for example how to avoid a duplicate navigation path or an Organization block coming from the theme. Each step has buttons to check it and to jump straight to the relevant setting:

Screenshot 13: first-steps guide tailored to the theme

The product data quality tab shows, as percentages, how many products have a brand, GTIN, MPN, description and image filled in. Lists of the most common gaps lead straight to editing specific products, so you know exactly where to start tidying up before Google does it for you:

Screenshot 14: product data quality statistics

The same validator run on a category page confirms that the add-on generates a CollectionPage schema with a product list. This proves that not only product pages but also category pages are readable for Google and AI search engines:

Screenshot 15: validator report for a category page (CollectionPage)

The finished llms.txt file opened in a browser at /llms.txt. It contains a short company description, product categories, blog articles and contact details in a format that AI bots read directly. It is the counterpart of robots.txt, only addressed to artificial intelligence rather than to indexing crawlers:

Screenshot 16: the generated llms.txt file available at /llms.txt

The JSON-LD, GEO Structured Data add-on organizes what a standard CS-Cart does not provide: a complete set of Schema.org schemas linked into one entity graph, a clear split between brand and manufacturer, a return policy that meets Google 2026 requirements, and an llms.txt file for AI search engines. Setup comes down to filling in the company data and pointing to the product features, while the built-in validator, the diagnostic dashboard and the first-steps guide keep an eye on the markup quality at all times.

Feel free to contact us and purchase the add-on!