aidentity

<h4>The problem: your site is invisible to AI assistants</h4>
<p>Millions of people now look for information by asking ChatGPT, Claude, Perplexity or Google Gemini directly, instead of using a traditional search engine.</p>
<p><strong>But how do these AI assistants decide which sites to cite in their answers?</strong></p>
<p>They use specific protocols — such as <strong>llms.txt</strong> — to understand which sites exist, what they contain and whether they are reliable sources. Without these files, your site is essentially invisible: AI assistants do not know you exist, they do not cite you, and you lose potential traffic.</p>
<p><strong>Aidentity Generative Engine Optimizer</strong> implements these protocols on your WordPress site automatically.</p>
<h4>How it works</h4>
<p>Once installed, your site starts “speaking the language of AI”:</p>
<ol>
<li>
<p><strong>Creates the llms.txt file</strong> — Think of it as a business card for AI assistants. It tells them who you are, what your main content is and how to find it. The file is generated automatically and updated every time you publish.</p>
</li>
<li>
<p><strong>Generates FAQ Schema</strong> — If your articles use headings such as “How does X work?” or “What does Y mean?”, the plugin turns them into structured data that Google and AI assistants recognise as authoritative questions and answers.</p>
</li>
<li>
<p><strong>Adds optimized summaries</strong> — AI assistants love to find the key takeaway right away. The plugin adds a short summary at the top of your articles to make content easier to cite.</p>
</li>
</ol>
<h4>Why it matters now</h4>
<p>Traditional SEO is built around Google. But traffic is shifting:</p>
<ul>
<li>ChatGPT has more than 200 million active users</li>
<li>Perplexity is becoming the preferred search engine for many professionals</li>
<li>Google itself is integrating AI Overview into search results</li>
</ul>
<p>If your site is not optimized for AI assistants, you are losing visibility every day.</p>
<h4>What is llms.txt?</h4>
<p>It is an emerging standard (similar to robots.txt) that lets websites communicate with Large Language Models. The file tells AI assistants:</p>
<ul>
<li>Who you are and what your site is about</li>
<li>What the main content is</li>
<li>How information is organised</li>
<li>Where to find machine-readable versions of your content</li>
</ul>
<p>Without llms.txt, AI assistants have to “guess” what your site contains. With llms.txt, you tell them directly.</p>
<h4>What the plugin actually does</h4>
<ul>
<li><strong>Generates /llms.txt</strong> — Structured index of your site for AI assistants</li>
<li><strong>Generates /llms-full.txt</strong> — Full version including all content</li>
<li><strong>Creates automatic FAQ Schema</strong> — From H2/H3 headings written as questions</li>
<li><strong>Adds AI-friendly summaries</strong> — At the top of articles</li>
<li><strong>Updates itself</strong> — Every time you publish or edit content</li>
</ul>
<p>All these features work on every post and page, without artificial limits.</p>
<h4>Looking for more advanced AI optimization?</h4>
<p>The free Aidentity Generative Engine Optimizer covers the essentials. For deeper AI optimization workflows — content scoring, citability analysis, structure auditing, entity recognition, freshness monitoring and Google Search Console integration — visit <a href="https://www.aidentity.it/" rel="nofollow ugc">aidentity.it</a> to discover the full Aidentity GEO suite.</p>
<h4>Supported languages</h4>
<p>The plugin automatically detects questions in Italian and English when generating FAQ schemas.</p>


Aidentity Generative Engine Optimizer

Make your site discoverable by ChatGPT, Claude and Perplexity. Automatically generates llms.txt and FAQ Schema.

provimedia

