Crawlbench now has a public blog, individual article pages, an Atom feed, and a staff publishing workflow. Published posts carry canonical and BlogPosting metadata and appear in the sitemap. Staff can write, preview, publish, or schedule posts in admin, while a command-line workflow handles draft files without requiring manual copy and paste.
What shipped
The public Crawlbench blog is now the home for guides, comparisons, and release notes. Each post has its own URL and page metadata. Published article pages include a canonical URL and BlogPosting structured data, so search engines receive a clear article identity and publication record.
Published posts also appear in two machine-readable places:
/blog/feed.atomprovides an Atom feed for feed readers and other subscribers- The public sitemap includes each published post URL and its latest update time
Draft and scheduled posts stay out of those public collections until their publication time. Staff can still preview them while signed in.
Admin publishing
The admin post editor now supports the full writing path in one place. Staff can create a draft, edit the title and slug, write the Markdown body, set search metadata, choose an author byline, and preview the result.
Publication has three states:
- Leave the publish time blank to keep a draft
- Publish immediately from the editor
- Set a future UTC time to schedule publication
The same page can unpublish a post if it needs to return to draft status. Draft and scheduled previews carry a noindex instruction, so unfinished copy is not meant for search results.
File-based publishing
The bin/blog-publish command supports the draft-file workflow used for Crawlbench updates. It reads YAML frontmatter and Markdown from a file under plans/blog-drafts, removes the preview-only H1, and upserts the post by slug.
The command can publish to a local database, send the post to production, keep it as a draft, or apply a specified publication time. Re-running it updates the existing post without replacing the original publication time unless a new time is supplied.
This keeps editorial work reviewable as a file while still using the same Post validations and rendering path as the admin editor.
Why this matters
The publishing system gives product updates and buyer guidance a stable public home. Readers can browse the blog index or follow the Atom feed. Search engines receive canonical article pages and sitemap entries only after publication.
It also connects product education to the rest of the site. The features page explains what Crawlbench does, while the Facebook Marketplace monitoring tools guide is one example of how the acquisition content system can answer a purchase-stage question without turning a release note into a sales page.