The thing that kills a business blog is almost never the writing. It is the twenty minutes afterwards: logging into the CMS, pasting the text, watching the formatting collapse, fixing the headings one at a time, hunting for the excerpt field, giving up on the meta description.
Do that four times and you start postponing. Postpone twice and the blog is over. Worth solving properly at the start, because it is the part everybody underestimates.
The short answer
Embedding means your posts live in one place and appear on your site through a snippet you install once — new posts show up with no further work. Exporting means taking the finished HTML or Markdown and putting it into your own CMS, where it becomes an ordinary page on your site. Embed removes the repeated work; export gives you complete control. Most people should start with embed.
Embedding: install once, forget about it
You add a snippet to one page of your website — usually /blog. From then on, publishing means approving the post; it appears on your site by itself.
The appeal is that the recurring work goes to zero. There is no second login, no formatting to repair, no field to forget. The structure you wrote survives exactly as written, which matters more than it sounds — headings and lists are what makes a post readable on a phone and quotable by answer engines, and manual copy-paste is precisely where they get flattened.
It also keeps click tracking intact without configuring anything, so you can actually see whether readers went from a post to your service page.
The trade-off is that the posts are rendered by the embed rather than built into your theme, so styling follows the embed's layout rather than your designer's. For most business websites this is unnoticeable. On a heavily designed site it can look slightly like a guest.
Embedding suits you if you are the person doing everything, if your CMS is painful, or if your website is looked after by someone you have to email.
Exporting: your page, your theme, your problem
Export gives you the post as HTML or Markdown, and you put it into WordPress or whatever you run. It becomes a page on your site like any other.
The advantages are real. Complete design control, the post sits natively inside your own templates, and you own the markup outright — nothing depends on anyone else's service continuing to exist. If you have a developer, or a CMS you already like, this is the cleaner outcome.
The cost is that it is manual, every time, forever. Ten or fifteen minutes per post if your CMS is well behaved, longer if it is not. That is fine at one post a month and genuinely annoying at four, and it is the friction that quietly ends most publishing schedules.
Export suits you if design consistency matters, if a client's security policy forbids third-party snippets, or if someone else handles publishing anyway and the time is not yours.
The SEO question everyone asks
Does embedded content rank? It can, and the honest answer is that the publishing method is not the important variable.
What matters is that a search engine can read substantive text when it visits the page, and that the content sits on the domain that takes your enquiries rather than somewhere else entirely. Both are achievable either way. An empty shell that loads nothing until a script runs is a problem; so is a beautifully exported post nobody links to.
The genuinely consequential decision is same-domain publishing, and it applies to both paths equally. Content on yourdomain.co.nz builds up your website. Content parked elsewhere builds up somebody else's.
The mixed approach
Plenty of people end up doing both, and it is a sensible outcome rather than a compromise.
Embed the ordinary flow of posts, where the value is in answering questions consistently and nobody will ever notice the template. Then export the two or three cornerstone pages that deserve custom layout — the big pricing guide, the page you send to every prospect — and build those properly into your theme.
That keeps the routine cheap and the flagship pages exactly as you want them.
If you publish for clients
Agencies, hosting companies and web designers have a different calculation, because the per-post friction multiplies by the number of clients.
Fifteen minutes of manual publishing is nothing on one site. Across thirty client sites it is seven and a half hours a month of work you cannot bill for, and it is the reason most agencies quietly stop offering content after the first year. An install-once approach per client is frequently the difference between a service that scales and one that becomes a chore.
The second consideration is what you can show at the end of the month. "We published four posts" is an invoice nobody enjoys paying. "These four posts sent eleven people to your quote page" is a renewal, and it needs tracking that survives however you publish.
The checks worth doing either way
Whichever path, look at the first few posts properly before assuming the pipeline works.
- Open it on a phone. Most of your readers are on one. Headings should be obvious and paragraphs should not run to fifteen lines.
- Click the internal link. The link to your service page is the entire commercial point of the post, and it is the thing most likely to have broken in transit.
- Check the title and description that appear in search. Not the heading on the page — the title tag. These get lost constantly in manual publishing.
- Search for it a week later. Type
site:yourdomain.co.nzand confirm the post is there. If your posts are not being indexed, nothing else on this list matters.
Pick the one you will still be doing in a year
Both paths work. Blog Lab does both — a snippet for the sites that want it, HTML and Markdown export for the ones that do not, and you can see the whole process before committing to either.
The thing to be honest about is your own tolerance for repetition. If publishing takes fifteen minutes and you are the one doing it, you will publish less than you intend to, and the blog will fade for reasons that have nothing to do with whether the writing was any good. Choose for the version of you in month eight, not the enthusiastic one in week one.