<p>Geo Widget creates structured, citable answer blocks (Answer Cards) directly in the WordPress Gutenberg Editor. This optimizes your content specifically for AI-powered search engines like Google AI Overviews, Bing Copilot, or Perplexity.</p>
<p>Each block consists of a question, answer, bullet points, and sources — including copy buttons so readers and AI systems can correctly cite your content.</p>
<h4>Who is this plugin for?</h4>
<ul>
<li>Content creators who want to be cited in AI answers</li>
<li>SEO teams focusing on Generative Engine Optimization</li>
<li>Editorial teams needing structured fact blocks in articles</li>
<li>Developers integrating Answer Cards into external systems via REST API</li>
</ul>
<h3>Features</h3>
<h4>Gutenberg Block “Answer Card”</h4>
<ul>
<li><strong>Question Field</strong> — Input field with character limit (max. 140 characters) and live counter</li>
<li><strong>Answer Field</strong> — Multi-line text field for the citable answer</li>
<li><strong>Word Counter with Traffic Light Indicator</strong> — Real-time color-coded assessment of answer length:
<ul>
<li>Gray: Too short (under 40 words)</li>
<li>Green: Ideal length (40-80 words)</li>
<li>Yellow: Getting long (81-120 words)</li>
<li>Red: Too long (over 120 words)</li>
</ul>
</li>
<li><strong>Bullet Points (Key Points)</strong> — Up to 6 key statements with add/remove buttons</li>
<li><strong>Source Management</strong> — Up to 6 sources with label, URL, publisher, and date</li>
<li><strong>Anchor ID</strong> — Automatically generated from the question, with umlaut support. Manually overridable with reset option</li>
<li><strong>Server-Side Rendering</strong> — Output is fully rendered server-side (no frontend JavaScript required)</li>
</ul>
<h4>Copy Buttons</h4>
<ul>
<li><strong>Copy Link</strong> — Copies the permalink including anchor fragment to clipboard</li>
<li><strong>Copy Citation</strong> — Copies a formatted citation: “Question” — Post Title (Site Name, Date) URL</li>
<li><strong>Visual Feedback</strong> — Button shows “Copied!” and is briefly disabled</li>
<li><strong>Fallback for Older Browsers</strong> — Automatic fallback when Clipboard API is unavailable</li>
<li><strong>Configurable Display</strong> — Controllable via sidebar: link only, citation only, or both</li>
</ul>
<h4>REST API</h4>
<ul>
<li><strong>Public Endpoint</strong> — <code>GET /wp-json/provimedia-geo-widget/v1/answers</code> returns all Answer Cards as JSON</li>
<li><strong>Filter by Post</strong> — Parameter <code>post_id</code> to retrieve blocks from a specific post</li>
<li><strong>Pagination</strong> — Parameters <code>per_page</code> and <code>page</code> with response headers <code>X-WP-Total</code> and <code>X-WP-TotalPages</code></li>
<li><strong>Read-only</strong> — GET requests only, no write operations</li>
<li><strong>Disableable</strong> — Can be completely disabled in settings</li>
</ul>
<h4>Settings Page</h4>
<ul>
<li><strong>Enable/Disable REST API</strong> — Toggles the public API endpoint on or off</li>
<li><strong>Include Answer in Citation</strong> — Adds the answer text to the citation</li>
<li><strong>Default Copy Mode</strong> — Global default: Link & Citation, Link only, or Citation only</li>
<li><strong>Strict Word Limit</strong> — Enforces the 120-word limit when saving</li>
</ul>
<h4>Security</h4>
<ul>
<li>Input sanitization of all attributes</li>
<li>Consistent late-escaping against XSS</li>
<li>Protocol whitelist for URLs (http/https only)</li>
<li>No innerHTML or eval in frontend JavaScript</li>
<li>Drafts and password-protected posts excluded from API</li>
<li>SQL injection protection via parameterized queries</li>
<li>Whitelist validation of all setting values</li>
<li>Nonce protection (CSRF) on settings page</li>
<li>External links with <code>rel="noopener noreferrer"</code></li>
</ul>
<h4>Clean Uninstallation</h4>
<ul>
<li>On uninstall, all plugin options and transients are completely removed from the database</li>
</ul>
<h4>Compatibility</h4>
<ul>
<li>WordPress 6.0 or higher</li>
<li>PHP 7.4 or higher</li>
<li>Gutenberg Block API v3</li>
<li>RTL support (automatically generated stylesheets)</li>
<li>Translation-ready (Text Domain: provimedia-geo-widget)</li>
</ul>
<h3>Development</h3>
<p>The compiled JavaScript and CSS files in the <code>/build</code> directory are generated from source files in the <code>/src</code> directory using WordPress build tools.</p>
<h4>Source Code</h4>
<p>All source code is included in the plugin:</p>
<ul>
<li><code>/src/index.js</code> – Editor block component (React/JSX)</li>
<li><code>/src/frontend.js</code> – Copy button functionality (Vanilla JS)</li>
<li><code>/src/editor.scss</code> – Editor-only styles (SCSS)</li>
<li><code>/src/style.scss</code> – Frontend styles (SCSS)</li>
</ul>
<h4>Build Instructions</h4>
<ol>
<li>Install Node.js (v18 or higher recommended)</li>
<li>Navigate to the plugin directory</li>
<li>Run <code>npm install</code> to install dependencies</li>
<li>Run <code>npm run build</code> to compile assets</li>
</ol>
<h4>Build Commands</h4>
<ul>
<li><code>npm run build</code> – Compile production assets</li>
<li><code>npm run start</code> – Watch mode for development</li>
<li><code>npm run lint</code> – Run code linting</li>
<li><code>npm run test</code> – Run unit tests</li>
</ul>
<h4>Dependencies</h4>
<ul>
<li>@wordpress/scripts – WordPress build toolchain</li>
<li>@wordpress/blocks – Block registration API</li>
<li>@wordpress/block-editor – Block editor components</li>
<li>@wordpress/components – UI components</li>
<li>@wordpress/i18n – Internationalization utilities</li>
<li>@wordpress/element – React abstraction layer</li>
<li>@wordpress/url – URL validation utilities</li>
</ul>


Provimedia GEO Widget

Citable Answer Blocks for Generative Engine Optimization (GEO). Optimize your content for AI-powered search engines.

Aidentity Generative Engine Optimizer vs Provimedia GEO Widget