diff --git a/_data/sidebar.yml b/_data/sidebar.yml
index 51f0796b85..597c439e23 100644
--- a/_data/sidebar.yml
+++ b/_data/sidebar.yml
@@ -358,8 +358,6 @@ docs:
         url: /en/reference/services-http.html
       - page: services.xml - processing
         url: /en/reference/services-processing.html
-      - page: services.xml - routing
-        url: /en/reference/services-routing.html
       - page: services.xml - search
         url: /en/reference/services-search.html
       - page: hosts.xml
diff --git a/en/operations-selfhosted/routing.html b/en/operations-selfhosted/routing.html
index 4839052425..f3f8286643 100644
--- a/en/operations-selfhosted/routing.html
+++ b/en/operations-selfhosted/routing.html
@@ -4,6 +4,7 @@
 redirect_from:
 - /documentation/routing.html
 - /en/routing.html
+- /en/reference/services-routing.html
 ---
 
 <p>
@@ -17,11 +18,11 @@
 <p>There are other, more in-depth, articles on routing:
 <ul>
   <li>
-    Use <a href="reference/vespa-cmdline-tools.html#vespa-route">vespa-route</a>
+    Use <a href="/en/reference/vespa-cmdline-tools.html#vespa-route">vespa-route</a>
     to inspect routes and services of a Vespa application, like in the
     <a href="#example-reconfigure-the-default-route">example</a>
   </li><li>
-    <a href="reference/routingpolicies.html">Routing policies reference</a>.
+    <a href="/en/reference/routingpolicies.html">Routing policies reference</a>.
     See the <a href="#routing-policies">routing policies</a> note
     for complex routes and default routing
   </li>
@@ -30,10 +31,10 @@
 In Vespa, there is a transport layer and a programming interface that
 are available to clients that wish to communicate with a Vespa application.
 The transport layer is <em>Message Bus</em>.
-<a href="document-api-guide.html">Document API</a> is
+<a href="/en/document-api-guide.html">Document API</a> is
 implemented on top of Message Bus.
-Configuring the interface therefore exposes some of the features available in Message Bus.
-Refer to the <a href="api.html">Vespa APIs and interfaces</a>
+Configuring the interface therefore exposes some features available in Message Bus.
+Refer to the <a href="/en/api.html">Vespa APIs and interfaces</a>
 for clients using the <em>Document API</em>.
 The atoms in Vespa routing are <em>routes</em> and <em>hops</em>.
 </p>
@@ -113,11 +114,11 @@ <h2 id="a-hop-is-a-point-to-point-transmission">A hop is a point-to-point transm
 gives an insight into what symbolic names exist for any given
 application by looking at its current configuration subscriptions.
 All available Message Bus services use their <code>ConfigId</code> as their host's symbolic name.
-See <a href="reference/vespa-cmdline-tools.html#vespa-route">vespa-route</a> for how to inspect this,
-or use the <a href="reference/config-rest-api-v2.html">config API</a>.
+See <a href="/en/reference/vespa-cmdline-tools.html#vespa-route">vespa-route</a> for how to inspect this,
+or use the <a href="/en/reference/config-rest-api-v2.html">config API</a>.
 </p><p>
 A hop can be prefixed using the special character "?" to force it to behave as if its
-<a href="reference/services-routing.html#hop">ignore-result</a> attribute was configured to "true".
+<a href="#hop">ignore-result</a> attribute was configured to "true".
 </p>
 
 
@@ -156,7 +157,7 @@ <h2 id="routing-policies">Routing policies</h2>
 that pretty much allows it to do whatever it pleases to the route and replies.
 The same policy object and the same context object is used for both selection and merging.
 </p><p>
-Refer to the <a href="reference/routingpolicies.html">routing policy reference</a>.
+Refer to the <a href="/en/reference/routingpolicies.html">routing policy reference</a>.
 </p>
 
 
