=== citelayer® === Contributors: jyria Tags: ai-seo, schema, llms-txt, ai-visibility, seo Requires at least: 6.4 Tested up to: 6.9 Requires PHP: 7.4 Stable tag: 1.2.2 License: GPL-2.0+ License URI: http://www.gnu.org/licenses/gpl-2.0.txt Get found by ChatGPT, Perplexity & AI search. AI Visibility, llms.txt, Schema.org — make your site the answer AI recommends. == Description == **AI is changing how people find your website.** Tools like ChatGPT, Perplexity, Gemini, and AI Overviews are replacing traditional search for millions of users. If AI can't find your content, you're invisible to a growing audience. citelayer® makes your WordPress site visible to AI — instantly. No coding, no configuration. Install, activate, done. = What citelayer® Does for Your Site = **🔍 Get Found by AI Search Engines** Your site gets an llms.txt file — a new standard that tells AI crawlers what your site is about, what content you publish, and what products you sell. Think of it as robots.txt, but for AI. **📊 Speak AI's Language with Schema.org** Automatically generates structured data (JSON-LD) that AI agents actually understand — your organization info, articles, products, and more. Better structured data = better AI recommendations. **📄 Serve Clean Content to AI Agents** When ChatGPT or Perplexity visit your page, citelayer® serves an optimized Markdown version instead of messy HTML. This uses 80% fewer tokens and gives AI a crystal-clear picture of your content. **🛡️ Stay in Control of Your Content** Configure how AI systems may use your content — allow or deny training, search indexing, and RAG/context usage. Your content, your rules. = Works with WooCommerce = If you run a shop, citelayer® makes your products visible to AI: * Product data automatically included in llms.txt * Product Schema.org markup generated * Product pages served as structured Markdown tables * AI agents can discover your shop via UCP (Universal Commerce Protocol) = Why AI Visibility Matters Now = * **58% of online searches** will involve AI by the end of 2026 * Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO) are the next evolution of SEO * Sites without AI-readable content are **invisible** to ChatGPT, Claude, Perplexity, and AI Overviews * citelayer® is the easiest way to make your WordPress site AI-ready = Free vs. Premium = The free plugin covers everything you need to get started: ✅ llms.txt generation ✅ Schema.org markup (Organization, WebSite, Article, Product) ✅ Markdown for AI agents ✅ Content-Signal headers ✅ WooCommerce product discovery **Premium adds:** 🚀 Full UCP product browsing, cart & checkout for AI agents 📈 AI Visibility Monitoring Dashboard 🔧 Advanced Schema.org (Reviews, FAQ, Shipping) 🛒 Product feed optimization [Learn more about Premium →](https://citelayer.ai/pricing) == Installation == 1. Upload the plugin files to `/wp-content/plugins/citelayer/` or install via WordPress plugin installer 2. Activate the plugin through the 'Plugins' menu in WordPress 3. Go to Settings → citelayer® to configure options 4. Visit `/llms.txt` on your site to verify everything works == Frequently Asked Questions == = Do I need technical knowledge to use this? = No. Install the plugin, activate it, and it works immediately. There are optional settings if you want to fine-tune, but the defaults work great for most sites. = Will this help my site rank better in Google? = Yes! The Schema.org markup improves how search engines understand your content. Plus, as Google integrates more AI into search results (AI Overviews), having AI-readable content helps you appear in those new formats. citelayer® detects Yoast SEO and Rank Math to avoid duplicate Schema. = What is llms.txt? = llms.txt is a new standard (similar to robots.txt) that helps AI systems understand your site. It tells AI crawlers what your site is about, what content you have, and what services you offer. More AI tools are starting to look for this file. = Will this slow down my site? = Not at all. Everything is aggressively cached — llms.txt refreshes every 24 hours, Schema every 7 days. AI-specific features only activate when an AI agent visits, not for regular users. = What is GEO / AEO? = GEO (Generative Engine Optimization) and AEO (Answer Engine Optimization) are the next evolution of SEO. Instead of optimizing for Google's blue links, you optimize for AI-generated answers. citelayer® handles the technical foundation so your content can appear in AI responses. = Can I control how AI uses my content? = Yes. citelayer® supports Content-Signal headers (contentsignals.org) that let you set rules: * Allow or deny AI training on your content * Allow or deny search indexing * Allow or deny use in AI responses (RAG) Default: Training denied, search and AI responses allowed. = What is UCP? = UCP (Universal Commerce Protocol) is a new standard by Google and Shopify that lets AI agents browse, compare, and even purchase products. The free version enables product discovery; Premium adds full shopping capabilities. == Screenshots == 1. Settings page with all configuration options 2. Example llms.txt output 3. Schema.org markup in page source 4. Markdown response for AI agents == Changelog == = 1.2.2 = * Rewritten plugin description — user-centric, benefit-driven (AI Visibility, GEO, AEO) * Updated FAQ in plain language * Optimized tags for WordPress.org discoverability * Updated plugin banner images = 1.2.1 = * Fixed WordPress.org deploy trigger (SVN deploy now runs in same workflow as auto-tag) * Added manual deploy fallback with dry-run support = 1.2.0 = * Added automated WordPress.org SVN deploy workflow (deploy on GitHub Release) * Added plugin directory assets (icons, banners) * Added .distignore for clean SVN deployments * Added readme/assets update workflow (update WordPress.org without new release) * Streamlined auto-tag workflow (ZIP build now handled by deploy action) = 1.1.9 = * Re-included composer.json in distribution ZIP (required when vendor/ is present) = 1.1.8 = * Removed vendor CLI binaries (bin/html-to-markdown) from release ZIP * Excluded composer.json from distribution * Improved forbidden file detection in build workflow = 1.1.7 = * Lowered PHP requirement from 8.1 to 7.4 (code + vendor deps confirmed compatible) * Fixed deploy workflow: .gitattributes and README.md now excluded from production * Added PHP 7.4 to CI syntax check matrix = 1.1.6 = * Converted inline scripts to wp_add_inline_script() for WP Codex compliance * Extracted inline styles to external CSS files with wp_enqueue_style() * Updated contributor and Author URI metadata = 1.1.5 = * Fix fatal error: rebuild vendor with composer --no-dev for release ZIP = 1.1.4 = * Exclude dev dependencies from release ZIP (phpstan, phpcs, etc.) = 1.1.3 = * Plugin name fix = 1.1.1 = * Respecting WP / WordPress trade mark = 1.1.0 = * Code Quality: PHPCS + PHPStan Audit — alle Violations behoben (PHPCS 260→1, PHPStan 649→0) * Tooling: phpcs.xml.dist, phpstan.neon, Composer Scripts (lint, fix, analyse) * CI: Strikte PHPCS- und PHPStan-Jobs (kein continue-on-error mehr) * Infrastructure: Pre-Commit-Hook für automatisches Code-Formatting * Fix: Schema.php — post_author Type-Cast für get_the_author_meta() = 1.0.0 = * Production release * Version synchronization (header, constant, readme.txt) * Security: Admin email no longer exposed in llms.txt by default * UCP Discovery: Dynamic platform detection (WordPress vs WooCommerce) * WebMCP: Removed non-implemented endpoint references * WebMCP: Fixed option check consistency * Added PHPCS configuration (WordPress Coding Standards) * Added PHPStan Level 6 configuration * Comprehensive CI pipeline (syntax, PHPCS, PHPStan, integrity checks) * Removed development artifacts from repository = 0.3.1 = * Compatibility V3.1: Multi-Family Safeguard — Conflict State detection * Admin: Conflict State banner on all admin pages * llms.txt: 503 response in Conflict State * Schema: No output in Conflict State * WebMCP context.json discovery endpoint = 0.3.0 = * Compatibility Layer V3: Enhance-Fix * serve_llms_txt() uses should_register_own_route() to prevent double output * Yoast Fallback: Citelayer takes over when Yoast has no physical file * State-Reset on plugin deactivation * Improved AIOSEO detection (defined + class_exists checks) = 0.2.0 = * Composer Support: league/html-to-markdown integration * PSR-4 Autoloading with SPL fallback * Feature-Detection on module level (Rank Math llms.txt, Yoast llms.txt) * All classes refactored to Citelayer\Plugin namespace * File structure: includes/ → src/ = 0.1.0 = * Initial release * llms.txt generation with WooCommerce awareness * Schema.org JSON-LD (Organization, WebSite, Article, Product) * UCP Discovery endpoint * Markdown for Agents with Content Negotiation * Content-Signal header configuration * Settings page in WordPress admin == Upgrade Notice == = 1.1.0 = Code Quality Audit. PHPCS + PHPStan Tooling. = 1.0.0 = First production release. Includes security improvements and CI pipeline.