Carrd Blog: Every Way to Add One in 2026, Honestly Compared

There is no Carrd blog feature. Carrd builds one-page sites, and nothing in its product or its documentation covers posts, collections, or a CMS. So the real question is not how to turn a blog on. It is what you attach to the site you already have.

You have four options, and they are not equal. You can link out to Medium or Substack, embed a third-party widget inside a Carrd section, run a blog on a subdomain like blog.yourdomain.com, or route a blog to yourdomain.com/blog. The first two are quick and cost you the search value. The third works today with a DNS record. The fourth is the strongest for SEO and it is the one Carrd cannot do on its own hosting, which nobody tells you before you start. Here is all four with the trade-offs stated plainly.

Why there is no Carrd blog feature, and why that is not a flaw

Carrd does one thing extremely well: a single page, published in an afternoon, for nine to forty-nine dollars a year, the Pro range Carrd lists as of August 2026. That focus is the whole product.

The focus is also the constraint. A Carrd site is one page. What looks like multiple pages is the Sections feature, which Carrd's own documentation describes as a way to divide a site into named regions that "simulate the effect of having multiple pages on a one-page site." Section links are hash URLs, written as #section-name. They are anchors within one document, not separate addresses.

That distinction matters more than it sounds. A blog earns organic traffic through many indexable URLs, each targeting a different query, each carrying its own title, meta description, canonical tag, and Article schema. A hash fragment is not a URL Google indexes separately. So the forum advice about adding a "blog section" to your Carrd site produces a page with posts stacked on it. It does not produce a blog that ranks.

None of this is a reason to leave Carrd. Your one-page site is fine. The blog is a separate layer, and the only decision is where that layer lives.

Option 1: Link out to Medium, Substack, or Notion

The fastest route. Publish on Medium or Substack, then point a button on your Carrd site at it.

Carrd even ships a feature for this. On Pro Plus ($49/year), the Redirects feature lets you map slash URLs to destinations in a /request=destination format. The example in Carrd's own documentation is literally /blog=https://medium.com/untitled. Carrd states that "All redirects are handled as 301 redirects."

Read that last line again, because it is the entire problem. A 301 is a permanent redirect. Someone who types yourdomain.com/blog lands on medium.com with medium.com in the address bar. Google follows the same hop and files every one of your posts under Medium's domain.

Here is what that costs over a year of writing. Every post builds topical authority for Medium. Every backlink is a link to Medium. Every reader who finishes your article sees Medium's membership upsell and its recommendations for other writers' work. You wrote the content, you paid for it, and the compounding asset sits on someone else's domain. When you eventually want that traffic on your own site, you start from zero, because you never owned a ranking URL. Substack behaves the same way, with a newsletter wrapper around it.

Now the correction most Carrd guides get backwards: all three of these platforms do sell custom domains. Medium connects one to a profile or publication for anyone with an active membership. As of August 2026, Substack charges a one-time $50 fee per publication, and Notion Sites sells a custom domain add-on at $10/month, or $8/month billed annually, on top of a paid Notion plan. So the criticism is not that your posts are stuck on someone else's URL forever. It is narrower and it still bites.

What none of them can do is serve the blog at yourdomain.com/blog while Carrd keeps serving yourdomain.com. Each one wants a hostname to itself. Notion is explicit about it: its help documentation requires the domain you connect to include a subdomain, typically www, and tells you to point the root domain there with a registrar redirect. So with Carrd holding your root domain, a custom domain on any of these three lands your blog on a subdomain, which is Option 3's architecture at Option 3's cost, without Option 3's control over templates, schema, or page speed. And if you skip the custom domain and take the Carrd redirect above, you are back to the 301 and Medium keeps the URL.

The narrow case where this is still the right call: you are writing for an existing audience on that platform and the blog is distribution rather than acquisition. Past that stage, the Medium alternatives comparison covers what to move to.

Verdict: takes ten minutes. Free, and the asset is theirs. Pay for their custom domain and the asset is yours but it sits on a subdomain you do not control the output of. Fine for distribution either way, wrong for organic growth.

Option 2: Embed a blog widget in a Carrd section

Carrd supports embedded custom code. The Building documentation covers embedding custom HTML, CSS, and JavaScript, plus IFRAMEs. The Embed element requires Pro Standard ($19/year) or higher; it is not available on the free tier or on Pro Lite.

So you can drop a script tag from a third-party blog widget into a Carrd section and get posts rendering on your page. Several tools sell exactly this. The output is where it falls apart. A widget injects post content into the page after load, using client-side JavaScript. An iframe loads the content in a separate document belonging to the vendor's domain. In both cases the HTML your domain actually serves contains a container and a script, not your article.