@@ -170,7 +171,7 @@ <h2 id="selection-logic">Selection logic</h2>
 Finally, the message is <a href="#3-send-to-services">sent</a> to all chosen recipient services.
 Because each policy can select multiple recipients,
 this can give rise to an arbitrarily complex routing tree.
-There are, of course, safe-guards within Message Bus to prevent infinite recursions
+There are, of course, safeguards within Message Bus to prevent infinite recursions
 due to circular dependencies or misconfiguration.
 </p>
 {% include note.html content="It <strong>is</strong> possible to develop a different protocol with other
@@ -223,7 +224,7 @@ <h3 id="1-resolve-policy-directives">1. Resolve Policy Directives</h3>
 <p>
 This hop has a selector but no recipients.
 The reason for this is best explained in
-the <a href="reference/routingpolicies.html">policies article</a>,
+the <a href="/en/reference/routingpolicies.html">policies article</a>,
 but it serves as an example of a hop that has no configured recipients.
 Notice how the policy directive contains a colon (":")
 which denotes that the remainder of the directive is a parameter to the policy constructor.
@@ -233,7 +234,7 @@ <h3 id="1-resolve-policy-directives">1. Resolve Policy Directives</h3>
 What routing policies are available depends on what protocol is currently running.
 As of this version the only supported protocol is "Document".
 This offers a set of routing policies discussed in
-<a href="reference/routingpolicies.html">this article</a>.
+<a href="/en/reference/routingpolicies.html">this article</a>.
 </p>
 
 
@@ -280,7 +281,7 @@ <h3 id="3-send-to-services">3. Send to Services</h3>
 these will adhere to the new routes.
 </p><p>
 If the resolution of a recipient passed through a hop that was configured
-to <a href="reference/services-routing.html#hop">ignore results</a>,
+to <a href="#hop">ignore results</a>,
 the network layer will reply immediately with a synthetic "OK".
 </p>
 
@@ -366,3 +367,296 @@ <h3 id="the-document-api">The Document API</h3>
 <p>
 Refer to the <a href="https://javadoc.io/doc/com.yahoo.vespa/documentapi">Document API JavaDoc</a>.
 </p>
+
+
+
+
+<h2 id="routing-services">Routing services</h2>
+<p>
+  This is the reference documentation for all elements in
+  the <em>routing</em> section of <a href="/en/reference/services.html">services.xml</a>.
+</p>
+<pre class="pre-config">
+<a href="#routing">routing [version]</a>
+    <a href="#routingtable">routingtable [protocol, verify]</a>
+        <a href="#route">route [name, hops]</a>
+        <a href="#hop">hop [name, selector, ignore-result]</a>
+            <a href="#recipient">recipient [session]</a>
+    <a href="#services">services [protocol]</a>
+        <a href="#service">service [name]</a>
+</pre>
+
+
+
+<h2 id="routing">routing</h2>
+<p>
+  Contained in <a href="/en/reference/services.html#services">services</a>.
+  The container element for all configuration related to routing.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>version</th>
+  <td>required</td>
+  <td>number</td>
+  <td></td>
+  <td>Must be set to "1.0" in this Vespa-version</td></tr>
+</tbody>
+</table>
+<p>Optional subelements:</p>
+<ul>
+  <li><a href="#routingtable">routingtable</a></li>
+  <li><a href="#services">services</a></li>
+</ul>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;routingtable protocol="document"&gt;
+        &lt;route name="route1" hops="hop1 hop2" /&gt;
+        &lt;route name="route2" hops="hop3 hop4 hop5" /&gt;
+        &lt;hop name="hop1" selector="docproc/cluster.foo/docproc/*/feed-processor"&gt;
+            &lt;recipient session="docproc/cluster.foo/docproc/*/feed-processor" /&gt;
+        &lt;/hop&gt;
+        &lt;hop name="hop2" selector="search/cluster.bar/[SearchGroup]/[SearchRow]/[SearchColumn]/feed-destination"&gt;
+            &lt;recipient session="search/cluster.bar/g0/c0/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g0/c1/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g0/c0/r1/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g0/c1/r1/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g1/c0/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g1/c1/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g1/c0/r1/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.bar/g1/c1/r1/feed-destination" /&gt;
+        &lt;/hop&gt;
+    &lt;/routingtable&gt;
+    &lt;services protocol="document"&gt;
+        &lt;service name="foo/bar" /&gt;
+    &lt;/services&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="routingtable">routingtable</h2>
+<p>
+  Contained in <a href="#routing">routing</a>.
+  Specifies a routing table for a specific protocol.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>protocol</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>Configure which protocol to use.
+    Only the protocol <em>document</em> is defined,
+    so if you define a routing table for an unsupported protocol,
+    the application will just log an INFO entry that contains the name of that protocol.</td></tr>
+<tr><th>verify</th>
+  <td>optional</td>
+  <td>boolean</td>
+  <td></td>
+  <td>ToDo: document this</td></tr>
+</tbody>
+</table>
+<p>Optional subelements:</p>
+<ul>
+  <li><a href="#route">route</a></li>
+  <li><a href="#hop">hop</a></li>
+</ul>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;routingtable protocol="document"&gt;
+        &lt;route name="route1" hops="hop1 hop2" /&gt;
+        &lt;hop name="hop1" selector="docproc/cluster.foo/docproc/*/feed-processor"&gt;
+            &lt;recipient session="docproc/cluster.foo/docproc/*/feed-processor" /&gt;
+        &lt;/hop&gt;
+    &lt;/routingtable&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="route">route</h2>
+<p>
+  Contained in <a href="#routingtable">routingtable</a>.
+  Specifies a route for a message to its destination through a set of intermediate hops.
+  If at least one hop in a route does not exist,
+  the application will fail to start and issue an error that contains the name of that hop.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>name</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>Route name.</td></tr>
+<tr><th>hops</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>A whitespace-separated list of hop names, where each name must be a valid hop.</td></tr>
+</tbody>
+</table>
+<p>Subelements: none</p>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;routingtable protocol="document"&gt;
+        &lt;route name="route1" hops="hop1 hop2" /&gt;
+        &lt;route name="route2" hops="hop3 hop4 hop5" /&gt;
+    &lt;/routingtable&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="hop">hop</h2>
+<p>
+  Contained in <a href="#routingtable">routingtable</a>.
+  Specifies a single hop that can be used to construct one or more routes.
+  A hop must have a name that is unique within the routing table to which it belongs.
+  A hop contains a selector string and a list of recipient sessions.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>name</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>Hop name.</td></tr>
+<tr><th>selector</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>Selector string.</td></tr>
+<tr><th>ignore-result</th>
+  <td>optional</td>
+  <td></td>
+  <td></td>
+  <td>If set to <em>true</em>, specifies that the result of routing through that hop should be ignored.</td></tr>
+</tbody>
+</table>
+<p>Optional subelements:</p>
+<ul>
+  <li><a href="#recipient">recipient</a></li>
+</ul>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;routingtable protocol="document"&gt;
+        &lt;hop name="hop1" selector="docproc/cluster.foo/docproc/*/feed-processor"&gt;
+            &lt;recipient session="docproc/cluster.foo/docproc/*/feed-processor" /&gt;
+        &lt;/hop&gt;
+    &lt;/routingtable&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="recipient">recipient</h2>
+<p>
+  Contained in <a href="#hop">hop</a>.
+  Specifies a recipient session of a hop.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>session</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>This attribute must correspond to a running instance of a
+    service that can be routed to.
+    All session identifiers consist of a location part and a
+    name. A search node is always given a session name on the form
+    <em>search/cluster.name/g#/r#/c#/feed-destination</em>,
+    whereas a document processor service is always named
+    <em>docproc/cluster.name/docproc/#/feed-processor</em>.</td></tr>
+</tbody>
+</table>
+<p>Subelements: none</p>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;routingtable protocol="document"&gt;
+        &lt;hop name="search/cluster.music" selector="search/cluster.music/[SearchGroup]/[SearchRow]/[SearchColumn]/feed-destination"&gt;
+            &lt;recipient session="search/cluster.music/g0/c0/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.music/g0/c0/r1/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.music/g1/c0/r0/feed-destination" /&gt;
+            &lt;recipient session="search/cluster.music/g1/c0/r1/feed-destination" /&gt;
+        &lt;/hop&gt;
+    &lt;/routingtable&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="services">services</h2>
+<p>
+  Contained in <a href="#routing">routing</a>.
+  Specifies a set of services available for a specific protocol.
+  At the moment the only supported protocol is <em>document</em>.
+  The services specified are used by the route verification step
+  to allow hops and routes to reference services known to exist,
+  but that can not be derived from <em>services.xml</em>.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>protocol</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>Configure which protocol to use. Only the protocol <em>document</em> is defined.</td></tr>
+</tbody>
+</table>
+<p>Optional subelements:</p>
+<ul>
+  <li><a href="#service">service</a></li>
+</ul>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;services protocol="document"&gt;
+        &lt;service name="foo/bar" /&gt;
+    &lt;/services&gt;
+&lt;/routing&gt;
+</pre>
+
+
+
+<h2 id="service">service</h2>
+<p>
+  Contained in <a href="#services">services</a>.
+  Specifies a single known service that can not be derived from the <em>services.xml</em>.
+</p>
+<table class="table">
+  <thead>
+  <tr><th>Attribute</th><th>Required</th><th>Value</th><th>Default</th><th>Description</th></tr>
+  </thead><tbody>
+<tr><th>name</th>
+  <td>required</td>
+  <td></td>
+  <td></td>
+  <td>The name of the service.</td></tr>
+</tbody>
+</table>
+<p>Subelements: none</p>
+<p>Example:</p>
+<pre>
+&lt;routing version="1.0"&gt;
+    &lt;services protocol="document"&gt;
+        &lt;service name="foo/bar" /&gt;
+    &lt;/services&gt;
+&lt;/routing&gt;
+</pre>
diff --git a/en/reference/services.html b/en/reference/services.html
index f20ecd9198..40ae918a57 100644
--- a/en/reference/services.html
+++ b/en/reference/services.html
@@ -13,7 +13,7 @@
   <a href="services-container.html">container [version]</a>
   <a href="services-content.html">content   [version]</a>
   <a href="services-admin.html">admin     [version]</a>
-  <a href="services-routing.html">routing   [version]</a>
+  <a href="/en/operations-selfhosted/routing.html#routing-services">routing   [version]</a>
 </pre>
 Nodes/hosts referred to in <em>services.xml</em> must be defined in
 <a href="hosts.html">hosts.xml</a> using <em>hostalias</em>.
@@ -41,7 +41,7 @@ <h2 id="services">services</h2>
   <li><a href="services-admin.html"><code>admin</code></a></li>
   <li><a href="services-content.html"><code>content</code></a></li>
   <li><a href="services-container.html"><code>container</code></a></li>
-  <li><a href="services-routing.html"><code>routing</code></a></li>
+  <li><a href="/en/operations-selfhosted/routing.html#routing-services"><code>routing</code></a></li>
 </ul>
 <p>Example:</p>
 <pre>
@@ -101,5 +101,5 @@ <h2 id="modular">Modular Configuration</h2>
 will be used as if it was inlined in <em>services.xml</em>.
 This is supported for <a href="services-search.html#chain">search chains</a>,
 <a href="services-docproc.html">docproc chains</a> and
-<a href="services-routing.html">routing tables</a>.
+<a href="/en/operations-selfhosted/routing.html#routing-services">routing tables</a>.
 </p>