November 2025 Link Checker Report: Fix Broken Links
Stay ahead of broken links with our comprehensive Link Checker Report for November 2025. This report provides a detailed overview of the broken links found in our content, helping you prioritize fixes and maintain a seamless user experience. Discover the insights and action items necessary to keep your website's links healthy and your content accessible.
π Summary
This link checker report provides a comprehensive overview of the link status across our content directories as of 2025-11-24.
- Total broken links: 0
- Internal HashiCorp links: 0 π¨
- External links: β οΈ
- Scan date: 2025-11-24
- Content scanned: All
/content/directories
This summary highlights the current state of our links, with a focus on identifying and addressing any broken links to ensure a smooth user experience. Let's dive into the details.
π― Prioritization Guide
When reviewing broken links, itβs crucial to prioritize fixes effectively. Focusing on the most critical links first ensures that users have access to the most important resources. Here's a guide to help you prioritize:
- π¨ High Priority: Internal HashiCorp links (developer.hashicorp.com, etc.)
- β οΈ Medium Priority: External documentation/API references users rely on
- βΉοΈ Low Priority: External blog posts, news articles, or optional resources
By following this guide, we can efficiently address broken links and maintain the integrity of our content ecosystem.
π Action Items
Based on the scan results, several action items need attention to maintain the quality and accessibility of our documentation. These action items are designed to address broken links and ensure a seamless user experience.
- [ ] Review high-priority internal links (0 found)
- [ ] Check if external links have moved to new URLs
- [ ] Update or remove links that are permanently broken
- [ ] Consider adding warnings for unreliable external sources
These steps will help us keep our content up-to-date and reliable for our users. Regularly addressing these action items is key to maintaining a healthy link ecosystem.
π Link Details
The following section provides a detailed breakdown of the link scan results, including a summary of link statuses and specific errors found in our content.
| Status | Count |
|---|---|
| π Total | 588377 |
| β Successful | 513879 |
| β³ Timeouts | 70 |
| π Redirected | 0 |
| π» Excluded | 14490 |
| β Unknown | 0 |
| π« Errors | 59910 |
This summary provides an overview of the link scan, showing the total number of links checked, the number of successful links, timeouts, redirects, excluded links, unknown statuses, and errors. Understanding these numbers helps us gauge the overall health of our links and identify areas needing immediate attention. Now, let's delve into the specifics of the errors encountered.
Errors per input
Errors in ./content/nomad/v1.3.x/content/docs/configuration/telemetry.mdx
- [404] https://developer.hashicorp.com/nomad/docs/telemetry | Network error: Not Found
This error indicates that the link to the Nomad telemetry documentation is broken. We need to investigate and update this link to ensure users can access the correct information. Broken internal links like this are high priority, as they directly impact the user's ability to navigate our documentation effectively.
Errors in ./content/terraform-enterprise/v202209-1/docs/enterprise/api-docs/private-registry/modules.mdx
- [404] https://developer.hashicorp.com/enterprise/api-docs/#query-parameters | Error (cached)
- [404] https://developer.hashicorp.com/registry/api-docs | Error (cached)
- [404] https://developer.hashicorp.com/registry/api-docs#service-discovery | Error (cached)
- [404] https://developer.hashicorp.com/registry/modules/publish#requirements | Error (cached)
- [404] https://developer.hashicorp.com/enterprise/api-docs/#authentication | Error (cached)
- [404] https://developer.hashicorp.com/enterprise/api-docs/oauth-tokens | Error (cached)
These errors show multiple broken links within the Terraform Enterprise API documentation. These links are critical for users trying to understand and use the API. It's essential to update these links to provide accurate and accessible information. The repeated