Google can render JavaScript, so this is not a guaranteed failure. It is a guaranteed handicap. Rendering happens on a second pass and on a budget, so indexing is slower and less reliable. More importantly, a widget cannot give each post a real URL on your domain with its own title tag, meta description, canonical, and structured data, because there is only one Carrd page underneath it. You end up with one URL trying to rank for everything you have ever written. Iframes have a sharper version of the same problem: the content inside the frame is attributed to the vendor's domain. The mechanics of both are in embedding a blog into a website.

Verdict: looks native, indexes poorly. Reasonable for a "latest posts" teaser strip on your Carrd page. Not a place to put the posts themselves.

Option 3: Run the blog on a subdomain

Point blog.yourdomain.com at a hosted blog platform with one DNS record. Your Carrd site keeps serving the root domain, untouched. Nothing about your Carrd setup changes.

This works today. No proxy, no Worker, no infrastructure to maintain. Point the record at a hosted blog platform (Superblog takes one CNAME) and you have indexable URLs, schemas, and page speed without touching your Carrd site.

The cost is architectural. Search engines treat a subdomain as its own host. Backlinks your blog earns strengthen blog.yourdomain.com, and that authority does not flow cleanly to the root domain where your product and pricing live. Internal links between the two are cross-host links. You are building two properties instead of one.

Google's public position is that subdomains and subdirectories are treated about the same, which is true of crawling and indexing mechanics. What practitioners keep observing after consolidation migrations is a different story. The full argument on both sides, including when a subdomain is genuinely correct, is in subdomain vs subdirectory.

Verdict: real blog, real URLs, fifteen minutes of DNS. Splits your authority across two hosts.

Option 4: A subdirectory blog at yourdomain.com/blog

This is the setup you want if the blog exists to grow the business: yourdomain.com/blog/post-name/, same host as your Carrd landing page, one link graph, one domain accumulating everything.

Now the honest part, which other Carrd blog guides skip.

