diff --git a/scripts/ci/jobs/build-docs.yml b/scripts/ci/jobs/build-docs.yml
index 536a3f9b657efc2eda735517e88e65d9d5f5aa14..6a26f67f6c424a1df063e5aa9c7114f21d355b4d 100644
--- a/scripts/ci/jobs/build-docs.yml
+++ b/scripts/ci/jobs/build-docs.yml
@@ -100,13 +100,14 @@ check docs links:
       --exclude search_opensearch.php
       --exclude eigen.tuxfamily.org
       --exclude wiki.sei.cmu.edu
+      --exclude www.opengeosys.org/project/license
       --exclude-path build/docs/d0/de3/citelist.html
       --exclude-path build/docs/doxygen_crawl.html
       build/docs
-    - lychee --cache --max-cache-age 14d
-      --max-concurrency 2
-      --include gitlab.opengeosys.org/ogs/ogs
-      build/docs
+    # - lychee --cache --max-cache-age 14d
+    #   --max-concurrency 2
+    #   --include gitlab.opengeosys.org/ogs/ogs
+    #   build/docs
   cache:
     paths:
       - .lycheecache
diff --git a/scripts/ci/jobs/build-wheels.yml b/scripts/ci/jobs/build-wheels.yml
index 8617cc2d384a810a77524ef9749af349459bf209..f769602e237a6f40a6ad4f2eb839a07fb999f2a7 100644
--- a/scripts/ci/jobs/build-wheels.yml
+++ b/scripts/ci/jobs/build-wheels.yml
@@ -61,6 +61,7 @@ build wheels win:
     - .vs-environment
   variables:
     SKBUILD_BUILD_OPTIONS: "/m" # TODO not supported yet in scikit-build-core
+  timeout: 10h
   <<: *wheels_template
 
 publish wheels:
diff --git a/scripts/ci/jobs/web-check.yml b/scripts/ci/jobs/web-check.yml
index 769f9401594031966c29dc44de3dc49bbd02b015..2ce21a3e7ac2c8ee47522da4010cf90424a24c3c 100644
--- a/scripts/ci/jobs/web-check.yml
+++ b/scripts/ci/jobs/web-check.yml
@@ -14,7 +14,7 @@ check web links:
     - yarn index
     - HUGO_ENVIRONMENT=lychee hugo
     - lychee --config ./lychee.toml --cache --max-cache-age 2d --threads ${CTEST_PARALLEL_LEVEL:-4} public
-    - lychee --config ./lychee-gitlab.toml --cache --max-cache-age 14d --max-concurrency 2 public
+    # - lychee --config ./lychee-gitlab.toml --cache --max-cache-age 14d --max-concurrency 2 public
   cache:
     paths:
       - web/.lycheecache
diff --git a/web/content/docs/devguide/getting-started/build-configuration/index.md b/web/content/docs/devguide/getting-started/build-configuration/index.md
index 93e4329b13c4c70609524876337c44a8066c8be3..bb825252c8f68856ae9ea98b7667142b3e992642 100644
--- a/web/content/docs/devguide/getting-started/build-configuration/index.md
+++ b/web/content/docs/devguide/getting-started/build-configuration/index.md
@@ -153,7 +153,7 @@ Additionally to
 sudo apt-get install python3 python3-pip
 ```
 
-(from https://www.opengeosys.org/docs/devguide/getting-started/prerequisites/), do
+(from [Set Up Prerequisites]({{< ref "prerequisites.md" >}})), do
 
 ```bash
 sudo apt-get install python3-venv
diff --git a/web/content/docs/tools/getting-started/first_steps/index.md b/web/content/docs/tools/getting-started/first_steps/index.md
index 06ded098424f4e4eb83e83cb24a8bf7baac374b6..5cd21d5e1eb6016ac759e310aa1fad8c182e6d81 100644
--- a/web/content/docs/tools/getting-started/first_steps/index.md
+++ b/web/content/docs/tools/getting-started/first_steps/index.md
@@ -19,7 +19,7 @@ To use a mesh created by SALOME, it must be converted to the Gmsh file format fi
 
 To extract a surface mesh (in order to define appropriate boundary conditions) one can use the tool [ExtractSurface]({{< ref "extract-surface" >}}) for different kinds of 3D meshes. Different tools like [ParaView](https://www.paraview.org/) are suited as well. Care must be taken to make sure that all element types are of dimension `d-1`, where `d` is the dimension of the bulk mesh, and that no degenerated elements are left in the mesh and all nodes are connected appropriately. Furthermore, ensure that the element orders match. In the current version ExtractSurface stores meshes of first order (linear elements), even when the input mesh was of second order (quadratic elements).
 
-Alternatively, the tool [msh2vtu](https://ogs.ogs.xyz/tools/ogstools/user-guide/msh2vtu.html) can be used to convert Gmsh meshes to VTU and to extract boundary meshes directly from physical groups defined in Gmsh.
+Alternatively, the tool [msh2vtu](https://ogstools.opengeosys.org/stable/user-guide/msh2vtu.html) can be used to convert Gmsh meshes to VTU and to extract boundary meshes directly from physical groups defined in Gmsh.
 
 Heterogeneous fields, e.g., for the use as initial conditions, can be easily generated using the [VTUinterface](https://github.com/joergbuchwald/VTUinterface) Python package.
 
diff --git a/web/content/docs/tutorials/advancing-glacier/index.md b/web/content/docs/tutorials/advancing-glacier/index.md
index 640dab99c39d96335d601669a449878e7ac136a7..746184a56ccae91fe59655ce5367b95ce20a6fe7 100644
--- a/web/content/docs/tutorials/advancing-glacier/index.md
+++ b/web/content/docs/tutorials/advancing-glacier/index.md
@@ -52,7 +52,7 @@ source .venv/bin/activate
 pip install ogstools
 ```
 
-More detailed information about the usages and development of ogstools can be found in [ogstools Documentation](https://ogs.ogs.xyz/tools/ogstools/index.html).
+More detailed information about the usages and development of ogstools can be found in [ogstools Documentation](https://ogstools.opengeosys.org/stable/index.html).
 After installation the tool can be applied as described in the first video-tutorial.
 To apply msh2vtu on the mesh_basin.msh the command should look like: