Markdown for AI Agents
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 Accept: text/markdown 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 Accept: text/markdown HTTP header. Normal browser requests always receive the standard HTML page. Key Features: Automatically detects Accept: text/markdown headers. Converts HTML content to clean Markdown using the League HTMLToMarkdown library. Strips away theme layout, navigation, headers, footers, and sidebars — serving only the main content. Adds useful HTTP response headers: Content-Type: text/markdown, Vary: Accept, and X-Markdown-Word-Count. Respects WordPress visibility rules and filters. No configuration required — works out of the box for posts, pages, and custom post types. How It Works 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: A regular browser sends Accept: text/html → receives your normal HTML page. An AI agent sends Accept: text/markdown → receives a clean Markdown version of the same page. No extra URLs, no duplicate content, no configuration needed. The plugin hooks into WordPress’s template_redirect action, detects the Accept header, captures the rendered HTML, converts it to Markdown, and returns it with appropriate headers. Why Markdown for AI Agents? 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: Lower API costs — fewer tokens ingested when loading pages into vector stores or LLM pipelines. Faster processing — less text for the model to parse, filter, and discard. Better retrieval accuracy — higher signal-to-noise ratio improves the quality of RAG results. Simpler pipelines — no need for custom HTML stripping logic on the client side; the plugin handles it server-side. Any AI agent, crawler, or ingestion script that sends Accept: text/markdown in its request header will automatically receive the clean Markdown version — no extra URLs, no separate endpoints, no changes to your content workflow.
Top keywords
- markdown15×3.38%
- content10×2.25%
- html9×2.03%
- text9×2.03%
- accept8×1.80%
- ai8×1.80%
- accept text6×1.35%
- page6×1.35%
- text markdown6×1.35%
- accept text markdown5×1.13%
- clean5×1.13%
- clean markdown4×0.90%
WP SMTP Mailer – SMTP7
WP SMTP Mailer – SMTP7 allows you to configure and send all outgoing emails via a SMTP server (It works like the postman). This will prevent your emails from going into the junk/spam folder of the recipients. Go to Settings > SMTP7 and configure SMTP then post SMTP credentials. You can set the following options: Specify the from name and email address for outgoing email. Choose to send mail by SMTP or PHP’s mail() function. Specify an SMTP host (defaults to localhost). Specify an SMTP port (defaults to 25). Choose SSL / TLS encryption (not the same as STARTTLS). Choose to use SMTP authentication or not (defaults to not). Specify an SMTP username and password. SMTP Testing server : MailMug.net SMTP Testing : https://youtu.be/fAXevTJ0r8I Support : http://www.ciphercoin.com/contact/ Contact Form 7 Not Sending Emails WordPress SMTP Mailer Features Send email using a SMTP sever. You can use Gmail, Yahoo, Hotmail’s SMTP server if you have an account with them. Securely deliver emails to your recipients. Username and password encryption List of SMTP Servers (Outgoing) Gmail :- Host: smtp.gmail.com – Secure(SSL) – Port(465) Gmail :- Host: smtp.gmail.com – Secure(TLS) – Port(587) Outlook.com :- Host: smtp-mail.outlook.com – Secure(TLS) – Port(587) Office365.com :- Host: smtp.office365.com – Secure(TLS) – Port(587) Hotmail.com :- Host: smtp.live.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(TLS) – Port(587) Yahoo Mail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Deutschland :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Yahoo Mail Plus :- Host: plus.smtp.mail.yahoo.com – Secure(SSL) – Port(465) AOL.com :- Host: smtp.aol.com – Secure(TLS) – Port(587) AT&T :- Host: smtp.att.yahoo.com – Secure(SSL) – Port(465) NTL @ntlworld.com :- Host: smtp.ntlworld.com – Secure(SSL) – Port(465) BT Connect :- Host: smtp.btconnect.com – No-Encryption – Port(25) BT Openworld :- Host: mail.btopenworld.com – No-Encryption – Port(25) BT Internet :- Host: mail.btinternet.com – No-Encryption – Port(25) Orange :- Host: smtp.orange.net – No-Encryption – Port(25) Orange UK :- Host: smtp.orange.co.uk – No-Encryption – Port(25) Wanadoo UK :- Host: smtp.wanadoo.co.uk – No-Encryption – Port(25) Comcast :- Host: smtp.comcast.net – No-Encryption – Port(587) Yahoo Mail AU/NZ :- Host: smtp.mail.yahoo.com.au – Secure(SSL) – Port(465) O2 Deutschland :- Host: mail.o2online.de – No-Encryption – Port(25) zoho Mail :- Host: smtp.zoho.com – Secure(SSL) – Port(465) T-Online Deutschland :- Host: securesmtp.t-online.de – Secure(TLS) – Port(587) 1&1 (1and1) :- Host: smtp.1and1.com – Secure(TLS) – Port(587) 1&1 Deutschland :- Host: smtp.1und1.de – Secure(TLS) – Port(587) Verizon :- Host: outgoing.verizon.net – Secure (SSL) – Port(465) Verizon (Yahoo hosted) :- Host: outgoing.yahoo.verizon.net – No-Encryption – Port(587) Mail.com :- Host: smtp.mail.com – Secure(SSL) – Port(465) GMX.com :- Host: smtp.gmx.com – Secure(SSL) – Port(465) Yahoo Mail UK :- Host: smtp.mail.yahoo.co.uk – Secure(SSL) – Port(465) Airmail :- Host: smtp.airmail.net – Secure(SSL) – Port(465) Bluewin.ch :- Host: smtpauth.bluewin.ch – Secure(SSL) – Port(465) Eartlink.net :- Host: smtpauth.earthlink.net – Secure(SSL) – Port(587) iCloud Mail :- Host: smtp.mail.me.com – Secure(SSL) – Port(587) Rocketmail :- Host: smtp.mail.yahoo.com – Secure(SSL) – Port(465) Rogers :- Host: smtp.broadband.rogers.com – Secure(SSL) – Port(465) Ameritech.net :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Pacbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Swbell :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Bellsouth :- Host: smtp.mail.att.net – Secure(SSL) – Port(465) Flash :- Host:- smtp.mail.att.net – Secure(SSL) – Port(465) Note: These SMTP Ports and Settings may be different depending upon your Host Provider. Please contact your Web Server Host for correct details.