docs: document broken link checker feature in dashboard #2969
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| @@ -0,0 +1,7 @@ | |||
| ## Broken link checker in the dashboard | |||
|
|
|||
| The Fern Dashboard now includes a broken link checker that scans your published documentation for broken links. The checker validates both internal links (links to other pages within your docs) and external links (links to external websites). | |||
Contributor
There was a problem hiding this comment.
[FernStyles.Current] Avoid time-relative terms like 'now' that become outdated
| To check for broken links, open your docs site in the Fern Dashboard and navigate to the **Broken Links** section. The dashboard displays a list of any broken links found, including the page where the link appears and the target URL that failed. | ||
|
|
||
| <Note> | ||
| The dashboard broken link checker is recommended over the CLI's [`fern check --strict-broken-links`](/learn/cli-api/cli-reference/commands#strict-broken-links) option because it checks your live published site and validates external links that the CLI cannot verify. |
Contributor
There was a problem hiding this comment.
🚫 [vale] reported by reviewdog 🐶
[Microsoft.Contractions] Use 'can't' instead of 'cannot'.
Contributor
…ken-link-checker-docs
Contributor
Contributor
Contributor
Contributor
devalog
approved these changes
Jan 6, 2026
Contributor
dannysheridan
approved these changes
Jan 6, 2026
Contributor
| @@ -0,0 +1,5 @@ | |||
| ## Broken link checker | |||
|
|
|||
| The Fern Dashboard now includes a link checker that scans your published documentation for broken links, validating both internal links (links to other pages within your docs) and external links (links to external websites). | |||
Contributor
There was a problem hiding this comment.
[FernStyles.Current] Avoid time-relative terms like 'now' that become outdated
Contributor
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Documents the new broken link checker feature available in the Fern Dashboard. The changes add:
fern check --strict-broken-linksfor comprehensive link checkingThe documentation emphasizes that the dashboard checker is recommended over the CLI because it validates both internal and external links on the live published site.
Review & Testing Checklist for Human
/learn/docs/preview-publish/publishing-your-docs#check-for-broken-linksand/learn/cli-api/cli-reference/commands#strict-broken-linksresolve correctly in the previewSuggested test plan: Open the preview link, navigate to the publishing-your-docs page, and verify the new section renders correctly. Click the internal links to ensure they work. Cross-reference with the actual dashboard to confirm the documentation matches the real feature.
Notes