A Blog for Every Store, Built Into PersonaCart

This is a written-up look back at one week of work on PersonaCart, 10 to 16 August 2026. I am writing it on 12 October 2026, from the code history of our app, not from memory. Period covered: 10-16 August 2026.

In short

• The big piece of the week was a blog for every store, with its own name, its own web address and five templates.
• We also worked on how search engines and AI assistants find a store, and on alerts when someone leaves their details on a BioLink page.
• We built a first version of "Bring Your HTML": paste a page you already own and have it turned into sections you can edit.

The lead feature: a blog that belongs to the store

A coach or academy owner usually needs somewhere to write. A season update, a training tip, a note to parents. Before this week, that was thin. By the end of it, a store had a real blog. Everything below is built and sits on our staging branch. The platform is still pre-launch and our own accounts are the main users, so read this as "built", not "in the hands of customers".

What we built for the blog:

• Your own name and address. You can call the blog anything ("Journal", "Newsletter") and pick the path it lives at. If you rename it later, the old addresses forward to the new one, so no old link breaks. We also tell you that a rename can take a few minutes to spread.
• Five templates that look different. Not one layout in five colours: five structurally different designs.
• A writing editor that stays within what the page can safely show, plus a "copy as Markdown" button.
• Search settings that actually save. The search title and description you type are kept. You can decide whether the blog is open to search engines at all.
• Scheduled posts. Pick a future time and the post goes live then.
• Reader helpers. A table of contents, related posts, breadcrumbs and an RSS feed that browsers can discover.
• Question-and-answer markup. If a post contains questions and answers, we mark them up so search engines and AI assistants can read them.
• A Blog link in the default header and footer of a store.

One thing to be straight about: on 14 August the blog was set up as a feature for the higher plans only. That changed four days later, and I cover it in the next post. Check /pricing for what each plan includes today.

The other things that moved

Being found. We made every storefront point to two machine-readable files, `llms.txt` and `feed.json`, which describe the store for AI assistants. The SEO page got a card that shows whether that is set up. We also added real Bing keyword rank, impressions and clicks to the SEO page, a card that proves a page was sent to search engines, a competitor keyword gap view, and suggested keywords that Pie proposes for you to approve. Nothing here promises a ranking. It shows you what is going on.

Leads from a BioLink page. When someone leaves their details on a BioLink page, the creator now gets an alert in the app and by email. People who opted in get a branded welcome email. A "new leads" count shows next to the sidebar item and clears when you have looked.

Bring Your HTML. In the "Beautify with AI" dialog there is now a second tab where you paste a page you already own. We built it so the page is carried over in your own words, not rewritten. Video embeds are kept, a tab strip switches panels, and a sign-up form on the old page sends its entries to the leads list. We also added a check that compares the result with the original and flags real loss of content. This is a first version.

Smaller items. A Hero Pager section (a full-width, multi-slide hero with dots). A Table block. An emoji tab in the icon picker. A store header whose menu moves into a drawer instead of wrapping onto a second row. Legal pages that can be generated from a template. A dashboard "Action Center" at the top. A warning before you publish a product that still has no title. The order list marks subscription renewals and can filter by where an order came from.

What it means for a coach or academy

Most coaches I talk to already write: a parent email, a post on social media. A blog on your own store means that writing sits next to your programs and your Academy, under your name, and can be found by search. The lead alerts matter for the same reason: a parent who fills in a form on your link page should not sit unseen for two days.

If you build with our tools, /tools lists what is available today.

What is next

The next week's history shows the blog opening to every plan, and a "Write with AI" flow for posts. That is in the next post.

Want to talk? I am one of the co-founders of PersonaCart. If you have a question, an idea or something you want us to build, write to me directly: [email protected].

Vinod Morya, Co-founder, PersonaCart