Blog posts on a branch. You just merge.
Your agent writes new posts in your website's repository, following the repository's own rules, and commits each one on its own branch. Publit.Si never pushes or merges; you read, merge and deploy as usual.
How it works
- Accounts → your project → + Connect → Blog / website: the repository, the posts folder (found on its own for the usual places) and the address of a post.[1]
- In the Studio, use Write a blog post – “Write a new blog post for the next free day about: …” – or ask in your own words.[2]
- The agent opens a separate worktree on a new branch
blog/<slug>, reads the repository's rules (AGENTS.md or CLAUDE.md), writes the Markdown file, runs your checks and commits there. Your checked-out branch stays untouched.[1] - Read it, merge it and deploy as usual. Copy merge command puts
git merge blog/<slug>on your clipboard.[1]
What you get
- Your blog shown like a channel: posts on their days in the calendar, a preview with cover, an editor.[1]
- Drag a post that isn't online yet to another free day, and Publit.Si commits the new date on its branch.[1]
- Clicks, impressions and position of every post from Google Search Console, updated every 6 hours.[1]
- A weekly goal – e.g. 2 posts a week – with your streak of weeks met.[3]
- Claude Code, Codex, Cursor or OpenCode writes, whichever you use in the Studio.[1]
In practice
The blog on publit.si uses the same layout: each post is a Markdown file in the site's repository (content/blog/en, content/blog/de) with its day in the front matter, and an English post and its German version share a translationKey. A post merged with a future date goes online on its day. Once a post has been online for a while, its clicks and position in Publit.Si show which titles and descriptions need work.[4]
Limits
- Publit.Si never pushes, merges or deploys. A post goes live only after you merge.[1]
- Your posts must be Markdown files in a repository on your computer.[1]
- There is no keyword tool. The topic comes from you; the search numbers show afterwards how a post does.[1]
- Search numbers need Google Search Console and the same Google project as YouTube. Google reports them 2–3 days late.[1]
- In Google's test mode, the Search Console sign-in ends after 7 days and the Blog line asks you to reconnect.[1]
Questions
Does it publish to my website?
No. Publit.Si never pushes or merges. The agent commits on blog/<slug>; you merge and deploy as usual.
Which blogs work?
Markdown posts in your own repository, e.g. content/blog/de/*.md. Publit.Si finds the posts folder on its own for the usual places, or you enter it.
Where do the SEO numbers come from?
From Google Search Console: clicks, impressions and position of every post, updated every 6 hours. Google reports them 2–3 days late.
Related
Sources
- [1] Docs: Connect your blog: publit.si/docs/platforms/blog
- [2] Docs: Studio: publit.si/docs/guide/studio
- [3] Docs: Posting slots and goals: publit.si/docs/guide/slots-and-goals
- [4] Docs: Analytics: publit.si/docs/guide/analytics