Marketing · Blogs
How far the text was read. No cookie, no IP.
Write, schedule and publish on the line's address or at /blog on your site. Each post ships with sitemap, RSS and versions, and shows how many opened, which section they read to and how many reached the end.
One sign-in for every dashboard in the line. A code arrives in your email; you paste it once. The dashboard is in Portuguese for now.
Why this exists
A visit does not tell you the text was
READ.
The post had a thousand visits, and nobody knows if anyone got past the second paragraph. Here each post shows the section where reads stop, without asking anyone for a cookie. That is where the text needs a different opening, or a cut.
- The blog in one tool and the site in another, each on its own address
- The good post nobody finds, because it was not in the sitemap
- The agent's draft published without anyone reading it first
The whole path
Write, schedule, publish, get found.
And you know how far each text was read.
1 · Write
A text editor, with the draft saved in versions.
Headings, lists, quotes, code, highlights, images with required alt text, video and an embedded form. A version is created at every pause, every publish and every restore, and restoring deletes nothing.
status Draft → In review → Scheduled → Published
versions after every 10 min pause, at every publish
and at every restore, up to 50 per post
image alt text required
changes a published post changes in a separate step2 · Schedule
In the blog's time zone, with the people who sign it.
The editorial board has the columns Idea, Draft, Review, Scheduled and Published. The calendar marks publishing days left without a post, and a late scheduled post shows up on the status page.
board Idea · Draft · Review · Scheduled · Published calendar the publishing day left without a post scheduled goes out on time, in the blog's time zone byline one or more authors, each with a role
3 · Publish
On the line's address, or at /blog on your site.
Each blog starts on an address of the line. With your own domain, it becomes a subdomain or a path inside the site you already have: anything outside /blog keeps going to your site, as before.
default https://blogs.mymarketing.click/<blog>/<post>
subdomain blog.yoursite.com
CNAME → cname.blogs.mymarketing.click
path yoursite.com/blog/<post>
the rest of the site goes to your origin
checked DNS · origin · route · certificate4 · Get found
Sitemap, RSS and llms.txt are generated for you.
Each blog publishes a sitemap, a feed and an llms.txt for agents, with Open Graph and structured data on every post. On publish, IndexNow notifies the search engines that support it. AI crawlers are allowed by default, and one setting blocks the training ones.
/<blog>/sitemap.xml /<blog>/feed.xml summary or full text /<blog>/llms.txt each post Open Graph · JSON-LD · canonical URL publish IndexNow, for search engines that support it AI crawlers training ones blocked with one setting
5 · Read the result
How many opened, how far they read, how many reached the end.
A script that runs only on post pages counts who opened, the deepest section each read reached, and whether it reached the end. Totals are per post, day and version, never per reader. Bots and app previews are left out.
opened 2 s with the post visible section the deepest one the read reached end reached the last part, or not stored per post, day and version never cookie, IP, browser or reader
Model Context Protocol
The agent writes, publishes and schedules with your role on the blog. You sign it.
Four tools do everything the dashboard does, through the same API: the agent reads the guide, reads, creates, edits, publishes, and generates or rotates the key. It writes, reviews, schedules and publishes with the role of whoever connected it. The whole catalog costs the agent under 3,400 characters before the first word.
The server's limits
- Publishing and scheduling only if the person who connected the agent can publish on that blog. Whoever wrote a text does not approve it.
- Deleting, revoking or canceling only after your yes, in the conversation: the first call only asks and shows what will happen.
- Signing a post never. The post is signed by a person; the agent does not appear as the author of what went live.
The account comes from the token and never from an argument. The bk_ key does not publish, unpublish or delete.
The yardstick
What It Does, and Where It Stops
The limits, stated before you need to ask.
What it measures
Reading
Opens, deepest section and end, per post, day and version. It does not measure visits or where they came from: that is for your analytics tool.
Cookie to measure
None
No identifier and no IP. The only cookie belongs to readers who prove their email to read a restricted post, and it does not measure.
Where it lives
On the line's address or on your domain
A subdomain or a path like /blog inside the site you already have.
Email list
Not kept
Blogs does not send email about posts. The letter to people who asked for it belongs to Newsletter, which receives the publish notice as an event.
Look
The design system's
No themes or colors per blog. The reader is clean, fast and the same on every blog.
Agent
Drafts, publishes and schedules
Through the MCP server, with the role of whoever connected it. Unpublishing and deleting only after your yes, in the conversation.
Pricing
1, 3, 9 or 99 blogs
Free to start
1 blog, complete.
What changes between plans is how many blogs the account keeps. Posts, readers, team and MCP are in every plan, with no plan limit. Prices are in Brazilian reais (BRL), charged by Stripe. No card, and the free plan never expires. The yearly plan costs ten months.
FAQ
The Questions, in the Order They Come Up
Does your blog need something that is not here?
Talk directly to the person who wrote the code. A real case changes the design.
Marketing · Blogs
How far the text was read. No cookie, no IP.
On your domain or the line's, with sitemap, RSS and versions, and an agent that publishes only with your role on the blog.