---
title: "Docs Benchmark Report: Contentsquare"
description: "Contentsquare benchmark report with category scores and check-level detail."
canonical: "https://docsalot.dev/benchmarks/docs/contentsquare"
human_url: "https://docsalot.dev/benchmarks/docs/contentsquare"
markdown_url: "https://docsalot.dev/benchmarks/docs/contentsquare.md"
index_url: "https://docsalot.dev/benchmarks/docs"
index_markdown_url: "https://docsalot.dev/benchmarks/docs.md"
updated: "2026-05-04"
---

[Back to docs benchmark index](https://docsalot.dev/benchmarks/docs.md)

# Docs Benchmark Report: Contentsquare

> Copy this markdown report into a developer ticket or coding agent prompt when you want concrete docs fixes tied to benchmark checks.

## Report Links

- Human report: https://docsalot.dev/benchmarks/docs/contentsquare
- Markdown report: https://docsalot.dev/benchmarks/docs/contentsquare.md
- Benchmark index: https://docsalot.dev/benchmarks/docs
- Benchmark index markdown: https://docsalot.dev/benchmarks/docs.md
- Public docs URL: https://docs.contentsquare.com/

## Score Summary

- Report for: Contentsquare
- Display URL: docs.contentsquare.com
- Report type: Public benchmark report
- Score: 97
- Grade: A
- Summary: Contentsquare scored 97/100 on Fern's public Agent Score report across 22 published checks.
- Checked at: May 4, 2026 at 9:03 PM UTC
- Category: Other
- Source: Fern Agent Score
- Checks passed: 18/22
- Warnings: 3
- Failed checks: 0
- Skipped checks: 1

## What Already Works

- Observability and Content Health is relatively strong at 100/100.
- URL Stability and Redirects is relatively strong at 100/100.
- Authentication and Access is relatively strong at 100/100.

## What To Improve Next

- LLMS TXT Size in Content Discoverability.
- LLMS TXT Directive (HTML) in Content Discoverability.
- Content Start Position in Page Size and Truncation Risk.

## Full Score Breakdown

### Page Size and Truncation Risk - 99/100

- Question: Can an agent read the page without losing important context?
- Category focus: Checks for oversized pages, noisy navigation, and chunking risks.
- Category note: 1 warning still need cleanup here.
- Passed: 3
- Warnings: 1
- Failed: 0
- Skipped: 0

Checks:
- PASS - Rendering Strategy: All 10 sampled pages contain server-rendered content
- PASS - Page Size Markdown: All 10 pages under 50K chars (median 4K, max 10K)
- PASS - Page Size Html: All 10 sampled pages convert under 50K chars (median 4K, 0% boilerplate)
- WARN - Content Start Position: 1 of 10 sampled pages have content starting at 10–50% (worst 12%)

### Observability and Content Health - 100/100

- Question: Can an agent tell whether the docs are fresh and trustworthy?
- Category focus: Checks for freshness signals, content health, and crawl confidence.
- Category note: This area is already one of the stronger parts of the report.
- Passed: 3
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT Freshness: llms.txt covers 99% of 371 sitemap doc pages
- PASS - Markdown Content Parity: All 10 pages have equivalent markdown and HTML content (avg 0% missing)
- PASS - Cache Header Hygiene: All 11 endpoints have appropriate cache headers

### URL Stability and Redirects - 100/100

- Question: Can an agent trust that URLs will stay predictable?
- Category focus: Checks for stable docs URLs and minimal redirect churn on core paths.
- Category note: This area is already one of the stronger parts of the report.
- Passed: 2
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Http Status Codes: All 10 sampled pages return proper error codes for bad URLs
- PASS - Redirect Behavior: No redirects detected across 10 sampled pages

### Authentication and Access - 100/100

- Question: Can an agent access the docs without getting blocked?
- Category focus: Checks whether public docs stay accessible and auth-gated content is handled clearly.
- Category note: 1 check were skipped in this report.
- Passed: 1
- Warnings: 0
- Failed: 0
- Skipped: 1

Checks:
- PASS - Auth Gate Detection: All 10 sampled pages are publicly accessible
- SKIP - Auth Alternative Access: All docs pages are publicly accessible; no alternative access paths needed

### Content Structure - 100/100

- Question: Can an agent understand how the page is organized?
- Category focus: Checks for headings, code block formatting, and readable section hierarchy.
- Category note: This area is already one of the stronger parts of the report.
- Passed: 3
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Tabbed Content Serialization: No tabbed content detected across 10 sampled pages
- PASS - Section Header Quality: No tabbed content found; header quality check not applicable
- PASS - Markdown Code Fence Validity: All 38 code fences properly closed across 11 pages

### Markdown Availability - 100/100

- Question: Can an agent fetch a clean text version of the docs?
- Category focus: Checks for markdown routes and clean text delivery without UI-heavy wrappers.
- Category note: This area is already one of the stronger parts of the report.
- Passed: 2
- Warnings: 0
- Failed: 0
- Skipped: 0

Checks:
- PASS - Markdown Url Support: 10/10 sampled pages support .md URLs (100%)
- PASS - Content Negotiation: 10/10 sampled pages support content negotiation (100%)

### Content Discoverability - 91/100

- Question: Can an agent find the right starting point?
- Category focus: Checks for llms.txt, sitemaps, and a clear public docs entry point.
- Category note: 2 warnings still need cleanup here.
- Passed: 4
- Warnings: 2
- Failed: 0
- Skipped: 0

Checks:
- PASS - LLMS TXT Exists: llms.txt found at 1 location(s)
- PASS - LLMS TXT Valid: llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
- WARN - LLMS TXT Size: llms.txt is 65,788 characters (between 50,000 and 100,000; consider splitting)
- PASS - LLMS TXT Links Resolve: All 10 same-origin sampled links resolve (366 total links)
- PASS - LLMS TXT Links Markdown: 10/10 same-origin sampled links point to markdown content (100%)
- WARN - LLMS TXT Directive (HTML): llms.txt directive found in 10 of 10 sampled pages, but buried deep in the page (past 50%)


## Suggested Handoff

Ask the developer or coding agent to work through the failed checks and next-step items first, then rerun the benchmark on https://docs.contentsquare.com/ to confirm the score moves in the right direction.