Ecommerce blog: how to write and organise your store's blog

In short: an ecommerce blog is the section of your store with articles that answer what shoppers ask before they buy, sorted newest first and by topic. In CloudCart you add a post in Marketing → Blog → Articles → + Add article: a title of 3 to 191 characters, an author, one category and up to 100 tags. The post goes live at /article/handle, and all 4 plans include the blog.

This guide is for sellers in any EU country who launch or tidy up a blog on CloudCart. Admin paths come from the CloudCart documentation and the plans page; what to write so you rank is in the ecommerce SEO checklist.

What an ecommerce blog is and which posts to write

An ecommerce blog is a set of articles that answer the shopper's questions before and after the purchase and link to your products. Five post types cover nearly every search that ends in a sale:

Post type	Shopper's question	Example for a coffee store	Links to
Buying guide	"How do I choose…"	How to choose a coffee grinder for home	The grinders category
Comparison	"X or Y"	French press or moka pot: differences in taste	2 or 3 specific products
How-to and recipe	"How do I make…", "How much…"	How much coffee per cup in a French press	The product and its consumables
Answer to a common question	"Why…", "Can I…"	Why your coffee tastes bitter and how to fix it	The category that solves the problem
Store news	"What's new"	The new Ethiopian harvest is in stock	New products, plus a reason to email subscribers

The first four types bring visitors from Google and AI assistants for months. Keep news in its own category and send it to subscribers with an email campaign in CloudCart.

Does a blog help ecommerce SEO

Yes, when posts answer real searches and link to your categories and products. Google ranks pages that give a helpful answer to a specific question, as its guidance on helpful, people-first content explains. A product page answers "buy X"; an article answers "how to choose X" and "X or Y", searches people make earlier, while still deciding.

A direct answer up top, a table and numbered steps also make a page easy for ChatGPT, Gemini and Google's AI Overviews to quote; see the guide to GEO for ChatGPT, Gemini and AI Mode.

In CloudCart every post, category and tag has its own URL, and they behave differently:

	Post	Blog category	Tag
Storefront URL	/article/handle	/blog/category/handle	/blog/tag/handle
SEO title and description	Yes, up to 191 characters each	Yes, filled with the name if left empty	None
301 redirect on a new URL	Automatic	Automatic	None, add it by hand
In the sitemap	Yes	Only with at least 1 active post	No
Limit	One category per post	Up to 500 posts, one level only	Up to 100 per post

The store's full SEO toolkit, with redirects and the sitemap, is on the CloudCart SEO page.

How to create blog categories and tags

You create a category in Marketing → Blog → Categories with + Add blog category, and a tag by typing it into a post. Blog categories are separate from product categories, so changing them does not touch the catalog.

1. Click + Add blog category and enter the Blog category title (3 to 191 characters). The URL under /blog/category/ is built from it.
2. Choose the comment rule in the Comments settings card (the options are explained below).
3. Write the SEO fields in Advanced settings: SEO title, SEO description and URL handle. Empty fields are filled with the category name, so write your own description with the keyword you want to rank for.
4. Add a cover, save and publish a post in it soon. An empty category stays out of the sitemap until it has an active post.

Categories are flat, with no parent and child levels; for "Guides › Coffee" use two categories or tags. At post 501 in one category the platform shows "The blog can not have more than 500", and you open a second category.

A tag is created when you type it into a post's Tags field and press Enter; Marketing → Blog → Tags lists, renames and deletes them. Tags are stored in lower case, so "Coffee" and "coffee" are one tag. Since tags have no SEO fields, no sitemap entry and no redirect on rename, use categories for topics you want to rank for and tags for navigation: brand, product type, season.

How to add a blog post to your store: step by step

You add a post in Marketing → Blog → Articles → + Add article. The editor has two columns: title, text and SEO fields on the left, author, category, cover and tags on the right.

