<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MergePress blog</title>
    <link>https://mergepress.dev/blog/</link>
    <description>Notes on shipping SEO content through pull requests: permission scopes, approval trails, and the trust boundary between a content tool and your site.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 09 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://mergepress.dev/rss.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>Why we ship three posts a month, not thirty</title>
      <link>https://mergepress.dev/blog/three-posts-a-month-not-thirty/</link>
      <guid isPermaLink="true">https://mergepress.dev/blog/three-posts-a-month-not-thirty/</guid>
      <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
      <description>The autoblog offer — thirty posts for $99 — sells the wrong number. Why a few genuinely-reviewed posts beat a flood, and what Google&apos;s 2024 policy changed.</description>
    </item>
    <item>
      <title>Your content tool doesn&apos;t need your keys</title>
      <link>https://mergepress.dev/blog/why-your-content-tool-should-not-have-your-keys/</link>
      <guid isPermaLink="true">https://mergepress.dev/blog/why-your-content-tool-should-not-have-your-keys/</guid>
      <pubDate>Sun, 09 Aug 2026 00:00:00 GMT</pubDate>
      <description>What a CMS admin login lets a content tool do to your site, why vendor promises aren&apos;t architecture, and what changes when every edit arrives as a pull request.</description>
    </item>
  </channel>
</rss>
