Description
KROK LLMs Transit gives site owners control over which public content appears in llms.txt and how each entry is described.
The visual description editor is designed for sites whose important information lives in custom fields. Combine post metadata, ACF fields, nested repeater rows, Flexible Content layouts and related entries into reusable descriptions and Markdown templates. Configure labels, formatting and conditions, preview an individual entry, and inspect warnings and exclusion reasons.
- Choose public content types, filter taxonomy terms and arrange sections and entries.
- Build descriptions with clickable field lists and reusable text templates.
- Read WordPress fields, post metadata, taxonomies and optional ACF or WooCommerce sources.
- Configure repeating rows, related entries and separate theme-template descriptions.
- Enable detailed Markdown pages with their own templates and optional list or table output.
- Add editorial descriptions or replace generated descriptions for individual entries.
- Exclude expired entries using an explicitly selected date field and stored format.
- Preview, save and explicitly publish complete cached representations.
- Schedule refreshes and export or import configuration.
- Extend sources, formatters, access policies and output through PHP hooks documented in the bundled developer-guide.txt.
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.
Installation
Upgrading from LLM Bridge: export settings, deactivate the old plugin without uninstalling it, then install and activate KROK LLMs Transit. Settings, templates and editorial values are retained. Re-enable publication and rebuild. Do not run both plugins together or uninstall the old copy with data deletion enabled.
Upgrading from LLM Shuttle, LLMs Shuttle or LLMs Transit: deactivate the previous installation without uninstalling it, then install and activate KROK LLMs Transit. Saved content rules and editorial values remain available. Review the settings and save and publish again: deactivation of the old version intentionally disables publication and clears its snapshot. Do not activate the old copy alongside the new one.
- Install the ZIP through Plugins > Add New > Upload Plugin, or upload the krok-llms-transit folder to wp-content/plugins.
- Activate KROK LLMs Transit and open its administration page.
- On a new installation, standard posts and pages are preselected. Click Save & publish to queue an index with normal titles, links and automatic short descriptions. Review compatibility notices if publication is blocked.
- For custom descriptions, optionally use Edit description template to insert fields and write text around their tokens. Save the main settings form after closing the editor.
- Optionally enable detailed Markdown pages and configure their separate templates.
- Existing installations keep their selections. Review a private preview and compatibility notices before publishing manually when needed.
- Background publication continues through WP-Cron; the administration page also displays progress. If progress fails, use Continue publication. Open llms.txt to verify the result.
Existing physical llms.txt files block publication. They are replaced only through the explicit publisher switch after review, confirmation and a private backup. Otherwise resolve the conflict manually. Disable competing generators first. Pretty permalinks are required for /llms.txt; /?cbridge_llms=1 is available with plain permalinks.
FAQ
-
How does AIOSEO work with KROK LLMs Transit?
-
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.
-
How does Elementor work with KROK LLMs Transit?
-
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.
-
Does opening settings rebuild my site?
-
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.
-
What does the event history store?
-
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.
-
How are custom metadata changes tracked?
-
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.
-
What does Compare changes compare?
-
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.
-
Can I keep Yoast SEO active?
-
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.
-
Does this improve AI rankings?
-
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.
-
How do separate theme templates work?
-
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.
-
How do I place repeating rows in my description?
-
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.
-
How does publication refresh?
-
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.
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.
-
Can I move settings to another site?
-
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.
-
Does it support restricted or multilingual content?
-
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.
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.
-
What happens on deactivation or uninstall?
-
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.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“KROK LLMs Transit” is open source software. The following people have contributed to this plugin.
Contributors
Translate “KROK LLMs Transit” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.3.8
- Add the KROK brand; align the plugin directory, text domain and script handles with krok-llms-transit.
- Preserve existing option keys, hooks, namespace and publication logic.
1.3.7
- Rename the plugin to KROK LLMs Transit with the krok-llms-transit text domain, directory and script handles.
- Document the structured-field description editor and the transition from previous Shuttle installations.
- Keep the WordPress.org language-pack changes from the previous release.
1.3.6
- Rename the plugin to KROK LLMs Transit with the krok-llms-transit text domain and directory.
- Use WordPress.org language packs instead of bundled translations in the installation ZIP.
- Retain saved content rules when switching from the previous directory; save and publish again after activation.
1.3.5
- Explain new-line item separation beside all description and collection text editors, in all bundled languages.
1.3.4
- Skip unchanged healthy scheduled refreshes between daily full verification runs; explicit refreshes still build.
- Bound warning entry links while retaining complete affected counts across preview pages.
- Respect the WordPress search-engine visibility setting and revoke older publications immediately.
- Preserve another worker’s private preview after lease replacement.
- Use owned, atomic leases for the publisher switch, including legacy lock cleanup.
1.3.3
- Restore complete content diagnostics across preview pages, including empty descriptions and Markdown warnings.
- Distinguish an unbuilt preview from a checked result without warnings.
1.3.2
- Read AIOSEO descriptions and inherited robots settings; detect its llms.txt generator before it creates a file.
- Track editorial AIOSEO table saves and completed Elementor document saves while ignoring analysis and CSS-cache updates.
1.3.1
- Remove built-in starter templates and restore the previous description editor controls.
- Preselect standard posts and pages for new installations; first save queues a standard index when compatibility checks pass.
- Retain publication, storage, diagnostics and performance improvements from 1.3.0.
1.3.0
- Verify publication persistence before reporting success; retain the previous snapshot on storage failures.
- Reset source validation for every language and use atomic lease ownership checks.
- Ignore unused metadata counters while tracking configured fields, ACF child keys, access settings and extension callbacks.
- Load settings without a full-site preview; fetch editor samples and field catalogs only when opened.
- Add resumable private previews, paginated resource review, before/after comparisons and source explanations.
- Add safe starter templates, a sticky Save action and retained access to valid previous publications after refresh errors.
- Store Markdown in immutable pages; public requests load only the needed representation.
- Add private seven-day event history, a 1,000-event/512-byte-per-event cap, JSON export and temporary sampled diagnostics.
- Add operational and Site Health checks; translate stored built-in error codes in the administrator’s language.
- Update all nine interface locales and add release acceptance coverage.
1.2.5
- Resume generation inside a page with a four-second processing target and one batch per progress request.
- Schedule recovery before resource callbacks and reduce batch size after interrupted requests.
- Count active processing instead of cron waiting; replace restart termination with paced retries and explicit diagnostics.
- Validate resource and dependency versions before publishing, without restarting for unrelated metadata changes.
- Ignore additional Spectra asset versions unless explicitly mapped.
- Recover the obsolete build_budget error once on upgrade.
1.2.4
- Replace shared resource revision rewrites with bounded per-post tokens.
- Ignore derived frontend asset metadata unless explicitly mapped, and avoid content tracking while publication is disabled.
1.2.3
- Refresh publication status, template warnings and exclusions after background builds without reloading.
1.2.2
- Show immediate loading feedback when opening description and Markdown editors.
- Paint the dialog before creating editor controls; support closing during preparation and retrying after a rendering error.
1.2.1
- Use the short plugin name KROK LLMs Transit for the initial directory submission.
- Keep llms.txt and Markdown functionality in the plugin description.
1.2.0
- Rename the plugin to KROK LLMs Transit, including the plugin slug, text domain and PHP namespace.
- Keep existing settings, templates and scheduled hook names for compatibility.
- Disable LLM Bridge before activating KROK LLMs Transit; do not run both versions together.
1.1.9
- Refresh counters, preview, status and publish button after background publication without reloading.
- Make the publish button larger and more prominent.
1.1.8
- Create Advanced field selectors only when expanded to reduce template editor opening delays.
1.1.7
- Initial directory submission: curated llms.txt and optional Markdown pages from public content.
- Include field templates, ACF sources, editorial descriptions, expiry rules and bounded background builds.
- Support Polylang language indexes and nine interface languages.
- Keep Done and the desktop preview panel visible while editing long templates.
- Defer WPML support until real integration testing is complete.