1. Type the Article title. 3 to 191 characters; the URL handle fills in as you type. Put the searched words first: "French press: how much coffee per cup".
2. Write the Content. Headings, lists, tables, links and images. An image from another website is copied into the store's media library on save.
3. Fill in Advanced settings. SEO title is the headline in Google and SEO description the text under it, up to 191 characters each, with a Google preview below. An empty SEO title falls back to the post title.
4. Choose the Author, one of the store's admins (required).
5. Choose the Blog category. The + Create category link creates a new one without leaving the post.
6. Upload the Cover image. It shows at the top of the post and on its card in the blog list.
7. Add Tags and save. Saving publishes at once. Check the /article/handle URL in a window where you are not logged in.

Important: the post URL is locked after the first save, so a new title keeps the old URL. If you change the URL handle itself, CloudCart creates a 301 redirect from the old URL, and links and rankings carry over.

Put the key point first in the SEO description; Google may rewrite it under its rules for snippets.

How to hide, publish or schedule a post

You hide or show a post with the Published switch on its row in Marketing → Blog → Articles. A hidden post leaves /blog/ and its URL returns a 404. There is no separate draft stage: save the post and switch Published off until the text is ready.

The editor has no future publish date. You schedule through the store's REST API (an API key from Settings → Api keys, from Starter Pack up) with the publish_date field in /api/v2/posts: the post stays hidden and appears at the chosen minute in the store's time zone.

Important: deleting a post is final and removes its comments. Deleting a category leaves its posts without a category, so move them to another one.

How to show the blog on your storefront and homepage

The blog lives at /blog, newest first, 10 posts per page. You change that in Design → Modules, section Blogs, articles and comments:

1. Blog sets 2 to 50 posts per page for /blog, category and tag pages.
2. Latest articles shows 2 to 10 of the newest posts where your theme provides a slot: homepage, sidebar or footer.
3. Last comments shows 2 to 10 of the latest approved comments.
4. Recent Articles in the page builder's dynamic pages shows 2 to 10 posts from one category, 1 to 5 per row, so a coffee machine promotion page can show only "How to choose" posts. The page builder depends on the plan.
5. Save module updates the storefront at once; Reset module restores the theme defaults.

Which cards you see depends on the theme. Add the blog to the main menu from the store's navigation.

How to turn on comments and stop spam

Comments are set per category in its Comments settings card, and every post in the category inherits the rule.

Category setting	What happens to a comment	When to use it
Automatic comments approval	Goes live at once	A small audience you know
Comments need approval	Hidden until you approve it	Most stores
Turn off comments	No form; old comments stay	News, terms, promotions

Switching off Automatic comments approval moves the category to Turn off comments, so pick Comments need approval yourself. You moderate in Marketing → Blog → Comments; Pending Comments (N) opens the queue, where you Approve comment or Mark as spam. A comment is up to 1,000 characters.

The built-in spam guard allows up to 5 comments per minute from one IP address, with no captcha or word filter, so stores that get spam should require approval. The alternative is the Disqus or Facebook Comments app, both on all 4 plans on /pricing, which replace the form with their own and bring their own spam filter.

Mind the GDPR: a guest comment is saved with a name and email address, and under Regulation (EU) 2016/679, applicable since 25 May 2018, any information relating to an identifiable person is personal data. Cover blog comments in your privacy policy; the wider rules are in the guide to GDPR, cookies and legal pages.

How to move an old blog from a CSV file

You move a blog from WooCommerce or another platform with the Blog CSV Import app, which adds the Add via CSV button in Marketing → Blog → Articles.

1. Upload the file in the Import CSV window, mark the header row, set the separator for category paths (for example >) and choose the Author for all posts.
2. Map the columns: Name (required), Content, Image, category path and Blog ID. Missing categories are created with automatic comment approval, so switch them to approval afterwards.
3. Follow the import with Track importing progress: total, processed, successful and failed rows, with the reason for each error.

