diff --git a/_config.yml b/_config.yml
index 6493c1f9..fb202fd7 100644
--- a/_config.yml
+++ b/_config.yml
@@ -25,7 +25,7 @@ apis:
   dotnet: https://parseplatform.org/Parse-SDK-dotNET/api/
   flutter: https://parseplatform.org/Parse-SDK-Flutter/flutter/flutter_parse_sdk_flutter/flutter_parse_sdk_flutter-library.html
   dart: https://parseplatform.org/Parse-SDK-Flutter/dart/flutter_parse_sdk/flutter_parse_sdk-library.html
-  parse-server: https://parseplatform.org/parse-server/api/
+  parse-server: https://website.parseplatform.org/parse-server/api/
 
 # Build settings
 markdown: kramdown
diff --git a/_includes/dart/getting-started.md b/_includes/dart/getting-started.md
index 733a9859..2b046a84 100644
--- a/_includes/dart/getting-started.md
+++ b/_includes/dart/getting-started.md
@@ -41,7 +41,7 @@ await Parse().initialize(
 Due to Cross-Origin Resource Sharing (CORS) restrictions, web support requires adding `X-Parse-Installation-Id` as an allowed header in the Parse Server configuration:
 
 - When running directly via docker, set the env var `PARSE_SERVER_ALLOW_HEADERS=X-Parse-Installation-Id`.
-- When running via express, set the [Parse Server option](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) `allowHeaders: ['X-Parse-Installation-Id']`.
+- When running via express, set the [Parse Server option](https://website.parseplatform.org/parse-server/api/master/ParseServerOptions.html) `allowHeaders: ['X-Parse-Installation-Id']`.
 
 ## Desktop Support (macOS)
 
@@ -70,4 +70,4 @@ await Parse().initialize(
   //...
   clientCreator: ({bool? sendSessionId, SecurityContext? securityContext}) => ParseDioClient(sendSessionId: sendSessionId, securityContext: securityContext),
 );
-```
\ No newline at end of file
+```
diff --git a/_includes/flutter/getting-started.md b/_includes/flutter/getting-started.md
index 965cde54..f971f613 100644
--- a/_includes/flutter/getting-started.md
+++ b/_includes/flutter/getting-started.md
@@ -41,7 +41,7 @@ await Parse().initialize(
 Due to Cross-Origin Resource Sharing (CORS) restrictions, web support requires adding `X-Parse-Installation-Id` as an allowed header in the Parse Server configuration:
 
 - When running directly via docker, set the env var `PARSE_SERVER_ALLOW_HEADERS=X-Parse-Installation-Id`.
-- When running via express, set the [Parse Server option](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) `allowHeaders: ['X-Parse-Installation-Id']`.
+- When running via express, set the [Parse Server option](https://website.parseplatform.org/parse-server/api/master/ParseServerOptions.html) `allowHeaders: ['X-Parse-Installation-Id']`.
 
 ## Desktop Support (macOS)
 
@@ -70,4 +70,4 @@ await Parse().initialize(
   //...
   clientCreator: ({bool? sendSessionId, SecurityContext? securityContext}) => ParseDioClient(sendSessionId: sendSessionId, securityContext: securityContext),
 );
-```
\ No newline at end of file
+```
diff --git a/_includes/graphql/getting-started.md b/_includes/graphql/getting-started.md
index 678373cb..7b54e3a1 100644
--- a/_includes/graphql/getting-started.md
+++ b/_includes/graphql/getting-started.md
@@ -12,7 +12,7 @@ $ parse-server --appId APPLICATION_ID --masterKey MASTER_KEY --databaseURI mongo
 ```
 
 Notes:
-* Run `parse-server --help` or refer to [Parse Server Options](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) for a complete list of Parse Server configuration options.
+* Run `parse-server --help` or refer to [Parse Server Options](https://website.parseplatform.org/parse-server/api/master/ParseServerOptions.html) for a complete list of Parse Server configuration options.
 * ⚠️ Please do not use `--mountPlayground` option in production as anyone could access your API Playground and read or change your application's data. [Parse Dashboard](#running-parse-dashboard) has a built-in GraphQL Playground and it is the recommended option for production apps. If you want to secure your API in production take a look at [Class Level Permissions](/js/guide/#class-level-permissions)
 
 After running the CLI command, you should have something like this in your terminal:
diff --git a/_includes/parse-server/deploying-aws-ubuntu.md b/_includes/parse-server/deploying-aws-ubuntu.md
index 3e969d8d..494bc3ca 100644
--- a/_includes/parse-server/deploying-aws-ubuntu.md
+++ b/_includes/parse-server/deploying-aws-ubuntu.md
@@ -117,7 +117,7 @@ After that, we need to setup the configuration file, use your own `appId`, `mast
 ```bash
 sudo nano -w config.json
 ```
-This are the basic options of the config.json file, for the full list you can type `parse-server --help` or refer to the [full options document](https://parseplatform.org/parse-server/api/5.2.0/ParseServerOptions.html) for more details.
+These are the basic options of the config.json file. For the full list, you can run `parse-server --help` or refer to the [full options document](https://website.parseplatform.org/parse-server/api/5.2.0/ParseServerOptions.html) for more details.
 ```jsonc
 {
   "appId": "exampleAppId",
diff --git a/_includes/parse-server/usage.md b/_includes/parse-server/usage.md
index 370221cb..b9b54326 100644
--- a/_includes/parse-server/usage.md
+++ b/_includes/parse-server/usage.md
@@ -16,7 +16,7 @@ const api = new ParseServer({
 });
 ```
 
-A few of the [Parse Server Options](https://parseplatform.org/parse-server/api/master/ParseServerOptions.html) are as follows:
+A few of the [Parse Server Options](https://website.parseplatform.org/parse-server/api/master/ParseServerOptions.html) are as follows:
 
 * `databaseURI`: Connection string for your database.
 * `cloud`: Path to your app’s Cloud Code.
diff --git a/parse-server-api.md b/parse-server-api.md
index 2a1c5b24..c9436c69 100644
--- a/parse-server-api.md
+++ b/parse-server-api.md
@@ -3,5 +3,5 @@ layout: redirected
 sitemap: false
 permalink: /parse-server/api/
 redirect_to:
-  - https://parseplatform.org/parse-server/api
+  - https://website.parseplatform.org/parse-server/api/
 ---