Skip to content
Integration and Troubleshooting

Markdown Scope, Archives and Exclusions

2 min read

Markdown output depends on both an explicit Markdown request and the content scope selected in citelayer®. Use exclusions for content that should stay outside this surface.

Choose the public content types

Open the Markdown settings and review selected post types and scope mode. Supported posts, pages, custom post types and product content can be served when they are published and in scope. Private or unpublished content is not a public Markdown source.

Archive behavior

Archives and the posts index have their own scope checks. Test the exact archive URL rather than assuming that a working article route means every category or custom archive works.

Exclude an individual page

Use the per-post Markdown exclusion when appropriate. A separate llms.txt exclusion affects index listing, not necessarily Markdown availability. Shop utility pages such as cart, checkout and account need special care because they are user/session surfaces.

Troubleshoot HTML instead of Markdown

  1. Confirm the feature is enabled.
  2. Send an explicit Accept header or use the documented Markdown URL form.
  3. Check publication status, selected post type and per-post exclusions.
  4. Inspect cache/redirect/provider interference and compare a second known in-scope page.

See request examples.

Next step

Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.

Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.