Carrd cannot do this on its own hosting. A subdirectory blog requires a reverse proxy: a rule sitting in front of your domain that catches requests for /blog and /blog/*, fetches the response from wherever the blog is hosted, and returns it without changing the URL in the browser. Carrd has no such feature. Its documentation covers custom domains, redirects, sections, forms, and embeds, with no path routing, rewrite, or proxy capability anywhere in the product. Its Site Files feature, the closest thing to an escape hatch, only exposes supporting files like robots.txt and ads.txt. The Redirects feature from Option 1 is a 301, the opposite of a proxy: it changes the URL instead of preserving it.

So if a tutorial claims it can put a blog at yourdomain.com/blog while Carrd serves your root domain and nothing else changes, that is not accurate. Something has to sit in front of the domain.

What actually makes it work

You put a proxy layer in front of your domain, most commonly Cloudflare, and let it split traffic by path: /blog/* goes to your blog platform's origin, everything else passes through to Carrd.

The sequence, in the order it has to happen:

1. Move your domain's DNS to Cloudflare. Change the nameservers at your registrar. Carrd is unaffected; it only cares that the records resolve.
2. Set up the Carrd custom domain first, with the Cloudflare proxy off. Carrd requires Pro Standard or higher for a custom domain and asks for an A record pointing @ to the target IP address it shows you, plus a CNAME pointing www back to the bare domain. Carrd's documentation then describes an automatic initialization step that can take up to an hour, after which the site is reachable on the custom domain over SSL. Leave those records in DNS-only mode (grey cloud) until initialization finishes. That last step is our own recommendation rather than a documented requirement: with the record unproxied there is nothing in the path but Carrd, so a failure is unambiguously Carrd's provisioning and not your Cloudflare config, and there is exactly one thing to change once it works.
3. Switch the record to proxied and set SSL/TLS to Full (strict). This part Carrd does document. Its troubleshooting page covers turning Cloudflare on and getting the site stuck in a redirect loop, and says setting SSL to Full SSL (Strict) on Cloudflare's end should immediately fix it (carrd.co/docs/sites/troubleshooting). Full (strict) is also what Cloudflare recommends generally, since it validates the origin certificate instead of accepting any certificate the origin presents. Confirm the Carrd site still loads over HTTPS before going further. Cloudflare will not run a Worker on a hostname that is not proxied, so this is a prerequisite, not an optimization.
4. Add a Worker route on yourdomain.com/blog*. The Worker strips the /blog prefix, fetches the matching path from your blog platform's origin, and returns the response. Because the route matches only /blog, requests for anything else still land on Carrd exactly as they do today.

The Worker code, the prefix-stripping rule, the Host header behavior, and the trailing-slash trap that quietly creates duplicate URLs are all in subdirectory blog hosting.

One variation: keep the Carrd site on its free yourproject.carrd.co address, skip Carrd's custom domain entirely, and let the Worker proxy your root path to the Carrd origin and /blog/* to the blog. That gives you control of headers and caching, which Carrd does not expose, at the cost of owning the edge config for your whole site.

Verdict: the correct architecture for SEO, and genuinely more setup than a typical Carrd user signed up for. Budget an afternoon and a working knowledge of Cloudflare. If that is not you today, Option 3 is a legitimate stopping point, and a subdomain can be migrated to a subdirectory later with redirects.

The comparison

Which one to pick

You want your writing in front of an existing Medium or Substack audience. Link out, and treat it as distribution rather than acquisition.

You need something on the page this week and search is not the goal yet. Embed a widget in a section. Replace it when it matters.

You want a blog that ranks, live today. Subdomain. This is the honest default for most Carrd users: real URLs, fifteen minutes, and the only thing you give up is authority consolidation.

Organic search is a channel you are actually investing in. Subdirectory, with Cloudflare in front. Every post compounds onto the domain your product lives on. If you are weighing this against rebuilding the whole site on another platform, don't. The broader version of this decision is in adding a blog to an existing website.

Where Superblog fits

Superblog is the blog layer, not a replacement for Carrd. Your Carrd page stays exactly where it is and keeps doing its job. Superblog runs the blog behind it: the editor, the hosted blog pages, the CDN, SSL, and the SEO engine.

What that means for a Carrd site. Every post ships as a static, pre-rendered page, so there is no JavaScript rendering gamble like the widget route. JSON-LD schemas (Article, FAQ, Organization), the XML sitemap, canonical tags, and Open Graph tags are generated automatically. IndexNow fires on publish, so the search engines on that protocol, Bing and Yandex among them, hear about new posts within minutes rather than waiting for a crawl. Superblog also publishes a machine-readable llms.txt index of your posts. The thing that actually makes AI assistants able to quote you is the same thing that helps Google: the words are in the HTML at the URL, not assembled by a script after the page loads.

Run it on blog.yourdomain.com with a single DNS record today, or on yourdomain.com/blog through the Cloudflare Worker route above, and move between the two later without rewriting anything. Pro is $49/month, Super is $99/month with AI assistance, multilingual SEO, the API, and Zapier. The trial is 7 days with no credit card. Setup detail for this stack is on the blog for Carrd page.

Start the trial, publish one post, and see what an indexable URL on your own domain does.

FAQ

Does Carrd have a blog feature?

No. Carrd has no native blog, CMS, or post management. Its documentation is organized into General, Sites, Building, Forms, Account, and Pro, with nothing for posts or collections. Carrd builds one-page sites, and blogging was never part of the product.

Can I add a blog to my Carrd site?

Yes, by attaching an external blog. You have four routes: link out to a platform like Medium, embed a third-party widget in a Carrd section, run the blog on a subdomain, or route yourdomain.com/blog to a blog platform through a Cloudflare proxy. Only the last two give you indexable pages that build your own domain's authority.

Can I host a blog at mydomain.com/blog if Carrd serves mydomain.com?

Not through Carrd alone. Carrd has no reverse proxy or path routing feature, so the request for /blog never reaches an external blog. You need a proxy layer in front of the domain, typically Cloudflare with a Worker route on yourdomain.com/blog*. Move your DNS to Cloudflare, get the Carrd custom domain working DNS-only first, then enable the proxy and add the route.

Do I need a paid Carrd plan to add a blog?

It depends on the route. A custom domain requires Pro Standard ($19/year) or higher, and so does the Embed element. The Redirects feature that maps /blog to an external URL requires Pro Plus ($49/year). If you take the subdomain route, your blog runs on its own DNS record and your Carrd plan is irrelevant to it.

Will Carrd sections work as blog posts?

Not for search. Carrd sections live on one page and are linked with hash URLs like #section-name. Google does not index a hash fragment as a separate page, so ten posts in ten sections is still one URL competing for every query you write about.

Does redirecting /blog to Medium hurt my SEO?

It does not hurt your existing rankings, but it gives away everything you build afterward. Carrd's redirects are 301s, so the URL changes to medium.com and every post, backlink, and ranking signal is attributed to Medium's domain. A year of writing leaves your own domain exactly where it started.

Can I move from a subdomain blog to a subdirectory later?

Yes. Set up the proxy route, then 301 each subdomain URL to its subdirectory equivalent with identical slugs. You lose some momentum during reindexing and regain it as the root domain absorbs the authority. Starting on a subdomain is a reasonable first move if the Cloudflare setup is not something you want to take on this week.