This page is a draft outline and is not indexed yet. Monitoring for Redocly sites already works.
Redocly docs monitoring
Draft. This outline will be expanded with verified, platform-specific detail.
How Redocly sites typically break
- Redoc typically renders API references on the client, so anchors for operations and tags may only exist after JavaScript runs.
- Operation ids drive deep-link anchors, so renaming an operation breaks external links.
- Multi-product portals change URL prefixes when products are restructured.
What Redocly catches, and what it misses
- Redocly's tooling focuses on OpenAPI linting and configuration validation; check Redocly's docs for what link checking, if any, its portals include.
- It misses external links, anchors from other sites, sitemap drift and orphans.
Setting up redirects on Redocly
- Redirects are typically configured in the portal configuration or through host-level rules; check Redocly's docs for the current syntax.
How PathIntact monitors a Redocly site
- PathIntact detects Redoc sites from their Redoc script and markup signatures and marks them as needing JavaScript rendering, which runs on a paid plan; Free reads the static HTML, where a Redoc reference page has almost no content.
Check a Redocly site now
Free 50-page crawl with broken links, anchors, orphans and sitemap problems.
Guides
Last updated 2026-09-16. Redocly is a trademark of its owner; PathIntact is not affiliated.