Notion Sites vs Birta: Where Should the Public Version Live?

The short answer

Yes, a Notion page can end up as a site published through Birta, and the route is the agent you already talk to. If the page is published to the web, the agent reads it from the link. If it is private, Notion runs its own hosted connection for exactly this, and the agent searches and reads your workspace through it. Either way it then writes the files into a Birta draft and publishes them.

Birta itself never opens Notion. It does not need to, because reading a document is the thing the agent is already good at, and repeating that inside a publishing service would buy nobody anything.

What decides this page is one question. Does the site have to update itself every time somebody edits the page?

If it does, stay where you are. Notion Sites does that for free and Super does it with more design control, and this page will say so again at the end. With an agent the site changes when you ask for it, not when the document changes.

If it does not have to, the interesting part is everything that happens after the first publish: versions you can put back, and a way for someone to mark up the published page and have the agent act on it. That is where Birta is a different answer rather than a worse one.

What Notion already gives you for free

Worth putting up front, because a lot of comparisons in this category quietly skip it.

Notion's own help centre says the free plan can "Publish an unlimited number of Notion Sites", "Claim one notion.site domain", and "Turn on search engine indexing for your Sites". That last one matters more than it sounds. It means the free answer is not a private preview link, it is a real indexable site.

Paid plans raise that to five notion.site domains and add a Homepage setting, site customization, and a Google Analytics integration.

Your own domain is the one thing that sits outside the plan. Notion sells it as a separate add-on at "$10 per month", or $8 with annual billing, and the wording is per domain: "For each custom domain you want to use with Notion Sites, you'll have to purchase a separate custom domain add-on." Up to 25, bought at workspace level.

All of that was read from Notion on 5 September 2026. Vendor pricing moves, so check it before you decide anything on the strength of a number here.

The tools that keep the site following the page

Two products rank on this search for a reason, and if a site that follows the document is what you want, they are better answers than an agent.

Super calls itself "The #1 tool for turning a Notion document into a website" and puts the value proposition in one line: "Your work stays in a place you control and love, while Super handles the technical parts of publishing it to your website." On sync it is explicit. "Edits in Notion are automatically synced." There is a free plan with unlimited pages, no card and no time limit, holding one active site. The paid plan is $16 per site per month, $144 annually, and brings custom domains, themes, password protection, SEO settings and custom code.

Bullet is the interesting one, because it does not actually sell the same promise. It positions itself as "The Only AI Notion Website Builder" with "Keep writing and building inside Notion, the tool you already love. Bullet AI handles publishing, hosting, speed, and security", and its own comparison table, read on 6 September 2026, lists "Manual Publishing" and "Rollback to Previous version" among the rows where it claims an advantage. So Bullet sits closer to the publish-when-you-say-so side of this page than to Super's. Its own table puts it at $9 a month against Super's $16.

Notion Sites needs no third product at all. Its publishing help says that "As you make changes to the content in your Notion page, the Site will update automatically", which is the whole feature in one sentence.

Both prices read 5 September 2026, the Bullet feature rows on 6 September.

How the content actually gets across

Both sides of this comparison have an agent connection, and Notion's reaches further into Notion than Birta's ever will.

Notion runs a hosted MCP server at https://mcp.notion.com/mcp. Its documentation says a client "can combine Notion MCP tools to: Search content in Notion and connected sources. Read, create, and update Notion content. Create pages and databases," and names Claude Code, Cursor and Codex among the clients it works with. If the idea of an assistant working through a connection is new to you, that is what this is.

So on this search the reader's agent is very likely already wired into Notion, with permission to read the pages they can read. That is the reader half of the job, done, by the vendor whose content it is.

Now the other half. Notion's supported-tools reference covers search, fetch, creating and updating pages and databases, moving and duplicating them, views and data-source queries, file uploads, comments, users and teams, and tools for driving Notion's own Custom Agents. As of 5 September 2026 it lists nothing for publishing a page to the web, making a page public, creating a Notion Site, or connecting a domain. That tool set mirrors the workspace it belongs to, and publishing a Notion Site is a switch a person flips in the panel, on the far side of the connection.

Birta is built from the connection outwards, so what the agent reaches is the product: projects, files, versions, publishing, domains, forms, leads and review. It has no reader for anybody else's document, and it needs none.

Put the two together and one agent holding both connections reads the page and writes a versioned site, without you leaving the conversation. Nothing keeps them in step afterwards, which is the next section, and it is the one real difference on this page.

Automatic on edit, or published when you say so

Notion Sites and Super hold the site against the page. You edit a paragraph and the public version changes, with nothing else to do and nobody to ask. For a handbook, a changelog, a help centre or anything else still being written, that is not a feature you would trade away.

Publishing through an agent works the other way round. The site is a set of files that went live at a moment you chose. Your next Notion edit does not reach it. You say "put the new pricing up" and a new version goes out.

These are opposite defaults, and the cost sits in a different place for each. Automatic sync means a half-finished sentence in Notion is a half-finished sentence on the public site for as long as it takes you to fix it. On-request publishing means the site can quietly fall behind the document, and it is on you to notice.

What the on-request side buys is the thing the automatic side structurally cannot have. If the site only ever changes at a moment you picked, then every one of those moments can be kept, named and put back. Every successful publish becomes a version, the last ten stay available, any of them can go live again with its original files, and each downloads as a single archive. There is nothing to roll back to when the site is a live mirror of a document.

Send a version out for review

Here is the part that has no equivalent on the other side of this comparison, and it is worth spelling out because it does not look like a hosting feature.

Every version, draft or published, has its own permanent address. create_version and publish_version hand that address back to the agent, which hands it to you. You send it to the client, the colleague or the person who wrote the copy.

