Platforms
Connect your blog and Google search numbers
If your project has a blog in its own repository (Markdown posts, e.g. content/blog/de/*.md), Publit.Si shows it like a connected account: planned posts, a preview with cover, an editor, and your AI (Claude Code, Codex, Cursor or OpenCode) writes new posts for you. With Google Search Console you also see clicks, impressions and position of every post.
You need
- Your project's repository on this computer, with the blog posts as Markdown files
- For search numbers: the Google project and client from the YouTube guide, and your website added in Google Search Console
Connect the blog
Publit.Si → Accounts → your project → + Connect → Blog / website.
Repository: the project folder, i.e. the repository's top folder.
Posts folder: found on its own for the usual places. The dialog lists the posts it found, so you see it's the right one. Otherwise enter it, e.g.
content/blog/de.Website: your website and the address of a post, with
{slug}for the file name without.md. Test opens your newest post to check the address.https://example.com/blog/{slug}
Prepare Google for search numbers
Search numbers use the same Google project and OAuth client as YouTube. Without YouTube, do the parts project, branding, test user and client of the YouTube guide first.
console.cloud.google.com → your project → APIs & Services → Library → search Google Search Console API → Enable.
In Publit.Si, open the Blog / website dialog at step 4 and copy the redirect URI shown there. Google: Clients → your Web application client → Authorized redirect URIs → + Add URI → paste it → Save. Keep the YouTube URI; the client has both.
http://localhost:3000/api/oauth/search-console/callbackData Access → Add or remove scopes → tick
…/auth/webmasters.readonly→ Update → Save.Audience → Test users: add the Google account that owns the website in Search Console, if it isn't on the list yet.
Connect Search Console
Publit.Si → Accounts → the Blog line → ⋯ → Blog settings → step 4 → Connect with Google.
Pick the Google account that owns the website in Search Console. In test mode Google warns that the app isn't verified: click Continue. It's your own app.
Publit.Si picks the property that matches your website. Several properties? Choose one in step 4.
The first numbers come within minutes; then Publit.Si updates them every 6 hours. Google reports search numbers 2–3 days late.
Your blog next to your platforms
Sidebar: the blog is a channel of its project. Pick it to see only the blog in Calendar and Statistics.
Calendar: posts sit on their days, with cover and status on hover. Drag a post that isn't online yet to another free day – Publit.Si commits the new date on
blog/<slug>.Statistics and Home: clicks and impressions from Google, the most clicked posts, and posts waiting for your merge.
Weekly goal: Accounts → the Blog line → ⋯ → Weekly goal, e.g. 2 posts a week. The line shows this week and your streak of weeks met.
Check
Accounts shows a line “Blog · your-domain”, and Backlog → Blog lists your posts with their covers. With Search Console, Statistics shows clicks and impressions after the first update.
Troubleshooting
redirect_uri_mismatch- The redirect URI in the dashboard must match exactly, including
http/httpsand port. - Blog: Search Console shows "No property found"
- Add the website in Google Search Console with the Google account you connected, or connect with the account that owns it.
- Blog: Search Console connected but no numbers
- Check that the post address in the blog settings matches the real addresses (Test button). Google reports numbers 2–3 days late.
- Blog: "… is checked out right now" when saving a post
- The post's branch
blog/<slug>is checked out in your repository. Switch to another branch, then save again.
Stuck? Search the troubleshooting list or write to us . Leave out secrets and tokens.