Security hardening: nonce verification added to admin notice display; POST inputs sanitized earlier; physical llms.txt copy now writes to uploads directory instead of site root. No configuration changes needed.<\/p>","1.1.3":"
Prefix rename for WordPress.org compliance. If you used wp-config.php constants ( Maintenance release (WordPress.org compliance). No behavior change for sites already on 1.1.x.<\/p>","1.1.0":" First public release on this slug; if you used a development copy under another folder name, deactivate the old plugin and activate this one.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.1.4"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Settings \u2014 connect, GA4 property, exclusions, and sync for llms.txt<\/strong>.","2":"Connected state \u2014 last sync and GA4 vs appended URL counts for your LLMS.txt<\/strong>.","3":"Manual paste and preview of the live llms.txt<\/strong> output."}},"plugin_section":[],"plugin_tags":[2353,193472,266013,244604,186],"plugin_category":[55],"plugin_contributors":[266014],"plugin_business_model":[],"class_list":["post-305117","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-ga4","plugin_tags-llms-file","plugin_tags-llms-txt","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-gcco","plugin_committers-gcco"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/ai-view-sync.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n AI View Sync<\/strong> is a WordPress plugin built around the llms.txt<\/strong> convention: a small text file at The llms.txt<\/strong> file (often written LLMS.txt<\/strong>) is becoming a common way to publish machine-readable hints for large language models: preferred pages, policies, and pointers to content you want highlighted. This plugin makes it straightforward to host llms.txt on WordPress<\/strong> at the standard location so tools that look for Site owners who want a maintained llms.txt for WordPress<\/strong>, care about AI SEO<\/strong> and LLM<\/strong> visibility, and optionally want GA4<\/strong>-aware content combined with a full sitemap-style URL list\u2014without hand-editing llms.txt<\/strong> every week.<\/p>\n\n This plugin connects to GcCo AI View<\/strong> (gcco.io), a third-party analytics and LLMS.txt generation service operated by GCCO LLC.<\/p>\n\n What the service does:<\/strong> AI View uses your Google Analytics 4 (GA4) data to rank your site's pages by traffic and generate an LLMS.txt file tailored to your content.<\/p>\n\n When data is sent:<\/strong> Data is transmitted to gcco.io only when you actively use the Connect flow or click \"Sync now.\" Specifically:<\/p>\n\n No data is sent automatically (no cron or background requests). All requests are made over HTTPS.<\/p>\n\n Service provider: GCCO LLC\nService website: https:\/\/gcco.io\nTerms of Service: https:\/\/gcco.io\/terms\/\nPrivacy Policy: https:\/\/gcco.io\/privacy-policy\/<\/p>\n\n\n After activation, visitors and crawlers can request your file at llms.txt<\/strong> (often written LLMS.txt<\/strong>) is a plain-text file at No. A normal install does not require API keys. Optional wp-config.php<\/strong> constants (for example No. You can paste LLMS.txt<\/strong> manually, or use Add published URLs from WordPress<\/strong> (when not connected) to append published URLs without an account. Connecting to GcCo AI View<\/strong> adds automatic sync and GA4-informed prioritization from your account.<\/p><\/dd>\n Many plugins only serve<\/strong> a file you write yourself. AI View Sync<\/strong> can fill<\/strong> that file using traffic-aware ordering from GA4<\/strong> (via GcCo AI View), then merge<\/strong> in extra WordPress URLs so newer or sitemap-only pages are not missed. You can also set path and post-type exclusions<\/strong> (connected flow) and optionally write a physical Your live file is served at Yes. After you connect, use Sync now<\/strong> in the plugin admin whenever you want to pull the latest LLMS.txt<\/strong> from GcCo AI View and re-run the WordPress merge. There is no built-in WordPress cron<\/strong> in this plugin yet\u2014refresh is on demand<\/strong> unless you add your own automation outside the plugin.<\/p><\/dd>\n Yes. On sync, the plugin can append<\/strong> eligible published URLs from WordPress that are not already listed in the synced body, subject to your exclusion rules.<\/p><\/dd>\n Yes. When you are not<\/strong> connected, use Add published URLs from WordPress<\/strong> on the manual panel. That uses your saved manual text as the base (or a short starter if empty). It does not<\/strong> apply GA4 ranking\u2014that comes from connecting and syncing.<\/p><\/dd>\n The plugin fetches LLMS.txt<\/strong> from your GcCo AI View account, merges in additional WordPress URLs, applies exclusions, updates what is served at No. It only registers the llms.txt<\/strong> route and settings; it does not change posts or theme output.<\/p><\/dd>\n Settings and the synced or manual llms.txt<\/strong> body are stored in the WordPress options table ( The Text Domain is AI_VIEW_APP_URL<\/code>, etc.) rename them to AIVISY_APP_URL<\/code>, AIVISY_CONNECT_BASE<\/code>, AIVISY_SYNC_API_URL<\/code>, AIVISY_PROPERTIES_API_URL<\/code>, AIVISY_BIND_API_URL<\/code>.<\/p>","1.1.2":"https:\/\/yoursite.com\/llms.txt<\/code><\/strong> that tells AI systems and crawlers how to interpret your site\u2014similar in spirit to robots.txt<\/code>, but aimed at LLM<\/strong> and AI discovery rather than crawl rules alone.<\/p>\n\nWhy llms.txt \/ LLMS.txt?<\/h3>\n\n
\/llms.txt<\/code><\/strong> find your file.<\/p>\n\nWhat this plugin does for your llms.txt<\/h3>\n\n
\n
\/llms.txt<\/code><\/strong> when that mode is active.<\/li>\nllms.txt<\/code><\/strong> file in the site root (in addition to the pretty URL).<\/li>\n<\/ul>\n\nWho should use this llms.txt plugin?<\/h3>\n\n
External services<\/h3>\n\n
\n
\n
ai-view-sync<\/code> folder to \/wp-content\/plugins\/<\/code> (or install the ZIP from Plugins \u2192 Add New \u2192 Upload). The ZIP root should be ai-view-sync\/<\/code> containing ai-view-sync.php<\/code>.<\/li>\ngcco-ai-view-sync<\/code>, deactivate and delete that copy first, then install this one (WordPress treats it as a new plugin path).<\/li>\nhttps:\/\/example.com\/llms.txt<\/code><\/strong> (pretty permalinks recommended). Verify in a browser or with curl<\/code> that \/llms.txt<\/code><\/strong> returns your text.<\/p>\n\n\n\n
What is llms.txt?<\/h3><\/dt>\n
\/llms.txt<\/code><\/strong>. It signals to AI and LLM tools what to prioritize on your site (separate from robots.txt<\/strong>, which controls crawling). This plugin helps you publish and update llms.txt on WordPress<\/strong> without FTP.<\/p><\/dd>\nDo I need an API key?<\/h3><\/dt>\n
AIVISY_APP_URL<\/code> or custom sync URLs) exist only for advanced or self-hosted setups.<\/p><\/dd>\nDo I need GcCo AI View to use the plugin?<\/h3><\/dt>\n
What makes this different from other llms.txt plugins?<\/h3><\/dt>\n
llms.txt<\/code><\/strong> on disk in addition to the pretty URL.<\/p><\/dd>\nWhere does the file get published?<\/h3><\/dt>\n
https:\/\/yoursite.com\/llms.txt<\/code><\/strong> (pretty permalinks recommended). The plugin may also write llms.txt<\/code><\/strong> in your site root when the server allows it.<\/p><\/dd>\nCan I resync the file later?<\/h3><\/dt>\n
Can I include WordPress pages that are new and not yet in GA4?<\/h3><\/dt>\n
Can I build llms.txt from WordPress only, without GA4?<\/h3><\/dt>\n
What happens on \"Sync\" (connected)?<\/h3><\/dt>\n
\/llms.txt<\/code><\/strong>, and shows last sync time plus counts (URLs from the synced body vs appended).<\/p><\/dd>\nWill this replace my theme or SEO plugin?<\/h3><\/dt>\n
Where is content stored?<\/h3><\/dt>\n
aivisy_settings<\/code>).<\/p><\/dd>\nWordPress.org says my text domain does not match the plugin slug. What should I do?<\/h3><\/dt>\n
ai-view-sync<\/code><\/strong>. It must match your WordPress.org plugin slug<\/strong> and the top-level folder name<\/strong> in the ZIP (ai-view-sync\/<\/code>). That is independent of the admin URL parameter page=aivisy-settings<\/code> used for OAuth callbacks.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.4<\/h4>\n\n
\n
1.1.3<\/h4>\n\n
\n
AI_VIEW_*<\/code> \/ ai_view_llms_*<\/code> prefixes with unique AIVISY_*<\/code> \/ aivisy_*<\/code> prefix throughout (constants, options, transients, hooks, admin slugs).<\/li>\n1.1.2<\/h4>\n\n
\n
ai-view-sync<\/code>; package folder and main file use the same slug (ai-view-sync\/ai-view-sync.php<\/code>).<\/li>\n<\/ul>\n\n1.1.0<\/h4>\n\n
\n
\/llms.txt<\/code><\/strong>.<\/li>\n