Fix redirected links

stefano-ottolenghi · stefano-ottolenghi · commit 857a1c911dce · 2025-07-04T08:36:27.000+02:00
diff --git a/modules/ROOT/pages/appendix/gql-conformance/unsupported-mandatory.adoc b/modules/ROOT/pages/appendix/gql-conformance/unsupported-mandatory.adoc
@@ -28,7 +28,7 @@ Neo4j offers session management through the link:{neo4j-docs-base-uri}/create-ap
 | GQL defines the following transaction commands: `START TRANSACTION`, `COMMIT`, and `ROLLBACK`.
 
 Neo4j offers transaction management through the link:{neo4j-docs-base-uri}/create-applications[driver] transaction API.
-Cypher Shell also offers specific link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell/#cypher-shell-commands[commands] to manage transactions.
+Cypher Shell also offers specific link:{neo4j-docs-base-uri}/operations-manual/current/cypher-shell/#cypher-shell-commands[commands] to manage transactions.
 
 | 11.1
 | Graph expressions
diff --git a/modules/ROOT/pages/clauses/delete.adoc b/modules/ROOT/pages/clauses/delete.adoc
@@ -120,7 +120,7 @@ Deleted 1 node, deleted 1 relationship
 [NOTE]
 ====
 The `DETACH DELETE` clause may not be permitted to users with restricted security privileges. 
-For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/access-control#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/tutorial/access-control/#detach-delete-restricted-user[Operations Manual -> Fine-grained access control].
 ====
 
 
diff --git a/modules/ROOT/pages/clauses/load-csv.adoc b/modules/ROOT/pages/clauses/load-csv.adoc
@@ -70,10 +70,10 @@ Added 4 nodes, Set 8 properties, Added 4 labels
 ====
 
 [NOTE]
-For ways of importing data into an Aura instance, see link:https://neo4j.com/docs/aura/auradb/importing/importing-data/[Aura -> Importing data].
+For ways of importing data into an Aura instance, see link:https://neo4j.com/docs/aura/classic/auradb/importing/importing-data/[Aura -> Importing data].
 
 [TIP]
-When using `+file:///+` URLs, spaces and other non-alphanumeric characters must be link:https://developer.mozilla.org/en-US/docs/Glossary/percent-encoding[URL-encoded].
+When using `+file:///+` URLs, spaces and other non-alphanumeric characters must be link:https://developer.mozilla.org/en-US/docs/Glossary/Percent-encoding[URL-encoded].
 
 
 ==== Configuration settings for file URLs
@@ -369,7 +369,7 @@ You can't load zipped CSV files from remote URLs.
 === Import data from relational databases
 
 If the source data comes from a relational model, it's worth evaluating how to gain the most from moving to a graph data model.
