diff --git a/fern/products/docs/pages/navigation/products.mdx b/fern/products/docs/pages/navigation/products.mdx
index 8960ca8d5..15719ed01 100644
--- a/fern/products/docs/pages/navigation/products.mdx
+++ b/fern/products/docs/pages/navigation/products.mdx
@@ -188,6 +188,8 @@ products:
```
+
+
diff --git a/fern/products/docs/pages/navigation/versions.mdx b/fern/products/docs/pages/navigation/versions.mdx
index ac4d3faa9..db6bd76d1 100644
--- a/fern/products/docs/pages/navigation/versions.mdx
+++ b/fern/products/docs/pages/navigation/versions.mdx
@@ -44,7 +44,7 @@ Version-specific `yml` files:
-Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`.
+Define a version in the top-level `docs.yml` by adding an item to the `versions` list and specifying the `display-name` and `path`.
```yaml
@@ -55,6 +55,9 @@ versions:
path: ./versions/v2.yml
```
+
+
+
diff --git a/fern/snippets/default-version.mdx b/fern/snippets/default-version.mdx
new file mode 100644
index 000000000..a59f45991
--- /dev/null
+++ b/fern/snippets/default-version.mdx
@@ -0,0 +1,6 @@
+
+
+ Versions appear in the version dropdown in the order listed in `versions`. The first version in your `versions` list is your default version. This version uses unversioned paths like `/docs/getting-started`, while other versions use versioned paths like `/docs/getting-started/v2`.
+
+ Fern automatically handles version routing by [redirecting](/docs/seo/redirects) broken versioned links to the default version and managing canonical URLs.
+
\ No newline at end of file
diff --git a/fern/snippets/redirects.mdx b/fern/snippets/redirects.mdx
index 9c3c6a1bb..127f123f2 100644
--- a/fern/snippets/redirects.mdx
+++ b/fern/snippets/redirects.mdx
@@ -1,6 +1,6 @@
The `redirects` object allows you to redirect traffic from one path to another. You can redirect exact paths or use dynamic patterns with [`regex`](https://www.npmjs.com/package/path-to-regexp) parameters like `:slug` to handle bulk redirects. You can redirect to internal paths within your site or external URLs.
-If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include the subpath in both the source and destination paths.
+If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include the subpath in both the source and destination paths.
@@ -38,3 +38,40 @@ If your docs are hosted on a subpath (like `buildwithfern.com/learn`), include t
Toggle between **permanent** and **temporary** redirects (default `false`). When true, the status code is 308. When false, the status code is 307.
+
+### Best practices
+
+For optimal site performance, only add redirects when necessary. Avoid using redirects for behavior that Fern already handles automatically, such as 404 handling and version routing.
+
+
+
+
+Don't create redirects to send broken links to your homepage:
+
+```yaml title="docs.yml"
+redirects:
+ - source: /docs/event-notifications
+ destination: / # Don't do this
+```
+
+Instead, reach out to Fern to enable automatic homepage redirects, an internal setting that handles broken links without needing manual redirects.
+
+
+
+
+If you have [versions](/docs/configuration/versions) configured, your default version uses unversioned paths (`/docs/getting-started`), while other versions use versioned paths (`/docs/getting-started/v2`). Fern automatically handles version routing by redirecting broken versioned links to the default version and managing canonical URLs.
+
+Avoid redirecting from unversioned to versioned URLs:
+
+```yaml title="docs.yml"
+redirects:
+ - source: /docs/event-notifications
+ destination: /docs/event-notifications/v2 # Don't do this
+```
+
+Manually overriding the default versioning behavior can lead to unexpected redirect patterns.
+
+If you frequently need to redirect from the default version to another version, consider changing which version is set as default in your versions configuration.
+
+
+
\ No newline at end of file