The store blog: publish posts that sell

The built-in blog at `/dashboard/blog` is a real publishing tool — rich editor, AI writer, cover images, tags — wired directly into your store. Posts inherit your theme automatically, product ads can run inside articles, comments and likes give you engagement signals, and an RSS feed keeps subscribers and aggregators current. Content marketing lives in the same dashboard as the catalog it sells. ## Write a post 1. Open **Blog** → **New Post**. Write a title, then compose in the rich editor: headings, formatting, images, links, and lists all behave the way you expect. 2. Use the **AI writer** when you want a running start — give it a brief ("sizing guide for our abayas, mention the size chart page") and it drafts the post for you to edit. Always edit: the drafts are good raw material, not finished copy. 3. Upload a **cover image** — it becomes the post's visual everywhere the post appears, including social Auto-Pilot posts. 4. Add **tags**. Tags organize the blog for readers and double as targeting for in-post product ads. 5. Click **Publish**. The post goes live under your store's blog at `/<storeSlug>/blog`. ## Moderate comments **Blog** → **Comments** is the moderation queue: approve, reply, or delete. Comment notifications land in your dashboard notifications, so a quick daily check is enough. Replying publicly to a good question is one of the cheapest trust signals a store can earn. ## Watch likes and views Every post tracks **likes** and **views**. Views tell you which topics draw readers; likes tell you which ones resonated. The two do not always agree — a post can pull clicks and disappoint — and the gap is the interesting signal. Feed the winners into the Content Studio as templates for repeat formats. ## Sell inside the article with product ads In-post **product ads** place real product cards inside the article body, and you choose the targeting: - **By tag** — posts tagged "skincare" automatically show skincare products - **By collection** — pin a collection like "Ramadan Essentials" to matching posts - **Hand-picked** — choose exact products for a specific article The ads render as native product cards with images and prices, not banner spam, and they are the shortest possible path from "reader interested in this topic" to "shopper viewing that product." Tag-based ads are the set-and-forget option: tag new posts correctly and the right products follow. ## Offer the RSS feed Every store blog ships an RSS feed at: ``` /<storeSlug>/api/blog/rss.xml ``` Readers can subscribe in any feed reader, and aggregators or automation tools can consume it. Point the "RSS" link in your blog's footer or sidebar at that URL, and new posts flow out without anyone checking the site manually. ## It renders themed, everywhere The blog is not a bolted-on page with different fonts. Every post, the index, and the RSS feed render with your store's active theme — same header, footer, colors, and navigation as the rest of the storefront. Switch themes and the blog switches with it, so content never looks orphaned from the shop. That also means the blog benefits from your SEO settings, custom domain, and branding automatically. ## What happens next A sustainable rhythm: two posts a week beats a ten-post burst followed by silence. Draft both on one day — one AI-assisted, one from your Ideas Bank — schedule them a few days apart, and tag them properly so product ads do the selling while the articles do the trusting. ## FAQ **Does the blog have its own SEO settings?** Posts inherit the platform's SEO Suite: meta titles and descriptions are editable in the on-page optimizer, new posts can be submitted via IndexNow, and the blog is included in your sitemap. **Can I edit a published post?** Yes. Open it under **Blog**, edit, and save — changes are live immediately and the RSS feed and theme render update with them. **Do comment authors need accounts?** Storefront visitors can comment through the blog's comment flow; everything lands in the moderation queue before it appears publicly, so nothing goes live unchecked.