A1 Local Markdown Delivery Inspector

Markdown represents headings, paragraphs, lists and links as readable text. An agent or other client can request that representation instead of processing a complete HTML page. This plugin makes the representation available; each client decides whether to use it.

No. Conversion runs inside WordPress. No external AI service, account or API key is required. This is an independent plugin from A1 Local and is not affiliated with Cloudflare.

With pretty permalinks, the dedicated route is /a1-local-markdown-delivery-inspector/POST_ID.md. With plain permalinks, the canonical URL uses the a1local_mdi_format=markdown query parameter. The inspector includes an Open Markdown link. Eligible pages also advertise the alternate URL in an HTML link and HTTP Link header.

Yes. Dedicated URLs serve Markdown. Header delivery is optional and requires an explicit Accept preference for text/markdown over HTML. Wildcards and equal preferences keep HTML. If you enable header delivery, test the real cache in front of WordPress; some hosts need a bypass rule for Markdown requests.

Yes. Enter phrases that should already appear on the page, one per line. The inspector checks whether each phrase occurs in the delivered document, ignoring case and punctuation. These phrases are checks, not extra public content: saving a phrase does not insert it into the Markdown.

No ranking, indexing, citation, training-exclusion or crawler-adoption guarantees are made. Markdown Delivery Inspector publishes a content representation and helps you inspect its delivery. It does not submit pages to AI providers or search engines.

The document is rendered on request. Markdown responses ask caches not to store them. A host configured to ignore these headers can still cache incorrectly, and a previously downloaded document cannot be recalled. The inspector reports observed behaviour on its request path.

It reads the full server-rendered theme output. Content created only by browser JavaScript is unavailable. Test your theme, page builder, multilingual setup, WooCommerce store and membership rules on staging. No universal compatibility is claimed. Private areas, accounts, carts and checkout pages are not suitable content to publish through this tool.

Return false from the a1local_mdi_can_export_post filter for a restricted post. The filter can restrict access further but cannot override the built-in exclusions. Add a data-a1local-mdi-exclude attribute to a rendered element to remove that element and its descendants, including nested structured data.

It declares a preference using the Content-Signal header; it does not enforce access restrictions. The default is ai-train=no, search=yes, ai-input=yes. An existing Content-Signal response header takes precedence. Whether a client respects the signal is outside the plugin’s control.

Settings and per-page exclusions/important phrases remain in your WordPress database. Check results stay in the current browser screen. The plugin does not send content to an external conversion service or add telemetry, IP logging or a visitor analytics database. Your hosting provider, other plugins and WordPress may have their own logs. Uninstalling removes this plugin’s settings and page metadata.

The plugin handles singular public posts, pages and enabled custom post types, with a 2 MB limit on rendered HTML. It selects the first main landmark, then an article/content/body fallback. Inspect unusual themes and pages with several main containers. Archives, browser-only rendering, llms.txt generation, bulk exports and analytics are not included.