# VeloCMS — Full Content Dump > Generated: 2026-11-17T13:47:01.312Z > Source: https://velocms.org/llms-full.txt > Index: https://velocms.org/llms.txt > AI Sitemap: https://velocms.org/ai-sitemap.xml This file contains the full text of all VeloCMS help articles, blog posts, and static marketing pages in markdown format for single-fetch LLM ingestion. ## Comparison Pages (/vs/) Each page provides an honest comparison between VeloCMS and the named platform. - [VeloCMS vs Wordpress](https://velocms.org/vs/wordpress) - [VeloCMS vs Ghost](https://velocms.org/vs/ghost) - [VeloCMS vs Substack](https://velocms.org/vs/substack) - [VeloCMS vs Medium](https://velocms.org/vs/medium) - [VeloCMS vs Squarespace](https://velocms.org/vs/squarespace) - [VeloCMS vs Hashnode](https://velocms.org/vs/hashnode) - [VeloCMS vs Emdash](https://velocms.org/vs/emdash) - [VeloCMS vs Aelestra](https://velocms.org/vs/aelestra) - [VeloCMS vs Notion](https://velocms.org/vs/notion) - [VeloCMS vs Webflow](https://velocms.org/vs/webflow) - [VeloCMS vs Framer](https://velocms.org/vs/framer) - [VeloCMS vs Astro](https://velocms.org/vs/astro) - [VeloCMS vs Bubble](https://velocms.org/vs/bubble) - [VeloCMS vs Shopify](https://velocms.org/vs/shopify) - [VeloCMS vs Beehiiv](https://velocms.org/vs/beehiiv) - [VeloCMS vs Kit](https://velocms.org/vs/kit) - [VeloCMS vs Wix](https://velocms.org/vs/wix) - [VeloCMS vs Mailchimp](https://velocms.org/vs/mailchimp) - [VeloCMS vs Carrd](https://velocms.org/vs/carrd) - [VeloCMS vs Circle](https://velocms.org/vs/circle) - [VeloCMS vs Typedream](https://velocms.org/vs/typedream) - [VeloCMS vs Patreon](https://velocms.org/vs/patreon) - [VeloCMS vs Gumroad](https://velocms.org/vs/gumroad) - [VeloCMS vs Lemonsqueezy](https://velocms.org/vs/lemonsqueezy) - [VeloCMS vs Wpengine](https://velocms.org/vs/wpengine) - [VeloCMS vs Buttondown](https://velocms.org/vs/buttondown) - [VeloCMS vs Kofi](https://velocms.org/vs/kofi) - [VeloCMS vs Memberful](https://velocms.org/vs/memberful) - [VeloCMS vs Linkedin Newsletter](https://velocms.org/vs/linkedin-newsletter) - [VeloCMS vs Teachable](https://velocms.org/vs/teachable) - [VeloCMS vs Linktree](https://velocms.org/vs/linktree) - [VeloCMS vs Tumblr](https://velocms.org/vs/tumblr) - [VeloCMS vs Sanity](https://velocms.org/vs/sanity) - [VeloCMS vs Godaddy](https://velocms.org/vs/godaddy) - [VeloCMS vs Hostinger](https://velocms.org/vs/hostinger) - [VeloCMS vs Woocommerce](https://velocms.org/vs/woocommerce) - [VeloCMS vs Format](https://velocms.org/vs/format) - [VeloCMS vs Mighty Networks](https://velocms.org/vs/mighty-networks) - [VeloCMS vs Hugo](https://velocms.org/vs/hugo) - [VeloCMS vs Wordpress Com](https://velocms.org/vs/wordpress-com) - [VeloCMS vs Discourse](https://velocms.org/vs/discourse) - [VeloCMS vs Brevo](https://velocms.org/vs/brevo) - [VeloCMS vs Drupal](https://velocms.org/vs/drupal) - [VeloCMS vs Strapi](https://velocms.org/vs/strapi) - [VeloCMS vs Mailerlite](https://velocms.org/vs/mailerlite) - [VeloCMS vs Hubspot](https://velocms.org/vs/hubspot) - [VeloCMS vs Eleventy](https://velocms.org/vs/eleventy) - [VeloCMS vs Jimdo](https://velocms.org/vs/jimdo) - [VeloCMS vs Cargo](https://velocms.org/vs/cargo) - [VeloCMS vs Contentful](https://velocms.org/vs/contentful) - [VeloCMS vs Storyblok](https://velocms.org/vs/storyblok) - [VeloCMS vs Aweber](https://velocms.org/vs/aweber) - [VeloCMS vs Klaviyo](https://velocms.org/vs/klaviyo) - [VeloCMS vs Jekyll](https://velocms.org/vs/jekyll) - [VeloCMS vs Podia](https://velocms.org/vs/podia) - [VeloCMS vs Honeybook](https://velocms.org/vs/honeybook) - [VeloCMS vs Showit](https://velocms.org/vs/showit) - [VeloCMS vs Kinsta](https://velocms.org/vs/kinsta) - [VeloCMS vs Duda](https://velocms.org/vs/duda) - [VeloCMS vs Blogger](https://velocms.org/vs/blogger) - [VeloCMS vs Leadpages](https://velocms.org/vs/leadpages) - [VeloCMS vs Unbounce](https://velocms.org/vs/unbounce) - [VeloCMS vs Instapage](https://velocms.org/vs/instapage) - [VeloCMS vs Payhip](https://velocms.org/vs/payhip) - [VeloCMS vs Activecampaign](https://velocms.org/vs/activecampaign) - [VeloCMS vs Drip](https://velocms.org/vs/drip) - [VeloCMS vs Disqus](https://velocms.org/vs/disqus) - [VeloCMS vs Commento](https://velocms.org/vs/commento) - [VeloCMS vs Cusdis](https://velocms.org/vs/cusdis) - [VeloCMS vs Clickfunnels](https://velocms.org/vs/clickfunnels) - [VeloCMS vs Elementor](https://velocms.org/vs/elementor) - [VeloCMS vs Divi](https://velocms.org/vs/divi) - [VeloCMS vs Beaver Builder](https://velocms.org/vs/beaver-builder) - [VeloCMS vs Optinmonster](https://velocms.org/vs/optinmonster) - [VeloCMS vs Getresponse](https://velocms.org/vs/getresponse) - [VeloCMS vs Keap](https://velocms.org/vs/keap) ## Alternatives Roundup Pages (/alternatives-to/) Each page ranks VeloCMS against several alternatives to the named platform, with an honest comparison table. - [Best Alternatives to Wordpress](https://velocms.org/alternatives-to/wordpress) - [Best Alternatives to Ghost](https://velocms.org/alternatives-to/ghost) - [Best Alternatives to Substack](https://velocms.org/alternatives-to/substack) - [Best Alternatives to Medium](https://velocms.org/alternatives-to/medium) - [Best Alternatives to Squarespace](https://velocms.org/alternatives-to/squarespace) - [Best Alternatives to Hashnode](https://velocms.org/alternatives-to/hashnode) - [Best Alternatives to Wix](https://velocms.org/alternatives-to/wix) ## Niche Landing Pages (/for-*) Each page explains how VeloCMS and a recommended theme solve a specific audience's publishing needs, with a comparison table against alternatives. - [VeloCMS for academic researchers](https://velocms.org/for-academic-researchers) - [VeloCMS for accountants](https://velocms.org/for-accountants) - [VeloCMS for agencies](https://velocms.org/for-agencies) - [VeloCMS for ai prompt engineers](https://velocms.org/for-ai-prompt-engineers) - [VeloCMS for amateur astronomers](https://velocms.org/for-amateur-astronomers) - [VeloCMS for amateur historians](https://velocms.org/for-amateur-historians) - [VeloCMS for amateur radio operators](https://velocms.org/for-amateur-radio-operators) - [VeloCMS for antique dealers](https://velocms.org/for-antique-dealers) - [VeloCMS for aquarists](https://velocms.org/for-aquarists) - [VeloCMS for architects](https://velocms.org/for-architects) - [VeloCMS for beekeepers](https://velocms.org/for-beekeepers) - [VeloCMS for birders](https://velocms.org/for-birders) - [VeloCMS for bloggers from medium](https://velocms.org/for-bloggers-from-medium) - [VeloCMS for board game designers](https://velocms.org/for-board-game-designers) - [VeloCMS for bonsai growers](https://velocms.org/for-bonsai-growers) - [VeloCMS for bookbloggers](https://velocms.org/for-bookbloggers) - [VeloCMS for car bloggers](https://velocms.org/for-car-bloggers) - [VeloCMS for chess content creators](https://velocms.org/for-chess-content-creators) - [VeloCMS for cigar aficionados](https://velocms.org/for-cigar-aficionados) - [VeloCMS for climate tech writers](https://velocms.org/for-climate-tech-writers) - [VeloCMS for coffee bloggers](https://velocms.org/for-coffee-bloggers) - [VeloCMS for coin collectors](https://velocms.org/for-coin-collectors) - [VeloCMS for comedy writers](https://velocms.org/for-comedy-writers) - [VeloCMS for comic book collectors](https://velocms.org/for-comic-book-collectors) - [VeloCMS for cosplay creators](https://velocms.org/for-cosplay-creators) - [VeloCMS for craft distillers](https://velocms.org/for-craft-distillers) - [VeloCMS for creators](https://velocms.org/for-creators) - [VeloCMS for dance instructors](https://velocms.org/for-dance-instructors) - [VeloCMS for developers](https://velocms.org/for-developers) - [VeloCMS for diy bloggers](https://velocms.org/for-diy-bloggers) - [VeloCMS for doctors](https://velocms.org/for-doctors) - [VeloCMS for dropshippers](https://velocms.org/for-dropshippers) - [VeloCMS for etsy sellers](https://velocms.org/for-etsy-sellers) - [VeloCMS for expat bloggers](https://velocms.org/for-expat-bloggers) - [VeloCMS for fashion bloggers](https://velocms.org/for-fashion-bloggers) - [VeloCMS for film critics](https://velocms.org/for-film-critics) - [VeloCMS for financial advisors](https://velocms.org/for-financial-advisors) - [VeloCMS for fitness coaches](https://velocms.org/for-fitness-coaches) - [VeloCMS for food bloggers](https://velocms.org/for-food-bloggers) - [VeloCMS for fountain pen enthusiasts](https://velocms.org/for-fountain-pen-enthusiasts) - [VeloCMS for game devs](https://velocms.org/for-game-devs) - [VeloCMS for gamers](https://velocms.org/for-gamers) - [VeloCMS for gardeners](https://velocms.org/for-gardeners) - [VeloCMS for genealogy researchers](https://velocms.org/for-genealogy-researchers) - [VeloCMS for hackers](https://velocms.org/for-hackers) - [VeloCMS for hospitality bloggers](https://velocms.org/for-hospitality-bloggers) - [VeloCMS for illustrators](https://velocms.org/for-illustrators) - [VeloCMS for indie makers](https://velocms.org/for-indie-makers) - [VeloCMS for interior designers](https://velocms.org/for-interior-designers) - [VeloCMS for knife collectors](https://velocms.org/for-knife-collectors) - [VeloCMS for knitters and crocheters](https://velocms.org/for-knitters-and-crocheters) - [VeloCMS for language tutors](https://velocms.org/for-language-tutors) - [VeloCMS for lawyers](https://velocms.org/for-lawyers) - [VeloCMS for life coaches](https://velocms.org/for-life-coaches) - [VeloCMS for magicians](https://velocms.org/for-magicians) - [VeloCMS for makeup artists](https://velocms.org/for-makeup-artists) - [VeloCMS for mental fitness coaches](https://velocms.org/for-mental-fitness-coaches) - [VeloCMS for minimalism bloggers](https://velocms.org/for-minimalism-bloggers) - [VeloCMS for music critics](https://velocms.org/for-music-critics) - [VeloCMS for musicians](https://velocms.org/for-musicians) - [VeloCMS for mycologists](https://velocms.org/for-mycologists) - [VeloCMS for newsletter writers](https://velocms.org/for-newsletter-writers) - [VeloCMS for nonprofits](https://velocms.org/for-nonprofits) - [VeloCMS for nutritionists](https://velocms.org/for-nutritionists) - [VeloCMS for parenting bloggers](https://velocms.org/for-parenting-bloggers) - [VeloCMS for personal finance bloggers](https://velocms.org/for-personal-finance-bloggers) - [VeloCMS for pet bloggers](https://velocms.org/for-pet-bloggers) - [VeloCMS for photographers](https://velocms.org/for-photographers) - [VeloCMS for pickleball coaches](https://velocms.org/for-pickleball-coaches) - [VeloCMS for podcasters](https://velocms.org/for-podcasters) - [VeloCMS for pop culture critics](https://velocms.org/for-pop-culture-critics) - [VeloCMS for pottery and ceramics](https://velocms.org/for-pottery-and-ceramics) - [VeloCMS for quilters](https://velocms.org/for-quilters) - [VeloCMS for real estate agents](https://velocms.org/for-real-estate-agents) - [VeloCMS for recipe bloggers](https://velocms.org/for-recipe-bloggers) - [VeloCMS for restaurants](https://velocms.org/for-restaurants) - [VeloCMS for saas founders](https://velocms.org/for-saas-founders) - [VeloCMS for science communicators](https://velocms.org/for-science-communicators) - [VeloCMS for shopify migrants](https://velocms.org/for-shopify-migrants) - [VeloCMS for stamp collectors](https://velocms.org/for-stamp-collectors) - [VeloCMS for stand up comedians](https://velocms.org/for-stand-up-comedians) - [VeloCMS for sustainability bloggers](https://velocms.org/for-sustainability-bloggers) - [VeloCMS for tattoo artists](https://velocms.org/for-tattoo-artists) - [VeloCMS for tea bloggers](https://velocms.org/for-tea-bloggers) - [VeloCMS for therapists](https://velocms.org/for-therapists) - [VeloCMS for toy collectors](https://velocms.org/for-toy-collectors) - [VeloCMS for travel bloggers](https://velocms.org/for-travel-bloggers) - [VeloCMS for twitter creators](https://velocms.org/for-twitter-creators) - [VeloCMS for typewriter collectors](https://velocms.org/for-typewriter-collectors) - [VeloCMS for veterinarians](https://velocms.org/for-veterinarians) - [VeloCMS for vintage camera collectors](https://velocms.org/for-vintage-camera-collectors) - [VeloCMS for vintage clothing curators](https://velocms.org/for-vintage-clothing-curators) - [VeloCMS for vinyl collectors](https://velocms.org/for-vinyl-collectors) - [VeloCMS for watch collectors](https://velocms.org/for-watch-collectors) - [VeloCMS for watchmakers](https://velocms.org/for-watchmakers) - [VeloCMS for wedding planners](https://velocms.org/for-wedding-planners) - [VeloCMS for wine bloggers](https://velocms.org/for-wine-bloggers) - [VeloCMS for women in tech](https://velocms.org/for-women-in-tech) - [VeloCMS for writers](https://velocms.org/for-writers) - [VeloCMS for yoga teachers](https://velocms.org/for-yoga-teachers) - [VeloCMS for garages](https://velocms.org/for-garages) ## Blog (/blog/) VeloCMS's own marketing blog — full articles below where the byte budget allows, an index line otherwise. --- # How do I move my newsletter subscribers from Mailchimp, Kit, or beehiiv to VeloCMS? > Source: https://velocms.org/blog/move-newsletter-from-mailchimp-kit-beehiiv-to-velocms > Published: 2026-09-17 You move your newsletter to VeloCMS by exporting a CSV from your current platform and running it through the built-in import wizard, which detects whether the file came from Mailchimp or Kit, shows you exactly who will and won't come across, and writes your subscriber list in on a single confirmation. For beehiiv, the wizard accepts your posts export and your subscribers export as two separate files, so your published archive can come along with your readers instead of just the list. Switching email platforms has always carried a quiet tax nobody mentions in the marketing copy: the list. Your posts you can usually copy-paste one at a time if you're patient enough. Your subscribers are a different problem entirely. Ask someone who has actually done this and they'll tell you about the afternoon spent staring at a CSV in Excel, guessing which column is the email address and which one is a custom merge tag nobody remembers adding. VeloCMS built a dedicated importer so that afternoon doesn't have to happen to you. ## What do I need to export from Mailchimp or Kit? Both platforms let you export your audience as a CSV from their own dashboard — Mailchimp calls it exporting your audience, Kit calls it exporting your subscribers. You don't need to reformat anything or strip out columns first. Drop the raw file into VeloCMS's import wizard under Admin, and the wizard reads the column headers itself to figure out which platform it came from. If your file's headers don't clearly match one provider's pattern, the wizard shows you a confidence score for each and asks you to confirm before it maps a single row, rather than guessing silently and hoping it got it right. This matters more than it sounds. A silent wrong guess means subscribers land with the wrong status or get skipped entirely, and you don't notice until three weeks later when someone emails asking why they stopped getting your newsletter. Being asked to confirm the provider once, up front, is a small extra click that avoids a much larger headache down the line. ## What actually gets imported, and what doesn't? This importer is subscriber-list only for Mailchimp and Kit — it does not bring your old newsletter issues or blog posts across, and it says so plainly on the preview screen before you commit to anything. What it does bring is every subscriber whose status in your export counts as active or subscribed. Anyone who unsubscribed, bounced, or was marked as cleaned in your old platform is left out on purpose, and the preview breaks that count down by the real status name from your export rather than lumping everyone into one vague "excluded" bucket. You'll see something like: 1,842 subscribers will import, 96 are excluded (61 unsubscribed, 22 bounced, 13 cleaned). That's a number you can sanity-check against what you remember your list looking like, instead of trusting a black box. Any column in your file the wizard doesn't recognize — a custom merge field, a location tag, whatever your old platform let you bolt on — isn't thrown away, but it also isn't silently imported as structured data either. The preview flags it as an unrecognized column so you know it exists and can decide whether it matters, rather than having it vanish with no record. For Mailchimp exports specifically, the wizard also looks at your tags for the usual paid-subscriber signals and carries that distinction into VeloCMS's own membership tiers, so readers who were paying you before generally keep that status here too. If a subscriber's email address already exists on your VeloCMS blog — maybe from a manual add, or a previous partial import — the wizard doesn't create a duplicate or silently overwrite anything. It skips that row and tells you how many it skipped in the final report, so the numbers you see at the end actually add up to something you can trust. ## What's different about moving from beehiiv? beehiiv splits its export into two separate downloads instead of one combined file: an "Export All Posts" file and an "Export Subscribers" file. VeloCMS's importer is built around that same shape — you can hand it either file on its own, or both together, and it treats them independently. Give it just the subscribers file and you get the same subscriber-only import described above. Give it just the posts file and your published archive comes across without touching your list. Give it both, and you get your back catalog and your readers in the same pass. When your beehiiv posts do come across, any images referenced inside them — a hero image, an inline screenshot, whatever you embedded in the body — get automatically re-hosted onto VeloCMS's own storage rather than continuing to point back at beehiiv's servers. That's a detail people don't think about until six months after a migration, when the old platform quietly cleans up "unused" media and every image in an old post breaks at once. ## Do I need to do anything before I import? Not really, beyond having your export files ready. The wizard walks you through three steps: upload the file, review a preview that shows exactly what will and won't come across (and asks you to confirm the provider if the file was ambiguous), and apply the import. Nothing writes to your live subscriber list until you approve the preview. If something in the preview looks off — a status count that doesn't match your memory, or more excluded rows than you expected — you can back out and re-export from your old platform before anything changes. The honest version of this feature is that it moves your list and, for beehiiv, your archive — it's not a magic button that also recreates your automations, your segments, or your old platform's specific tagging structure inside VeloCMS from day one. But the part that used to take the longest, and the part where a copy-paste mistake actually costs you subscribers, is now a guided upload with a preview you can check before you commit. If you're weighing whether to make the jump, you can bring your list over during your 14-day free trial (card required) and see your actual subscriber count land in VeloCMS before you decide anything else. --- # How to send client growth reports that non-technical clients understand? > Source: https://velocms.org/blog/monthly-growth-reports-your-clients-can-actually-read > Published: 2026-09-08T09:00:00.000Z You can send plain-language client growth reports directly from VeloCMS using our new automated reporting engine. These monthly summaries turn search rankings, backlinks, published articles and site traffic into plain sentences your clients can read in two minutes. This eliminates manual spreadsheet exports while clearly showing the business value of your work. If you run an agency or manage client sites, you know the dreaded monthly reporting cycle all too well. You export three different CSV files, screenshot a handful of web traffic charts, paste them into a slide deck, and email it off into the void. Half the time, your client opens the attachment, gets overwhelmed by bounce rates and API response times, and asks if their sales actually went up. That disconnect frustrates developers and store owners alike. ## Why do traditional analytics reports confuse clients? Most analytics dashboards are designed for growth hackers and engineers, not business owners who just want to know if their store is growing. When a client opens a standard analytics dump, they see numbers without context. They do not care that average position moved from 14 to 11 unless you explain what that means for the phone ringing. Drowning non-technical stakeholders in raw metric graphs usually leads to endless follow-up calls or, worse, clients who do not see the value in your ongoing retainer. ## How do VeloCMS growth reports simplify client communication? We shipped our new monthly growth reports on September 5th to bridge this exact gap. Instead of dumping raw database queries or complex traffic graphs on your clients, VeloCMS now compiles a clean, readable summary of the work you did this month, built entirely from figures you already have connected. It pulls rankings, backlinks, published content and page traffic into plain language that anyone can understand on a quick coffee break. Your clients get a clean breakdown of what changed this month: keywords tracked and how many sit in Google's top ten, estimated organic visits, referring domains and links acquired, articles published, and page views counted by the site's own beacon. Every number comes with last month's figure next to it, so the direction is obvious without a degree in data science. ## What does a report section actually look like? This is the part most reporting tools get wrong: they hand you a chart and expect the client to translate it herself. VeloCMS writes the translation for you, section by section. The rankings section reads something like this: "We tracked 42 keywords in September 2026. On average they sat at position 18.4, up from 21.2 in August 2026. 6 keywords now sit on page one. 9 keywords climbed and 4 slipped since August." No jargon, just what moved and by how much. The search visibility section follows the same pattern, but it's careful to say where the number comes from: "Google has your site ranking for 340 keywords. The modelled organic traffic estimate was 2,850, 12% higher than last month. This estimate comes from a market model, not from your own analytics, so treat it as direction rather than a headcount." That last sentence matters. A client who thinks an estimate is a headcount will ask questions your real analytics can't answer. Backlinks get the same honest framing: "Your site has links from 56 referring domains, up 4 on last month. 3 new links were logged this month. The profile figure counts every domain linking to you, including the press coverage you already had before we started." Content and page views close it out: how many articles went live, how the total is climbing, and how many times your pages were actually read, straight from the site's own beacon rather than a third-party estimate. ## What should you write when the numbers go down? Every agency hits a month where a keyword slips, a competitor outranks you, or search volume just dips for the season. The instinct is to bury the bad month or explain it away in a phone call the client half-remembers a week later. Neither works long term. This is what the commentary field is for. Before you publish a report, you can add two or three sentences in your own words: a Google core update landed mid-month, a competitor shipped a bigger content push, seasonal search volume always dips in this category. That commentary sits right next to the numbers when the client opens the report, so your explanation and the dip arrive in the same breath instead of a separate, easy-to-forget conversation. The report also refuses to fake a number it doesn't have. If a data source hasn't synced yet, or a snapshot didn't land this month, the section says so plainly rather than showing a zero that reads as a failure. A missing figure and a genuine zero look different on purpose, because a client should never mistake "we're still collecting this" for "nothing happened." ## How does this fit into an agency's Monday? Picture the reporting day you actually have, not the one on the retainer agreement. You open your VeloCMS workspace, and each client site already has a draft report waiting, generated from the same figures you've been watching all month. You skim it, add your two or three lines of commentary where a metric needs context, and publish it to that client's portal. Repeat for the next site. There's no CSV export, no slide deck, and no separate email thread. Reports for past months stay in the same list, so if a client asks how things looked back in June, you're not digging through old exports to find out. Only the roles that manage the site can generate a draft or publish it; the client only ever sees the finished, published version once you've stood behind it. ## How do you start sending these reports to your clients? If you already manage client sites on VeloCMS, the new reporting features are waiting for you inside your workspace dashboard right now. You can preview the generated monthly draft, write a short commentary in your own words, and publish it to the client's portal when you are happy with it. It turns hours of monthly administrative overhead into a simple two-minute check. If you are still wrestling with bloated legacy CMS platforms that require five different paid plugins just to send a basic email summary, it might be time to evaluate your tech stack. You can start building on VeloCMS today with our 14-day free trial (card required) and see how smooth client management can actually be. --- # Substack vs Ghost vs Beehiiv: Which Newsletter Platform Keeps More of Your Revenue? (2026) > Source: https://velocms.org/blog/substack-vs-ghost-vs-beehiiv-revenue-2026 > Published: 2026-09-02 **Question:** For a paid newsletter, which keeps more of my money: Substack, Ghost, or Beehiiv? **Short answer:** Substack is free to run but takes 10% of paid subscription revenue forever. Ghost(Pro) Publisher starts at $29/month billed yearly with a 0% platform fee, and Beehiiv Scale starts at $43/month billed yearly, also at 0%. Below roughly $300 to $500 a month in paid revenue, Substack is cheapest. Above that, the flat-fee platforms keep more, and the gap widens every month you grow. ## Three platforms, three different bets on your money The three most-recommended paid newsletter platforms in 2026 price themselves in three different ways, and that's the whole decision. Substack bets that you'll start free and never leave, so it charges nothing up front and a percentage forever. Ghost bets that you're a publisher who wants to own the site as much as the list, so it charges a flat monthly fee that rises with your member count. Beehiiv bets that you're building a newsletter business with ads and referrals, so it charges a flat fee by subscriber count and layers growth tools on top. None of those bets is wrong. Which one is right for you depends on two numbers: how much paid revenue you have today, and how large your free list is. This guide runs both. All prices were read from vendor pricing pages in July and August 2026; they change, so check the page before you commit. ## What each platform actually is **Substack** is a hosted newsletter and publication platform with a built-in reader network, notes, podcasts and video. It's free to use at any list size. On paid subscriptions, Substack takes 10% of revenue, and Stripe's processing fee (about 2.9% + $0.30 per transaction) comes out on top. There's no plan to upgrade to and no way to reduce the percentage. Custom domains cost a one-time $50 fee. You get discovery from the network, which for many writers is the real reason to be there. **Ghost** is an open-source publishing CMS with newsletters and memberships built into the same product. You can self-host it for free (Ghost's own docs estimate a realistic self-hosted setup at around $72/month once you add email delivery, CDN and backups) or use the managed Ghost(Pro). As of July 2026, Ghost(Pro) Starter is $15/month billed yearly ($18 monthly) for up to 1,000 members but no longer supports paid subscriptions. Publisher, the plan you need to charge readers, is $29/month billed yearly ($35 monthly) at 1,000 members and scales with your list, reaching about $88/month at 10,000 members. Platform fee on subscriptions is 0% on every plan. **Beehiiv** is a newsletter-first platform built by former Morning Brew engineers, with a landing page builder, referral program, an ad network and recommendation network. As of July 2026, the Launch plan is free up to 2,500 subscribers but doesn't include paid subscriptions. Scale starts at $43/month billed yearly ($49 monthly) and unlocks monetisation; Max starts at $96/month billed yearly ($109 monthly) and removes Beehiiv branding. Prices step up by subscriber bracket: a list that just passed 2,500 subscribers lands at about $77/month on Scale billed yearly. Platform fee on paid subscriptions is 0%. ## Side-by-side comparison | | Substack | Ghost(Pro) | Beehiiv | |---|---|---|---| | Free tier | Yes, any list size | No (14-day trial) | Yes, up to 2,500 subscribers | | Cheapest plan with paid subscriptions | Free | Publisher, $29/mo yearly (Jul 2026) | Scale, $43/mo yearly (Jul 2026) | | Platform fee on paid revenue | 10% | 0% | 0% | | Stripe processing | ~2.9% + $0.30 | ~2.9% + $0.30 | ~2.9% + $0.30 | | Price scales with | Revenue | Member count (free + paid) | Subscriber count | | Custom domain | $50 one-time | Included | Included on free plan | | Website / CMS | Basic publication page | Full CMS, themes, pages | Landing pages + posts | | Discovery network | Strongest | None built in | Recommendation network + Boosts | | Ad monetisation | No | No | Ad network (Scale and up) | | Data export | Subscribers CSV, posts | Full JSON export | Subscribers CSV | | Open source / self-host | No | Yes | No | ## The real question: what do you pay at each revenue level? Percentage fees and flat fees cross over. Here's where, using Ghost Publisher and Beehiiv Scale at their entry brackets, yearly billing, and Substack's 10%. Stripe is left out because all three pay it. **$200/month in paid revenue (say 40 readers at $5).** Substack takes $20/month, or $240/year. Ghost Publisher costs $348/year. Beehiiv Scale costs $516/year. Substack wins clearly. **$1,000/month in paid revenue.** Substack takes $100/month, or $1,200/year. Ghost is still $348/year at up to 1,000 members. Beehiiv is $516/year up to its entry bracket. Both flat-fee platforms now save you $700 to $850 a year. **$5,000/month in paid revenue.** Substack takes $500/month, or $6,000/year. By now your total list is probably past 1,000, so Ghost Publisher might be $46 to $88/month ($552 to $1,056/year) and Beehiiv Scale roughly $77 to $109/month ($924 to $1,308/year). Either way, you keep $4,500 to $5,400 more per year than on Substack. The break-even sits around $300 to $500 a month in paid revenue, depending on which platform and bracket you'd land in. Below it, pay the percentage and enjoy the free ride. Above it, the percentage becomes the most expensive line in your business. One thing the table hides: Ghost counts free members toward your plan bracket, and Beehiiv counts all active subscribers. A newsletter with 9,000 free readers and 300 paying ones pays Ghost's 10,000-member rate. Substack doesn't care how big the free list is. If your free-to-paid ratio is very high, that shifts the break-even upward. ## Migration: what moves and what doesn't All three let you export subscribers as CSV, so the list is never trapped. Paid subscriptions are the sticking point: Stripe customers can be transferred between platforms if the destination supports importing existing Stripe subscriptions (Ghost and Beehiiv both document this), but readers on Substack may need to re-enter payment details depending on how the migration is handled. Plan a week of overlap and expect a few percent of churn. Content moves as posts or JSON; Substack's reader network does not move at all. ## When each platform is the better choice **Choose Substack if:** 1. You have little or no paid revenue yet and want zero fixed cost while you find out whether readers will pay. 2. Discovery matters more than margin. Recommendations and Notes still bring new readers in a way the other two can't replicate. 3. You want podcasts, video and text in one place without stitching tools together. **Choose Ghost if:** 1. You want a real website as well as a newsletter: pages, themes, tags, structured content, on your own domain, with nothing that says "Ghost" unless you want it to. 2. You value the exit. Open source means you can move from Ghost(Pro) to your own server, or back, without asking anyone. 3. Your paid revenue is past a few hundred dollars a month and your free list isn't enormous relative to it. **Choose Beehiiv if:** 1. Your model is ads and sponsorships rather than (or alongside) paid subscriptions. The ad network is the reason most Beehiiv publishers are there. 2. You want built-in referral and recommendation growth loops without third-party tools. 3. Your list is under 2,500 and you want a free plan that includes a landing page and custom domain while you grow. If you want all three of those things (a full CMS, 0% fees and newsletter segments) in one subscription, that's the category VeloCMS sits in; the [compare page](/compare) shows it next to Substack and Ghost, and the individual [Substack](/vs/substack), [Ghost](/vs/ghost) and [Beehiiv](/vs/beehiiv) comparisons cover the trade-offs in detail. If you'd rather run your own numbers first, the [compare page](/compare) is the place to start. ## Frequently asked questions ### Does Substack take a percentage of paid subscriptions? Yes. Substack takes 10% of paid subscription revenue on every plan, and Stripe's processing fee (about 2.9% + $0.30 per transaction) applies on top. There's no paid tier that lowers the percentage. Free newsletters cost nothing to run. ### How much does Ghost cost for a paid newsletter in 2026? As of July 2026, the Ghost(Pro) Publisher plan starts at $29/month billed yearly ($35 monthly) at 1,000 members and scales with your list, to about $88/month at 10,000 members. Platform fee on subscription revenue is 0%. The cheaper Starter plan ($15/month yearly) no longer supports paid subscriptions. ### How much does Beehiiv cost for a paid newsletter in 2026? As of July 2026, paid subscriptions need Beehiiv's Scale plan, which starts at $43/month billed yearly ($49 monthly) and steps up by subscriber bracket, reaching about $77/month yearly once you pass 2,500 subscribers. Max, from $96/month yearly, removes Beehiiv branding. Platform fee on paid revenue is 0%. ### At what revenue does Substack become more expensive than Ghost or Beehiiv? Roughly $300 to $500 a month in paid subscription revenue. At $1,000/month, Substack's 10% costs $1,200/year versus about $348/year for Ghost Publisher or $516/year for Beehiiv Scale at their entry brackets. The gap grows with revenue. ### Do free subscribers cost money on Ghost or Beehiiv? Yes. Ghost prices Publisher and Business by total members, free and paid combined. Beehiiv prices Scale and Max by total active subscribers. A large free list pushes you into a higher bracket even if few readers pay. Substack charges nothing for free subscribers. ### Can I move my paid subscribers from Substack to Ghost or Beehiiv? Subscriber lists export as CSV from all three. Existing Stripe subscriptions can be imported into Ghost and Beehiiv, but the process depends on how the payments were set up on Substack, and some readers may need to re-enter card details. Expect some churn during the move and plan an overlap week. --- # The Real Cost of Running a WordPress Blog in 2026: Hosting, Plugins, and the Fees Nobody Adds Up > Source: https://velocms.org/blog/real-cost-of-running-a-wordpress-blog-2026 > Published: 2026-09-02 | Updated: 2026-10-04 **Question:** How much does it actually cost to run a WordPress blog in 2026? **Short answer:** WordPress itself is free, but a working blog isn't. Once you add managed hosting, an SEO plugin, a page builder, caching and a membership or newsletter tool, a single serious WordPress blog typically lands between $600 and $900 a year in 2026, before any percentage fees on paid subscriptions. A budget shared-hosting setup can run under $200 a year, but you give up speed, security and support to get there. ## "WordPress is free" is true and misleading at the same time WordPress the software costs nothing. You can download it today and install it on a $5 server. That's the part everyone repeats. Here's the part most cost breakdowns skip: WordPress out of the box is a text editor with a theme. It doesn't do SEO properly, it doesn't cache, it doesn't send newsletters, it doesn't take payments and it doesn't build landing pages. Every one of those jobs is a plugin, and the good plugins are paid, per site, per year. The real question isn't "how much does WordPress cost." It's "how much does the WordPress you'd actually publish on cost." This guide adds it up with dated prices from vendor pages, then shows where the number swings depending on the choices you make. If you'd rather see the same question framed as a head-to-head, the [VeloCMS vs WordPress](/vs/wordpress) page covers the trade-offs. ## What you're actually paying for Think of a WordPress blog as five bills that arrive at different times. **Hosting.** This is the one recurring cost you can't avoid. Managed WordPress hosts handle updates, backups and security for you. As of Oct 2026, Kinsta's single-site Single 20GB plan lists at $35/month billed monthly ($350/year billed annually), and WP Engine's Essential plan starts at $28/month billed yearly ($35/month billed monthly), per kinsta.com/plans and wpengine.com/plans. Budget shared hosting from the likes of Hostinger or Bluehost is advertised at low introductory prices (Bluehost's Starter plan listed $3.99/month on a 36-month term and renews at $9.99/month, per its pricing page in September 2026), and you're doing your own patching. See how the two premium hosts compare on their own pages: [Kinsta](/vs/kinsta) and [WP Engine](/vs/wpengine). **SEO.** Yoast SEO Premium is the default choice for most blogs. As of Oct 2026, Yoast lists Premium at $118.80 per site per year (ex VAT, yoast.com), and the plan includes the Local, News and Video SEO plugins. Rank Math Pro is the usual cheaper alternative, listed at €7.99/month billed annually for unlimited personal sites (rankmath.com/pricing, Oct 2026). **Page builder.** The free block editor is fine for posts and poor for landing pages, so most sites add a builder. Elementor Pro's Essential plan lists at $60/year for one site (elementor.com/pricing, checked Oct 2026), with higher plans for more widgets and more sites. Read the [Elementor comparison](/vs/elementor) for what that money buys. **Speed.** A page-caching plugin is close to mandatory on shared hosting and still common on managed hosts. WP Rocket lists at €49.95/year for a single site as of Oct 2026 (as shown on wp-rocket.me/pricing, which prices in euros), with no free tier. Some managed hosts include server-side caching, which lets you skip this line. **Monetisation and email.** This is where the bill stops being predictable. A membership plugin, a newsletter plugin or email service, a form builder and an anti-spam tool each carry their own licence. Prices vary widely by list size and features, so check the vendor page for the exact tools you'd pick. The point for budgeting is that each one is another renewal on a different date. ## The 2026 bill, three ways | Line item | Budget setup | Standard serious blog | Growth setup | |---|---|---|---| | Hosting | Shared, ~$96/yr (renewal rates vary) | Kinsta Single 20GB, $350/yr (Oct 2026, annual) | Kinsta or WP Engine mid-tier, $700+/yr | | SEO plugin | Yoast free, $0 | Yoast Premium, $118.80/yr (Oct 2026) | Yoast Premium, $118.80/yr | | Page builder | Block editor, $0 | Elementor Pro Essential, $60/yr (Oct 2026) | Elementor Pro, a higher plan (see elementor.com/pricing) | | Caching | Free plugin, $0 | WP Rocket, €49.95/yr (Oct 2026) | Included in host or WP Rocket, €49.95/yr | | Memberships, newsletter, forms, anti-spam | Free tiers where they exist | Typically $150 to $300/yr combined, see vendor pages | $300+/yr plus email volume pricing | | Platform fee on subscriptions | 0% (you use your own Stripe) | 0% | 0% | | **Estimated total** | **~$100 to $200/yr** | **~$680 to $830/yr, plus WP Rocket** | **~$1,250+/yr** | | Your time on updates and conflicts | High | Medium | Medium, or you pay someone | The "standard serious blog" column is the one most bloggers land in after a year. Not because they're extravagant, but because each free tool eventually hits a wall (no redirects in free Yoast, no theme builder in free Elementor, no real caching on a $4 host) and the paid upgrade fixes it for about $50 here and $118 there. ## The costs that don't show up on any invoice Money is the visible half. Three other costs decide whether a WordPress blog is cheap or expensive. **Renewal creep.** Most plugin and hosting prices are introductory. Shared hosting advertised at $3/month often renews at two to four times that. Check each vendor's renewal price before you commit. Your year-two bill is the honest one. **Conflict time.** Eight plugins from eight vendors means eight update schedules and a real chance that one breaks another. If you value your time at even $30/hour, a couple of hours a month on updates, patches and "why is the checkout blank" is $700 a year on its own. **Security exposure.** Every plugin widens the attack surface. Managed hosts partly cover this, which is exactly why they charge $30/month instead of $5. ## How an all-in-one plan changes the math The alternative isn't "WordPress but cheaper." It's a platform where the SEO scoring, page builder, caching, newsletters, memberships and commerce are part of the product, so the plugin column goes to zero and the renewal dates collapse into one. VeloCMS is built that way: block editor, page builder, AI SEO scoring, newsletter segments, paid memberships and native commerce ship without add-ons, payments run through your own Stripe account at a 0% platform fee, and pages are pre-rendered and served from an edge cache, so there is no caching plugin to configure. Current plan prices are on the [pricing page](/pricing); the whole side-by-side matrix, including Ghost, Substack and Squarespace, is on the [compare page](/compare). Compare that to the "standard serious blog" column above. The hosting line disappears (it's included), the four plugin lines disappear, and what's left is one subscription. Whether that's cheaper for you depends on which column you're really in, which is the honest part of this decision. ## When WordPress is still the better choice A cost guide that pretends WordPress always loses isn't worth reading. There are real cases where the plugin tax is worth paying. 1. **You need a plugin that only exists on WordPress.** The ecosystem is 20 years deep. If your blog depends on a specific LMS, booking system, multilingual plugin or industry integration, WordPress has it and most platforms don't. 2. **You already have a developer.** If someone on your team maintains WordPress for a living, the conflict-time cost drops to near zero and self-hosted WordPress on a cheap VPS can be the lowest-cash option available. 3. **You want full server access.** Custom PHP, custom database tables, unusual caching layers, on-prem hosting for compliance reasons. WordPress gives you the whole machine. 4. **Your blog is tiny and static.** One author, a few posts a month, no memberships, no store. Free Yoast, the block editor and $4 shared hosting will do, and the $100/year column is real. 5. **You need WooCommerce at scale.** For a large physical-product catalogue with complex shipping and tax, [WooCommerce](/vs/woocommerce) remains one of the most flexible options, plugin costs and all. If you're in one of those five, stay put. The point of this guide is that most bloggers aren't, and they're paying the standard column without ever having added it up. If you want to see what your current stack would cost on one plan, the [pricing page](/pricing) lays it out, and every plan starts with a 14-day free trial (card required). ## Frequently asked questions ### How much does a WordPress blog cost per year in 2026? A budget WordPress blog on shared hosting with free plugins costs roughly $100 to $200 a year. A typical serious blog with managed hosting (Kinsta Single 20GB at $350/year billed annually as of Oct 2026), Yoast Premium ($118.80/yr) and Elementor Pro ($60/yr) lands around $529 a year in dollar-priced items, plus WP Rocket (€49.95/yr, as shown on the vendor's pricing page), and between $680 and $830 once membership, forms or email tools are added. ### Is WordPress really free? The WordPress software is free and open source. Hosting is never free, and the plugins most blogs rely on for SEO, page building, caching, forms, memberships and newsletters are paid, usually per site per year. "Free" describes the download, not the running cost. ### What is the cheapest way to run a WordPress blog? Shared hosting on a promotional rate, free Yoast, the built-in block editor, a free caching plugin and no paid memberships. Expect roughly $100 to $200 a year, and expect the hosting price to rise at renewal. You trade money for your own time on updates and security. ### How much do WordPress plugins cost in total? For a standard blog, the dollar-priced plugins cost about $179 a year (Yoast Premium $118.80 and Elementor Pro Essential $60), plus WP Rocket at €49.95 (as shown on the vendor's pricing page) and a membership or newsletter tool that varies by vendor. Agencies running multiple sites pay per site unless they buy multi-site licences. ### Does an all-in-one CMS actually save money over WordPress? It depends on which column you're in. If you're paying for managed hosting plus three or four premium plugins, an all-in-one plan that includes hosting, SEO, builder, caching, newsletters and memberships usually costs less and removes renewal creep and plugin conflicts. If you run a small static blog on free tools, WordPress can still be cheaper in cash. ### Does WordPress charge a fee on paid memberships? WordPress itself doesn't, and neither does VeloCMS. Both let you connect your own Stripe account at 0% platform fee. That's different from newsletter platforms like Substack, which takes 10% of paid subscriptions, or Patreon at 10% plus payment processing fees. See the [Substack comparison](/vs/substack) for that side of the decision. --- # What is VeloCMS? An honest review of the all-in-one blogging platform (2026) > Source: https://velocms.org/blog/what-is-velocms-honest-review > Published: 2026-09-02 **Question:** What is VeloCMS, and is it worth switching to? **Short answer:** VeloCMS is a hosted, all-in-one publishing platform. Themes, a visual page builder, memberships and paywalls, a newsletter, native commerce, AI writing and SEO tools, and migration importers all ship inside one subscription, with no plugins to buy or maintain. Plans are $9, $29 and $69 a month (less on annual billing), and every plan starts with a 14-day free trial, card required. The honest catch: it's managed SaaS only. There's no self-hosted core and no open third-party plugin ecosystem yet. ## What is VeloCMS, exactly? It's a content platform for people who publish for a living, or who'd like to. You sign up, pick one of 39 built-in themes (as of September 2026), connect a domain, and you already have a blog with an editor, a page builder, an email list, a paywall and a store attached to it. Nothing gets installed. Nothing needs updating by you. The homepage states the thesis without much decoration: stop paying for plugins one by one. That's aimed squarely at the WordPress stack, where the software is free right up until you need SEO, caching, a page builder, forms, memberships and a newsletter, at which point you're quietly running six vendors on six renewal dates and hoping none of them breaks the other five. Under the hood it's a server-rendered app on managed hosting behind a CDN, which is why the front page advertises a 0.8s desktop LCP target instead of selling you a caching plugin. You never see any of that. There's no server to log into and no PHP to patch, which is the point and also, for some people, the objection. ## Who is it for? Solo creators and small publishing teams. The niche pages give the audience away pretty clearly: photographers, podcasters, restaurants, writers, developers, indie makers, agencies, plus roughly a hundred more specific ones. What they have in common is one person, maybe three, who writes, wants to charge readers or sell something alongside the writing, and has no interest in running infrastructure as a side hobby. If you're a developer who wants root access and a repo you can fork, this is not your platform, and the section further down says so plainly. ## What do you get without installing anything? This is the part that decides whether the pitch holds up, so here's what's actually in the box today. **Writing and layout.** A block editor for posts and a visual page builder with 70-plus blocks for everything that isn't a post: landing pages, pricing tables, galleries, embeds, forms. Themes number 39 (as of September 2026) and every one is included on every plan, not gated behind a tier. **Getting paid.** Memberships and paywalls are native, and payments run through your own Stripe account with a 0% platform fee (Stripe's own processing cut still applies, as it does everywhere). Native commerce covers physical products with variants and shipping, digital downloads, event tickets, gift cards and online courses. The store speaks in your theme's visual language rather than looking like a bolted-on plugin. **Email.** A newsletter with tag segmentation, sent to your own subscriber list, and no percentage taken from paid subscriptions. **AI, and where it's pointed.** There's a Gemini-based writing assistant in the editor, alt-text generation, translation with hreflang handling, plus SEO scoring and an AI-search visibility score that grades a draft on how likely it is to be quoted by answer engines rather than only ranked by Google. Google Search Console performance sits right next to that score, so you see what a post actually did after publishing. You can bring your own AI key if you'd rather use your own quota. **Getting your stuff in.** A WordPress migration wizard, a Squarespace XML importer, Webflow CMS collection imports, Substack and Ghost exports, and a Wix importer that reads your public URL directly so you never have to produce a backup file. **Automation.** An official n8n node, publishing straight from Claude over MCP, Zapier and Make, plus a plain REST API and webhooks for anything else. **The unglamorous parts.** Full Arabic and right-to-left support across the site and admin, GDPR tooling, two-factor auth and WebAuthn passkeys, instant on-site search, and domains you can either connect from any registrar or buy inside the dashboard. ## What does VeloCMS cost? | Plan | Monthly | Annual (per month) | Who it's for | |---|---|---|---| | Pro | $9 | $7.20 | One creator, one site | | Business | $29 | $23.20 | A team of five, bigger limits | | Agency | $69 | $55.20 | Five client sites, white-label, unlimited team | Every plan starts with a 14-day free trial and a card is required upfront. You aren't charged until day 15, and cancelling before then costs nothing. Refunds run 14 days from the first payment, no questions asked. If you cancel later, the site drops to read-only rather than vanishing, and you can export or reactivate within 90 days. The limits are worth reading before you commit. Pro includes 5 GB of storage, 5,000 subscribers, 1,000 AI calls a day, 100 AI translations a month and one site. Business raises those to 50 GB, 50,000 subscribers, 5,000 AI calls and unlimited translations. Agency includes five sites with extras at $9 a month each, and lifts the storage and subscriber caps entirely. ## Where VeloCMS falls short A review that only lists features isn't a review, so here are the four things most likely to disqualify it for you. **There's no self-hosted version.** The application is proprietary and managed SaaS only: no source access, no server, no fork. The plugin SDK and CLI are MIT-licensed on npm, but the platform itself is not. If your requirement is "I must be able to move this onto my own box," VeloCMS fails that requirement today and there's no roadmap date to point you at. Your content isn't hostage (posts, members and settings export as JSON, CSV or Markdown from the dashboard whenever you like), but the software is not yours. **There's no third-party plugin or theme marketplace yet.** The developer program is written up publicly and clearly marked as not open. Every plugin and theme you can use today is first-party. That's a genuine strength for reliability and a genuine weakness for coverage: if your business depends on one specific WordPress plugin, nobody can build you the equivalent right now. **Importers cover platforms, not folders.** WordPress, Wix, Squarespace, Webflow, Substack and Ghost all have their own path in. A Markdown archive from Jekyll or Hugo doesn't, so those posts go in one at a time. The Wix importer also has a known soft edge: pages built almost entirely from client-side scripts can arrive thinner than expected, and Wix's own RSS feed carries no images, so imported drafts deserve a scroll-through before you publish them. **There's no free plan.** The trial is free, the platform isn't. If you want to publish indefinitely at zero cost, this is the wrong product and Substack or a free WordPress.com site is a better answer. If you want the side-by-side against specific tools rather than the overview, the [compare page](/compare) puts VeloCMS next to Substack, Ghost, Squarespace and Medium, and the [WordPress comparison](/vs/wordpress) covers the plugin-tax argument in detail. Current plan pricing lives on the [pricing page](/pricing). ## Frequently asked questions ### Is VeloCMS free? No. There's no free plan. Every plan starts with a 14-day free trial that requires a card upfront, and you're charged on day 15 unless you cancel first. Paid plans are $9, $29 and $69 a month, with a 20% discount on annual billing. ### Can I self-host VeloCMS? No. VeloCMS is proprietary, managed SaaS with no self-hosted core and no source access. The plugin SDK and CLI tooling are MIT-licensed and published on npm, but the platform itself isn't open source. Your data stays portable either way, since posts, members and settings export as JSON, CSV or Markdown at any time. ### Does VeloCMS take a cut of my subscription or product revenue? No. Memberships, paid newsletters and store sales run through your own Stripe account at a 0% platform fee. Stripe's normal processing fee (roughly 2.9% plus $0.30 per transaction) still applies, the same as it would on any platform. --- # How do I move my Wix blog without downloading a backup? > Source: https://velocms.org/blog/how-do-i-move-my-wix-blog-without-downloading-a-backup > Published: 2026-09-02 You can now point VeloCMS at your live Wix URL and pull your content straight in. No export file, no manual copy-paste, no wrestling with ZIP archives. The importer reads your public site and turns pages and posts into real VeloCMS content you can edit immediately. Switching blog platforms used to feel like moving house through a keyhole. You'd export some partial file, lose half your media, then spend a weekend rebuilding everything the old builder wouldn't give back. We shipped the Wix importer to skip that whole ritual. ## How does the Wix import actually work? You paste your public Wix URL into the importer and let it read what's already live. VeloCMS walks the rendered site, pulls out pages and posts, maps images and text into the VeloCMS structure, and lands everything in your draft workspace. You're not scraping raw HTML into a static page; each piece becomes real, editable content inside VeloCMS. That means you can rewrite a headline, swap a hero image, or change the URL slug after the import finishes. ![The VeloCMS Import hub with the Wix platform card](/screenshots/blog/wix-import-hub.jpg "Import lives in the admin sidebar; pick Wix and paste your public URL") ## What comes over from Wix? Pages, blog posts, and the media embedded in them make the trip. The importer preserves the body content and structure as closely as possible, then hands you clean VeloCMS blocks you can rearrange. It won't clone Wix's exact theme (that would be a copyright and maintenance mess), so your site gets a fresh VeloCMS look that you control. Think of it as rescuing your writing and assets, not photocopying the old design. ## What does NOT come over? Not everything on your Wix site counts as content the way VeloCMS understands it. Forms, booking widgets, and members-only areas are Wix apps, not article bodies, so the importer leaves them alone entirely (there's nothing there to migrate; you'd rebuild those with a VeloCMS-native equivalent if you still need them). And because the importer reads what's actually served in your site's HTML rather than rendering the page the way a browser does, a page built almost entirely out of client-side scripts can come through thinner than you'd expect, missing text or sections that only appear once Wix's own JavaScript runs. Media deserves its own callout here. Wix's RSS feed, usually the fastest route to your posts, doesn't include images at all. That's a known limitation of the feed itself, not something we're getting wrong on our end. So every post that arrives through the feed gets a second pass that goes back to the live page and recovers its images directly, rather than trusting the feed to hand them over. It's worth a quick scroll through your imported drafts once the run finishes, just to confirm the images you expected actually landed where they should. ## Why import from the public URL? Because most Wix owners don't have a clean export sitting around. Asking someone to dig through Wix settings, generate a backup, and upload mystery files is exactly the friction that keeps people locked on a platform they've outgrown. Reading the live URL removes that gate entirely. If your site is public, the importer can see it, which means migration day becomes "paste link, review drafts, publish" instead of a multi-day project. ![The Wix importer's URL step, asking only for your public site address](/screenshots/blog/wix-import-url.jpg "One field: your live Wix URL. No backup file required.") ## How does the importer find your content? Under the hood, it's less a single scraper and more a short ladder, and each rung only matters if the one above it comes up short. First it tries your Wix blog feed directly at `/blog-feed.xml`, which is where Wix publishes RSS by default. If that's missing or oddly configured, it falls back to a more general feed-discovery pass that checks the handful of other places a feed might live. If there's still nothing usable, it walks your sitemap instead and collects every page on your domain that isn't a product page. From there, each page gets read on its own: the importer looks for JSON-LD Article or BlogPosting markup, Open Graph tags, and a readability pass over the page content, then decides for itself whether what it found is a blog post or a plain static page. The point of building it this way, rather than betting everything on one method, is that Wix sites aren't all wired the same. Some have a clean RSS feed and nothing else is needed. Others never set one up, or their feed has drifted out of sync with what's actually published. A scraper that only knows one trick fails outright the moment a site doesn't match its assumptions; a ladder just moves down a rung and keeps going, so the importer degrades gracefully instead of giving up. ## Is this part of a broader import push? Yes. This same week we shipped Webflow CMS collection imports and Squarespace XML uploads, plus a new Google Search performance panel next to your SEO score. Wix was the missing piece for a huge slice of creators who started there and now need a faster, cleaner platform. We built it because those creators kept asking for a way out that didn't start with "first, become a backup expert." ## What happens after the import finishes? Everything the importer pulls in lands as a draft, sitting in your normal post editor exactly like anything you'd written from scratch. Nothing gets published automatically, so there's no risk of an old Wix post going live on your new domain before you've had a chance to look at it. You can review each one, tidy up a headline, swap an image, or change the slug, and only publish once it actually reads the way you want. It isn't locked behind a paid plan, either, so this isn't something you have to upgrade into just to try. If you're sitting on a Wix site that has outgrown its editor, the new importer is live now under Import in your admin sidebar. Start a 14-day free trial (card required), paste your URL, and see your content in VeloCMS within minutes. --- # How do I know my blog is ready to launch? > Source: https://velocms.org/blog/how-do-i-know-my-blog-is-ready-to-launch > Published: 2026-08-28 Technically, your blog is "live" the moment a post is published and the URL resolves. But live isn't the same as ready, and most of the gap is invisible until a reader bumps into it. VeloCMS's Setup Assistant, sitting permanently at `/admin/setup`, checks the dozen or so things that actually matter — a first post that's published, a domain that's verified rather than just typed in, a newsletter whose sender domain is confirmed rather than merely switched on — and it tells you honestly which are done, which need attention, and which it simply couldn't verify right now. You don't notice an unverified sender domain until your newsletter batch lands in spam. You don't notice a custom domain stuck in "pending" over one bad DNS record until someone tells you your link doesn't work. The point of a launch-readiness surface is to catch exactly that class of problem before a reader does. ## What does "ready to launch" actually mean? It's less a ceremony and more a short list of things that are each easy to skip on your own. Some are content — a published post, an active theme, a real description instead of a placeholder. Some are discoverability — SEO defaults filled in, social links added, and, on plans that include it, a custom domain that's actually verified rather than just connected. Some are the plumbing readers never see until it breaks — a newsletter sender domain, a payment provider, whether your privacy and terms pages still carry the seeded default text from day one. None of these block you from publishing. Together, they're the difference between "I started a blog" and "my blog is set up the way I meant it to be." ## Where do I find the launch-readiness checklist? Open your admin dashboard and look at the sidebar. Setup Assistant has its own permanent page at `/admin/setup`, not a one-time banner that disappears the moment you close it. That's the deliberate change. The old onboarding checklist only showed up on first login and vanished forever once dismissed, which meant there was nowhere to go back three months later and ask "wait, is everything still okay?" after you'd switched newsletter providers or your SSL quietly lapsed. Setup Assistant re-checks everything live, every time you open the page. ![The VeloCMS Setup Assistant overview screen, showing an honest three-part count of passing, to-do, and unknown checks above a segmented status bar](/screenshots/blog/setup-assistant-overview.jpg "Setup Assistant gives you three separate counts — pass, to-do, and unknown — never a single percentage") At the top, instead of a collapsed percentage, you get three separate numbers: how many checks are passing, how many need your attention, and how many couldn't be verified this time around. That last bucket matters more than it sounds. A percentage that treats a database hiccup as a failure is lying to you about your own work; a page that says "we couldn't check this, try again" is telling you the truth about what it actually knows. ## What does the Setup Assistant actually check? The checks are grouped into five categories, and each one maps to something a reader would eventually notice if it stayed broken. Foundation covers the basics: a published first post, an active theme, a real blog description. Reach handles whether search engines and social previews have anything to work with — SEO defaults filled in, social links added, and, on plans with custom domains, whether yours is verified rather than just entered. Audience is your newsletter: a provider connected, and — the one that used to slip through unnoticed — a sender domain that's verified, not just switched on. Revenue checks whether a payment provider is explicitly configured if you've turned on commerce, whether your Stripe account is connected for memberships, and whether your member webhook endpoint is listening for the right subscription events. Integrity has one deliberately gentle check: whether your privacy and terms pages have actually been edited, or still carry the default text every blog starts with. ![The Reach and Audience categories of the Setup Assistant, showing individual check rows with Done, To do, and Fix this links](/screenshots/blog/setup-assistant-checks.jpg "Each unfinished check carries a Fix this link straight to the screen that resolves it") Two checks get flagged more urgently than the rest: a custom domain that's been added but never verified, and a newsletter provider that's switched on with a sender domain that hasn't been confirmed. Those are the pair that used to pass silently under the old checklist while quietly breaking real reader experiences. Everything else nudges you toward "materially better" — worth doing, never an emergency. The legal-pages check is graded optional on purpose, because every new blog starts with the same seeded privacy and terms text. If it colored the whole page red on day one, it would just be noise. ## What does "unknown" mean? It means exactly what it says: the assistant tried to read the signal it needed and couldn't get a clean answer, usually because of a momentary database hiccup. This is the detail that makes the page trustworthy rather than decorative. A checklist that quietly treats "I couldn't check" the same as "this failed" will tell a fully configured blog that it's done nothing at all — worse than useless, actively misleading. Setup Assistant keeps "unknown" as its own separate bucket, and if every check comes back unknown at once, the page says so plainly instead of showing a wall of red. Refresh a moment later and it usually resolves. ## How do I actually fix something it flags? Every check that needs attention comes with a "Fix this" link that goes to the real settings screen — the newsletter check links to newsletter settings, the domain check links to the domain setup screen, and so on. There's no dead end where the link dumps you on a generic page and leaves you hunting for the actual control. If you're working through the domain checks, our [walkthrough on connecting a custom domain](/blog/connect-custom-domain-to-your-blog) covers the DNS side in more detail than Setup Assistant's short summary needs to. Work through the list category by category. Once every check that applies to your blog is passing, the page tells you so — plainly, with its own small celebration, not a vague "all good" you have to take on faith. ## Do I need every check green before I launch? Not necessarily — and this is where the checklist earns trust instead of nagging you. Custom-domain checks only show up if you're on a plan that includes one; if you're happily running on your velocms.org subdomain, they don't appear at all. Commerce and payment checks only apply once you've turned that module on. Setup Assistant is scoped to what your blog is actually trying to be, not a generic checklist written for a hypothetical tenant running every feature at once. A photography blog with no store enabled will never see a payment-provider check demanding attention, because there's nothing there to demand. Ready, in the end, isn't a certificate you earn once. It's a page you can return to whenever something changes — a new plan, a new newsletter provider, six months of not thinking about your legal pages — and get an honest answer instead of a guess. If your blog is still finding its footing, or if you haven't started one yet, VeloCMS is available on a [14-day free trial](/signup), card required, no surprises — and Setup Assistant is there in your sidebar from the first login, quietly keeping score. --- # How Do I Keep My Photo's Location and Camera Data Off My Blog? > Source: https://velocms.org/blog/keep-photo-location-camera-data-off-your-blog > Published: 2026-08-17 Every photo your phone or camera takes carries a hidden passenger. EXIF metadata embeds the GPS coordinates of where you stood, the exact camera and lens you used, even the time and date you pressed the shutter. Most of the time that data sits harmlessly in the file. The moment you upload it to a blog, though, it becomes a privacy leak you probably didn't mean to share. None of this is exotic or hidden behind some setting you'd have to know to look for. Journalists have warned about it for years: a source's location given away by a geotagged photo, a shelter's address pinpointed by a well-meaning volunteer's post, a public figure's home narrowed down from a handful of casually shared vacation snapshots. Bloggers rarely think of themselves in the same category as any of that, but the mechanism is identical either way. The metadata doesn't care whether the account has twelve readers or twelve million. ## Why does photo metadata matter for bloggers? If you write about your home office, your weekend hike, or your kid's soccer game, the image you publish can quietly reveal your street address or daily routine. A reader with basic tools can pull latitude and longitude straight out of a downloaded photo. Camera and lens details might seem harmless until they become another data point someone can combine with everything else you've posted online. For photographers, creators, and indie publications, this is exactly the kind of small detail that erodes trust over time. Think about the kind of images that actually end up on an independent blog. A recipe post shot in your real kitchen. A gear review photographed on your real desk. A travel diary entry taken from the balcony of wherever you're actually staying that week. None of those photos are trying to reveal anything — they're just photos, taken where you happen to be, published because they illustrate the story you're telling. The metadata riding along with them was never part of that story. ## What does VeloCMS do with uploaded photos? Starting this week, VeloCMS removes location and camera metadata before the image ever reaches your public site. Upload a photo to a post, a page, or the media library, and the file you publish is scrubbed clean of GPS tags, camera make and model, lens information, and other identifying EXIF fields. The image itself stays untouched, so color, resolution, and quality remain exactly as you intended. You don't flip a switch or pick a setting. It just happens. It isn't a separate step you have to remember, and it isn't a checkbox buried three menus deep in some settings panel. It happens in the same upload pipeline that already resizes your image and converts it for the web — one more pass through a process your photo was going through anyway. You don't notice it happening, which is really the point. The protections that work best are usually the ones you never have to think about. ## Does this work everywhere photos appear? Yes. Whether the image lands in a blog post, a portfolio showcase, a product listing, or a theme header, the published version has already been stripped. The original upload is still available to you in the admin media library if you need it for your own records, but visitors and search engines only see the clean copy. That separation is what makes the feature reliable: your workflow stays the same while your readers get a safer version by default. ## What about photographers who want to keep some metadata? We built this with the default set to privacy-first because most creators forget metadata exists until it's too late. If you specifically need to preserve technical metadata for a portfolio proof or licensing context, you can download the original file from your media library at any time. The published copy remains stripped, which is the right default for anything living on the open web. That's really the decision underneath all of this, more than any single technical detail. Defaults are what most people actually experience, because most people never open a settings panel to go looking for a toggle. A privacy feature that only works if you remember to turn it on protects the minority who read documentation and quietly skips everyone else. Stripping metadata automatically means the protection covers every blogger from their very first upload, not just the ones who went hunting for a setting called "privacy." Privacy-by-default shouldn't be a feature you have to configure. It should be the floor. VeloCMS already handles responsive images, WebP conversion, and CDN delivery automatically, so adding metadata stripping fits the same philosophy: publish great-looking media without becoming an accidental source of personal data. If you're building a site where images matter and you don't want to worry about what's hiding inside them, VeloCMS is available on a 14-day free trial. Upload a photo, publish it, and rest easy knowing the story your readers see is the one you actually wrote. --- # How Do I Sell Event Tickets Directly From My Own Website? > Source: https://velocms.org/blog/sell-event-tickets-from-your-own-website > Published: 2026-07-29 You can sell event tickets directly from your VeloCMS site without sending readers to a third-party platform. The new event ticketing feature lets you create ticket tiers, collect payments, and manage attendees inside the same dashboard you already use for your blog and storefront. Selling event tickets usually means surrendering your audience to Eventbrite or another middleman, paying their fees, and hoping attendees remember your brand later. That never felt right for independent creators who already own a website and an audience. With VeloCMS, event tickets now live on the same domain as your blog, your shop, and your newsletter — one login, one checkout experience, one place where your business actually lives. When you create an event, you build ticket tiers the same way you would build product variants. A general admission ticket at one price, an early-bird tier at another, maybe a VIP option with extras like priority seating or a meet-and-greet. Each tier gets its own stock count, so overselling a small venue becomes a non-issue. Readers browse the event page, pick the tier that fits them, and check out through the same Stripe flow that already powers memberships and physical products. The whole transaction happens under your brand, on your custom domain, with your own design wrapped around it. ## What happens after someone buys a ticket? The purchase lands in your orders dashboard alongside everything else you sell, and the buyer turns into a row on that event's attendee list with the details you actually need: name, email, ticket type, quantity. No separate login to a second platform, no exporting a CSV from somewhere else and reconciling it by hand, no wondering whether the payment cleared before you print the guest list. It is the same commerce engine you already use, just pointed at a date and a venue instead of a box you ship. That single-dashboard part sounds like a small convenience until the week of the event, when it stops being one. Most independent organisers end up running a spreadsheet next to a ticketing platform next to their email list, and every one of those three has a slightly different idea of who is coming. Reconciling them is the actual work, and it always lands the night before. When the sale, the attendee record, and the customer relationship are the same object in the same database, that reconciliation job simply does not exist. ## How do I check people in at the door? Every registration carries its own check-in token, and your admin has a check-in view for each event. You open it on a phone at the door, scan or look people up, and the list updates as they arrive — so you can see at a glance how many of the people who paid have actually walked in. Because the tokens are random and single-purpose, a forwarded screenshot does not quietly become two admissions. This is the part most creators underestimate when they first sell tickets. Taking the money is easy; knowing who is standing in front of you is what makes the evening run. A printed list works right up until someone is not on it, and then you are the person holding up a queue while you search an inbox on your phone. ## Do I need a separate events plugin? Not anymore. Event tickets are built into the core commerce layer. If your site already accepts payments, you can list an event in minutes without installing anything extra. The same tax settings, the same payout routing, and the same custom-domain checkout your readers already trust. You do not have to patch together another tool, sign another terms-of-service agreement, or train yourself on a new interface that looks nothing like the rest of your site. This matters most when your events are part of a larger business rather than the whole of it. A photography educator running workshops, a podcaster hosting live shows, a restaurant doing ticketed tastings, or an indie maker running a small conference. For every one of them the event is a chapter in something longer — the workshop attendee is next year's course buyer, the tasting guest is a regular, the conference ticket is the start of a mailing list. Hand that first transaction to a marketplace and you get the money but not the thread. The buyer's email belongs to the platform, the follow-up gets sent by the platform, and the next time you have something to announce you are renting access to people you already met. Selling on your own domain keeps the thread in your hands: same customer record, same list, same site they will come back to. The attendee is your customer, not the platform's. ## How do I get started? Open your VeloCMS admin, head to the commerce section, and create a new event. Set the date, location, and ticket tiers, then publish the page. Your existing audience can buy without leaving your domain, and you can manage everything from the dashboard you already know. If you are not on VeloCMS yet, start a 14-day free trial and publish your first event this week. --- # How to Automate Your Blog Publishing with n8n and Claude > Source: https://velocms.org/blog/automate-blog-publishing-n8n-claude > Published: 2026-07-20 Most blogging routines have a copy-paste tax hiding in them somewhere. You draft in one tool, paste into another, upload the image separately, publish, then go tell your other systems it happened. None of those steps is hard. Together, they're the reason "I'll post twice a week" quietly becomes once a month. This week that tax gets a lot smaller. VeloCMS now has an official community node for n8n — the open-source automation platform — and an MCP server that lets AI tools like Claude work your blog directly. Both talk to the same public REST API, both authenticate with a single scoped API key from your dashboard, and both were built by us, not a third party guessing at our endpoints. ## What can you actually automate with the n8n node? The node covers the things a real publishing workflow needs: create a post, publish it (immediately or as a draft for review), update or fetch existing posts, and upload media. There's a companion trigger node too, so a workflow can *start* from your blog instead of ending there — a new post goes live and n8n fans it out to wherever you want the news to travel. The workflows practically write themselves once the node exists. A form submission becomes a draft for your review. A row added to a spreadsheet becomes a scheduled post. A new post triggers a message to your community. If you've used n8n at all, you already know this shape — the node just makes your blog one of the thousand-plus things it can wire together. ## How do you connect n8n to your blog? Two steps, and neither involves code. First, install the node: in n8n, open Settings, choose Community nodes, and install `n8n-nodes-velocms` by name. ![The n8n community nodes install dialog with n8n-nodes-velocms entered in the npm package name field](/screenshots/blog/n8n-install-node.jpg "Settings → Community nodes → install n8n-nodes-velocms") Second, create a credential. In your VeloCMS dashboard, go to Settings and open API Keys, generate a key (it starts with `velo_` and you scope what it's allowed to touch), then paste it into the node's credential form along with your blog's URL. n8n's built-in credential test tells you on the spot whether the connection works — no publishing a test post to find out. ![The VeloCMS node open in n8n with a connected account credential and a Create Post operation executing](/screenshots/blog/n8n-credential-create.jpg "One scoped API key connects the credential — the test confirms it before you build anything") Here's the whole thing end to end — install, credential, first post, and an AI agent reading the blog — in about a minute: [[video src="https://pub-8a9958c265c64c16ab56981176d74563.r2.dev/marketing/n8n/verified-node-demo-1.0.5.mp4" poster="/screenshots/blog/n8n-credential-create.jpg" caption="Installing the VeloCMS node, connecting a credential, publishing a post, and handing the blog to an AI agent — in about a minute." duration="PT1M2S"]] ## Can an AI agent run your blog? This is the part that surprised us in testing. The node is marked as usable by n8n's AI Agent, which means an agent can pick up your blog as a *tool* — read what's published, draft something new, publish it — as one step in whatever reasoning loop you've given it. You describe the job in plain language; the agent decides when touching the blog is the right move. ![An n8n AI Agent workflow with the VeloCMS node attached as a tool, its description set automatically, processing real post data](/screenshots/blog/n8n-ai-agent-tool.jpg "The node plugs into n8n's AI Agent as a tool — the agent decides when to use it") That's a different proposition from a fixed automation. A workflow does the same thing every time. An agent with your blog as a tool can summarize the week's posts into a digest, or notice a gap and draft something to fill it — and you still hold the publish gate if you route its output to drafts. ## What if you'd rather stay in Claude? Not everyone wants a workflow canvas. If your writing already happens in Claude Code, Claude Desktop, or Cursor, the MCP server is the shorter path: run `npx @velocms/mcp` with your API key and your assistant gets thirteen tools against your blog — drafting and publishing posts, uploading media, moderating comments, managing members, reading site settings. You finish a piece in conversation, say "publish it," and it's live. No tab switch, no paste. Both integrations respect the same boundary: the API key is scoped, revocable in one click from the dashboard, and never gives an automation more access than you chose to hand it. (And if your dashboard is getting busy enough that finding that settings page takes a beat — the new command palette ships this week too. Press one shortcut, type "api", you're there.) The larger point isn't any single workflow. It's that your blog stopped being a destination you have to visit and became infrastructure other tools can build on. If you want to try it on a blog of your own, [start a 14-day free trial](/signup) — the API keys page is waiting in the dashboard, and the node is one install away. --- # How to Connect a Custom Domain to Your Blog (From Any Registrar) > Source: https://velocms.org/blog/connect-custom-domain-to-your-blog > Published: 2026-07-13 There's a moment, usually a few weeks into blogging, when the training wheels start to chafe. Your posts are good. People are reading them. And then someone asks for your website and you hear yourself spelling out a subdomain — your-name-dot-something-dot-org — and it lands with all the authority of a school project. A domain of your own is one of those small purchases that changes how seriously everyone takes the work, including you. The good news is that the scary part of connecting one — the DNS records, the SSL certificates, the acronyms that read like radio static — has mostly been automated away. On VeloCMS, the whole process is one screen and a short visit to wherever you bought the domain. Here's the entire walkthrough, plus what's actually happening under the hood, so nothing about it feels like a magic trick you're afraid to touch. ## Why does a custom domain matter for a blog? Three reasons, in ascending order of importance. First, memorability: "myblog.com" survives being said out loud at a dinner table; a subdomain usually doesn't. Second, ownership: your domain is an asset you control, independent of any platform, and every link anyone ever shares accrues to something that's yours. Third — and this is the one people underrate — search engines treat your domain as the container for all of your reputation. Reviews, backlinks, mentions, years of posts: all of it compounds against one name. Starting that compounding early is one of the cheapest SEO decisions you'll ever make. None of this means you need a domain on day one. Your blog is live on its velocms.org subdomain the moment you sign up, and that address keeps working even after you connect your own. But the earlier you make the switch, the less link equity you leave scattered behind you. ## What do you need before you start? Two things. A VeloCMS blog on any paid plan, and a domain you own — from literally any registrar. Namecheap, GoDaddy, Cloudflare, Porkbun, Google-Domains-refugee registrars, the one your uncle recommended in 2011: all fine. You don't transfer the domain to us, you don't change nameservers, and you don't need a hosting add-on. The domain stays exactly where it is; you'll just add a couple of DNS records to point it at your blog. Both root domains (myblog.com) and subdomains (blog.mystudio.com) work, which matters if your main site lives elsewhere and you only want the blog on a subdomain. ## How do you connect the domain in VeloCMS? From your admin dashboard, head to the custom domain setup screen. It looks like this — one field, one button, and a note reminding you the subdomain keeps working if you'd rather do this later: ![The VeloCMS custom domain setup screen, showing a single domain input field with an Add Domain button and an explanation that SSL and CDN routing are handled automatically](/screenshots/blog/custom-domain-setup.jpg "One screen: type the domain you own, click Add Domain") Type the domain exactly as you want visitors to reach it — root or subdomain — and click Add Domain: ![The same setup screen with "myblog.com" typed into the domain field and the Add Domain button active](/screenshots/blog/custom-domain-filled.jpg "Root domains and subdomains both work, from any registrar") That's the entire VeloCMS side of the job. The moment you add the domain, the platform provisions it through Cloudflare behind the scenes and shows you the exact DNS records to create at your registrar — copy-paste values, no guesswork. ## What DNS records do you add at your registrar? This is the part with the reputation, so let's demystify it. DNS records are just address-book entries: they tell the internet which server answers for your name. VeloCMS shows you precisely which entries to add for your specific domain, and they fall into two familiar shapes. A root domain gets a record pointing it at our edge; a subdomain gets a CNAME doing the same. There's also a small TXT record that proves to the certificate authority that you actually control the domain, which is what lets the SSL certificate get issued for you automatically. You add those records in your registrar's DNS panel — usually under a tab literally called "DNS" — and then you wait. Propagation typically takes a few minutes, occasionally a few hours if your registrar is slow to publish. VeloCMS keeps checking in the background and flips your domain to verified the moment the records are visible. HTTPS comes with it; there is no certificate to buy, renew, or think about ever again. While you wait, nothing breaks. Your velocms.org subdomain keeps serving your blog the whole time, so readers mid-scroll never notice the plumbing being connected beneath them. ## What about the links people already shared? They keep working. The subdomain doesn't die when your custom domain goes live — both addresses resolve to your blog, so old bookmarks, old newsletter links, and that one post that did numbers on X all still land where they should. Going forward, your custom domain is the address on your site's canonical tags and the one you should put on everything, but the transition costs you nothing you've already earned. One quiet detail worth knowing: because the certificate and routing run through Cloudflare's network, your blog also picks up CDN-grade delivery on your own domain — the same edge delivery of pre-rendered pages VeloCMS is built around, now under your name. The whole thing — buying a domain excluded — takes maybe ten minutes, most of which is your registrar's dashboard loading. If your blog is still wearing its subdomain, [start a 14-day free trial](/signup) or open your dashboard, and give the work a name that's actually yours. --- # How to Sell Products on Your Blog Without Installing Shopify > Source: https://velocms.org/blog/sell-products-on-your-blog-without-shopify > Published: 2026-07-12 Somewhere around your two-hundredth post, a strange thought creeps in. You've got readers now — real ones, people who show up, who reply to your newsletter, who send you a DM saying one specific paragraph changed how they think about something. And somewhere inside that audience is a handful of people who would, if you let them, just buy the thing you keep talking about. A print. A notebook. A digital template you built for yourself and never bothered to package up. The instinct, for most of us, is to reach for Shopify. It's the obvious answer, the one every "how to sell online" guide points you toward. But bolting a full e-commerce platform onto a blog you already built somewhere else is its own project — a new subdomain, a second design system to maintain, an embed widget that looks like it got airlifted in from a completely different website, because, well, it did. You end up paying a monthly platform fee for a store that doesn't match your blog, plus a cut on every sale, plus the quiet tax of switching between two admin panels every time you want to change a price. There's a simpler version of this. What if the shop wasn't bolted on at all — what if it just lived there, using the same theme, the same nav, the same voice, because it's the same site? ## Why does bolting Shopify onto a blog you already built feel like duct tape? Because it is duct tape. Most "add a store to your blog" tutorials walk you through embedding a Shopify Buy Button, or an iframe, or a widget script — and every one of those approaches has the same tell. The typography doesn't match. The button radius is off by a few pixels from everything else on the page. The colors were picked for a generic storefront template, not for the specific, deliberate aesthetic you spent a weekend tuning. Readers notice, even if they can't say exactly why. A mismatched shop reads as an ad, not a product you're proud of. The deeper issue is architectural. Shopify (and most standalone store builders) are designed to be the *entire* website. Your blog is an afterthought bolted onto their system, not the other way around. So when you already have the blog — the content, the SEO, the years of archive — and you just want to add selling on top, you're forcing two products that were never meant to share a roof to somehow cohabit. One of them always loses the design argument, and it's never the store. ## What does a store built into your own theme actually look like? VeloCMS takes the opposite approach: the shop isn't a separate app you embed, it's a rendering surface your theme already owns. Under the hood, the platform hands your active theme a plain, structured feed of your products, prices, and cart state — what we call the raw-data shop contract — and the theme decides how to actually draw it. That's the whole trick. Nobody hand-designed all 39 individual storefronts (as of September 2026) by copying one another; every theme's designer just extended the visual language they'd already built for posts and pages into commerce, using the same data every other theme gets. You can see the difference immediately when you put two themes side by side. Here's Maker Supply Co., running the Terminal theme — dark background, monospace type, a shop rendered like a command-line directory listing, right down to the "grep --query" search field: ![The Terminal theme's shop page, styled as a dark command-line interface with monospace type and a grep-style product search field](/screenshots/blog/shop-terminal-theme.jpg "Terminal theme — the shop reads like a directory listing, not a bolted-on widget") And here's Atelier Lumen, running the Atelier theme on the exact same underlying commerce engine — light background, a large serif "Shop" headline, soft category pills, product cards with generous whitespace: ![The Atelier theme's shop page, styled as a light, editorial boutique with a large serif headline and rounded category filter pills](/screenshots/blog/shop-atelier-theme.jpg "Atelier theme — same commerce data, an entirely different design language") Same product grid, same filters, same cart. Neither one looks like a plugin. Neither one looks like the other. ## How do you actually start selling products on your blog? There's no separate onboarding flow to learn. From your VeloCMS admin, you flip commerce on for the tenant, and a Shop link appears in your nav automatically — themes pick it up without you touching a template file. From there you add your first product, choosing digital (a PDF, a Notion template, a video course you deliver instantly on purchase) or physical (something that needs a shipping address and, eventually, a tracking number). Pricing, a description, and a cover image are all you need to get a product live. The part that actually matters for your margin comes next: connecting a payment processor. VeloCMS is BYOK here — bring your own keys — so you link your own Stripe or PayPal account directly, and money from a sale lands in *your* account, not ours, with 0% platform commission taken off the top. No revenue share, no waiting period, no third party sitting between you and your buyer's card. If you'd rather not build a full catalog yet, gift cards are built in too, which turns out to be a surprisingly good way to test whether your audience is willing to spend money on you at all before you commit to inventory. ## Does every one of VeloCMS's 39 themes (as of September 2026) really look different? It's worth pushing on this claim, because "every theme is unique" is the kind of thing marketing copy says about everything. Here's Chloe Noir, running the Velvet Editorial theme — a warm, cream-and-blush fashion-magazine aesthetic, italic serif headline, product cards that look like they belong in a print catalog rather than a checkout flow: ![The Velvet Editorial theme's shop page, styled as a warm cream and blush fashion magazine layout with an italic serif headline](/screenshots/blog/shop-velvet-theme.jpg "Velvet Editorial theme — the same product data rendered as a fashion catalog spread") Put this next to the Terminal and Atelier screenshots above and you're looking at three completely different visual systems rendering identical underlying data: same product titles, same prices, same cart logic. That's the raw-data shop contract doing its job — the theme decides the shape, not the commerce engine. ## What happens when a reader actually wants to buy something? For a digital product, checkout is fast: the reader pays through your connected Stripe or PayPal, and delivery happens instantly — a download link, an access grant, whatever you configured. For a physical product, you collect a shipping address at checkout the same way, and fulfillment is on you, exactly like it would be anywhere else. The cart itself lives quietly in the corner of your theme's nav, the same one your readers already recognize, so buying something never feels like leaving your site. If you'd rather watch this than read about it, here's a short walkthrough across a handful of VeloCMS's 39 themes (as of September 2026), shop pages included: [[video src="https://pub-8a9958c265c64c16ab56981176d74563.r2.dev/marketing/howto/howto47-full.mp4" poster="/screenshots/blog/shop-atelier-theme.jpg" caption="39 blog themes as of September 2026 — including how each one renders its own shop." duration="PT1M49S" youtubeUrl="https://www.youtube.com/watch?v=mF5gjM1Hsmg"]] None of this requires you to abandon the blog you've spent years building, or to learn a second platform's admin panel, or to hand a chunk of every sale to a company that's never read a word you've written. The shop is just another part of the site your readers already trust. If you want to see it on your own blog, [start a 14-day free trial](/signup) and turn commerce on from the dashboard — the theme you're already using will handle the rest. --- # Why Subscriber-Owned Newsletters Beat Substack After You Hit 1K Readers > Source: https://velocms.org/blog/subscriber-owned-newsletters-vs-substack > Published: 2026-04-28 Let's give credit where it's due: Substack changed the game. It made starting a newsletter dead simple. You get a landing page, a text editor, and a payment system all rolled into one, with zero upfront cost. For someone just dipping their toes into the creator economy, that's an incredible deal. It's the perfect incubator for finding your voice and your first hundred fans. But incubators, by their nature, are temporary. They're meant for starting, not for scaling. There comes a point in every successful newsletter's journey where the cozy convenience of Substack starts to feel less like a support system and more like a golden cage. That point, for many, is the 1,000-subscriber mark. Why a thousand? It's a magic number. It's the moment your project often transforms from a hobby into a potential business. It's the point where you've proven product-market fit. People are not only reading your work, but they're willing to pay for it. And it's precisely at this milestone that Substack's business model begins to work against you. Let's do some back-of-the-napkin math. Say you have 1,000 paying subscribers at a pretty standard $10 a month. That's $10,000 in monthly revenue, or $120,000 a year. It's a fantastic, life-changing amount of money for an independent writer. Substack takes a 10% cut of that. So, you're paying them $1,000 a month, or $12,000 a year, just for the privilege of using their platform. And remember, that's *before* Stripe takes its own processing fee (usually around 2.9% + 30¢ per transaction). Suddenly, that "free" platform is your single biggest business expense. The question you have to ask yourself is: what am I getting for that $12,000? Early on, the answer is "discovery." Substack's network and recommendation engine can be a huge boost. But once you have 1,000 dedicated readers, where is your next subscriber *really* coming from? Is it the Substack homepage, or is it from your own guest appearances on podcasts, your social media presence, and—most importantly—your existing readers sharing your work? For most established writers, the engine of growth is their own brand, not the platform's algorithm. This leads to the thornier issue: ownership. When your business is built on someone else's platform, you don't truly own it. You're a tenant, not a homeowner. You can export a CSV of your email list from Substack, which is better than nothing, but it's not the whole story. Substack does connect your own Stripe account behind the scenes to collect the money, but the subscription record itself was created under Substack's platform, so it doesn't come with you if you leave — every paid reader has to re-enter their card details wherever you land next. You don't own the design, either. You're subject to their terms of service, their content moderation policies, and their future business pivots. If Substack decides to change its algorithm, raise its fees, or gets acquired by a company with different priorities, your business is at their mercy. True ownership means controlling the core assets of your business. It means your subscriber data is yours, period. It means the revenue flows directly from your readers into your bank account, without a middleman taking a hefty percentage. This is where moving to a platform like VeloCMS comes into the picture. With VeloCMS, you bring your own keys (BYOK) to Stripe. When a reader subscribes, the payment goes straight to your Stripe account. We never touch your money. That 10% platform fee vanishes. Our model is a predictable, flat fee that you can see on our [pricing page](/pricing), which doesn't penalize you for growing. That $12,000 you were paying to Substack? It's back in your pocket, where you can reinvest it in your business, hire an editor, or just, you know, live on it. I know what you're thinking—migration sounds like a nightmare. We've worked hard to make it as painless as possible. You export your list from Substack and import the CSV into VeloCMS. Free subscribers land in your new list right away. For paid subscribers, VeloCMS marks them as paid members the moment they're imported, so their access to paid content isn't interrupted while you get set up—and they sign in with a magic link instead of creating a new password. What doesn't come across is the Stripe subscription itself: an active subscription is tied to the Stripe account that created it, so there's no way to move recurring billing between platforms, on VeloCMS or anywhere else. You'll still need to invite paid subscribers to set up billing with you directly through a short checkout link, not a full signup flow, to keep that revenue flowing once you're ready to start charging on your own account. And the ownership goes further than the export button. VeloCMS runs on a flat fee with no revenue cut at any subscriber count, which means the math that made Substack expensive at 1,000 subscribers just doesn't happen here — you don't watch your platform bill climb in lockstep with your success. Your subscriber data, your posts, your media: all of it is yours, and you can pull a full export of everything, any time, straight from the dashboard. No support ticket, no waiting period, no proprietary format designed to make leaving annoying. The trade-off, if you can call it that, is that you take on a little more responsibility for your own discovery than a marketplace-style platform hands you. It's a step up in complexity from Substack's all-in-one simplicity. But at 1,000 subscribers, you're ready for that step. You're no longer just a writer; you're a business owner. For a more detailed breakdown of the differences, our [Substack comparison page](/vs/substack) lays it all out. Graduating from Substack isn't a knock against it. It's a sign that you've succeeded on the very terms it enabled. You built an audience so loyal and a product so valuable that it no longer makes sense to pay a five-figure tax for the training wheels you've long since outgrown. It's time to own your work, own your audience, and own your revenue. --- # The First 90 Days of a Photographer's Online Portfolio That Actually Sells Prints > Source: https://velocms.org/blog/photographer-portfolio-first-90-days > Published: 2026-04-28 There's a moment of truth for every photographer who decides to sell their work online. It's that jump from creating for yourself to creating for a collector. The dream is a clean, beautiful space on the web that feels like your personal gallery—a place where your work breathes. The reality, too often, is a stall in a crowded digital marketplace like Etsy or a generic template on Squarespace, where platform fees nibble away at every single sale. Building your own home online feels like a monumental task, but it's more achievable than you think. It's not about becoming a web developer overnight. It's about a focused, three-month push to build a foundation for a business that can sustain your art for years. Let's walk through what that actually looks like. ### Days 1-30: The Brutal Edit and a Solid Foundation The first month is all about laying the groundwork. And let's be honest, the hardest part isn't the technology—it's the edit. Culling years of work down to a cohesive, powerful portfolio is an agonizing but essential process. It's tempting to show everything, but curation is what separates a professional gallery from a camera roll. This is where you have to be ruthless. Your portfolio should be a short, powerful sentence, not a rambling paragraph. Here's a piece of data that might help you make those tough choices: in the fine art world, it's widely understood that about 80% of a photographer's print revenue will come from just 20% of their images. The Pareto principle is alive and well. Your job in this first month is to make an educated guess about which images belong in that top 20%. These are your hero shots, the ones that define your style and your point of view. Lead with them. Once your edit is locked in, getting the site live is the next step. You need a platform that puts your images front and center without compressing them into oblivion or hitting you with surprise bandwidth bills. This is why we built VeloCMS with native Cloudflare R2 storage—it's designed to handle massive, high-resolution files without breaking a sweat (or your bank account). You can upload your best work and know it will load fast and look stunning. Alongside your gallery, set up a simple blog. This isn't for sharing vacation photos; it's your long-term SEO engine. Write about the story behind a specific photo, the gear you used for a particular series, or the location that inspired you. These posts are magnets for search traffic and people who are genuinely interested in your craft. ### Days 31-60: Opening the Shop and the First Sale With your digital gallery walls up, month two is about unlocking the door and putting a price on the work. This is where many artists get stuck. How do you price a photograph? You can go the simple route: (cost of printing + cost of shipping) + your desired margin. It's a clean, logical formula. But are you selling paper and ink, or are you selling a piece of your vision, a story, a moment that can never be repeated? This is the argument for value-based pricing. Your price should reflect the skill, time, and artistic sensibility that went into creating the image. It positions you as an artist, not just a print-shop operator. Start with a few of your strongest pieces. Offer them in a limited run, maybe signed and numbered, in one or two standard sizes. Don't overwhelm visitors with a dozen different paper types and framing options. Keep it simple and elegant. And then, you wait. The days or weeks leading up to the first sale can be nerve-wracking. You'll check your analytics, you'll tweak your product descriptions. Then, one day, you'll get that first email notification. That first sale is rarely about the money. It's pure validation. It's proof that someone out there connected so deeply with your work that they wanted to make it a physical part of their life. Don't underestimate how powerful that feeling is. It's the fuel for everything that comes next. ### Days 61-90: From Visitors to Collectors One sale is a victory. A sustainable business is a system. Month three is about building that system. You can't just hope the next person stumbles upon your site; you have to build a way to stay in touch. This is the crucial difference between a casual visitor and a true collector. Collectors want a relationship with the artist. The best way to build that is with an email list. Your email list is the only audience you truly own—it's immune to algorithm changes on Instagram or Facebook. Add a simple, non-annoying signup form to your site. Promise them first access to new series, stories behind the work, and maybe an exclusive print offering every now and then. Your newsletter isn't a sales circular; it's a letter from your studio. It's where you share your process and your passion. For your most dedicated fans—the ones who reply to your emails and ask about your technique—you can offer something even deeper. This is where a modern CMS can really shine. VeloCMS has a built-in paywall feature that lets you protect certain posts or pages for members only. You could create a section for a small monthly fee that gives collectors access to behind-the-scenes videos, essays on your creative process, or even digital contact sheets. It's an incredible way to serve your biggest supporters and generate a predictable, recurring income stream that isn't tied to one-off print sales. This 90-day framework isn't a magic formula, but it is a focused plan. It moves you from simply having a portfolio to running a photography business on your own terms. We've thought a lot about what photographers need to make this leap, building tools that support the art, not just the transaction. It's a different approach, and you can see a full breakdown of how we're building a better home for your work in our [guide for photographers](/for-photographers). The goal is independence—artistic and financial. And that's a project worth investing in. --- # What WordPress Got Wrong About Plugins (And What We're Trying) > Source: https://velocms.org/blog/what-wordpress-got-wrong-about-plugins > Published: 2026-04-28 Let's get one thing straight: the idea behind WordPress plugins is brilliant. It's a promise of infinite extensibility, a blank canvas where anyone can add any feature they can dream up. It's the reason WordPress powers something like 43% of the web. But after two decades, we have to admit that this promise has a dark side. The very thing that made WordPress a giant is also its most profound, deeply-rooted architectural flaw. We've all been there. You get a call from a client—or worse, an automated alert at 3 AM—that their site is down, defaced, or sending out spam. You log in, heart pounding, and start the grim process of elimination. Disable all plugins. Re-enable one by one. It's almost always a plugin. Maybe it was an obscure one the client installed for a blinking-text widget, or maybe it was a popular one with a zero-day vulnerability. The specific culprit doesn't matter as much as the underlying cause. The original sin of the WordPress ecosystem is that every plugin is just a bundle of PHP files running with the exact same permissions as the WordPress core itself. It's untrusted code, often written by a stranger with unknown skills and motivations, executing in the same process that handles your content, your users, and your database. There is no sandbox. There is no containment. A single poorly-written line in a free SEO plugin can read your `wp-config.php` file and hand over your database credentials to an attacker. That's not a bug; it's the design. This technical problem is compounded by a broken economic model. A developer builds a genuinely useful plugin. It gets popular. Suddenly, they're on the hook for support, security patches, and compatibility updates for a user base of thousands, all for free. It's completely unsustainable. So what happens? The developer either burns out and abandons the project (creating a ticking security time bomb for everyone still using it), or they sell it. Often, the buyer is a private equity firm or a large plugin conglomerate that immediately guts the free version, plasters it with aggressive upsells, and slowly lets the code quality slide. The user is left holding the bag every single time. Look no further than WooCommerce for the perfect case study in this sprawl. It's sold as a simple way to add a store to your site. But to build a functional, modern e-commerce operation, you don't just install WooCommerce. You need a plugin for Stripe payments. Another for advanced shipping calculations. One for subscriptions. Another for abandoned cart emails. One for custom product fields. Before you know it, you're juggling seven, ten, maybe fifteen different plugins from a dozen different vendors, each with its own update cycle, potential conflicts, and security surface area. Your simple store has become a fragile house of cards, and you're the one who has to live in it. When we started mapping out VeloCMS, we knew we couldn't ignore the need for extensibility. But we also refused to repeat the mistakes of the past. The problem isn't the *idea* of plugins; it's the lazy, insecure implementation that has become the industry standard. Our approach starts by treating third-party code with the healthy suspicion it deserves. We're building our plugin architecture around two core principles: isolation and explicit permissions. For isolation, we're designing the system to run third-party code in sandboxed V8 Isolates. Think of it like a secure container. A plugin lives and runs inside this little box, and it can't see or touch anything outside of it unless it's explicitly allowed to. If a plugin has a vulnerability, the damage is contained to its own sandbox, not your entire application. It's the difference between a leaky faucet in one apartment and a flood that brings down the whole building. The second piece of the puzzle is what we're calling a capability manifest. Before you even install a plugin, it will have to declare exactly what it needs to do. Does it need to read posts? Does it need to write to a specific database table? Does it need to make an external network request to a third-party API? It's all listed in a plain-text file. This is fundamentally about consent. It puts the power back in the hands of the site owner, just like your phone asks for permission before an app can access your camera or contacts. No more silently installing a plugin that turns out to be scraping your user data. This leads to an open-core model. The essential, high-stakes functionality—the stuff that absolutely needs to be secure and stable—will be built and maintained by our team as first-party features. For everything else, the sandboxed, permission-based plugin system will provide a safe way for the community to extend the platform. This is a core part of how we see ourselves as a serious [WordPress alternative](/vs/wordpress). Now, for a dose of honesty. This secure plugin sandbox is a cornerstone of our v2 architecture. It is not shipped today. Building a truly isolated, high-performance runtime for untrusted code is a massive undertaking, and we're not going to cut corners. But we're not just waving our hands and making promises, either. The groundwork is being laid right now. The capability manifest specification is already part of our core design, shaping how we think about every feature we build. We believe in getting the foundation right first, something that many platforms forget in their rush to add features. You can see the work we're putting into that foundation over on our pages [for developers](/for-developers). Fixing the plugin problem isn't about having more plugins. It's about having better, safer ones. It's about creating an ecosystem where developers can build and distribute extensions without inadvertently putting users at risk, and where users can extend their sites with confidence. It requires a fundamental shift in thinking, moving from a model of implicit trust to one of explicit, verifiable permissions. It's a harder path, but it's the only way to build a CMS that's truly fit for the next decade. --- # AI for Bloggers: Stop Using It to Write, Start Using It to Edit > Source: https://velocms.org/blog/ai-for-bloggers-stop-writing-start-editing > Published: 2026-04-28 Let's get the obvious out of the way. A machine is helping me with this post. But it didn't write it, and that's the whole point. The tension around AI in creative work is palpable. You can feel it. We're told it's the future, a tool to 10x our output, but every time we paste a chunk of AI-generated text into our draft, something feels… off. It's a bit like a meal replacement shake. Nutritionally complete, I guess, but utterly devoid of joy. Readers can feel it, too. They can sniff out that perfectly structured, grammatically flawless, and emotionally vacant prose from a mile away. It's the uncanny valley of text. It hits all the right notes but has no soul, no unique rhythm, no weird little authorial tics that make writing feel human. AI models are trained to predict the next most likely word, which makes them masters of the average. They create a smoothed-over, sanitized version of whatever they've been fed. The result is content that sounds like a B-student's book report: correct, but you'd never read it for fun. This is where so many creators get stuck. They try to use AI as a ghostwriter, get a hollow first draft, and then spend more time trying to inject a personality into it than it would have taken to just write the damn thing from scratch. It's a frustrating cycle. But what if we've been looking at the tool all wrong? The real leverage isn't in asking AI to create. It's in asking it to refine. This is the big shift in thinking. Don't use it as your writer; use it as your tireless, uncomplaining, and brutally honest editor. Think of the old (and probably apocryphal) Hemingway advice: "Write drunk, edit sober." Your first draft is the raw, passionate, messy "drunk" part. Get your ideas on the page. Don't worry about perfect phrasing or finding that one brilliant metaphor. Just pour it all out. Then, bring in your sober editor. AI is incredible at this. It doesn't have an ego. It will mercilessly point out that you used passive voice three times in one paragraph. It will highlight wordy sentences and suggest trimming the fat. It will spot weak paragraph openers that are lulling your reader to sleep. This isn't about replacing your voice; it's about sharpening it. The AI handles the mechanical grunt work, freeing you up to focus on the story, the argument, and the unique perspective that only you can bring. Here's what that looks like in practice inside VeloCMS. As you write, our analysis panel is working right alongside you, but it's not just a simple SEO score. We built a dual-scoring system. On one side, you have a 9-factor technical SEO analysis that checks all the boxes for search engines. But right next to it is an 11-factor LLM-readiness score that measures how easily an AI assistant can pull answers out of your post: heading density, short paragraphs, lists, sentence length, a direct-answer opening, a TL;DR block, and more. It's a set of rule-based checks, not a model grading your prose, and it's a constant, gentle nudge toward clearer structure. When you hit a specific roadblock—maybe a sentence feels clunky or a paragraph just isn't landing—you don't have to leave your workflow. You can just highlight the text, use the `/ai` slash command right in the editor, and give it a direct order. Things like "Make this more concise," "Rephrase this in an active voice," or "Suggest three alternative headlines for this section." It's surgical. You're not handing over the reins; you're using a precision tool to fix a specific problem. You remain the author, the architect of the piece. The AI is just your very capable assistant. This approach completely sidesteps the guilt and the hollowness of AI writing. You aren't faking it. The core ideas, the voice, the stories—they are all yours. You're simply using an incredibly powerful tool to polish your work to a professional shine, faster than you could on your own. It helps you get from a messy first draft to a sharp, compelling final piece without losing the very thing that makes people want to read your work in the first place: you. So, stop trying to make the robot sound human. It's a losing game. Instead, let your human voice be as messy and authentic as it needs to be, and then let the robot come in and tidy up afterward. That's the partnership that actually works, and it's how you can use these powerful new tools to elevate your craft, not replace it. You can see how we've integrated these tools into the VeloCMS editor on our [AI assistant feature page](/admin/tools). It's all about making your own voice clearer, not handing it over. One practical note: the best AI editing sessions happen when you give the tool a specific job. "Shorten this paragraph to three sentences" beats "make this better" every single time. Vague prompts produce vague results. Treat it like delegating to a junior editor — precise instructions, real constraints. That's when you start getting genuine value out of the tool, rather than just more generic-sounding prose. ## Help Center Articles --- # How to set up VeloCMS in 60 seconds > Source: https://velocms.org/help/setup-velocms-60-seconds > Category: getting-started | Updated: 2026-10-12 VeloCMS is designed to get you publishing in seconds, not hours. Here is the complete setup, start to finish, with no detours. [Video: Sign Up, Write, Publish — Start To Finish](https://media.velocms.org/marketing/howto/howto1-full.mp4) — Watch account creation, a niche-matched theme, an AI-assisted first draft, and a live publish, in one real walkthrough. ## Step 1 — Create your account Head to the pricing page, pick a plan (Pro is the most popular), and click Start Free Trial to open signup. You will be asked for your name, email, a password, and a blog name. The blog name becomes your subdomain — for example, a blog named "Jane Writes" will live at jane-writes.velocms.org. The slug is auto-generated from the name but you can edit it. Signing up does not start the trial or ask for a card; the plan you picked is remembered and used when you start the trial in Step 3. ## Step 2 — Verify your email We send a verification link to the address you provided. Click it within 24 hours to confirm ownership. Your tenant is not created until verification — this prevents squatting on reserved slugs. > **INFO:** Verification emails come from noreply@velocms.org. If it is not in your inbox within 2 minutes, check the Promotions or Spam folder. ## Step 3 — Start your free trial After verification your site is created with no plan, so you can draft but not publish until the trial starts. In the onboarding wizard, the last step takes the site owner to Stripe Checkout to start the 14-day free trial on the plan you picked on the pricing page; the card is added there, and you will not be charged until day 15. If you skip the wizard, the banner at the top of the admin and the Billing page offer the same Start your 14-day free trial button. You can cancel anytime from the admin billing page and you pay nothing. ## Step 4 — Write your first post Once your trial has started you can publish (until then you can write drafts). From your admin dashboard, click the big New Post button (or press the plus icon in the bottom-right). The editor supports slash commands — type / to insert headings, lists, code blocks, or AI-generated content. Save a draft or publish immediately. ## Step 5 — Share your blog Your blog is live at your subdomain (for example jane-writes.velocms.org) the moment you publish your first post. Content is served from Cloudflare's edge network — pages are server-rendered and cached rather than built from scratch on each visit. > **SUCCESS:** That is it. Five steps, about sixty seconds end-to-end, and you are a published writer. --- # How to write and publish your first post > Source: https://velocms.org/help/write-and-publish-first-post > Category: getting-started | Updated: 2026-04-11 You've created your VeloCMS account and verified your email. Time to publish something. This guide walks you through the editor end-to-end — from hitting New Post to seeing your article live on your subdomain. ## 1. Open the editor From your admin dashboard, click the big New Post button in the top-right or hit the floating plus icon in the bottom-right corner. The editor opens with a blank canvas and the cursor placed in the title field. Nothing else is on screen — that's intentional. We optimize for focus. ## 2. Write the title and lede Start with the title. The SEO score panel will grade it live — aim for 50–60 characters. After the title, press Enter and write a one-sentence lede that answers the question your title asks. Answer-first paragraphs are critical for AI search (AEO) — LLMs grab the first sentence as the authoritative answer. > **INFO:** The LLM score in the editor footer jumps as soon as your first sentence directly answers the title. That's the single highest-leverage optimization you can make. ## 3. Use slash commands for structure Press / on a new line to open the slash menu. Pick a heading (h2 is the default for top-level sections), a list, a code block, an image, or an AI continuation. Keep typing to filter — typing /ai shows only AI-related blocks. - /h2 — section heading - /list — bulleted list - /code — code block with syntax highlighting - /image — upload or paste an image URL - /ai — opens the AI Assistant panel to draft or continue your text - /callout — info, warning, or success callout ## 4. Add images and media Drag and drop an image anywhere in the editor — it uploads to Cloudflare R2 automatically and appears inline. You can also paste an image URL. For every image, fill in the alt text field that appears underneath — it's required for accessibility and SEO, and the AI assistant will suggest alt text if you leave it blank. ## 5. Set the slug, excerpt and SEO fields The slug is the editable address line right under the post title (yourblog/blog/your-slug). It defaults to a URL-safe version of your title, and shorter slugs rank better. Then open the post settings panel. The meta description is the Excerpt on the Settings tab (150–160 characters); the SEO tab shows it as Meta Description, next to the Meta Title and your SEO and LLM scores. The SEO tab also holds the Canonical URL and the Social image. Leave the Canonical URL empty unless this post is a copy of an article first published on another site: when you set it, search engines credit that site as the original, and the post is left out of your sitemap. Add a Social image only if you want a different picture when the post is shared; otherwise the featured image is used. ## 6. Save as draft or publish Drafts save automatically every few seconds — you won't lose work if the browser crashes. When you're ready, click the Publish button in the top-right. Your post goes live immediately at yoursubdomain.velocms.org/blog/your-slug and is picked up by the sitemap within a minute. > **SUCCESS:** That's it. You just published with better SEO scores than 90% of WordPress posts and in a fraction of the time. --- # Using the AI writing assistant > Source: https://velocms.org/help/ai-writing-assistant > Category: editor-writing | Updated: 2026-04-11 The VeloCMS AI writing assistant is not a bolted-on widget — it lives inside the TipTap editor and streams generations directly into your document. It runs on Google Gemini behind a secure server-side proxy, so your API key is never exposed, and the text appears token-by-token just like you'd see in ChatGPT. [Video: The AI Writing Assistant, Live In The Editor](https://media.velocms.org/marketing/howto/howto40-full.mp4) — See the built-in /ai assistant draft and rewrite content, streaming right into the editor. ## Quick start — generating your first AI paragraph Open any post, move to a blank line, type /, and filter down to AI Assistant (or just type /ai). The AI Panel opens below your cursor. Describe what you want — something like 'explain the benefits of headless CMS for non-technical blog owners in a friendly tone' — and press Enter. Gemini processes the request and streams the response directly into your editor at that cursor position. The text is immediately editable; you don't need to accept or reject it in a modal. Just keep writing from where the AI left off, or delete the bits you don't like and try again. ## Invoking the assistant from selected text Select any text in the editor and the floating toolbar appears above your selection with a sparkle (AI) button. Clicking it opens the same AI panel, but with Rewrite, Translate, and Summarize enabled (they need a selection to act on) alongside Generate. The AI sees your selected text as context, so it doesn't rewrite in a vacuum — it rewrites to stay consistent with what you've already written. ## The four actions - Generate — writes new content from a text prompt you type; works with or without a selection - Rewrite — improves the selected text (needs a selection) - Translate — translates the selected text into one of six languages (needs a selection) - Summarize — condenses the selected text (needs a selection) A fifth entry, My Templates, opens your own saved prompts (Admin → AI → Prompt Templates) instead of a built-in action — useful for a repeated instruction like a fixed brand voice or a boilerplate CTA you insert often. ## Streaming, cancellation, and cost Streaming is real SSE — if the generation is going in the wrong direction, hit Escape and the request is cancelled on the server immediately. You're not waiting for a full response to discard. We only count tokens actually generated (not the full potential response) against your monthly limit. Gemini is priced cheaply enough that we include generous monthly limits in all paid plans — for most bloggers, you'd have to be running AI nonstop to hit the ceiling. ## Bringing your own API key (BYOK) If you're on Business or Agency and want to use your own Gemini API key — or switch to OpenAI, Anthropic, or a custom provider like Groq or local Ollama — you can paste your key in Settings → AI. Keys are encrypted at rest with AES-256 before being stored. The platform never sees your plaintext key. If you enter a BYOK key, all AI calls from your blog route through your key and count against your own API quota, not VeloCMS's shared pool. ## Common pitfalls The AI assistant works best when your post already has some content to anchor on. Opening the AI Assistant on a completely blank document gives Gemini nothing to work with — the result tends to be generic. Write at least a title and a rough opening paragraph first, then use Generate to extend. Another thing: Rewrite and Summarize replace your selected text once you submit, not just annotate it. Review the output before you move on, since a rewrite can change your voice more than you'd expect. Finally, don't use the AI assistant for factual research without verifying the output. Gemini is a language model, not a fact database. ## Related articles - Using slash commands in the editor — the full slash command reference including /ai - Understanding SEO and LLM scores — how the AI's output affects your post's scoring - BYOK AI keys — connecting your own Gemini, OpenAI, or Anthropic key > **WARNING:** The AI assistant is a helper, not a replacement for your judgment. Always review generated text — factual claims need human verification. --- # How to optimize your blog for AI search (AEO) > Source: https://velocms.org/help/optimize-for-ai-search-aeo > Category: seo-ai | Updated: 2026-04-11 Answer Engine Optimization (AEO) is the practice of structuring content so that large language models can parse, extract, and cite it when answering user queries. Traditional SEO targets a ranked list of blue links; AEO targets a single sentence in an AI answer. The two overlap but the best practices are not identical. [Video: Optimize Your Blog For AI Search](https://media.velocms.org/marketing/howto/howto42-full.mp4) — See how llms.txt, JSON-LD, and the AEO checklist work automatically in VeloCMS. ## 1. Write answer-first paragraphs LLMs are trained to grab the sentence that best answers a question. Put the answer in the first sentence of each section, then elaborate. Avoid burying the conclusion at the end of a long paragraph — the model will grab whichever sentence is most concise and declarative. ## 2. Use semantic HTML VeloCMS renders every post with proper
,

,

,