Broken links in published documentation
Broken links in published documentation
Symptom: Clicking a link returns a 404 or jumps to the wrong page.Cause: The link path does not match the actual file route, or the target page was moved or renamed without updating references.Fix:
- Check the link path in your Markdown or MDX file. Use absolute paths starting from the content root, for example
/guides/authentication. - Verify the target file exists at that exact path, including case sensitivity.
- If you renamed a file, update all internal links that point to the old path.
- Rebuild and redeploy to confirm the links resolve.
Images not loading
Images not loading
Symptom: Image placeholders appear instead of your uploaded images.Cause: The image path is incorrect, the file is not committed to the repository, or the image format is unsupported.Fix:
- Confirm the image file is in your project directory, usually under an
imagesorassetsfolder. - Use a relative path from the Markdown file to the image, for example
../images/diagram.png. - Supported formats are PNG, JPG, GIF, and SVG. WebP is not supported.
- Commit the image file and redeploy.
Search not returning results
Search not returning results
Symptom: The search bar shows no matches for content you know exists.Cause: The search index has not been rebuilt after recent changes, or the content is in a file excluded from indexing.Fix:
- Trigger a fresh deploy. The search index rebuilds automatically after each successful deployment.
- Wait two to three minutes after deployment for indexing to complete.
- Check that the page is not hidden behind
noindexfrontmatter or excluded from navigation. - If the issue persists, clear your browser cache and try again.
Slow publish times
Slow publish times
Symptom: Deployments take much longer than usual or time out.Cause: Large image files, excessive page counts, or a large dependency tree can slow the build process.Fix:
- Compress images before adding them. Aim for under 200 KB per image.
- Remove unused pages or assets from the repository.
- Split very large docs into multiple projects if possible.
- Check the build logs for warnings about slow steps and address them.
404 on a custom domain
404 on a custom domain
Symptom: Your custom domain shows a 404 for all pages, but the default Mintlify URL works.Cause: DNS records are missing or incorrect, or the domain has not finished propagating.Fix:
- In Mintlify, go to Settings > Domain and copy the required DNS records.
- Add the CNAME or A records at your DNS provider exactly as shown.
- Verify propagation with a DNS lookup tool.
- Return to Mintlify and click Verify domain. If verification fails, double-check record values and TTL settings.
