diff --git a/backend/semrush-replace-url/index.content.js b/backend/semrush-replace-url/index.content.js
index 9ca253d623..c090211221 100644
--- a/backend/semrush-replace-url/index.content.js
+++ b/backend/semrush-replace-url/index.content.js
@@ -51,10 +51,10 @@ async function processFile(filePath, redirects) {
 
 		for (const item of redirects) {
 			const pagePermalink = item.page.replace(wwwazioncom, '').replace('/pt-br', '').replace('/en', '')
-			const url30x = item.initialUrl === wwwazioncom ? wwwazioncom : item.initialUrl // add .replace(wwwazioncom, '') to find permalinks only
-			const url200 = item.destinationUrl // add .replace(wwwazioncom, '') to find permalinks only
+			const url30x = item.initialUrl === wwwazioncom ? wwwazioncom : item.initialUrl.replace(wwwazioncom, '') // add .replace(wwwazioncom, '') to find permalinks only
+			const url200 = item.destinationUrl.replace(wwwazioncom, '') // add .replace(wwwazioncom, '') to find permalinks only
 			const isRoot = url30x === wwwazioncom
-			const rgx = new RegExp(`\\(${url30x}\\)`, 'g')
+			const rgx = new RegExp(`\\(${url30x}\\#`, 'g')
 			const contentMatch = utf8Content.match(rgx)
 
 			if(!contentMatch) continue
@@ -73,10 +73,10 @@ async function processFile(filePath, redirects) {
 			processedCount: ${counterFoundLinks}
 			}`)
 
-			const newContent = findReplace(utf8Content, isRoot ? /\\(https\:\/\/www\.azion\.com\/\\)/ : rgx, `(${url200})`)
+			const newContent = findReplace(utf8Content, isRoot ? /\\(https\:\/\/www\.azion\.com\/\\)/ : rgx, `(${url200}#`)
 			await fs.writeFile(filePath, newContent, async (err) => {
 				if(err) throw err
-				console.log(`[OK] ${filePath} updated`)
+				// console.log(`[OK] ${filePath} updated`)
 			})
 		}
 	})
diff --git a/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx b/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx
index b06ee2f4fa..870e31e327 100644
--- a/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx
+++ b/src/content/docs/en/pages/architectures/edge-firewall/waap-architecture.mdx
@@ -78,7 +78,7 @@ This solution is ideal for organizations looking to safeguard their digital infr
 - [Create rules in Rules Engine for Edge Firewall](/en/documentation/products/guides/secure/work-with-rules-engine/).
     - Configure the Set WAF Rule Set behavior.
     - Configure the Network criteria.
