diff --git a/docs.json b/docs.json
index d5905ad1..5f9adfbd 100644
--- a/docs.json
+++ b/docs.json
@@ -9,6 +9,11 @@
   },
   "favicon": "/favicon.ico",
   "redirects": [
+    {
+      "source": "/public-api/oauth",
+      "destination": "/oauth",
+      "permanent": true
+    },
     {
       "source": "/introduction",
       "destination": "/general/introduction",
@@ -453,7 +458,7 @@
           {
             "group": "OAuth2",
             "pages": [
-              "public-api/oauth"
+              "oauth"
             ]
           }
         ]
diff --git a/general/settings/developers.mdx b/general/settings/developers.mdx
index f05bc7d2..961a700f 100644
--- a/general/settings/developers.mdx
+++ b/general/settings/developers.mdx
@@ -52,7 +52,7 @@ Postiz users will authorise, rather than something that acts as you.
     You get a client ID and a client secret.
   </Step>
   <Step title="Implement the flow">
-    See [OAuth2 for developers](/public-api/oauth).
+    See [OAuth2 for developers](/oauth).
   </Step>
 </Steps>
 
diff --git a/mcp/introduction.mdx b/mcp/introduction.mdx
index db718827..c01905d8 100644
--- a/mcp/introduction.mdx
+++ b/mcp/introduction.mdx
@@ -56,7 +56,7 @@ Use it directly in the MCP endpoint URL, or as a Bearer token.
 
 ### OAuth Token
 
-If you're building an app for other Postiz users, use [OAuth2](/public-api/oauth) to obtain tokens. OAuth tokens start with `pos_` and work the same way as API keys.
+If you're building an app for other Postiz users, use [OAuth2](/oauth) to obtain tokens. OAuth tokens start with `pos_` and work the same way as API keys.
 
 ## Connecting
 
diff --git a/public-api/oauth.mdx b/oauth.mdx
similarity index 100%
rename from public-api/oauth.mdx
rename to oauth.mdx
diff --git a/public-api/introduction.mdx b/public-api/introduction.mdx
index 301824be..3cb57511 100644
--- a/public-api/introduction.mdx
+++ b/public-api/introduction.mdx
@@ -37,7 +37,7 @@ curl -H "Authorization: your-api-key" https://api.postiz.com/public/v1/integrati
 
 ### OAuth2 Token
 
-If you're building an app for other Postiz users, use [OAuth2 Authentication](/public-api/oauth) to get tokens that act on behalf of users. OAuth tokens start with `pos_` and are used the same way:
+If you're building an app for other Postiz users, use [OAuth2 Authentication](/oauth) to get tokens that act on behalf of users. OAuth tokens start with `pos_` and are used the same way:
 
 ```bash
 curl -H "Authorization: pos_your-oauth-token" https://api.postiz.com/public/v1/integrations
diff --git a/scripts/check-docs.mjs b/scripts/check-docs.mjs
index 118c75d3..43b221e6 100644
--- a/scripts/check-docs.mjs
+++ b/scripts/check-docs.mjs
@@ -32,14 +32,15 @@ const tabPrefixes = {
   Cloud: ['cloud/'],
   'Self-Hosting': ['self-host/'],
   'Public API': ['public-api/'],
-  Automation: ['cli/', 'mcp/'],
+  Agents: ['cli/', 'mcp/'],
+  'Add Postiz to your app': ['oauth'],
   Contributing: ['contributing/'],
 };
 
 // Deliberate cross-listings: the URL prefix still decides the audience, this
 // only moves where the page appears in the sidebar.
 //   self-host/cli-auth-server is self-hosting work that only CLI users do, so
-//   it sits in the Automation tab while keeping its /self-host/ URL.
+//   it sits in the Agents tab while keeping its /self-host/ URL.
 const tabPrefixExceptions = new Set(['self-host/cli-auth-server']);
 
 // Pages that are allowed to mention self-hosting mechanics despite living in a