fdfdfdfdfd 

• fdgfd
• fgd
• fdg
• df
• gfdg

Yes — if you want to start with the essentials. Free provides llms.txt, Markdown for posts and pages, basic OKF, robots.txt control, URL exclusions, and diagnostics.

Free also includes the full Content Purifier, using the same Purifier engine as Pro.

Pro extends Free with a broader AI publishing and control layer. It includes llms-full.txt, llms-ctx.txt, the media channel, WooCommerce, selected Custom Post Types, ACF, multilingual support, AI/TDM policies, GEO logs, cache, and OKF ZIP export.

It also provides more precise control over which data, sources, and representations are published for AI systems.

Not always. Free may be sufficient for a small site. Pro becomes relevant when you need more representations, data sources, policies, publishing controls, or analytics.

Free lets you start. Pro lets you scale the approach.

Yes. Both editions are based on the same approach, so moving to Pro does not require changing the overall publishing concept.

Yes. Pro extends the layer available in Free rather than creating a completely separate mechanism.

AIVM does not require rebuilding your website. It adds a publishing and control layer for content intended for AI systems on top of the existing site.

It uses existing WordPress data and works with the CMS, SEO tools, WooCommerce, ACF, CPTs, and multilingual systems.

The process can be summarized as:

SELECT → CLEAN → ENRICH → GOVERN → VERIFY

That means selecting sources, cleaning content, enriching representations, governing policy, and verifying published endpoints.

No. llms.txt is only one component.

AIVM also covers Markdown, llms-full.txt, llms-ctx.txt, OKF, WooCommerce data, CPTs, ACF, policies, and analytics.

Yes. An existing llms.txt can be a starting point, while AIVM can extend the approach with Markdown, llms-full.txt, llms-ctx.txt, OKF, source control, policies, and verification.

The goal is to move from a single manually managed resource to a controlled publishing and verification process.

HTML is primarily a presentation format and can contain substantial technical noise. Markdown makes it possible to prepare a cleaner representation of content for further processing by AI systems.

No. AIVM uses existing WordPress content.

Content Purifier removes technical noise, while subsequent layers can enrich and organize the prepared representations.

It is an AI publishing layer over existing content.

Content Purifier prepares content for AI representations by removing technical noise associated with builders, shortcodes, classes, and unnecessary markup.

The full Content Purifier is available in both Free and Pro.

Its purpose is not to modify the original WordPress source content. Purifier operates as a preparation layer for AI representations.

Yes. Content Purifier removes technical noise generated by supported page builders and shortcodes so that AI representations can be prepared from the meaningful content.

Yes. Pro adds a media channel, whose scope depends on configuration and available data sources.

Yes. AIVM provides control over publishing scope at several levels.

You can manage it through:

• data sources;

• the scope of published content;

• URL exclusions;

• AI policies;

• settings assigned directly to an individual page or post.

At the individual-content level, the “Exclude from AI (LLM)” option can exclude a specific page or post from AI publishing.

This means control does not have to be limited to global settings — you can decide that a particular piece of content should not be included in the AI layer.

Yes. AIVM provides AI settings directly in WordPress content parameters.

You can manage the availability of an individual post or page independently of the rest of the site. Free provides, among other things, the “Exclude from AI (LLM)” option, while Pro extends these capabilities with an AI Policy that can be assigned to the content.

Pro provides broader source and publishing-scope control as well as caching, so preparing a large number of representations does not have to require manual processing of every item.

AIVM can regenerate representations from the current site data. Caching mechanisms reduce unnecessary reprocessing.

No. AIVM complements SEO and tools such as Yoast SEO and Rank Math.

Its purpose is to prepare and control content representations for AI systems.

Yes. AIVM can use existing SEO data and settings, including Schema.org signals and noindex.

No. AIVM uses the existing configuration and signals rather than requiring those tools to be replaced.

Yes. Structured data can provide additional context for AI representations and diagnostics.

Yes. noindex signals are taken into account as a signal concerning content availability in the AI layer.

The goals are different. AIVM is an additional publishing and content-control layer for AI systems, not a replacement for traditional SEO.

If you also want to prepare, publish, and control content representations for AI systems, AIVM addresses a different problem from traditional SEO.

If you want to include these data sources in the AI layer, Pro provides the relevant capabilities: WooCommerce products, selected CPTs, and safely selected ACF fields can be handled through the same process.

Yes, particularly when products and the catalog are important information sources.

Pro can bring product data such as catalog information, prices, SKUs, and variants into the AI layer, depending on the available data source and configuration.

Structured data can be used as additional context.

The current version provides, among other things, Schema.org diagnostics and data structures used in representations, depending on the source and configuration.

Yes. AIVM supports multilingual websites using, among others, WPML and Polylang.

Yes. The current AIVM implementation includes TranslatePress support.

This means the publishing layer can also account for multilingual websites using this translation system.

The publishing layer can account for the multilingual structure of the website, the appropriate sources, and their corresponding URLs.

This allows AI representations to be prepared with language versions taken into account.

An AI Policy defines rules concerning AI systems’ use of and access to website content.

In AIVM, it is part of the governance layer and works together with content sources, exclusions, AI representations, and access-control mechanisms.

Yes. In Pro, an AI Policy can also be set at the level of an individual page or post.

This allows additional rules to be applied to selected content rather than treating the entire website as one indivisible set.

Yes. AIVM provides the “Exclude from AI (LLM)” option at the content level.

It can exclude a specific page or post from llms.txt and AI endpoints within the scope supported by AIVM.

No.

robots.txt and an AI Policy serve different functions and can work together.

robots.txt is a routing and crawler-access signaling layer, while the AI Policy is part of a broader layer for managing the publishing and use of content by AI systems.

AIVM uses these mechanisms as part of a multi-layer control model.

Depending on configuration and the supported feature, AIVM can use mechanisms including:

• robots.txt;

• X-Robots-Tag;

• TDM-Reservation;

• noai;

• noimageai;

• URL exclusions;

• settings at the individual-content level.

This allows control to be implemented across more than one layer.

No. AIVM combines global settings with the ability to apply controls at the individual-content level.

This makes it possible to have a general site-wide policy while selected pages or posts have additional settings or are completely excluded from the AI layer.

The architecture is designed to reduce this risk through sources, exclusions, policies, individual-content settings, and representation scope.

Published endpoints should still be verified.

That is not its purpose. AIVM adds a representation and control layer intended for AI publishing rather than rebuilding the normal presentation of the website.

Yes. Pro can record crawler history, the most frequently visited endpoints, and distinguish AI bot visits from supported visits originating from AI sources.

This does not mean that all citations are measurable.

No. AIVM prepares and controls published representations, but it cannot guarantee that a particular AI system will use a website or that it will appear as a cited source.

Yes. The approach is not tied to a single AI provider.

AIVM operates as a site-level publishing and control layer.

It should not.

In practice, after upgrading it is worth checking exclusions, noindex signals, bot policy, CPTs, products, cache, and the endpoints actually being published.

The recommended process is:

audit → configuration → preview → test → publish

Yes. After configuration, AIVM can generate and update representations from website data.

Caching reduces unnecessary processing, while periodic verification helps confirm the current publishing state.

Yes. You can prepare the publishing and control layer before traffic appears instead of waiting for it.

AIVM treats AI visibility as a process, not a single file.

Primarily more control.

Pro expands the range of sources, representations, policies, publishing scope, and verification.

In practice, it provides the ability to manage the AI publishing process at a larger scale.

Especially when a website has many important information sources, WooCommerce, multiple languages, a knowledge base, a service catalog, ACF/CPTs, or when AI publishing is part of a regular content-management and governance process.