They need no account. A project's version addresses open to whoever holds the link by default, so the guest passes a signed handoff and gets a nickname to sign their remarks with. No sign-up wall between the person reviewing your page and the page.

Then they mark up the page itself. They click the heading, the button or the paragraph they mean, and the remark pins to that element, in the browser, on the version you sent. The agent reads them with list_version_comments and each thread arrives with its number, the page and the element it points at, whether it is open or closed, and every message in it with its author and time. Thread numbers stick, so "do number 3" a week later still means one specific remark. The product tells the agent to "make the changes in this same draft, and tell them to refresh the same page", so the reviewer keeps one tab open through the whole round.

One boundary, on purpose: the agent reads remarks and changes the site. It cannot post a reply into a thread or mark one resolved, and the attempt is refused if it tries. Answering a remark is a change to the page, not a message.

Remarks also go out by mail. Everyone with access to the project gets one digest of what was written, roughly 15 minutes behind, minus whatever they wrote themselves. Nobody has to sit watching the tab.

None of this is gated by plan. It works on the free tier, and the version-remarks guide is the reader's walkthrough.

Against that, here is what the other side has, read at the vendors' own documentation on 6 September 2026. Notion has comments, and they live in the document rather than on the site. Its sharing help notes that "page visitors will need to be logged into Notion if they want to comment on or edit your page", and the Notion Sites pages describe a visitor as someone who can view, search and duplicate the Site, with nothing about commenting among the site customization settings. Super's site lists no commenting, review or annotation feature. Neither does Bullet's own comparison table.

A reviewer who has a Notion account and access to the document genuinely has the better place to discuss a draft. The moment the thing being reviewed is the page a stranger will see, that conversation has to move somewhere else. On Birta it stays on the page, at the version's own address, and the agent reads what came back.

Compare the work after the first publish

Notion takes more rows than Birta, which is what you would expect when one product is a whole workspace with publishing attached. The rows that go the other way are not scattered, though. They all sit after the moment the site goes public: putting a bad publish back, getting remarks on the page from someone without an account, and where the form submissions land.

Stay with Notion when…

Stay when the content is still being written. If the page changes weekly and the site is supposed to reflect that, everything else is a detail. Notion Sites does it for nothing and Super does it with more design control.

Stay when the free tier is already enough. Unlimited indexable sites at a notion.site address, from the tool you're in all day, is a genuinely good deal and plenty of readers of this page should just take it.

Stay when your team edits the site directly. Notion is built for several people working in one document, with a real editor and comments in the margin. Birta has no editor, so "someone else updates the copy" becomes "someone else asks the agent".

And stay if $10 a month for a domain is fine. It's a real price for a real thing, and it comes with everything already working.

Birta fits when…

The site is its own object now. It was a Notion page while it was being written, and what it needs from here is an address, a stable public version, and a way for people to reply. A launch page, a client deliverable, a signed-off spec, a portfolio that isn't rewritten every Tuesday.

Choose Birta when a bad publish has to be reversible. Ten versions stay available, any of them can go live again with the original files, and the agent can do it from the same conversation that broke the site.

Choose it when the page has to go past someone else before it counts. You send the version address, they mark up the page in their browser with no account, the agent reads the remarks and publishes the fixed version. That loop is the same on the free tier as on a paid one.

Choose it when the site needs a real lead form and you'd rather the replies didn't land back inside the workspace. The agent declares the fields, submissions show up in the project's panel, and everyone with access gets one email digest roughly 15 minutes after the first arrives.

Choose it when the price of a domain decides it. $12 a month on Solo includes one, against a Notion paid plan plus $10 per domain on top.

The tradeoffs are the ones from the table, and they are not subtle. The free tier carries a badge you can't remove and won't take a custom domain, and it caps leads at 10 a month. There's no payment acceptance yet at any tier. There's no editor. And the site will not follow your Notion page: it changes when you ask it to, and never on its own. That last one is the trade you are making, and what you get for it is a version you can put back and a remark your agent can act on.

If what you actually have is one document you want people to read at a link, there's a shorter route than either of these.

If you're moving the content out

For a page or two, there is nothing to move by hand. Give the agent the link, or just name the page if your agent is already connected to the workspace. It reads the content and builds the files.

For a large tree it is worth starting from Notion's export instead, because one download beats a hundred reads. Notion documents HTML as one of its formats, and if you "Switch on Include subpages" the download arrives with the child pages "neatly organized in their own folders", and "These folders will also contain the images and other assets on your pages saved separately."

Either way there is a step in the middle, and the agent does it. What comes out of Notion is content, not a designed site: the look of the page happened on Notion's side. Birta wants an index.html at the root of what you publish and refuses outright without one, naming the file it found if there's a candidate deeper in the tree.

1. Step 1Hand the source to your agentA link for a published page, the page itself through Notion's connection, or an HTML export with Include subpages switched on for a whole tree.
2. Step 2Have it build the siteAn index.html at the root, the assets beside it, the navigation you actually want. What an agent does with a folder is its own subject.
3. Step 3Review the version, then publish and move the domainSend the version address round, let the remarks come back, publish once the copy passes, and repoint DNS after that.

The middle step is where the work is, and publishing a folder of mixed material covers what an agent has to produce before anything can go live.

One thing that won't travel: anything that depended on being a Notion page. Databases, live views, in-document comments, collaborators. If those are load-bearing, this isn't a migration, it's a copy that stops being the source of truth.

The decision

If the site has to follow the page, this comparison has one answer and it isn't us. Notion Sites updates automatically and costs nothing, Super does the same with real design control at $16 a site.

If the site is finished enough to be its own thing, the agent gets the content across in one conversation and the fork is about what comes next: your own domain at $12 rather than a plan plus an add-on, ten versions you can put back, and remarks left on the published page by someone who never made an account.

Frequently asked questions