dmytroberberov

phwizard

rldp

Ethora Chat Assistant adds an AI chat widget to your WordPress site. The assistant reads your own pages and uses them to answer visitor questions, so when someone asks about your product, your pricing, or how to get in touch, they get a real answer instead of a generic contact form.
<h4>Set it up in one click</h4>
The plugin includes a Set Up Automatically button. Click it, sign up for a free Ethora account inside the popup, confirm your site URL, and the plugin will:
<ol>
<li>Create your Ethora account.</li>
<li>Provision an AI assistant configured for your site.</li>
<li>Crawl up to 100 of your pages so the assistant can answer questions about them.</li>
<li>Save the assistant’s App ID into your plugin settings automatically.</li>
</ol>
The widget is live on your site as soon as the wizard finishes. Total time: roughly a minute.
Already have an Ethora App ID? Paste it into the settings field instead – both flows produce the same result.
<h4>What you get</h4>
<ul>
<li>A chat launcher on every page of your site (header or footer placement).</li>
<li>Answers grounded in your own content – the assistant cites what it knows from your indexed pages instead of making things up.</li>
<li>A free Ethora admin panel where you can edit the assistant’s prompt, change its name and avatar, re-index your pages after you update them, and review past visitor conversations.</li>
<li>Mobile-responsive widget that works on every screen size.</li>
<li>Optional Google Sign-In so returning visitors keep their chat history.</li>
</ul>
<h4>Typical use cases</h4>
<ul>
<li>Product and SaaS sites – “what does your tool do, how much, how do I integrate it?”</li>
<li>Documentation sites – the assistant answers from your docs.</li>
<li>E-commerce – shoppers ask about shipping, returns, sizing.</li>
<li>Customer support and help centres – first-line triage before a human steps in.</li>
<li>Lead generation and pre-sales – answer FAQs, capture warm leads.</li>
</ul>
<h4>How it works behind the scenes</h4>
The widget JavaScript is bundled with the plugin and served from your own WordPress site (no remote script host). At runtime the widget connects to the Ethora chat / AI service to provision a chat session and stream responses. The full list of third-party services it contacts is in External services below.
The “Set Up Automatically” wizard runs in a popup on the Ethora admin domain (app.chat.ethora.com). When it finishes it sends only the new App ID back to your WordPress site via the browser’s <code>postMessage</code> API, and your WordPress site saves it to the plugin settings. No Ethora credentials are stored in WordPress.
<h3>External services</h3>
This plugin embeds the Ethora chat / AI assistant. Once you set an App ID and a visitor opens the chat, the widget connects to the following third-party services. No data is sent to these services until a visitor interacts with the chat widget.
1. Ethora chat & AI service (provided by Dappros Ltd, trading as Ethora) 
– Purpose: deliver real-time messaging, authenticate the chat session, and return AI assistant responses. 
– Data sent: chat messages, the configured App ID, session/authentication tokens, and basic profile data for signed-in users. 
– When: while a visitor uses the chat widget. 
– Service endpoints: Ethora REST API and XMPP real-time messaging servers on ethora.com domains. 
– Provider: https://ethora.com 
– Terms of Service: https://wiki.ethora.com/wiki/Info:Privacy_policy#Terms_of_Service 
– Privacy Policy: https://wiki.ethora.com/wiki/Info:Privacy_policy
2. Google Sign-In (Google Firebase Authentication / Google OAuth 2.0) 
– Purpose: optional “Sign in with Google” login for chat users. 
– Data sent: email address and basic Google profile information, only when a visitor chooses to sign in with Google. 
– When: during the optional Google sign-in flow. 
– Domains: identitytoolkit.googleapis.com, securetoken.googleapis.com, accounts.google.com. 
– Terms of Service: https://policies.google.com/terms 
– Privacy Policy: https://policies.google.com/privacy
3. LinkPreview (linkpreview.net) 
– Purpose: generate preview cards for URLs shared inside chat messages. 
– Data sent: URLs contained in chat messages. 
– When: when a message contains a link. 
– Provider & Privacy Policy: https://www.linkpreview.net
Profile images for signed-in users may be displayed directly from Google’s user-content servers (lh3.googleusercontent.com).
The Set Up Automatically wizard, when used, additionally exchanges sign-up form data (email, password, first/last name) with the Ethora API to create your Ethora account, and submits your site URL for crawling. This data is sent only when you actively run the wizard.
<h3>Source code</h3>
The chat widget bundled with this plugin is built from Ethora’s open-source code.
<ul>
<li>Plugin source: https://github.com/dappros/ethora-wp-plugin</li>
<li>Chat widget source: https://github.com/dappros/ethora-ai-chat-widget (Vite-built embeddable widget)</li>
<li>The non-minified, human-readable build of the widget is shipped alongside the plugin as <code>assets/js/ethora_assistant.js</code>.</li>
</ul>
The widget is produced with a standard <code>npm install</code> + Vite build from the source repository above; no build step is required to run the plugin.

