Automate generation and go-live times, email yourself a preview before posts hit your site, then measure views and engagement, or wire everything through our API and optional MCP tools for developers.
Set cadence, topic templates, and the wall-clock time posts should go live. We generate content, send you an email about two hours before publish, then flip each post to published so it appears in API results for your site.
Active schedules scale with your plan, for example up to one on Pulse, two on SEO Engine, and more on Programmatic Pro. Compare plans.
Your customer site does not receive pushed files. Posts are always available from our API; your blog page simply fetches JSON and renders. See GET /content.
status=publishedby-slugSEO Engine and Pro include dashboard analytics and a small embed script for your live site. Create an embed key with your allowed origins (for example https://www.yoursite.com), paste one script tag per article, and we record views, time on page, and link clicks.
<script src="https://autoblogs.dev/js/autoblog-track.js"
data-gateway="…/functions/v1/api-gateway"
data-site-key="ab_live_…"
data-content-id="…" async></script>Full setup: Analytics embed in the API docs. You may need a consent banner depending on your region.
The analytics dashboard translates raw engagement signals into clear takeaways for teams. See what to publish more often, what to refresh, and where attention drops.
AutoBlog summarizes best publish windows, top-performing topics, and early warning signs so marketers can act without exporting data.
AI insights are included on SEO Engine and Pro, with enterprise customization for reporting cadence and operating workflows.
Convert any published blog post into channel-ready assets in seconds. Keep your voice consistent by inheriting brand preferences from project settings.
Generate social and email variants from the same source post so campaign teams can ship distribution faster without rewriting manually.
Run repurposing directly from your content list, review each format, and copy approved variants into scheduling or posting tools.
Bring AutoBlog to the tools your team already uses.
Custom Code in site or page settings: load the track script and pass each post’s content ID. Point listing pages at our REST API from Velo or a serverless function if you keep keys off the client.
Site-level Custom Code or a Code component on your article template. Map CMS fields to data-content-id for analytics.
Add the script in your layout or article route; bind route params to the post UUID from your dashboard.
Server-side fetch with your full API key for listings and detail pages; use the embed key only in the browser for analytics.
The same REST surface powers your product. Optional: run the MCP server from the repo to let Cursor and other clients list posts, pull analytics summaries, and print embed instructions.
Set AUTO_BLOG_BASE_URL to your …/functions/v1/api-gateway URL and AUTO_BLOG_API_KEY to a full API key (never the embed-only key).
The MCP package lives at packages/autoblog-mcp in the AutoBlog repo. See README.md there for npm install and Cursor wiring.