简体中文
EnglishWebsite review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Remarkbox?
Remarkbox is a hosted comment system for websites, built to be embedded in a page so a conversation sits with the content it belongs to. It is open source, and its pitch is deliberately minimal: no ads, no tracking, and a lightweight embed aimed at keeping page load speeds fast.
It is most relevant to people running static sites, where publishing is fast but comments are missing by default. The founder's own account is that he moved a WordPress blog to a static site in 2014, found existing embedded comment products either slowed the site down or served ads, and built Remarkbox instead.
What it does
- Embedded comments that appear as part of your page rather than a separate forum.
- Markdown support, including syntax-highlighted code blocks — useful for technical blogs where readers paste snippets.
- Comment content treated as search traffic: the stated goal is to capture long-tail keyword traffic from user-generated comments.
- Control over behaviour and appearance, so comments can be styled to match your site.
- Standalone forum mode, where Remarkbox can operate as a forum on its own rather than only as an embed.
Who it suits
- Writers on static site generators (Hugo, Jekyll, Eleventy and similar) who want comments without adding a heavy third-party script.
- Technical bloggers whose readers benefit from Markdown and code blocks.
- Site owners who object to ad-supported comment widgets and the tracking that usually comes with them.
Trade-offs to weigh
The "pay what you can" model is a real difference from ad-funded comment platforms, but it also means the service depends on reciprocity and trust rather than a conventional subscription. For a hobby blog that is fine; for a business that needs contractual guarantees, support SLAs or predictable costs, it is worth checking the current plans page before committing. The minimalist default also means fewer built-in extras than large comment platforms bundle in.
A useful next step: open the Remarkbox demo page and scroll to the bottom to see the embed in place, then compare its load behaviour against whatever you use now. If you run a static site and your current comment widget is the slowest resource on the page, that comparison will tell you more than any feature list.
How does Remarkbox help improve my site's SEO?
Remarkbox's SEO pitch is narrower than "better rankings" in general. Its stated goal is to help capture search traffic from long-tail keywords that appear in your readers' comments, while keeping your pages fast enough that the comment system doesn't drag down load speed. Search engines rank using page load speed, and the page argues that many free comment systems prioritize ad revenue over speed. Remarkbox's answer is a lean, minimalist embed by default, with no ads or tracking, so comments feel like part of the page rather than a heavy third-party widget.
What that means in practice
- Comment text is user-generated content that often contains specific phrases people actually search for. If that content is crawlable, it can help you surface for those long-tail queries.
- A lightweight embed matters because the slowest resource on a page sets the ceiling for how fast the page feels and how it's assessed.
- Ads and tracking scripts in a comment widget work against both goals: they add weight and they can pull reader attention away from your site.
Where the trade-off sits
| If your priority is… | Remarkbox fits when… | Watch out for… |
|---|---|---|
| Fast static site with discussion | You want comments that don't undo your speed work | You still need to confirm crawlability of embedded comments for your setup |
| Owning the conversation | You dislike ad-driven widgets that hijack traffic | Moderation still falls on you |
| Low cost | The stated model is pay-what-you-can, with a $0 option for one moderator across a few domains | Pricing is set by contribution, not a fixed tier |
A concrete scenario
You run a static blog and a post about, say, repairing a specific appliance draws comments where readers describe their exact model and symptom. Those phrases are long-tail search material. If the comment system is fast and its content is visible to crawlers, that discussion can earn traffic you'd never have targeted yourself. If the widget loads slowly or hides comments behind scripts, you lose both the speed benefit and the content benefit.
Next step
Test it on one high-comment page: measure load time before and after, then check whether the comment text is actually being indexed. The demo on the homepage shows the embed in action, and setup details are at Remarkbox. If you want to compare against other hosted options, look at Disqus and Commento on the same two criteria: page weight and whether comments are crawlable.
Can I use Remarkbox on a static site?
Yes. Remarkbox is designed for exactly that situation. Its founder describes starting the project after moving a WordPress blog to a static site and needing a way for readers to keep commenting. Remarkbox is a hosted comment service you embed in your pages, so your static generator does not need a database or server-side comment code.
How it fits a static workflow
- You add an embed snippet to your page template; the comment thread loads from Remarkbox's servers.
- Because the site stays static, your hosting and build process are unchanged.
- The service handles storage, moderation and display of comments.
- It supports Markdown and syntax-highlighted code blocks, which suits technical blogs and documentation.
- Remarkbox says it optimizes for speed and a minimalist look, aiming to feel like part of your site rather than an add-on.
What to weigh
| Consideration | Why it matters on a static site |
|---|---|
| Hosted dependency | Comments require a third-party service to be reachable; if it is down, threads do not render. |
| Page speed | Any embedded comment system adds a request; Remarkbox positions speed as a priority, but you should still test your own pages. |
| Moderation | You need someone to review comments; a static site gives you no built-in admin panel. |
| Pricing model | The page describes a pay-what-you-can approach rather than a fixed price, with no credit card required for setup. |
| Data and control | You control behavior and appearance, but comments live with the provider. |
A practical next step
Pick one article on your static site and embed Remarkbox there first. Check how the thread affects your load time and how well it matches your typography before rolling it out across the whole site. If you want to see it working before committing, the Remarkbox site itself runs on Remarkbox, so its own comment area is a live demo. You can also compare the approach with other hosted options such as Disqus or utterances, which takes a different route by storing comments in GitHub issues.
Is Remarkbox free or paid, and what are the costs?
Remarkbox is best described as pay-what-you-can rather than strictly free or fixed-price. Its own page lists a production yearly plan at $0/mo with a “pay what you can” model, aimed at one moderator using it on a few domains with control over behavior and appearance. There is no required credit card for setup, and the site says its business model relies on reciprocity and trust rather than setting a price.
In practice, that means your cost depends on whether you choose to contribute and what level of service or support you need. The public page does not list mandatory paid tiers, per-comment fees, or overage charges, so you should treat any specific dollar amount beyond the $0/mo entry point as something to confirm directly.
For a concrete case: a personal static blog with one moderator and modest traffic can start on the $0/mo production yearly option. A larger publication with multiple moderators, heavier traffic, or a need for formal support should ask the founder about appropriate contribution or plan terms before committing.
Next step: use the site’s setup and plans pages, then contact the founder if your use case goes beyond one moderator on a few domains. If you are comparing hosted comment systems, evaluate them by moderation workload, page-speed impact, ad/tracking behavior, and export or migration options, since those practical differences usually matter more than a headline price.
How do I set up Remarkbox on my website?
The setup is a two-part job: create a namespace in the hosted dashboard, then paste a small embed snippet where you want comments to appear. Remarkbox describes itself as a hosted, open-source comment system you embed in your pages, and its page includes a Setup link alongside Demo, FAQ, Meta, About and Plans.
The practical steps
- Start at the setup page. From Remarkbox, follow Setup. The page claims no credit card is required, so you can create the namespace before deciding on payment.
- Create a namespace. Think of this as the container that owns your comments, moderation settings and appearance. The page's pricing section describes the free tier as "one moderator on a few domains with complete control over behavior & appearance," so a namespace maps to the site or group of domains you want covered.
- Copy the embed code. Remarkbox is designed to be embedded, and the page invites you to "scroll to the bottom of this page" to see it in action — the same widget you'd place on your own pages.
- Paste it into your template. Put the snippet at the point in your layout where the conversation should sit. On a static site generator, that usually means the post or article template rather than every page, so comments land under each piece of content instead of on your homepage.
- Style it to match. Because the free tier includes control over appearance, adjust colors, width and typography so the thread reads as part of your site. The page stresses comments should "feel like part of your site, not something bolted on."
- Test on a live URL. Publish one post, open it in a private window and post a test comment. Then check the same page on a phone, since an embedded widget can behave differently in a narrow layout.
- Moderate and configure. Sign in as the moderator, decide whether comments publish immediately or wait for approval, and confirm notifications reach you.
A quick decision guide
| Situation | What to do |
|---|---|
| Static site with no comment backend | Embed Remarkbox in the post template |
| Several domains, one person moderating | Use one namespace and add the domains |
| You want a standalone discussion area | The page notes Remarkbox "may operate as a forum in stand alone mode" — contact the founder if that interests you |
| Performance is your main worry | Load-test one article before rolling the snippet out site-wide |
What to watch
The page makes two claims worth testing yourself rather than assuming: that Remarkbox keeps pages fast, and that it helps capture search traffic from long-tail keywords in user comments. Both depend on your theme, hosting and how much JavaScript you already load. If your site is already heavy, measure before and after on a single post.
The other trade-off is the pay-what-you-can model. The page states the business "depends on reciprocity and trust," with pricing set by you rather than by a fixed rate. That is attractive if you want to support a small independent project, but it also means you should be comfortable with a service run by one person — the founder describes starting it in 2014 and launching after three years of work. If you need enterprise guarantees or a formal support contract, that is a real consideration, not a dealbreaker.
Next step: open Remarkbox, click Setup, create your namespace, and embed it on one test post before touching your whole site.
Does Remarkbox show ads or track users?
Remarkbox states that it is a hosted comment system without ads or tracking. That is the direct answer from the service itself: its own page describes it as "hosted comments without ads or tracking."
H3 What that means in practice
For a site owner, the practical value is that reader comments are less likely to be monetized against the reader's interests. Remarkbox also says its business model depends on reciprocity and trust, and its production plan is "pay what you can," which is consistent with a service that is not funded by advertising.
The page also frames free comment systems critically, saying they often have a business model that prioritizes ad revenue over page speed and can hijack traffic and readers. Remarkbox positions itself as the opposite: minimalist by default, optimized for speed, and designed to feel like part of your site rather than something bolted on.
H3 What is not claimed
The page says no ads or tracking, but it does not provide a detailed privacy policy on the evidence shown. "No tracking" is a broad phrase, and it can mean different things: no advertising cookies, no cross-site behavioral profiling, or no analytics at all. If your privacy requirements are strict, treat this as a starting point and check the full FAQ and privacy documentation before adopting it.
H3 A useful next step
If you run a static site and want comments without an ad-supported platform, test Remarkbox on one page first. Scroll to the bottom of its own site to see the comment system in action, then compare it with alternatives such as Disqus or Commento on the specific points that matter to you: ad behavior, tracking, page speed, moderation and data ownership.
DigitalOcean, LLC
User reviews (0)