Skip to main content
To serve your site at acme.com/blog, the host that runs acme.com forwards every request under /blog to Notra and passes the response back, so visitors and search engines only ever see acme.com. DNS can’t route paths, so this always needs a rewrite (also called a reverse proxy) on your side.

Pick your platform

Vercel

vercel.json, any framework

Next.js

next.config.ts, any host

TanStack Start

vite.config.ts with Nitro

Astro

Platform rewrites, or a proxy route with an adapter

Netlify

_redirects

Framer

Multi Site rewrites, Advanced Hosting

Cloudflare

A Worker on your zone

AWS CloudFront

Cache behaviors, plus Route 53

nginx

proxy_pass, plus Caddy
Site builders like Webflow, Squarespace and Wix can’t forward paths, so put Cloudflare or CloudFront in front of them.
Click the domain on the Domains page. Manual setup shows the exact code for your platform, already filled in with your address and section paths, and Copy agent prompt copies an instruction you can paste into Claude Code, Cursor or Codex to make the change for you.

The steps on every platform

1

Set the section paths

Under Settings → Content → Sections, set the paths you want on your website, for example /blog and /changelog, which are the paths you forward. See Section paths.
2

Add the domain in Notra

Open Domains → Add domain and enter the host and path, for example www.acme.com/blog. If acme.com redirects to www.acme.com, Notra notices and adds www.acme.com/blog instead, since that host serves your website. The domain shows up with the status Needs rewrites.
3

Add the rewrite

Forward each section path and everything below it to your Notra address with the path unchanged, following the guide for your platform.
4

Deploy your website and check

Deploy the change. Notra checks the domain on its own, every minute at first, so it turns Active shortly after your deploy, or click Check to check right away. Notra fetches a test file through your website for every section, and once it answers, the domain is Active and becomes the site’s primary address.
5

Add the sitemaps to your robots.txt

Your robots.txt stays yours, so add the section sitemaps to it:
robots.txt

What the rewrite has to do

Every platform guide meets these rules, so if you write your own proxy, check it against them. Notra doesn’t need cookies or Authorization headers, so don’t forward them where your platform lets you, which keeps your visitors’ sessions on your domain. Keep User-Agent and Referer, and send the visitor’s IP in X-Forwarded-For, so site analytics can tell visitors apart. Notra uses the last public address your proxy adds, so a value the visitor sends can’t stand in for it, and the nginx and Cloudflare guides set it explicitly. Countries come from Cloudflare’s location data with the Cloudflare Worker setup, and from Vercel’s X-Vercel-IP-Country header when your proxy sends it. Behind other proxies Notra would only see where your server is, so site analytics show those visits without a country.

How the check works

Check requests https://www.acme.com/blog/_notra/probe.txt for every section with the user agent NotraSitesVerifier/1.0, and it passes when all of these are true:
  • The file comes from this site.
  • https://www.acme.com/blog answers without a redirect.
  • The response doesn’t carry X-Robots-Tag: noindex.
When it passes, Notra rebuilds the site so that canonical URLs, feeds, sitemaps and social previews use https://www.acme.com/blog.

Search engines and AI agents

  • Search engines only index pages under your domain, because your Notra address stops being crawled once the domain is active and every page names www.acme.com/blog/... as canonical.
  • Each section has its own robots.txt, sitemap.xml, feed.xml and llms.txt under its path, for example /blog/robots.txt. The section’s robots.txt uses your domain in its links, so you can copy its Sitemap lines and llms.txt comment into your own robots.txt. Keep your website’s crawler rules as they are, because the section’s Allow rules for AI crawlers would override paths you block under User-agent: *.
  • /robots.txt and /llms.txt at the root of your domain belong to your website, so add the sitemaps to robots.txt (step 5) and link /blog/llms.txt from your own llms.txt if you have one.

Troubleshooting

Open https://www.acme.com/blog/_notra/probe.txt in your browser, where you should see a short text that starts with notra-site=. If you see your own 404 page, the rewrite isn’t live yet or doesn’t cover /blog/*. If the browser is redirected to another host, add that host instead (Notra already switches between acme.com and www.acme.com by itself). If it adds a trailing slash, turn that off for these paths.
Your rewrite forwards only /blog rather than /blog/*, while assets live under /blog/_notra/assets/.
Your proxy sends your own host in the Host header, so set it to your Notra address, for example proxy_set_header Host acme.notra.site; in nginx.
Firewalls like Vercel’s Attack Challenge Mode or Cloudflare’s Bot Fight Mode can block NotraSitesVerifier/1.0, so allow it for your section paths or pause the protection while you check.
Your proxy follows redirects instead of passing them on. In a Cloudflare Worker, set redirect: "manual", which the other platform guides already handle for you.
Last modified on November 11, 2026