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 frameworkNext.js
next.config.ts, any hostTanStack Start
vite.config.ts with NitroAstro
Platform rewrites, or a proxy route with an adapter
Netlify
_redirectsFramer
Multi Site rewrites, Advanced Hosting
Cloudflare
A Worker on your zone
AWS CloudFront
Cache behaviors, plus Route 53
nginx
proxy_pass, plus CaddyThe 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 requestshttps://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/bloganswers without a redirect.- The response doesn’t carry
X-Robots-Tag: noindex.
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.xmlandllms.txtunder its path, for example/blog/robots.txt. The section’srobots.txtuses your domain in its links, so you can copy itsSitemaplines andllms.txtcomment into your ownrobots.txt. Keep your website’s crawler rules as they are, because the section’sAllowrules for AI crawlers would override paths you block underUser-agent: *. /robots.txtand/llms.txtat the root of your domain belong to your website, so add the sitemaps torobots.txt(step 5) and link/blog/llms.txtfrom your ownllms.txtif you have one.
Troubleshooting
The check says it could not reach the test file
The check says it could not reach the test file
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.The page loads, but without styles
The page loads, but without styles
Your rewrite forwards only
/blog rather than /blog/*, while assets live under /blog/_notra/assets/.Notra answers with a 404 for every page
Notra answers with a 404 for every page
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.Bot protection blocks the check
Bot protection blocks the check
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.The blog link in the header goes to a 404
The blog link in the header goes to a 404
The header links between the blog and the changelog, so forward every section that’s turned on.
A link on my website opens my own 404 page instead of the blog
A link on my website opens my own 404 page instead of the blog
Your website’s client-side router opens
/blog in the browser instead of requesting it from your server, so the rewrite never runs. Make links to your sections load the page with a plain <a href="/blog">. React Router’s <Link reloadDocument> works too, but TanStack Router’s typed <Link> only accepts your app’s own routes, so use the plain <a> there. Opening https://www.acme.com/blog directly works either way.An old URL from my blog.json redirects shows the new page under the old URL
An old URL from my blog.json redirects shows the new page under the old URL
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.