This page is a draft outline and is not indexed yet. Monitoring for Sphinx sites already works.
Sphinx docs monitoring
Draft. This outline will be expanded with verified, platform-specific detail.
How Sphinx sites typically break
- Toctree membership decides reachability; documents outside any toctree are treated as orphans, and Sphinx typically warns about them at build time.
- Section ids are generated from section titles; renamed sections break
#fragmentlinks unless explicit labels are used. - Read the Docs typically serves documentation under language and version prefixes such as
/en/latest/; check your project's URL layout.
What Sphinx catches, and what it misses
- The
linkcheckbuilder (sphinx-build -b linkcheck) checks external links on demand at build time; check the Sphinx docs for how it scopes links and handles anchors. - It misses live-site drift, redirects, sitemap drift and cross-version canonicals.
Setting up redirects on Sphinx / Read the Docs
- Read the Docs offers redirect rules in the project dashboard, and self-hosted builds typically
use an extension such as
sphinx-reredirects; check your platform's docs for the exact behaviour.
How PathIntact monitors a Sphinx site
- PathIntact detects Sphinx sites from asset signatures such as
_static/doctools.jsand theme class names, reads the site statically, and recognises the/{lang}/{version}/versioning pattern.
Check a Sphinx site now
Free 50-page crawl with broken links, anchors, orphans and sitemap problems.
Guides
Last updated 2026-09-16. Sphinx is a trademark of its owner; PathIntact is not affiliated.