Ethora Chat Assistant

Add an AI chat assistant to your WordPress site in about a minute. The assistant learns from your own pages and answers visitor questions about your s …

Selvakumar Duraipandian

Markdown for AI Agents is a lightweight WordPress plugin that enables HTTP content negotiation for your site’s content. When a client (like an AI agent or a custom script) requests a page with the <code>Accept: text/markdown</code> header, the plugin intercepts the request and returns a clean, structured Markdown representation of the post or page content.
This is ideal for AI crawlers, RAG (Retrieval-Augmented Generation) systems, and non-browser clients that prefer machine-friendly text over complex HTML.
Important note: This plugin is primarily a developer/integration tool. Human visitors browsing your site will never see any difference — the Markdown output is only served when explicitly requested via the <code>Accept: text/markdown</code> HTTP header. Normal browser requests always receive the standard HTML page.
Key Features:
<ul>
<li>Automatically detects <code>Accept: text/markdown</code> headers.</li>
<li>Converts HTML content to clean Markdown using the League HTMLToMarkdown library.</li>
<li>Strips away theme layout, navigation, headers, footers, and sidebars — serving only the main content.</li>
<li>Adds useful HTTP response headers: <code>Content-Type: text/markdown</code>, <code>Vary: Accept</code>, and <code>X-Markdown-Word-Count</code>.</li>
<li>Respects WordPress visibility rules and filters.</li>
<li>No configuration required — works out of the box for posts, pages, and custom post types.</li>
</ul>
<h3>How It Works</h3>
This plugin uses a standard web technique called HTTP content negotiation. The same URL on your site can serve different representations of the same content depending on what the client asks for:
<ul>
<li>A regular browser sends <code>Accept: text/html</code> → receives your normal HTML page.</li>
<li>An AI agent sends <code>Accept: text/markdown</code> → receives a clean Markdown version of the same page.</li>
</ul>
No extra URLs, no duplicate content, no configuration needed. The plugin hooks into WordPress’s <code>template_redirect</code> action, detects the <code>Accept</code> header, captures the rendered HTML, converts it to Markdown, and returns it with appropriate headers.
<h3>Why Markdown for AI Agents?</h3>
When building RAG (Retrieval-Augmented Generation) applications or AI pipelines that ingest web content, HTML is extremely noisy. A typical WordPress page contains thousands of tokens worth of HTML tags, inline styles, navigation menus, scripts, and layout markup — none of which carries meaning for an AI model.
Serving clean Markdown instead can reduce token consumption by up to 60%, which means:
<ul>
<li>Lower API costs — fewer tokens ingested when loading pages into vector stores or LLM pipelines.</li>
<li>Faster processing — less text for the model to parse, filter, and discard.</li>
<li>Better retrieval accuracy — higher signal-to-noise ratio improves the quality of RAG results.</li>
<li>Simpler pipelines — no need for custom HTML stripping logic on the client side; the plugin handles it server-side.</li>
</ul>
Any AI agent, crawler, or ingestion script that sends <code>Accept: text/markdown</code> in its request header will automatically receive the clean Markdown version — no extra URLs, no separate endpoints, no changes to your content workflow.

Markdown for AI Agents

Serve clean Markdown versions of WordPress content to AI agents using HTTP content negotiation.

Ethora Chat Assistant vs Markdown for AI Agents