Nextra docs monitoring

Draft. This outline will be expanded with verified, platform-specific detail.

How Nextra sites typically break

• _meta files control the sidebar, so pages left out of them become orphans. The exact file name and format depend on your Nextra version; check its docs.
• Heading ids are generated from heading text, so renaming a heading breaks #fragment links.
• Migrating between the App Router and the Pages Router can change URL trailing-slash behavior.

What the Nextra build catches, and what it misses

• The Next.js build reports errors for pages that fail to render. Whether internal links are checked at build time depends on your Nextra version; check its docs.
• The build misses external links, anchors from other sites, sitemap drift and orphans.

Setting up redirects on Nextra

• Redirects are typically configured with redirects() in next.config.js, or in vercel.json when hosting on Vercel.

How PathIntact monitors a Nextra site

• PathIntact detects Nextra from the markup it generates, reads the site as static HTML, and offers a Vercel redirect snippet by default.