The Revnu-Hosted Blog and Your Own Domain

You approved a post: where is it?

If you haven't connected your own domain or site, it's live on your Revnu-hosted blog, at an address like yourcompany.revnu.sh/<post-slug>. The page is public, search engines can index it, and it's published under your business's name.

The hosted blog is built to be read by AI engines as well as Google. Each post carries structured data and its FAQ section, and the blog serves an llms.txt file that lists every post, so ChatGPT, Perplexity, Claude, Gemini and Google AI Overviews can find and cite it.

To see it, open Visibility > Posts. Press the eye icon (View Live Blog) on the post's row, or open the post and press View Live.

The one thing worth doing next is moving the blog onto your own domain, so search engines credit the posts to your domain rather than to revnu.sh. It takes two DNS records and no developer: put the blog on your own subdomain.

The hosted blog suits Wix, Squarespace, Lovable and other site builders, with no code needed. Sites with a developer can render posts themselves through the Content API. Which setup fits your site compares the options.

What the revnu.sh address is

Each account's blog has its own address at revnu.sh, with your blog's name in front. It's a complete blog: an index page, every post, a sitemap, structured data and an RSS feed. Until you connect your own domain, Publishing Settings lists it as the Temporary fallback.

Put the blog on your own subdomain

1. 1

   Ask Revnu for the domain

   Tell Revnu in chat which address you want: "put my blog on blog.acme.com". It sets the domain up and replies with the DNS records, and it can walk you through them in your own language (languages).

2. 2

   Copy the DNS records

   The records also appear on the domain's card in Visibility > Posts > Publishing Settings. A new domain needs two:

   • A CNAME record named after the first part of the address (blog for blog.acme.com), which points the subdomain at your blog.

   • A TXT record at _revnu. plus that first part (_revnu.blog), which proves the domain is yours.

   Copy the Type, Name and Value of each exactly as the card shows them.

3. 3

   Add them where your DNS is managed

   Sign in wherever your domain's DNS is managed and add both records. Not sure where that is? See Where do I add the DNS record?

   Warning

   Add new records. Don't change or delete the records your site already uses, or your main site can stop loading.

4. 4

   Press I've Added DNS

   Back in Publishing Settings, press I've Added DNS.

What you'll see

The card reads DNS Pending until the records check out. While you stay on the page it checks again every 30 seconds. DNS changes can take a while to spread. Once they do, the card reads Blog Domain Connected, posts publish on your domain, and Revnu starts the daily cadence. If Revnu's first post is waiting in Review, approve it now and it goes live on your domain.

Where do I add the DNS record?

At whoever manages your domain's DNS. That's usually the company you bought the domain from, unless you moved its DNS somewhere else.

• Bought the domain through Wix or Squarespace? The records go in that domain's DNS settings inside Wix or Squarespace.

• Bought it from GoDaddy, Namecheap or another registrar? The records go in that domain's DNS settings at the registrar, even if your site is built on Wix or Squarespace.

• Not sure? Look up your domain's nameservers with any free "NS lookup" tool. The company named there is where you add the record.

Put the blog at /blog on your main domain

There are two routes:

• A developer can render posts on your site's server: use the Content API. It puts posts at yourcompany.com/blog in your own design, with no proxy and no wait on Revnu's team.

• Revnu renders the posts: use a reverse proxy to the hosted blog. It takes one rewrite rule from a developer and a setting Revnu's team changes for you.

A reverse proxy (also called a rewrite) means your web server forwards every request under /blog to your Revnu blog. Visitors and search engines only ever see your domain. Revnu's team sets it up with you:

1. 1

   Email Revnu's team

   Email support@revnu.com. Copy this and fill in the brackets:

   Subject: Reverse proxy for my Revnu blog

   Please set my Revnu blog up to be served at [yourcompany.com/blog]. My Revnu account email is [you@yourcompany.com]. My site is hosted on [Vercel / Cloudflare / Netlify / other]. Please send me the host my rewrite should point at.

2. 2

   Wait for the reply

   Revnu's team sets your blog's address on its side and sends you the host to forward to.

   Use that host, not your revnu.sh address. A plain rewrite to the revnu.sh address loads pages without their styles.

3. 3

   Add the rewrite

   Your developer forwards /blog and everything under it to that host, keeping the path as it is. Replace YOUR-REVNU-HOST below with the host Revnu's team sent you.

   On Vercel, in vercel.json:

   {
     "rewrites": [
       { "source": "/blog", "destination": "https://YOUR-REVNU-HOST/blog" },
       { "source": "/blog/:path*", "destination": "https://YOUR-REVNU-HOST/blog/:path*" }
     ]
   }

   On Cloudflare, a Worker on the route yourcompany.com/blog*:

   export default {
     async fetch(request) {
       const url = new URL(request.url);
       if (url.pathname === "/blog" || url.pathname.startsWith("/blog/")) {
         // Same path, Revnu's host: the blog serves /blog/... once your address is set.
         url.hostname = "YOUR-REVNU-HOST";
         return fetch(new Request(url, request));
       }
       return fetch(request);
     },
   };

4. 4

   Check one post

   Open yourcompany.com/blog/<a post's slug>. It should load with its styling, and its canonical tag (in the page source) should point at yourcompany.com/blog/....

5. 5

   Submit the sitemap

   In your own Search Console property, submit yourcompany.com/blog/sitemap.xml.

Canonical URLs

A canonical tag tells search engines which address is the real one for a page. Revnu sets it for you:

When you move from revnu.sh to your subdomain, each post keeps the same path, and its canonical tag switches to your subdomain. The revnu.sh address keeps working but doesn't redirect.

On every setup the canonical tag points Google at your real address, and with the Content API the revnu.sh copy is also noindex. Check how your posts are doing there in Search Console.

If it doesn't work

What happens when you cancel

When you cancel or a payment fails, Revnu stops writing, publishing and measuring. Posts already published keep serving today, on revnu.sh and on a custom subdomain whose DNS record you leave in place. That's current behaviour rather than a guarantee, so keep a copy of your posts:

• With a developer: save every post through the Content API, which returns each one's full text and HTML.

• Without one: email support@revnu.com before you cancel and ask for an export of your posts.

To move the blog somewhere else, publish the posts on your new blog at the same paths if you can, point your subdomain's DNS at the new host, and set up permanent (301) redirects from any old addresses that change. The revnu.sh addresses don't redirect anywhere when you leave. Deleting your account is a separate step: delete your account.