Coveo

Coveo Documentation Audit

Coveo ships a polished, deep documentation site with a real llms.txt, .md source exports, and Redocly API references — but the agent-facing layer it advertises is partly broken: the .md files promised as "fully resolved plain text" leak raw Liquid and AsciiDoc across multiple pages, the API references render only under a real browser, and two different "authentication methods" pages give two different answers.

1. The .md exports promised to agents contain raw, unevaluated template code (critical)

Location: https://docs.coveo.com/en/llms.txt and https://docs.coveo.com/en/q2ib0310.md

Problem: llms.txt explicitly tells agents the per-page .md files "contain the full documentation content with all includes resolved, conditionals evaluated, and glossary terms expanded to plain text." The Deprecations page .md violates that promise directly. Instead of a table it ships raw Liquid:

{% assign by_order = site.deprecations | where_exp: ... | sort: "order" | reverse %}
{% assign sorted_deprecations = by_order | sort: "deprecation-date-for-sort-order" %}
| Deprecation date | Announcement |
|---|---|
| {{ notice.deprecation-date }} | [{{ notice.title }}]({{ site.baseurl }}/{{ notice.slug }}/) |

The template assigns sorted_deprecations but never iterates it (there is no {% for %} loop), and the single table row references an undefined notice variable. The live HTML page renders five real dated rows (e.g. "August 31, 2026 — .NET (C#) Platform SDK"); the .md renders zero.

Consequence: An AI agent — exactly the consumer llms.txt is built for — asking "what Coveo features are being deprecated and when" gets a table with no rows and no dates. The single most date-sensitive page in the docs is invisible to the machine-readable path Coveo advertises as authoritative.

The fix: Render the deprecations table to static Markdown in the .md export (iterate sorted_deprecations with a {% for %} and emit literal dates/titles), and add an export-time check that fails the build if any .md file still contains {% %} or {{ }} tokens.

2. API reference pages are 100% client-rendered — no-JS fetchers and HTML-only agents see only a banner (critical)

Location: and (and all pages)