Mount a site under a path

Path mounts let you publish a Static Studio site under a path on an existing domain.

For example, you can keep your SaaS app running at: https://acme-app.eu and serve your imported WordPress site at: https://acme-app.eu/blog

This is useful when your main domain is already hosted somewhere else, such as Vercel, Netlify, Cloudflare, or your own application server, but you want Static Studio to power a static WordPress section like a blog, marketing hub, help center, or documentation area.

When to use a path mount

Use a path mount when you want your Static Studio site to live under a subpath of an existing domain, for example:

• https://example.com/blog
• https://example.com/news
• https://app.example.com/resources

Do not use a path mount when you want Static Studio to serve an entire domain or subdomain, such as:

• https://blog.example.com
• https://www.example.com

For a full domain or subdomain, use the regular custom domain setup with a CNAME record.

How path mounting works

DNS can point a domain or subdomain to Static Studio, but DNS cannot route a single URL path like /blog.

That means a path such as /blog must stay on your current domain host. Your host then needs a rewrite or proxy rule that forwards requests for that path to your Static Studio origin.

The setup looks like this:

• Visitor requests: https://acme-app.eu/blog
• Your app host receives the request and proxies it to: https://slvgv74w7o9pr60.onstatic.studio/blog
• Visitor still sees: https://acme-app.eu/blog

Static Studio generates the correct public URLs for your static WordPress site, and your application host decides which requests should be sent to Static Studio.

Step 1: Create or import your WordPress site

Start by creating a new Static Studio site or importing an existing WordPress backup.

On the Import WordPress Site screen, upload your backup file as usual. To configure the site for a path mount before importing, click Edit Site Details.

Step 2: Set the public mount path

In Site Settings, enter the path where the site should be served in the Public Mount Path field.

For example: /blog

The mount path should start with a forward slash, should not include the domain, and usually should not include a trailing slash.

Use:

• /blog

Do not use:

• blog
• https://acme-app.eu/blog
• /blog/

When the site is imported, Static Studio uses this path when generating public URLs for pages, posts, assets, feeds, sitemaps, and canonical URLs.

Step 3: Open the path mount configuration

After the site has been created or imported, open Site Details and go to the Domain tab. In the connected domains area, click Configure a path mount.

This opens the path mount configuration generator.

Step 4: Generate the rewrite or proxy rule

In the Path Mount Config screen, enter the public domain and mount path.

For example:

• Public Domain: acme-app.eu
• Mount Path: /blog
• Studio Origin: https://slvgv74w7o9pr60.onstatic.studio
• Provider: Vercel

• The Public Domain is the domain currently serving your main site or app.
• The Mount Path is the public path where the Static Studio site should appear.
• The Studio Origin is the Static Studio origin that serves the generated static site.

The Provider determines which rewrite or proxy configuration Static Studio generates.

A subpath like /blog cannot be connected with DNS alone. Keep your main domain on its current host and add the generated rewrite or proxy rule there.

Step 5: Add the generated config to your host

Copy the generated configuration and add it to the project or platform that currently serves your public domain.

For example, for Vercel, add the generated rewrite rules to vercel.json in the project root:

{
  "$schema": "https://openapi.vercel.sh/vercel.json",
  "rewrites": [
    {
      "source": "/blog",
      "destination": "https://slvgv74w7o9pr60.onstatic.studio/blog"
    },
    {
      "source": "/blog/:path*",
      "destination": "https://slvgv74w7o9pr60.onstatic.studio/blog/:path*"
    }
  ]
}

Then redeploy your application.

The first rule handles the path itself:

• /blog

The second rule handles everything below the path:

• /blog/my-first-post
• /blog/category/news
• /blog/wp-content/uploads/image.jpg
• /blog/feed.xml

Both rules are required.

Step 6: Verify the mounted site

After redeploying your application, check the mounted path in your browser.

For example: https://acme-app.eu/blog

The blog index should load from Static Studio while the main application remains available at: https://acme-app.eu

You should also verify: https://acme-app.eu/blog/sitemap.xml

Make sure posts, uploads, CSS, JavaScript, fonts, feeds, and canonical URLs use the mounted path.

Finally, confirm that WordPress admin URLs are not publicly exposed: https://acme-app.eu/blog/wp-admin

Updating an existing mounted site

When updating an existing site, keep the same Public Mount Path unless you intentionally want to change the public URL structure.

Changing the mount path changes where the site expects to be served. For example, moving from /blog to /news means your pages, assets, sitemap, and canonical URLs will also move to the new path.

If you change the mount path, update the rewrite or proxy rule in your application host and redeploy it.

Troubleshooting

The mounted path returns a 404

Check that your host has a rewrite or proxy rule for both the exact path and all nested paths.

• /blog and /blog/:path* are both needed.
• The homepage works, but posts or assets return 404
• The wildcard rewrite is probably missing or incorrect.

Make sure requests such as the following are also forwarded to Static Studio:

• /blog/example-post
• /blog/wp-content/uploads/image.jpg
• /blog/sitemap.xml

Assets load from the wrong URL

Make sure the Public Mount Path in Static Studio matches the path in your host configuration.

For example, if Static Studio is configured for /blog, your host should also proxy /blog.

The main app stops working

Do not point the whole domain to Static Studio when using a path mount.

Your main domain should remain on its current host. Only the mounted path should be proxied to the Static Studio origin.

The site redirects to the Static Studio origin

Check that the public domain and mount path are configured correctly, and that your host is proxying or rewriting requests rather than redirecting visitors to the origin.

• Visitors should stay on your public URL, such as: https://acme-app.eu/blog
• They should not be sent to: https://slvgv74w7o9pr60.onstatic.studio/blog

Summary

Path mounts let you serve a Static Studio site from a subpath on an existing domain.

Use them when your main site or app should stay where it is, but a static WordPress section should appear under a path like /blog.

The important pieces are:

1. Set the Public Mount Path in Static Studio.
2. Keep your main domain on its current host.
3. Generate the rewrite or proxy rule in Static Studio.
4. Add the rule to your application host.
5. Redeploy and verify the mounted path.