Blogger posts on any website.

Blogger has shipped a standards-compliant Atom 1.0 feed at the path /feeds/posts/default on every public blog since Google acquired the platform in 2003. The same path returns full post content, author attribution, publish dates, label taxonomy, and links to image thumbnails. There is also a parallel /feeds/posts/summary path for summary-only entries when you want a lighter payload, plus per-post comment feeds at /feeds/COMMENT-ID/comments/default for blogs that have community discussion enabled. The Atom contract has been frozen for over twenty years, which means a widget that parses Atom today will still work in 2030 even if Google never touches Blogger again. The alternative is Blogger API v3, a JSON REST API that sits behind Google Cloud authentication. Blogger API v3 unlocks higher rate limits (10,000 requests per day per project on the free quota), private blog reads with OAuth, and the ability to write and edit posts programmatically. For an embed widget the Atom feed is almost always the right default because it requires no API key, has effectively unlimited rate limits for reasonable polling, and exposes everything a public widget needs. Poper uses Atom by default and exposes Blogger API v3 as an optional path for users who need the higher limits or want to embed a private blog. Either way, the widget never scrapes the rendered HTML and never hits undocumented internal endpoints, which is what some other tools do and which gets them blocked or broken whenever Google ships a Blogger template revision. The Atom-first design also means the widget gracefully degrades to summary entries when the full-content feed is too large, so even Blogspot blogs with twenty years of accumulated archives stay performant under polling load. Pagination across the full Blogger archive is handled through Atom's start-index parameter, which Poper uses transparently when an embed needs to surface posts older than the most recent 25 entries the default feed exposes.

Blogger has supported free custom domain mapping since 2010, which means a publication can run on journal.companyname.com while still hosted on Blogger under the hood. The Atom feed in that case still lives at journal.companyname.com/feeds/posts/default because Blogger transparently mirrors the feed path on the custom domain. The complication for widget tools is detecting whether a pasted URL is a Blogger blog at all, since the URL gives no obvious clue. Poper handles this by following redirects, reading the meta generator tag in the homepage HTML (Blogger injects content="blogger"), and checking for the canonical /feeds/posts/default path. If any of those signals match, the widget treats the URL as a Blogger blog and embeds the correct Atom feed. This makes custom-domain Blogger blogs as easy to embed as raw blogspot.com subdomains, with no manual configuration required. It is also the reason many long-running Blogger blogs feel completely white-labeled to readers but still get the benefit of Google's free hosting and AdSense integration on the backend. If you migrated TO Blogger years ago specifically because of its simplicity and Google account integration, custom domain mapping is what lets you keep that benefit while shipping a modern frontend through the widget.

Blogger blogs can have unlimited authors with admin or contributor roles, and Atom entries include the author name and email per post natively. This makes Blogger uniquely suited to multi-contributor blogs where attribution matters: writing societies pooling short fiction, book club blogs with rotating reviewers, and most importantly, classroom blogs running on Google Workspace for Education. Blogger is bundled with the free education tier of Google Workspace and remains one of the few blog platforms that school IT departments universally accept because it inherits Google account permissions, has no third-party data sharing, and is free at any scale. Teachers run year-long classroom journals, students contribute posts under shared authorship, and the whole thing is private by default with optional public reads. Poper handles multi-author Blogger blogs by reading per-entry author metadata and rendering correct attribution on every post. For school websites, district hubs, and learning portals, this means a classroom Blogger blog can be embedded on the school's public site with proper student credit, clear author labels, and zero OAuth friction for end readers. The widget never asks readers to sign in to Google to view posts, which matches how parents and prospective families actually browse school websites.

Google has visibly de-prioritized Blogger since 2017. There has been no major feature update in years, no mobile app, no theme marketplace expansion, and no public roadmap. By every conventional metric the platform should have been sunsetted alongside Google Reader, Google+, and dozens of other Google products that were quietly killed. Blogger is still online, still free, and still receiving security patches. The reason is that Blogger has hundreds of millions of active blogs accumulated over 25 years, an active AdSense revenue stream that Google still profits from, and a non-trivial Workspace for Education install base that would be politically expensive to remove. The result is an unusual product: a platform that is unfashionable, unloved, mostly forgotten by tech press, and yet legitimately useful as a free, lightweight, Google-integrated writing surface that does not require a credit card or a hosting bill. The honest framing for 2026 is that Blogger is not a place to start a new flagship publication, but it is an excellent place to keep a long-running personal blog, a hobbyist niche site, or a classroom journal alive without any operational overhead. A blogger feed widget makes that posture viable on the modern web by giving the Blogger archive a tasteful, well-styled home on any frontend you ship. Your readers see your posts on your domain, your writing process stays on Blogger, and the whole thing costs zero in hosting fees forever. The recipe blogger who has posted to a Blogspot URL since 2009 does not need to lose a decade of permalinks, AdSense earnings, and Google search ranking just to refresh the public surface in 2026. The classroom journal that started in 2014 does not need an IT department to migrate it. The hobbyist craft blog with a niche audience that already knows the URL does not need to break that audience by switching platforms. Embedding through the Atom feed lets every one of these blogs keep what works while presenting the result on whatever modern surface fits the brand today, which is the most pragmatic available answer to the long-tail Blogger question.

Many Blogger owners ask whether they should migrate to WordPress for the larger ecosystem, more themes, and modern plugin support. WordPress owners ask the inverse question when their hosting bills climb and they consider going back to Blogger for the free hosting. Both migrations are technically possible (Blogger to WordPress is one-click in the WordPress importer, WordPress to Blogger is harder but doable) and both are usually a mistake when an embed approach would solve the underlying problem at much lower cost. The real problem in most cases is not the writing platform, it is the public surface. Owners want their posts to feel modern, branded, and on-domain, and they assume the only way to get there is to migrate the entire blog. A blogger feed widget on a Webflow, Framer, or Shopify site achieves the same visible outcome with none of the migration risk: your existing Blogger archive stays in place, AdSense keeps earning, your Google account permissions stay intact, and the modern frontend gets fresh content automatically through the Atom feed. If you eventually decide the Blogger platform itself is the bottleneck, the same Poper feed widget configuration works against a WordPress feed, a Substack feed, or a Ghost feed by changing one URL, which keeps the cost of switching close to zero. The widget gives you the optionality that migration takes away. For a working Blogger publication in 2026 that has any audience at all, this is almost always the right play.