<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Signalbat blog</title>
    <link>https://signalbat.com/blog</link>
    <description>Field notes on AI visibility, source trails, competitor movement, and the answer layer.</description>
    <language>en</language>
    <item>
      <title>The competitor did not beat us. Their evidence was easier to summarize.</title>
      <link>https://signalbat.com/blog/competitor-evidence-easier-to-summarize</link>
      <guid>https://signalbat.com/blog/competitor-evidence-easier-to-summarize</guid>
      <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
      <description>When an AI assistant recommends a competitor, the useful question is not who ranked higher. It is which public evidence made that competitor easier to explain.</description>
    </item>
    <item>
      <title>What are the GEO basics if you already know SEO?</title>
      <link>https://signalbat.com/blog/geo-basics-if-you-know-seo</link>
      <guid>https://signalbat.com/blog/geo-basics-if-you-know-seo</guid>
      <pubDate>Fri, 12 Jun 2026 00:00:00 GMT</pubDate>
      <description>Generative engine optimization is not a separate bag of tricks. The basics are clear pages, credible sources, extractable claims, and repeated reads of what AI answers actually say.</description>
    </item>
    <item>
      <title>We found a stale claim living inside AI answers</title>
      <link>https://signalbat.com/blog/stale-claim-living-inside-ai-answers</link>
      <guid>https://signalbat.com/blog/stale-claim-living-inside-ai-answers</guid>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <description>AI assistants can keep repeating old claims long after your site moved on. The fix starts by tracing the source trail, not yelling at the model.</description>
    </item>
  </channel>
</rss>