-    - Configure the [Request URI](/en/documentation/products/guides/bot-manager/#setting-up-the-rules-engine) criteria.
+    - Configure the [Request URI](/en/documentation/products/guides/bot-manager-lite/#setting-up-the-rules-engine) criteria.
 
 ---
 
diff --git a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-main-settings/main-settings.mdx b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-main-settings/main-settings.mdx
index be8ae93851..6b7f5c91c6 100644
--- a/src/content/docs/en/pages/build-journey/edit-edge-app/edit-main-settings/main-settings.mdx
+++ b/src/content/docs/en/pages/build-journey/edit-edge-app/edit-main-settings/main-settings.mdx
@@ -36,7 +36,7 @@ Don't have an edge application? [Start with a template](/en/documentation/produc
 
         **Delivery protocols**
 
-        Modify your application to support the available [delivery protocols](/en/documentation/products/edge-application/build/main-settings/#delivery-protocols).
+        Modify your application to support the available [delivery protocols](/en/documentation/products/build/edge-application/main-settings/#delivery-protocols).
 
         1. Go to the **Main Settings** tab.
         2. Under **Protocol Usage**, select **HTTP support**.
@@ -56,7 +56,7 @@ Don't have an edge application? [Start with a template](/en/documentation/produc
 
         **Delivery ports**
 
-        Choose between the supported [delivery ports](/en/documentation/products/edge-application/build/main-settings/#ports) for each protocol selected.
+        Choose between the supported [delivery ports](/en/documentation/products/build/edge-application/main-settings/#ports) for each protocol selected.
 
         1. Go to the **Main Settings** tab.
         2. Under **HTTP Ports**, in addition to port `80`, select port `8008`.
@@ -106,7 +106,7 @@ Don't have an edge application? [Start with a template](/en/documentation/produc
 
         **Delivery protocols**
 
-        Modify your application to support the available [delivery protocols](/en/documentation/products/edge-application/build/main-settings/#delivery-protocols).
+        Modify your application to support the available [delivery protocols](/en/documentation/products/build/edge-application/main-settings/#delivery-protocols).
 
         1. Go to the **Main Settings** tab.
         2. Under **Delivery Protocol**, select **HTTP**.
@@ -126,7 +126,7 @@ Don't have an edge application? [Start with a template](/en/documentation/produc
 
         **Delivery ports**
 
-        Choose between the supported [delivery ports](/en/documentation/products/edge-application/build/main-settings/#ports) for each protocol selected.
+        Choose between the supported [delivery ports](/en/documentation/products/build/edge-application/main-settings/#ports) for each protocol selected.
 
         1. Go to the **Main Settings** tab.
         2. Under **Ports HTTP**, in addition to port `80`, select port `8008`.
diff --git a/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx b/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx
index 95073b2393..e989165cfd 100644
--- a/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx
+++ b/src/content/docs/en/pages/guides/marketplace/templates/azion-starter-kit.mdx
@@ -61,7 +61,7 @@ Fields identified with an asterisk are mandatory.
 - **Origin Address** *: the address of the hosted origin the edge application should fetch the content from.
     - Example: `www.yourwebsite.com`
 - **Custom Host Header**: in some cases, it may be necessary to add host information in the header request to retrieve information from the origin. This variable is used for that purpose.
-    - Example: `${host}`. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/edge-application/origins/#host-header) documentation.
+    - Example: `${host}`. Read more about the host header and how to customize it on the [Origins](/en/documentation/products/build/edge-application/origins/#host-header) documentation.
 
 After completing all the information, click the **Deploy** button, located in the bottom-right corner. This will start the deployment process.
 
diff --git a/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx b/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx
index f30f0fb20f..46baf13aa4 100644
--- a/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx
+++ b/src/content/docs/en/pages/guides/marketplace/templates/dynamic-and-static-file-optimization.mdx
@@ -88,7 +88,7 @@ Now you can [manage and adjust the settings](#managing-the-template) through Azi
 The deployed edge application includes the following rules and settings:
 
 - **Criteria**: if `${uri}` *starts with* `/`.
-- **Behavior**: then [Set Origin](/en/documentation/products/edge-application/rules-engine/#set-origin) as `Default Origin`.
+- **Behavior**: then [Set Origin](/en/documentation/products/build/edge-application/rules-engine/#set-origin) as `Default Origin`.
 - For image optimization and caching, the file extensions that can be enhanced with these configurations are `.jpg`, `.jpeg`, `.bmp`, `.ico`, `.gif`, `.png`. 
 - For static content, the template supports the common static file extensions. 
 - Additionally, the template:
diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/digital-certificates.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/digital-certificates.mdx
index a70dd02ea0..1ada5a6c3b 100644
--- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/digital-certificates.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/digital-certificates.mdx
@@ -81,7 +81,7 @@ A Trusted CA is an entity that is authorized to issue digital certificates that
 
 [Let's Encrypt](https://letsencrypt.org/)™ is a nonprofit global CA that allows people and organizations to obtain, renew, and manage TLS certificates for free. When [creating a Domain](/en/documentation/products/build/edge-application/domains/) with Azion, you may choose to obtain a TLS certificate signed by Let's Encrypt. You can request Let's Encrypt certificates for domains hosted in [Edge DNS](/en/documentation/products/secure/edge-dns/) or in a third-party DNS provider.
 
-Once you [create a domain with Azion](/en/documentation/products/getting-started/#step-4-creating-a-new-domain-associated-with-your-edge-application), you can choose the option **Let's Encrypt** to automatically generate a Let's Encrypt certificate. An entry for this certificate will be listed in the **Digital Certificates** page in [Azion Console](https://console.azion.com). After the certificate undergoes DNS validation, issuance, and storage, it'll become active.
+Once you [create a domain with Azion](/en/documentation/products/get-started/#step-4-creating-a-new-domain-associated-with-your-edge-application), you can choose the option **Let's Encrypt** to automatically generate a Let's Encrypt certificate. An entry for this certificate will be listed in the **Digital Certificates** page in [Azion Console](https://console.azion.com). After the certificate undergoes DNS validation, issuance, and storage, it'll become active.
 
 > See [How to generate a Let's Encrypt for your domain](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/) to know how to validate this type of certificate.
 
diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx
index f22a0708b1..4838dd165c 100644
--- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/domains/domains.mdx
@@ -20,7 +20,7 @@ You may also bind a **Digital Certificate** to domains that use the HTTPS protoc
 
 | Scope | Resource |
 | --- | --- |
-| Adding a custom domain | [Getting started](/en/documentation/products/getting-started/#step-3-adding-a-custom-domain) |
+| Adding a custom domain | [Getting started](/en/documentation/products/get-started/#step-3-adding-a-custom-domain) |
 | About Digital Certificates | [Digital Certificates](/en/documentation/products/secure/edge-firewall/digital-certificates/) |
 | About mTLS | [mTLS](/en/documentation/products/secure/edge-firewall/mtls/) |
 
diff --git a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx
index f8b6bab914..2d32e906b8 100644
--- a/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/build/edge-application/edge-caching.mdx
@@ -55,7 +55,7 @@ Find out more about how to automate your browser to obtain other cache data in t
 | **STALE** | When choosing to serve [stale cache](#stale-cache), if the origin fails to respond and the edge cache has expired, a stale version of the content is served |
 | **UPDATING** | The cached content has expired and a stale cache is being served, but the content is being updated in the origin |
 | **REVALIDATED** | The cached content is checked against the origin using conditional headers. If it's still up-to-date, the resource is not retransmitted from the origin |
-| **BYPASS** | The edge requests the content from the origin directly instead of using a cached version due to the active [Bypass Cache](/en/documentation/products/edge-application/rules-engine/#bypass-cache) behavior |
+| **BYPASS** | The edge requests the content from the origin directly instead of using a cached version due to the active [Bypass Cache](/en/documentation/products/build/edge-application/rules-engine/#bypass-cache) behavior |
 | **-** | If no status is received, the content requested is restricted from caching. For instance, if the requested content is a `POST` request and [Caching for POST](/en/documentation/products/build/edge-application/cache-settings/#caching-http-methods) is disabled, the status is not logged |
 
 ---
diff --git a/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx b/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx
index 9451b77b04..4a3c43aa4f 100644
--- a/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/observe/data-stream/data-stream.mdx
@@ -245,7 +245,7 @@ By selecting one of the templates provided by Azion, you can't modify the variab
 
 ## Domains
 
-You can associate your [existing domains](/en/documentation/products/build/edge-application/domains/) registered on Azion to your stream. If you haven't registered any domains to your account yet, see the [Creating a new domain associated with your edge application](/en/documentation/products/getting-started/#step-3-adding-a-custom-domain) documentation.
+You can associate your [existing domains](/en/documentation/products/build/edge-application/domains/) registered on Azion to your stream. If you haven't registered any domains to your account yet, see the [Creating a new domain associated with your edge application](/en/documentation/products/get-started/#step-3-adding-a-custom-domain) documentation.
 
 When you associate a domain, the events related with that or those specific domains are collected and sent to the endpoint you configure through a Data Stream. You can associate one or more domains and you have the option to **Filter Domains** or select **All Domains**.
 
diff --git a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx
index 2ea9506d01..876caf59b7 100644
--- a/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx
+++ b/src/content/docs/en/pages/main-menu/reference/secure/edge-firewall/digital-certificates.mdx
@@ -84,7 +84,7 @@ A Trusted CA is an entity that is authorized to issue digital certificates that
 
 <LetsEncryptExpiration />
 
-Once you [create a domain with Azion](/en/documentation/products/getting-started/#step-4-creating-a-new-domain-associated-with-your-edge-application), you can choose the option **Let's Encrypt** to automatically generate a Let's Encrypt certificate. An entry for this certificate will be listed in the **Digital Certificates** page in [Azion Console](https://console.azion.com). After the certificate undergoes DNS validation, issuance, and storage, it'll become active.
+Once you [create a domain with Azion](/en/documentation/products/get-started/#step-4-creating-a-new-domain-associated-with-your-edge-application), you can choose the option **Let's Encrypt** to automatically generate a Let's Encrypt certificate. An entry for this certificate will be listed in the **Digital Certificates** page in [Azion Console](https://console.azion.com). After the certificate undergoes DNS validation, issuance, and storage, it'll become active.
 
 > See [How to generate a Let's Encrypt for your domain](/en/documentation/products/guides/how-to-generate-a-lets-encrypt-certificate/) to know how to validate this type of certificate.
 
diff --git a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx
index 6dc949a000..fd13aafad5 100644
--- a/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx
+++ b/src/content/docs/en/pages/secure-journey/firewall-advanced-configurations/manage-bots.mdx
@@ -69,7 +69,7 @@ You can query the [Bot Manager dataset](/en/documentation/products/guides/query-
 
 ### Use Data Stream as observability tool
 
-To set up an edge function, follow the steps in [Setting up the function](/en/documentation/products/guides/bot-manager/#setting-up-the-function).
+To set up an edge function, follow the steps in [Setting up the function](/en/documentation/products/guides/bot-manager-lite/#setting-up-the-function).
 
 Then, you can use [Data Stream](/en/documentation/products/observe/data-stream/) to integrate with stream processing, SIEM, and big data platforms by using the **Edge Functions** source and the **Edge Functions Event Collector** template. This way, you can send your logs to the connector you use and monitor Bot Manager events.
 <br /><br />
diff --git a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx
index 6982376fd9..889598c8b7 100644
--- a/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx
+++ b/src/content/docs/pt-br/pages/arquiteturas/edge-firewall/waap-arquitetura.mdx
@@ -80,7 +80,7 @@ Esta solução é ideal para organizações que buscam proteger sua infraestrutu
 - [Crie regras no Rules Engine do Edge Firewall](/pt-br/documentacao/produtos/guias/secure/trabalhar-com-rules-engine/).
     - Configure o comportamento **Set WAF Rule Set**.
     - Configure os critérios de rede.
-    - Configure os critérios de [Request URI](/pt-br/documentacao/produtos/guias/bot-manager/#configure-o-rules-engine).
+    - Configure os critérios de [Request URI](/pt-br/documentacao/produtos/guias/bot-manager-lite/#configure-o-rules-engine).
 
 ## Documentação relacionada
 
diff --git a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/main-settings.mdx b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/main-settings.mdx
index 43fd82db0d..e77c267929 100644
--- a/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/main-settings.mdx
+++ b/src/content/docs/pt-br/pages/build-jornada/edite-edge-app/main-settings.mdx
@@ -40,7 +40,7 @@ Ainda não tem uma edge application? [Comece com um template](/pt-br/documentaca
 
     **Delivery protocols**
 
-    Modifique sua aplicação para suportar os [protocolos de entrega](/pt-br/documentacao/produtos/edge-application/main-settings/#protocolos-de-entrega) disponíveis.
+    Modifique sua aplicação para suportar os [protocolos de entrega](/pt-br/documentacao/produtos/build/edge-application/main-settings/#protocolos-de-entrega) disponíveis.
 
     1. Vá para a aba **Main Settings**.
     2. Em **Protocol Usage**, selecione **HTTP support**.
@@ -60,7 +60,7 @@ Ainda não tem uma edge application? [Comece com um template](/pt-br/documentaca
 
     **Delivery ports**
 
-    Escolha entre as [portas de entrega](/pt-br/documentacao/produtos/edge-application/main-settings/#portas) suportadas para cada protocolo selecionado.
+    Escolha entre as [portas de entrega](/pt-br/documentacao/produtos/build/edge-application/main-settings/#portas) suportadas para cada protocolo selecionado.
 
     1. Vá para a aba **Main Settings**.
     2. Em **HTTP Ports**, além da porta `80`, selecione a porta `8008`.
@@ -110,7 +110,7 @@ Ainda não tem uma edge application? [Comece com um template](/pt-br/documentaca
 
     **Delivery protocols**
 
-    Modifique sua aplicação para suportar os [protocolos de entrega](/pt-br/documentacao/produtos/edge-application/main-settings/#protocolos-de-entrega) disponíveis.
+    Modifique sua aplicação para suportar os [protocolos de entrega](/pt-br/documentacao/produtos/build/edge-application/main-settings/#protocolos-de-entrega) disponíveis.
 
     1. Vá para a aba **Main Settings**.
     2. Em **Delivery Protocol**, selecione **HTTP**.
@@ -130,7 +130,7 @@ Ainda não tem uma edge application? [Comece com um template](/pt-br/documentaca
 
     **Delivery ports**
 
-    Escolha entre as [portas de entrega](/pt-br/documentacao/produtos/edge-application/main-settings/#portas) suportadas para cada protocolo selecionado.
+    Escolha entre as [portas de entrega](/pt-br/documentacao/produtos/build/edge-application/main-settings/#portas) suportadas para cada protocolo selecionado.
 
     1. Vá para a aba **Main Settings**.
     2. Em **HTTP Ports**, além da porta `80`, selecione a porta `8008`.
diff --git a/src/content/docs/pt-br/pages/menu-principal/referencia/store/edge-storage/index.mdx b/src/content/docs/pt-br/pages/menu-principal/referencia/store/edge-storage/index.mdx
index 188203f01a..fd55bc5b57 100644
--- a/src/content/docs/pt-br/pages/menu-principal/referencia/store/edge-storage/index.mdx
+++ b/src/content/docs/pt-br/pages/menu-principal/referencia/store/edge-storage/index.mdx
@@ -82,7 +82,7 @@ O upload de um objeto diferente ou a modificação do conteúdo do objeto usando
 
 ### Origem
 
-Com **Edge Storage**, você pode usar buckets como uma [origin](/pt-br/documentacao/produtos/edge-application/origins/#edge-storage) na **Edge Application** da Azion para retirar o conteúdo de uma edge application.
+Com **Edge Storage**, você pode usar buckets como uma [origin](/pt-br/documentacao/produtos/build/edge-application/origins/#edge-storage) na **Edge Application** da Azion para retirar o conteúdo de uma edge application.
 
 Você pode determinar se o conteúdo é retirado da raiz do bucket ou de um prefix dentro do bucket.