Tags and publish dates do not come over, and URLs are rebuilt from titles: for every old URL with rankings or links, add a redirect in Marketing → SEO → 301 Redirects. CSV details are in the guide to importing products from CSV, XML and Google Sheets, and a full move with an old-URL map is in migrating from WooCommerce without losing SEO.

How to run the blog in several languages for EU markets

Each country gets its own store with its own language, and the Multilang app copies and translates the blog into it. The main store is the master: Multilang syncs products, categories, pages and blog articles to each country store and machine-translates them with Google's translation engine. Translation is part of the higher plans; see the multistore and languages page.

1. Write once in the main store. The country stores receive the translated copy.
2. Review each translation. Fix the title, SEO title and description with the words shoppers use in that country.
3. Keep local URLs. Each store has its own URL handles, and the language switcher still leads to the same post.
4. Let hreflang work. CloudCart generates hreflang tags between the stores, with the main store as x-default, the signal Google asks for when a page exists in several languages (Google: localized versions).

Important: sync runs one way. Translating a post again from the main store overwrites edits made in the country store.

How VAT and OSS work when you sell into other EU countries is in the guide to OSS and EU VAT for cross-border sales.

How to write blog posts with an AI agent

An AI agent such as Claude Code, ChatGPT Codex or Gemini CLI writes a post from your store's data and saves it to the blog once connected with a PAT token from Settings → PAT tokens. The CloudCart Admin GraphQL API covers the blog, and with read access to products, inventory and orders the agent links only to products you have in stock and sell.

A sentence such as "Write a post on how to choose a coffee cup with our 5 best-selling models and save it as inactive so I can review it" gives you a draft with the right links.

Task	By hand in the admin	With an AI agent
New post with product links	7 editor steps, products looked up separately	One sentence; saved hidden
SEO fields on 30 old posts	30 times open, write, save	One task fills the empty fields
Tags after a CSV import	By hand on every post	Added from title and text
Next topic	A guess	Picked from best sellers and stock

For writing posts, create the token with Custom Permissions: Blog on Read & Write, Products, Inventory and Orders on Read. The agent then cannot change orders, prices or settings. Setup is in Claude Code: how to run your online store with Claude. Ready sentences for content are in 30 ready prompts for the AI agent.

How to tell if the blog brings visitors and sales

Search Console shows which searches your posts appear for, and Google Analytics 4 shows what visitors do next. Both connect from Apps in CloudCart, without code.

1. Connect Search Console in Apps → Google Search Console with Google's verification code (see Google Search Console for an online store).
2. Submit the sitemap from Marketing → SEO, card Sitemap.xml file. Posts and non-empty categories are in it.
3. Connect GA4 in Apps → Google Analytics with the G- Measurement ID (see GA4 and Google Tag Manager for an online store).
4. Filter by /article/ in Search Console and in GA4 landing pages to see impressions, clicks, position and how many visits reach the cart.
5. Act on the numbers. Many impressions and few clicks: rewrite the SEO title and description. Position 8 to 15: add a section and a link from a stronger page.

Which metrics to follow is in the guide to ecommerce KPIs and the AI agent.

8 best practices for an ecommerce blog

1. One post per question. Shoe sizing and road versus trail shoes are two posts.
2. The answer in the first paragraph, with a number. Google and AI assistants quote it.
3. 2 to 4 links to categories and products. Without them a post brings visits but no orders.
4. Your own SEO description on every post, key point first.
5. 3 to 6 categories by shopper topics, each with at least one post.
6. A table or steps in every guide. That is what people save and AI quotes.
7. A yearly update of your most-read posts at the start of the season.
8. A pace you can keep. 2 to 4 useful posts a month beat 10 rushed ones that then stop.

Mistakes to avoid

• Renaming tags that rank without a manual 301 redirect.
• Posts that are ads. The product belongs in the guide as the answer.
• Raw machine translations that miss local search terms.
• Deleting instead of hiding. Deleted posts and comments do not come back.

Questions about setting up your blog: support@cloudcart.com.

Frequently asked questions