Zyte Documentation Audit
Deep, mostly well-structured docs for Zyte API and Scrapy Cloud with real error references and multi-language examples — undermined by a broken agent-facing surface (dead llms.txt links, corrupted Markdown-export anchors), cross-page contradictions on rate limits, and a Search API reference that never names a valid value for its own required parameter.
1. llms.txt links to eight pages that 404 (critical)
Problem: https://docs.zyte.com/llms.txt — the index explicitly published for AI agents — lists ~133 relative .md links, and 8 of them return HTTP 404: smart-proxy-manager.md, smart-proxy-manager/errors.md, smart-proxy-manager/fetch-api.md, smart-proxy-manager/headless.md, smart-proxy-manager/old-fetch-api.md, smart-proxy-manager/residential.md, smart-proxy-manager/sessions.md, and smart-proxy-manager/stats.md. The .html versions of the same pages return 200 (e.g. smart-proxy-manager/errors.html), and sibling pages like smart-proxy-manager/integrations/python.md and smart-proxy-manager/sunset.md resolve fine — so the Markdown export simply doesn't exist for those eight pages while the index still advertises them.
Location: https://docs.zyte.com/llms.txt
Consequence: An AI agent crawling the advertised index hits a 6% dead-link rate concentrated in one product area. Agents don't retry with .html; they silently lose the entire Smart Proxy Manager error reference and Stats API, exactly the pages a migrating SPM customer's coding agent would need.
The fix: Generate the .md exports for the eight missing SPM pages, or remove/redirect their entries in llms.txt. Add a CI link-check over every URL in llms.txt.
2. Search API requires a domain but never names one valid value (critical)
Location: https://docs.zyte.com/zyte-api/usage/search/request.md (also quickstart.md, geo.md, index.md)
Problem: The request reference marks domain as required: "A supported search domain. Unsupported domains return a 400 error." But no page in the Search API section — index, quickstart, request parameters, or geo-targeting — lists the supported domains. Every single example, including the geo page's "Targeting a regional domain" section whose entire point is choosing a real domain, uses the placeholder . Meanwhile the usage hub describes the feature as "Search Google with a typed interface."