-Before running the import, think about how the data can be modeled as a graph, and adapt its structure accordingly when running the import (see link:https://neo4j.com/docs/getting-started/data-modeling/guide-data-modeling/[Graph data modeling]).
+Before running the import, think about how the data can be modeled as a graph, and adapt its structure accordingly when running the import (see link:https://neo4j.com/docs/getting-started/data-modeling/tutorial-data-modeling/[Graph data modeling]).
 
 Data from relational databases may consist of one or multiple CSV files, depending on the source database structure.
 A performant approach is to run multiple passes of `LOAD CSV` to import nodes separately from relationships.
@@ -1168,7 +1168,7 @@ With increasing amounts of data, it is more efficient to create _all_ nodes firs
 
 There are a few other tools to get CSV data into Neo4j.
 
-1. *The link:{neo4j-docs-base-uri}/operations-manual/current/tools/neo4j-admin/neo4j-admin-import/[`neo4j-admin database import`] command* is the most efficient way of importing large CSV files.
+1. *The link:{neo4j-docs-base-uri}/operations-manual/current/import/[`neo4j-admin database import`] command* is the most efficient way of importing large CSV files.
 2. Use a link:https://neo4j.com/docs/create-applications/[*language library*] to parse CSV data and run creation Cypher queries against a Neo4j database.
 Created as an extension library to provide common procedures and functions to developers.
 This library is especially helpful for complex transformations and data manipulations.
diff --git a/modules/ROOT/pages/functions/aggregating.adoc b/modules/ROOT/pages/functions/aggregating.adoc
@@ -10,7 +10,7 @@ Aggregation can be computed over all the matching paths, or it can be further di
 
 [TIP]
 ====
-To learn more about how Cypher handles aggregations performed on zero rows, refer to link:https://neo4j.com/developer/kb/understanding-aggregations-on-zero-rows//[Neo4j Knowledge Base -> Understanding aggregations on zero rows].
+To learn more about how Cypher handles aggregations performed on zero rows, refer to link:https://neo4j.com/developer/kb/understanding-aggregations-on-zero-rows/[Neo4j Knowledge Base -> Understanding aggregations on zero rows].
 ====
 
 == Example graph
diff --git a/modules/ROOT/pages/functions/graph.adoc b/modules/ROOT/pages/functions/graph.adoc
@@ -16,7 +16,7 @@
 
 .Considerations
 |===
-| `graph.names()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/composite-databases[composite databases].
+| `graph.names()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite databases].
 |===
 
 .+graph.names()+
@@ -71,7 +71,7 @@ The names of all graphs on the current composite database are returned.
 
 .Considerations
 |===
-| `graph.propertiesByName()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/composite-databases[composite databases].
+| `graph.propertiesByName()` is only supported on link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite databases].
 | The properties in the returned `MAP` are set on the link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/aliases/manage-aliases-standard-databases/[alias]that adds the graph as a constituent of a composite database.
 |===
 
diff --git a/modules/ROOT/pages/genai-integrations.adoc b/modules/ROOT/pages/genai-integrations.adoc
@@ -39,7 +39,7 @@ The graph contains 28863 nodes and 332522 relationships.
 There are 9083 `Movie` nodes with a `plot` and `title` property.
 
 To recreate the graph, download and import this link:https://github.com/neo4j-graph-examples/recommendations/raw/main/data/recommendations-embeddings-50.dump[dump file] to an empty Neo4j database (running version 5.17 or later).
-Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
+Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/classic/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
 
 [NOTE]
 The embeddings on this are generated using link:https://platform.openai.com/docs/guides/embeddings[OpenAI] (model `text-embedding-ada-002`), producing 1536-dimensional vectors.
@@ -221,7 +221,7 @@ Each provider has its own configuration map that can be passed to `genai.vector.
 === Vertex AI
 
 * Identifier (`provider` argument): `"VertexAI"`
-* https://cloud.google.com/vertex-ai/docs/generative-ai/embeddings/get-text-embeddings[Official Vertex AI documentation]
+* https://cloud.google.com/vertex-ai/generative-ai/docs/embeddings/get-text-embeddings[Official Vertex AI documentation]
 
 .Configuration map
 [%header,cols="1m,1m,3a,2"]
@@ -338,7 +338,7 @@ Supported values: +
 === Azure OpenAI
 
 * Identifier (`provider` argument): `"AzureOpenAI"`
-* https://learn.microsoft.com/en-us/azure/ai-services/openai/[Official Azure OpenAI documentation]
+* https://learn.microsoft.com/en-us/azure/ai-foundry/[Official Azure OpenAI documentation]
 
 [NOTE]
 Unlike the other providers, the model is configured when creating the deployment on Azure, and is thus not part of the configuration map.
diff --git a/modules/ROOT/pages/indexes/search-performance-indexes/using-indexes.adoc b/modules/ROOT/pages/indexes/search-performance-indexes/using-indexes.adoc
@@ -28,7 +28,7 @@ image::using_indexes_example_graph.svg[width="600",role="middle"]
 In total, the graph contains 69165 nodes (of which 188 have the label `PointOfInterest`) and 152077 `ROUTE` relationships.
 
 To recreate the graph, download and import the link:https://github.com/neo4j-graph-examples/openstreetmap/raw/main/data/openstreetmap-50.dump[5.0 dump file] to an empty Neo4j database.
-Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
+Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/classic/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
 
 [[token-lookup-indexes]]
 == Token lookup indexes
diff --git a/modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc b/modules/ROOT/pages/indexes/semantic-indexes/full-text-indexes.adoc
@@ -391,7 +391,7 @@ The procedures for full-text indexes are listed in the table below:
 * Full-text indexes can be queried using the Lucene query language.
 * Full-text indexes are kept up to date automatically, as nodes and relationships are added, removed, and modified.
 * Full-text indexes will automatically populate newly created indexes with the existing data in a store.
-* Full-text indexes can be checked by the link:{neo4j-docs-base-uri}/operations-manual/current/tools/neo4j-admin/consistency-checker[consistency checker], and they can be rebuilt if there is a problem with them.
+* Full-text indexes can be checked by the link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/consistency-checker/[consistency checker], and they can be rebuilt if there is a problem with them.
 * Newly created full-text indexes get automatically populated with the existing data in the database.
 * Full-text indexes can support any number of properties in a single index.
 * Full-text indexes are created, dropped, and updated transactionally, and are automatically replicated throughout a cluster.
diff --git a/modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc b/modules/ROOT/pages/indexes/semantic-indexes/vector-indexes.adoc
@@ -17,7 +17,7 @@ The following resources provide hands-on tutorials for working with LLMs and vec
 * link:https://neo4j.com/docs/genai/tutorials/embeddings-vector-indexes/[GenAI documentation -> Embeddings & Vector Indexes Tutorial]
 
 Neo4j vector indexes are powered by the link:https://lucene.apache.org/[Apache Lucene] indexing and search library.footnote:[Lucene implements a Hierarchical Navigable Small World (HNSW) Graph to perform a k approximate nearest neighbors (k-ANN) query over the vector fields.
-For more information, see link:http://dx.doi.org/10.1109/TPAMI.2018.2889473[Efficient and Robust Approximate Nearest Neighbor Search Using Hierarchical Navigable Small World Graphs] -- Yury A. Malkov and Dmitry A. Yashunin]
+For more information, see link:https://ieeexplore.ieee.org/document/8594636/[Efficient and Robust Approximate Nearest Neighbor Search Using Hierarchical Navigable Small World Graphs] -- Yury A. Malkov and Dmitry A. Yashunin]
 
 [[example-graph]]
 == Example graph
@@ -30,7 +30,7 @@ image::vector_index_graph.svg[width="600",role="middle"]
 The graph contains 28863 nodes and 332522 relationships.
 
 To recreate the graph, download and import this link:https://github.com/neo4j-graph-examples/recommendations/raw/main/data/recommendations-embeddings-50.dump[dump file] to an empty Neo4j database (running version 5.13 or later).
-Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
+Dump files can be imported for both link:{neo4j-docs-base-uri}/aura/classic/auradb/importing/import-database/[Aura] and link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/[on-prem] instances.
 
 [NOTE]
 The dump file used to load the dataset contains embeddings generated by https://openai.com/[OpenAI], using the model `text-embedding-ada-002`.
diff --git a/modules/ROOT/pages/introduction/cypher-aura.adoc b/modules/ROOT/pages/introduction/cypher-aura.adoc
@@ -17,7 +17,7 @@ AuraDB is available on the following tiers:
 * AuraDB Business Critical
 * AuraDB Virtual Dedicated Cloud
 
-For more information, see link:{neo4j-docs-base-uri}/aura/auradb[Aura docs - Neo4j AuraDB overview].
+For more information, see link:{neo4j-docs-base-uri}/aura/classic/auradb/[Aura docs - Neo4j AuraDB overview].
 
 AuraDS is available on the following tiers:
 
@@ -26,7 +26,7 @@ AuraDS is available on the following tiers:
 * AuraDS Professional
 * AuraDS Enterprise
 
-For more information, see link:{neo4j-docs-base-uri}/aura/aurads[Aura docs - Neo4j AuraDS overview].
+For more information, see link:{neo4j-docs-base-uri}/aura/classic/aurads/[Aura docs - Neo4j AuraDS overview].
 
 == Using Cypher on Aura
 
@@ -42,6 +42,6 @@ For more information, see the link:{neo4j-docs-base-uri}/operations-manual/curre
 
 Each different tier of Aura has a customized version of the Cypher Cheat Sheet which only shows the features of Cypher available for the chosen tier. 
 
-The Cypher Cheat Sheet can be accessed link:{neo4j-docs-base-uri}/cypher-cheat-sheet/current/auradb-enterprise/[here].
+The Cypher Cheat Sheet can be accessed link:{neo4j-docs-base-uri}/cypher-cheat-sheet/5/auradb-enterprise/[here].
 You can select your desired Aura tier and Neo4j version by using the dropdown menus provided.
 Note that the default tier is AuraDB Virtual Dedicated Cloud. 
diff --git a/modules/ROOT/pages/introduction/cypher-neo4j.adoc b/modules/ROOT/pages/introduction/cypher-neo4j.adoc
@@ -55,7 +55,7 @@ Normally there is only one graph within each database, and many administrative c
 Cypher queries executed in a session may declare which graph they apply to, or use a default, given by the session.
 Composite databases can contain multiple graphs, by means of aliases to other databases.
 Queries submitted to composite databases may refer to multiple graphs within the same query.
-For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/composite-databases/[Operations manual -> Composite databases].
+For more information, see link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[Operations manual -> Composite databases].
 
 *Database*:: A database is a storage and retrieval mechanism for collecting data in a defined space on disk and in memory.
 
@@ -121,7 +121,7 @@ For examples of the API, or the commands used to start and commit transactions,
 * For information on using transactions with a Neo4j driver, see _The session API_ in the link:{docs-base-uri}[Neo4j Driver manuals].
 * For information on using transactions over the HTTP API, see the link:{neo4j-docs-base-uri}/http-api/current/transactions[HTTP API documentation -> Run transactions].
 * For information on using transactions within the embedded Core API, see the link:{neo4j-docs-base-uri}/java-reference/current/java-embedded/cypher-java/[Java Reference -> Cypher queries].
-* For information on using transactions within the Neo4j Browser or Cypher-shell, see the link:{neo4j-docs-base-uri}/browser-manual/current/reference-commands/[Neo4j Browser documentation] or the link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell/#cypher-shell-commands[Cypher-shell documentation].
+* For information on using transactions within the Neo4j Browser or Cypher-shell, see the link:{neo4j-docs-base-uri}/browser-manual/current/reference-commands/[Neo4j Browser documentation] or the link:{neo4j-docs-base-uri}/operations-manual/current/cypher-shell/#cypher-shell-commands[Cypher-shell documentation].
 
 When writing procedures or using Neo4j embedded, remember that all iterators returned from an execution result should be either fully exhausted or closed.
 This ensures that the resources bound to them are properly released.
diff --git a/modules/ROOT/pages/introduction/cypher-overview.adoc b/modules/ROOT/pages/introduction/cypher-overview.adoc
@@ -82,4 +82,4 @@ RETURN actor.name
 Neo4j supports the APOC (Awesome Procedures on Cypher) Core library.
 The APOC Core library provides access to user-defined procedures and functions which extend the use of the Cypher query language into areas such as data integration, graph algorithms, and data conversion.
 
-For more details, visit the link:{neo4j-docs-base-uri}/apoc/current[APOC Core page].
+For more details, visit the link:{neo4j-docs-base-uri}/apoc/current/[APOC Core page].
diff --git a/modules/ROOT/pages/planning-and-tuning/execution-plans.adoc b/modules/ROOT/pages/planning-and-tuning/execution-plans.adoc
@@ -91,8 +91,8 @@ MATCH (:Station { name: 'Denmark Hill' })<-[:CALLS_AT]-(d:Stop)
 RETURN count(*)
 ----
 
-This is the resulting execution planfootnote:[The format of the execution plans displayed in this section are those generated when using link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell[Cypher Shell].
-The execution plans generated by link:{neo4j-docs-base-uri}/browser-manual/current[Neo4j Browser] use a different format.]:
+This is the resulting execution planfootnote:[The format of the execution plans displayed in this section are those generated when using link:{neo4j-docs-base-uri}/operations-manual/current/cypher-shell/[Cypher Shell].
+The execution plans generated by link:{neo4j-docs-base-uri}/browser-manual/current/[Neo4j Browser] use a different format.]:
 
 [role="queryplan"]
 ----
diff --git a/modules/ROOT/pages/planning-and-tuning/runtimes/reference.adoc b/modules/ROOT/pages/planning-and-tuning/runtimes/reference.adoc
@@ -27,7 +27,7 @@ For a full list of all available Cypher write clauses, see the xref:clauses/inde
 
 It is not possible to use the parallel runtime if a change has been made to the state of a transaction.
 
-For example, the following transaction (initiated on link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell[Cypher Shell]) will be rolled back, because executing a Cypher query will make changes to the state of a transaction.
+For example, the following transaction (initiated on link:{neo4j-docs-base-uri}/operations-manual/current/cypher-shell/[Cypher Shell]) will be rolled back, because executing a Cypher query will make changes to the state of a transaction.
 
 .Step 1: Initiate a new transaction and change its state by creating a node
 [source, cypher, role=test-skip]
diff --git a/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc b/modules/ROOT/pages/subqueries/subqueries-in-transactions.adoc
@@ -221,7 +221,7 @@ For larger data sets, you might want to use larger batch sizes, such as `10000 R
 [[composite-databases]]
 == Composite databases
 
-As of Neo4j 5.18, `CALL { ... } IN TRANSACTIONS` can be used with link:{neo4j-docs-base-uri}/operations-manual/current/composite-databases[composite databases].
+As of Neo4j 5.18, `CALL { ... } IN TRANSACTIONS` can be used with link:{neo4j-docs-base-uri}/operations-manual/current/database-administration/composite-databases/concepts/[composite databases].
 
 Even though composite databases allow accessing multiple graphs in a single query, only one graph can be modified in a single transaction.
 `CALL { ... } IN TRANSACTIONS` offers a way of constructing queries which modify multiple graphs.
diff --git a/modules/ROOT/pages/syntax/parameters.adoc b/modules/ROOT/pages/syntax/parameters.adoc
@@ -32,7 +32,7 @@ Setting parameters when running a query is dependent on the client environment.
 For example:
 
 * To set a parameter in Cypher Shell use `+:param name => 'Joe'+`.
-  For more information refer to link:{neo4j-docs-base-uri}/operations-manual/current/tools/cypher-shell#cypher-shell-parameters[Operations Manual -> Cypher Shell - Query Parameters].
+  For more information refer to link:{neo4j-docs-base-uri}/operations-manual/current/cypher-shell/#cypher-shell-parameters[Operations Manual -> Cypher Shell - Query Parameters].
 * For Neo4j Browser use the same syntax as Cypher Shell, `+:param name => 'Joe'+`.
 * When using drivers, the syntax is dependent on the language choice.
   See the examples in _Transactions_ in the link:{docs-base-uri}[Neo4j Driver manuals].
diff --git a/modules/ROOT/pages/values-and-types/maps.adoc b/modules/ROOT/pages/values-and-types/maps.adoc
@@ -16,7 +16,7 @@ For information about how the `[]` operator behaves with respect to `null`, see
 == Literal maps
 
 The key names in a map must be literals.
-If returned through an link:{neo4j-docs-base-uri}/http-api/current[HTTP API call], a JSON object will be returned.
+If returned through an link:{neo4j-docs-base-uri}/http-api/current/[HTTP API call], a JSON object will be returned.
 If returned in Java, an object of type `java.util.Map<String,Object>` will be returned.
 
 
