diff --git a/.github/workflows/validate-external-links.yml b/.github/workflows/validate-external-links.yml
index 7d55371cc..9f011834b 100644
--- a/.github/workflows/validate-external-links.yml
+++ b/.github/workflows/validate-external-links.yml
@@ -18,7 +18,7 @@ jobs:
         uses: lycheeverse/lychee-action@v2
         with:
           fail: false
-          args: --retry-wait-time 10 --max-retries 3 --timeout 30 --accept=200,403,429,408 -s "https"  "**/*.html" "**/*.md" "**/*.txt" "**/*.json" --exclude "https://github.com/\[your*" --exclude "https://localhost:9200"
+          args: --retry-wait-time 10 --max-retries 3 --timeout 30 --accept=200,403,429,408 -s "https" "**/*.html" "**/*.md" "**/*.txt" "**/*.json" --exclude "https://github.com/\[your*" --exclude "https://localhost:9200" --exclude-path '(^|/)resources/guidelines/code/core(/|$)'
 
       - name: Find Link Checker Issue
         uses: micalevisk/last-issue-action@v2
diff --git a/guides/development/extensions/architecture/extendability.md b/guides/development/extensions/architecture/extendability.md
index c9e9e8af2..fe9ef5430 100644
--- a/guides/development/extensions/architecture/extendability.md
+++ b/guides/development/extensions/architecture/extendability.md
@@ -90,7 +90,7 @@ The best-known example is the [`checkout.order.placed`](https://github.com/shopw
 
 #### Hooks
 
-Hooks are another good example of the observer pattern. Hooks are entry points for apps where the so-called [**App scripts**](/docs/guides/plugins/apps/app-scripts/) are enabled. Since apps do not have the permission to execute code on the server directly, hooks are a way to execute more complex business logic within the request without having to address the own app server via HTTP. Hooks are the equivalent of **events**.
+Hooks are another good example of the observer pattern. Hooks are entry points for apps where the so-called [**App scripts**](../../../plugins/apps/app-scripts/) are enabled. Since apps do not have the permission to execute code on the server directly, hooks are a way to execute more complex business logic within the request without having to address the own app server via HTTP. Hooks are the equivalent of **events**.
 
 One of the best-known hooks is the [`product page loaded hook`](https://github.com/shopware/shopware/blob/v6.4.12.0/src/Storefront/Page/Product/ProductPageLoadedHook.php). This hook allows apps to load additional data on the product detail page. The hook is instantiated and dispatched [at the controller level](https://github.com/shopware/shopware/blob/v6.4.12.0/src/Storefront/Controller/ProductController.php#L100). Each app script registered to the hook is executed.
 
diff --git a/guides/development/monetization/quality-guidelines.md b/guides/development/monetization/quality-guidelines.md
index 09b523c6e..64d9fd761 100644
--- a/guides/development/monetization/quality-guidelines.md
+++ b/guides/development/monetization/quality-guidelines.md
@@ -312,7 +312,7 @@ Use Scheme.org's [Schema Markup Validator](https://validator.schema.org/) and Go
 
 ## Tools
 
-Use the [Shopware CLI](/development/tooling/cli) to build, validate, and upload Shopware 6 plugin releases to the Community Store. It also supports efficiently managing store descriptions and plugin images.
+Use the [Shopware CLI](../../../products/cli/) to build, validate, and upload Shopware 6 plugin releases to the Community Store. It also supports efficiently managing store descriptions and plugin images.
 
 ## Final notes
 
diff --git a/products/cli/command-types.md b/products/cli/command-types.md
index 4e647c40a..e3fbddf43 100644
--- a/products/cli/command-types.md
+++ b/products/cli/command-types.md
@@ -31,7 +31,7 @@ shopware-cli extension fix /path/to/your/extension
 shopware-cli project fix /path/to/your/project
 ```
 
-Always back up or version your code before running refactoring commands, as they will modify files in place. [Learn more here](../../products/cli/automatic-refactoring.md).
+Always back up or version your code before running refactoring commands, as they will modify files in place. [Learn more here](automatic-refactoring.md).
 
 ### Project commands
 
diff --git a/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md b/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
index 079c02c03..9c519fc75 100644
--- a/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
+++ b/products/extensions/advanced-search/How-to-define-your-custom-Elasticsearch-definition.md
@@ -9,7 +9,7 @@ nav:
 
 In the previous implementation, the Elasticsearch index was language-based, meaning each system's language would be indexed in a separate index. With the introduction of the multilingual index:
 
-Each index will contain multiple language-based fields; refer to the [ADR](/docs/resources/references/adr/2023-04-11-new-language-inheritance-mechanism-for-opensearch) and adjust your custom Elasticsearch definition's configuration mapping to adapt to the new mapping structure.
+Each index will contain multiple language-based fields; refer to the [ADR](../../../resources/references/adr/2023-04-11-new-language-inheritance-mechanism-for-opensearch) and adjust your custom Elasticsearch definition's configuration mapping to adapt to the new mapping structure.
 
 For instance, to define your custom Elasticsearch definition (this definition will be used for later examples).
 
@@ -78,7 +78,7 @@ class YourCustomElasticsearchDefinition extends AbstractElasticsearchDefinition
     }
 
     /**
-     * Build a bool query when searching your custom ES definition, by default we use the Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic  
+     * Build a bool query when searching your custom ES definition, by default we use the Shopware\Commercial\AdvancedSearch\Domain\Search\SearchLogic
      */
     public function buildTermQuery(Context $context, Criteria $criteria): BoolQuery
     {
@@ -86,7 +86,7 @@ class YourCustomElasticsearchDefinition extends AbstractElasticsearchDefinition
     }
 
     /**
-    * fetch data from storage to push to elasticsearch cluster when indexing data 
+    * fetch data from storage to push to elasticsearch cluster when indexing data
     */
     public function fetch(array $ids, Context $context): array
     {