AEOHelper – Markdown Publisher

AEOHelper – Markdown Publisher creates separate, reviewed Markdown versions of selected public WordPress Pages and Posts. It extracts the logged-out HTML response, converts useful content into Markdown, and lets an administrator review the result before anything is published.

The plugin does not replace or modify the original HTML page. It does not switch content based on a visitor’s user agent and does not send content or activity to an external AI service.

Features include:

• Specific-page and all-eligible publishing modes.
• Manual review and approval before first publication.
• Per-page content selector and exclusion controls.
• Automatic conversion of headings, paragraphs, links, lists, native HTML tables and disclosure/FAQ blocks.
• Opt-in conversion of div-based visual grids into structured Markdown tables using data-aeohelper-table.
• Markdown-only section context using data-aeohelper-context.
• Legacy data-zire-ai-* attributes remain supported for existing installations.
• Clean /index.md URLs with HTML discovery links and HTTP canonical headers pointing back to the original page.
• Optional llms.txt manager that remains off by default.
• Optional local request activity for Markdown and llms.txt endpoints.
• Manual, draft-only or automatic update handling when approved source content changes.
• Safeguards for drafts, passwords, known noindex settings and common account routes.

Markdown availability does not guarantee indexing, inclusion in an AI system or citations. The llms.txt format is an emerging proposal and support varies by provider.

Privacy

The plugin does not send telemetry or site content to any external service. When optional Request Activity is enabled, endpoint activity is stored only in the local WordPress database for the selected retention period. Administrators can clear it at any time. Deleting the plugin removes its settings, generated documents and request table.

The plugin includes a suggested privacy-policy paragraph in WordPress Privacy settings.

External services

No external service is required for core functionality. Conversion, previews, approved Markdown and optional request activity are handled locally by WordPress, except that preview generation makes a same-site public HTTP request to the page being converted.