Nurio Docs Connect your domain

Setup guide

Connect your domain

One small config change routes your blog through Nurio so it appears at yoursite.com/blog. No coding experience required — just copy, paste, and deploy.

One config change

2–5 minutes

Fully reversible

Before you start

You have a Nurio account

You've connected your website URL in Nurio (Settings → Routing & Proxy)

You know which platform hosts your website (Vercel, Netlify, etc.) — or you can use Auto-Detect in Settings

You have your workspace slug — find it in Settings → Routing & Proxy, shown in the code snippet as the part after /proxy/

Finding your workspace slug

Go to Settings → Routing & Proxy, run Auto-Detect, and look at the generated code snippet. You'll see a URL like nurio.sh/proxy/your-slug/blogs. That highlighted part is your workspace slug — replace YOUR-WORKSPACE in the snippets below with it.

Choose your platform

Not sure which one? Go to Settings → Auto-Detect and we'll figure it out from your domain.

Open your project folder

Open the folder where your website's code lives — in VS Code, Cursor, or any code editor. This is the same place you'd find files like package.json or index.html.

Don't have a code editor? Download VS Code — it's free.

Explorer

▾📁 my-website

▾📁 src

📄 index.ts

📁 public

📄 package.json

📄 README.md

📄 vercel.json ← you need this

Find or create vercel.json

Look for a file called vercel.json in the root of your project (same level as package.json). If it doesn't exist, create a new empty file with that exact name.

To create it:

A Right-click your project folder → New File → name it vercel.json

B Or in terminal:

Terminal

$ ls

src/ public/ package.json README.md

$ touch vercel.json

$ ls

src/ public/ package.json README.md vercel.json

File created

Paste this config into vercel.json

Open vercel.json, select all the existing content (if any), and replace it with the snippet below. Make sure to replace YOUR-WORKSPACE with your actual workspace slug from Settings.

vercel.json

{
  "rewrites": [
    {
      "source": "/blogs",
      "destination": "https://nurio.sh/proxy/YOUR-WORKSPACE/blogs"
    },
    {
      "source": "/blog",
      "destination": "https://nurio.sh/proxy/YOUR-WORKSPACE/blogs"
    },
    {
      "source": "/blog/:path*",
      "destination": "https://nurio.sh/proxy/YOUR-WORKSPACE/blog/:path*"
    }
  ]
}

Replace YOUR-WORKSPACE in all three places with your slug from Settings. It looks something like aura-40a60ab3.

Save, commit, and push

Save the file (Ctrl+S / Cmd+S), then open a terminal in your project folder and run these three commands one at a time:

Terminal

$ git add vercel.json

$ git commit -m "Add Nurio blog proxy"

[main a1b2c3] Add Nurio blog proxy

$ git push

Enumerating objects: 3, done.

Writing objects: 100% (3/3), done.

Pushed to GitHub

Wait for Vercel to deploy

Vercel automatically detects your push and starts deploying. This usually takes 60–90 seconds. You can watch the progress in your Vercel dashboard — look for the green "Ready" status.

You don't need to do anything — just wait for it to finish.

vercel.com → my-website

Deployments

Add Nurio blog proxy

Building... 45s

Building

Previous deploy

2 hours ago

Ready

Check the connection in Nurio

Once Vercel shows "Ready", come back to Nurio and go to Settings → Routing & Proxy. Click the refresh icon next to "Blog Route Status". It should turn green within a few seconds.

Go to Settings

nurio.sh → Settings → Routing

Blog Route Status

yoursite.com/blog

Connected

🎉

Your blog is live!

Visit yoursite.com/blog to see it

Troubleshooting

It still says "Proxy Offline" after deploying

Give it 1–2 minutes for your deployment to fully propagate. Then click the refresh icon in Settings again. CDN changes can take a moment to reach all edge nodes.

I see the connection but visiting /blog shows a 404

Double-check that YOUR-WORKSPACE in the snippet matches exactly what's shown in your Settings code snippet. Even a small typo will cause a mismatch.

I already have a /blog page on my site

If your framework (e.g. Next.js) has a page at /blog, it may take priority over the rewrite. You'll need to either remove that page or use a redirect rule with force = true (Netlify) or use Next.js middleware to intercept the route.

Vercel says "A rewrite cannot be used for the same source as another"

Your vercel.json already has a conflicting rule for /blog or /blogs. Find and remove the old one, then add the three rules from this guide.

I don't have access to my hosting config

Use the "Email your developer" button in Settings → Routing & Proxy. It pre-fills everything your developer needs — they just need to paste and deploy.

Ready? Go to Settings to check your connection status.

Open Settings Back to Dashboard