How Does AI Read Your Store? Markdown and Content Signals in PrestaShop

Markdown for Agents is a way of delivering page content to AI agents in a lightweight text format. Content Signals, in turn, make it possible to declare the rules for its use. In PrestaShop, it is worth combining these solutions with up-to-date product data and good SEO. However, each solves a different problem — neither on its own ensures that a store will be recommended by AI.

Markdown for Agents: less code, more information

An agent comparing products needs the name, parameters, price, and availability, not menus, scripts, or repeated template elements. Models can process HTML, but cleaned Markdown can reduce the amount of unnecessary data. At the same time, it preserves headings, lists, tables, and links.

Cloudflare showed the scale of the difference on its own article: 16,180 tokens in HTML versus 3,150 in Markdown, which is about 80% less. This is the result for a specific page, not a guarantee for every store. The savings depend on the template, content, and the method of counting tokens. See the Cloudflare example.

How to make store content available to agents?

One mechanism is format negotiation: the client sends Accept: text/markdown, and the server handling it returns Content-Type: text/markdown. A regular user still receives HTML. The Vary: Accept header signals to caches that the response depends on the requested format. This is how the Markdown for Agents service in Cloudflare works, converting HTML after it is enabled.

You can also provide separate .md URLs and indicate them as alternative versions of the page. The llms.txt proposal complements this mechanism with a short guide containing a site description and links to detailed documents. It is guidance for the agents handling it, not a replacement for a sitemap or a mandatory standard for all search engines.

Content Signals: search, answers, or training?

Content Signals Policy separates three uses of content that are easy to mistakenly throw into one “AI” bucket:

• search — building an index and presenting results with links and short snippets; it does not include AI-generated summaries.
• ai-input — passing content to a model as material for answers, e.g. in a RAG mechanism that retrieves information from sources while handling a query.
• ai-train — training or fine-tuning models on the content.

An example declaration allowing search and use in answers, but excluding training, looks like this:

Content-Signal: search=yes, ai-input=yes, ai-train=no

In robots.txt, such an entry should be placed in the appropriate group together with a policy description, while preserving the store’s existing rules. Omitting the signal does not mean consent — it means no declaration in this mechanism. Content Signals are not a technical block on crawling and do not replace access control.

Note for Cloudflare: according to the service documentation, if the origin server does not set the Content-Signal header, Markdown conversion adds yes by default for all three uses. So check not only robots.txt, but also the final response headers.

What should be optimized in PrestaShop first?

The practical order of work should start with the quality of information, and only then move on to the format:

1. Describe the product unambiguously. Provide the model, SKU or EAN, units, and variant features. Instead of “high performance,” write specifically what the product can do and what it fits.
2. Keep it up to date. The price must include the currency and tax information, and availability must apply to the correct variant. Include cache and index refreshes after changes.
3. Add shopping context. Publish specific FAQ answers, delivery rules, and return policies. Separate customer reviews from manufacturer parameters.
4. Maintain consistency and privacy. The Markdown version should match the public offer in the given language, indicate the original page, and not reveal account or cart data.
5. Check the actual response. Compare HTML and Markdown after passing through the CDN. Verify prices, links, and whether an allowed agent receives a blocking page instead of the content.

How does PD Markdown4Agents Pro help?

Our PD Markdown4Agents Pro for PrestaShop prepares documents from store data, not from the entire rendered template. It supports products, categories, CMS pages, and manufacturers; for products, it includes, among other things, prices, availability, features, and combinations. It provides .md URLs and optional format negotiation.

It also generates llms.txt and llms-full.txt — in this module, the latter is an extended index with summaries and links, not a patchwork of full descriptions. After enabling the appropriate integrations, it includes the ph_simpleblog blog, FAQ, and reviews from supported modules. It allows you to manage Content Signals in robots.txt. The statistics show content downloads, not the number of citations by AI.

Does Markdown improve SEO and GEO?

Markdown is a technical convenience, not a promise of rankings. Google does not require special AI files or additional Schema.org markup for presence in AI Overviews and AI Mode. Availability, indexing, helpful content, and data consistency still matter.

In practice, GEO, meaning optimization for generative answers, is worth basing on facts that are easy to find and cite. Keep good HTML and Schema.org structured data in PrestaShop consistent with the offer, and treat Markdown as an additional way of delivering the same reliable information.