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

The short answer

A Notion page can end up as a site published through Birta, and the route is the agent you already talk to: it reads the page from the link, or through Notion's own hosted connection if the page is private, then writes the files into a Birta draft. Birta never opens Notion itself. One question decides the rest. Does the site have to update itself whenever somebody edits the page? If yes, stay where you are: Notion Sites does that free, and Super does it with more design control. If no, what matters is what happens after the first publish.

What Notion already gives you for free

Notion's 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: the free answer is a real indexable site, not a private preview link.

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

Your own domain sits outside the plan, sold as an add-on at "$10 per month", $8 annually, and priced 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, at workspace level. Check before deciding on a number here.

The tools that keep the site following the page

If a site that follows the document is what you want, two products do it better than an agent.

Super is explicit about the mechanism: "Edits in Notion are automatically synced." Its free plan holds one active site with unlimited pages, no card and no time limit; the paid plan is $16 per site per month and adds custom domains, themes, password protection and SEO settings.

Bullet does not quite sell the same promise. Its own comparison table claims "Manual Publishing" and "Rollback to Previous version" as advantages, which puts it on the publish-when-you-say-so side of this page. It lists itself at $9 a month against Super's $16.

Notion Sites needs no third product: its help says "As you make changes to the content in your Notion page, the Site will update automatically."

How the content actually gets across

Both sides have an agent connection, and Notion's reaches further into Notion than ours ever will. It runs a hosted MCP server at https://mcp.notion.com/mcp whose clients "can combine Notion MCP tools to: Search content in Notion and connected sources. Read, create, and update Notion content. Create pages and databases," with Claude Code, Cursor and Codex named among them. If an assistant working through a connection is new to you, that is what this is.

So the reader's agent is probably already wired into Notion, with permission to read what they can read. That is the reading half done, by the vendor whose content it is.

The other half is missing there. Notion's supported-tools reference lists nothing for publishing a page to the web, making one public, creating a Site or connecting a domain. 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: versions, publishing, domains, forms, leads, review. 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.

Automatic on edit, or published when you say so

Notion Sites and Super hold the site against the page: edit a paragraph and the public version changes. For a handbook, a changelog or a help centre still being written, that is not a feature you trade away.

Publishing through an agent is the opposite default. The site is a set of files that went live at a moment you chose, and your next Notion edit does not reach it until you say "put the new pricing up".

Each default costs something different. Automatic sync means a half-finished sentence in Notion is a half-finished sentence in public until you fix it. On-request publishing means the site can quietly fall behind the document, and noticing is on you.

What on-request buys is what automatic structurally cannot have. If the site only changes at moments you picked, every one of those moments can be kept, named and put back: the last ten publishes stay, any goes live again with its original files, and each downloads as one archive. A live mirror of a document has nothing to roll back to.

Send a version out for review

Every version, draft or published, has its own permanent address. create_version and publish_version hand it to the agent, which hands it to you, and you send it on.

They need no account: version addresses open to the link holder by default, the guest gets a nickname, and they mark up the page itself, clicking the heading or the button they mean so the remark pins to that element on that version.

The agent reads them with list_version_comments: number, element, open or not, every message with author and time. Numbers stick, so "do number 3" still names one remark a week later. 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. It cannot reply in a thread or resolve one, and the attempt is refused. Remarks go out as one digest roughly 15 minutes behind, minus your own. Nothing is gated by plan; the version-remarks guide is the walkthrough.

The other side has comments, in the document rather than on the site. Notion's sharing help says "page visitors will need to be logged into Notion if they want to comment on or edit your page". Super lists no commenting feature, and neither does Bullet's comparison table.

A reviewer with a Notion account has the better place to discuss a draft. When the thing under review is the page a stranger sees, that conversation moves.

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; from here it needs 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 nobody rewrites on Tuesdays.

• A bad publish has to be reversible. Ten versions stay, any goes live again with the original files, and the agent does it from the conversation that broke the site.
• The page goes past someone before it counts. Send the version address, they mark up the page with no account, the agent reads the remarks and publishes the fix. Same on the free tier.
• The site needs a real lead form and the replies should not land back inside the workspace.
• A domain decides it. $12 a month on Solo includes one, against a Notion paid plan plus $10 per domain.

The trades are not subtle: the free tier carries a badge you cannot remove, takes no custom domain and caps leads at 10 a month, there is no payment acceptance at any tier, no editor, and the site will not follow your Notion page. That last one is the deal: it changes when you ask, and you get a version you can put back.

If what you have is one document people should read at a link, there is a shorter route.

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 name the page if it is already connected to the workspace, and it reads the content and builds the files.

For a large tree, start from Notion's export, because one download beats a hundred reads. Notion documents HTML as a format, and with Include subpages switched on the download arrives with child pages "neatly organized in their own folders", which "will also contain the images and other assets on your pages saved separately."

Either way the agent does the step in the middle. What comes out of Notion is content, not a designed site, because the look happened on Notion's side. Birta wants an index.html at the root and refuses without one, naming any candidate it finds 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 3Publish it, then review and move the domainThe agent publishes when the work is done and hands back the site address and the version address; send the version address round, let the remarks come back into the next version, and repoint DNS once the copy passes.

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