Serve a second website under a path

Serve a path of your main domain, such as acmeprecision.com/updates, with another of your websites.

Copy page for AIUpdated November 9, 2026
Watch: the whole walkthrough (39 seconds)

Sometimes a second website belongs under your main address rather than on its own: acmeprecision.com/updates for a news site, say, kept separate from the company website so each can change on its own. A route does that: one path of a domain is served by another of your websites, and everything else stays with the main one.

Open Websites now

Before you start

  • Both websites are in your workspace, and the second one has a live version.
  • The main website has the domain, such as acmeprecision.com. See Use your own domain.

1. Get the second website ready for the path

The second website receives its pages without the path in front (/updates/news arrives as /news), plus a note saying which path it's under. Its links, pictures and styles must take that into account, or the page loads without its look.

  1. Open the second website's page and click Edit in Module Builder.
  2. Ask: "Make this website work under /updates on acmeprecision.com: read the X-Forwarded-Prefix header and put that prefix in front of its links."
  3. Check that its preview still looks the same at its own address, then publish it.

2. Add the route

  1. Open the main website's page.
    Open the website
  2. Under Routes, choose the Domain, type the Path (such as /updates) and choose the website in Served by.
    Domain, path and served by
  3. Click Add route and confirm.
    Add route

3. Wait for it to switch on

Unlike a domain, a new route is switched on by Data Visions. The route shows:

StatusWhat it means
RecordedSaved, and not checked yet.
Waiting for the platform to switch it onData Visions still has to switch it on.
ServingVisitors to the path get the second website.

Press Check DNS on that domain in DNS instructions, or come back later: opening the Websites page checks each domain again once a day, and the route's status updates with it.

Then open acmeprecision.com/updates: it moves to /updates/ and shows the second website.

Good to know

  • Everything else stays with the main website. Only the path and what's under it goes to the second one.
  • The second website's page says where it's served, under Routes: Also served at …
  • Paths are one to four lower-case parts, such as /updates or /news/2026, never just /. A domain can have up to 20 routes.
  • A route also covers the www. address when both share the website, as in a typical setup.
  • Only your own websites. A route can't point at another workspace's website.
  • The page looks broken under the path but fine on its own? Its links don't use the path yet. Ask the Module Builder to fix step 1 again.
  • Remove next to a route stops serving that path with the other website.
  • Who can do this: Workspace Admins, and anyone whose role has Manage websites.

Can't find what you need? Contact support.