Your site's useful information is not always in the main content editor. It may live in ACF fields, repeater rows, product details or custom post types.<\/p>\n\n
KROK LLMs Transit helps you turn that information into a curated llms.txt index and optional Markdown pages. Choose the public content to include, build reusable descriptions with clickable fields, and preview the result before publishing.<\/p>\n\n
Combine WordPress content, post meta, ACF fields and taxonomy terms in one description. Add your own labels and text around field tokens. Configure repeating rows, Flexible Content layouts and related entries, then check the output against a real sample entry.<\/p>\n\n
Create a description once for a content type and reuse it across its entries. When needed, use a separate description for a theme template or override an individual entry. Configuring descriptions in the visual builder does not require writing PHP.<\/p>\n\n
Use KROK LLMs Transit for agency portfolios, service directories, editorial sites and product catalogues where a useful summary needs more than a title and an excerpt.<\/p>\n\n
ACF and WooCommerce are optional. Polylang can provide separate language publications. WPML and Multisite are not supported in this release. See the FAQ for compatibility details and publication limits.<\/p>\n\n
Publication is disabled on installation. No external AI service, API key, tracking, cookies or remote assets are required. The interface is translation-ready and follows the WordPress user language, including right-to-left layouts. WordPress.org language packs provide available translations through the standard WordPress update system. Translation availability depends on published language packs; interface translations do not automatically translate site content.<\/p>\n\n
Publishing llms.txt does not guarantee that an AI service will read it, cite your site or improve your rankings.<\/p>\n\n\n
Detailed Markdown pages are optional and have their own description settings.<\/p>\n\n
If another plugin already generates llms.txt, choose which plugin will manage it before publishing. An existing physical llms.txt file must also be reviewed to avoid overwriting it unexpectedly.<\/p>\n\n
Background updates use WordPress scheduled tasks. The settings page does not need to remain open. On low-traffic sites, a server cron job can provide more consistent update times.<\/p>\n\n\n
It publishes an llms.txt index containing selected public content and descriptions. You can also enable detailed Markdown pages for included entries. You choose the content types, sources and formatting used in the output.<\/p><\/dd>\n
No code is needed to configure descriptions with the visual builder. WordPress fields and ordinary post metadata work without ACF. ACF is optional; its Repeater and Flexible Content field types require ACF Pro. PHP hooks are available for developers who need custom integrations.<\/p><\/dd>\n
Yes. Publicly viewable custom post types appear in the content selection. Enable the types you want, then choose fields in their description builders. Registering a CPT does not automatically include it in your publication. The plugin does not create your site's CPTs or ACF field groups.<\/p><\/dd>\n
Yes. The short index description and the optional detailed Markdown page have separate settings. Keep the index concise and use the Markdown page for more detailed content.<\/p><\/dd>\n
Check that their content type is selected, the settings are saved and the entries are published and publicly viewable. Taxonomy filters, expiration rules, password protection and noindex settings can exclude entries. The WordPress search-engine visibility setting is respected: publication is blocked when the site discourages indexing. Review compatibility notices, exclusion reasons and diagnostics before publishing.<\/p><\/dd>\n
Yes. The bundled developer-guide.txt documents PHP hooks and extension points for field sources, formatting, access checks and generated output. See the guide for hook names, callback examples and integration requirements.<\/p><\/dd>\n
AIOSEO descriptions and smart tags are read from its post model and content-type settings. Explicit and inherited noindex settings are respected. Content smart tags use conservative stored text rather than invoking shortcodes or page-builder rendering. Custom-field tags use raw scalar post metadata; formatted ACF values, relationship fields and collections are not rendered. Editorial saves and configured custom-field dependencies invalidate affected resources; score-only and internal-counter updates do not. Turn off AIOSEO > Sitemaps > LLMs.txt if KROK LLMs Transit owns llms.txt. Existing physical files still need explicit review. Pre-adapter AIOSEO snapshots are revoked and rebuilt after updating.<\/p><\/dd>\n
For ordinary Elementor pages, automatic descriptions and Markdown read the text mirror that Elementor writes to post_content when saving a document. Completed document saves trigger refresh; CSS and element-cache regeneration do not. The plugin does not execute Elementor frontend rendering. Elementor Pro, Theme Builder output, arbitrary dynamic widgets and third-party visibility conditions are not covered by this compatibility claim. Use explicit fields and editorial overrides for content missing from the stored text mirror; access-control integrations require a supported adapter.<\/p><\/dd>\n
No. Settings display stored data. Build private preview processes saved settings in short resumable requests, never publishes, and keeps one bounded checkpoint. Leave the page or pause to stop private preview requests; use the same button to resume. A preview expires after one day. A public background refresh instead continues through WP-Cron or administrator progress requests.<\/p><\/dd>\n
Only event codes, build identifiers and numeric counters. History is private to administrators, retains at most seven days and 1,000 records of 512 bytes each, and is pruned on append, read and daily cron. These are payload limits, not a promise about database filesystem size or MySQL binary log retention. Detailed progress expires after 30 minutes and is sampled at most once per ten seconds. Download is a JSON attachment; no public log file is created.<\/p><\/dd>\n
Selected meta and ACF sources, repeater child keys, editorial fields, built-in SEO visibility and descriptions, and supported commerce metadata are tracked. Unused metadata such as view counters is ignored. Custom description, index and access callbacks keep conservative tracking because they may read additional fields. Integrations can declare dependencies with cbridge_metadata_dependency. Security-related fields must never be filtered out by an integration.<\/p><\/dd>\n
A completed private preview of the current saved settings and content revision against stored publication resources. It compares public titles, URLs, descriptions and Markdown content. It is a review aid rather than an approval gate: automatic schedules still publish, and Publish rebuilds saved settings so changed content is validated again. Site-level introductory text and section ordering are visible in the preview, with an index-change notice, rather than counted as resource changes. Healthy scheduled runs without content or configuration changes are skipped. Explicit queued refreshes still run and reuse unchanged resources between full verification runs, which are performed at most once per day when the selected schedule runs.<\/p><\/dd>\n
Yes. If Yoast publishes llms.txt, use the explicit publisher switch in KROK LLMs Transit. Review and confirm any existing file; private backups are saved before switching. Only Yoast's llms.txt feature is disabled. Download previous files from the admin screen and check the public index after publication. Other Yoast SEO settings are preserved.<\/p><\/dd>\n
No ranking or recommendation guarantees are made. llms.txt is an additional discovery surface for tools that choose to use it. It is not an access-control file or a replacement for robots.txt.<\/p><\/dd>\n
A separate theme-template description replaces the general description, even when empty. Disable Use a separate description for this theme template to inherit the general description. Publication preview follows the applicable template. New separate templates begin with an independent copy of the general template.<\/p><\/dd>\n
Configure the collection card and move its standalone {collection:name} line in the main editor. The marker controls output order and is not included in the public file. Removing it removes that collection and its settings.<\/p><\/dd>\n
Public requests read a saved snapshot. Complete replacements are built in batches of at most 50 posts, yielding between records after a four-second processing target. Progress inside each page is saved; final source and dependency checks are also resumable. Waiting for cron does not count toward the active-processing limit. The open administration page can finish pending batches without waiting for visitor-driven WP-Cron. Scheduled refreshes still use WordPress cron when the page is closed. Access revocation invalidates the snapshot immediately; expired snapshots are blocked even if cron is delayed.<\/p>\n\n
For reliable schedules on low-traffic sites, configure server cron. A single slow integration callback or database query cannot be interrupted by the plugin; repeatedly interrupted steps stop with a diagnostic error rather than retrying indefinitely. Exclude llms.txt and published Markdown URLs from external page and CDN caches. Limits are 1,000 entries per content type, 5,000 included entries overall, 10,000 scanned entries per type, 50 collection rows per loop and 4 MB of Markdown.<\/p><\/dd>\n
Use Configuration & cache > Export settings. Paste the JSON on the destination and choose Validate & import settings. Matching public content types must exist. Invalid imports preserve existing settings. Successful imports disable publication until you review and publish again. Editorial post fields are not transferred.<\/p><\/dd>\n
Drafts, private posts, password-protected posts and explicit noindex entries are excluded. Detected access-control plugins without an adapter block publication. Compatibility with every membership plugin is not promised; custom restrictions require a developer integration before publication.<\/p>\n\n
Multisite is not supported. Polylang builds separate language snapshots with translated URLs and template labels. WPML is not supported in this release; publication is blocked when WPML is detected to prevent mixing content languages. Interface translation is independent of multilingual site content. ACF and WooCommerce are optional; their fields are available only when the relevant plugin is active.<\/p><\/dd>\n
Deactivation stops scheduled tasks and disables publication while retaining settings and editorial fields. Uninstall deletes plugin data only if you enabled the deletion setting first.<\/p><\/dd>\n\n<\/dl>\n\n\n