<?xml version="1.0" encoding="utf-8"?>
<oembed>
  <version>1</version>
  <type>rich</type>
  <provider_name>Libsyn</provider_name>
  <provider_url>https://www.libsyn.com</provider_url>
  <height>90</height>
  <width>600</width>
  <title>#16: Your Instagram Posts Just Got Indexed by Google–And ChatGPT Is Watching</title>
  <description>As of July 2025, Instagram posts are now indexed by Google. Grace and Peter break down how brands should adjust their content strategy accordingly. Plus, a look at the other platforms showing up in search results, and signs that ChatGPT is sourcing answers from Google. The evidence is clear: social media, search engines, and LLMs are becoming increasingly intertwined. Listen to find out what this shift means and how to respond.&amp;amp;nbsp; Subscribe to our newsletter Chapters:&amp;amp;nbsp; 01:36 – Instagram Posts Now Indexed by Google 03:49 – Why B2B Should Reconsider Instagram 05:25 – ChatGPT Might Be Using Google Snippets 07:26 – SEO + AEO = Unified Strategy 08:10 – New AI Search Browser: Comet by Perplexity 08:52 – Does Search Convergence = Less Work? 10:30 – The 80% Stat That Should Scare News Sites 11:17 – What Non-SEO Experts Can Do&amp;amp;nbsp; Sources:&amp;amp;nbsp; “Instagram Posts Can Now Rank on Google (And Why That Changes Everything)” by Annie-Mai Hodge for Atlas SEO “Confirmed: ChatGPT uses Google SERP Snippets for its Answers [A Test with Proof]” by Aleyda Solis for aleydasolis.com &amp;amp;nbsp; </description>
  <author_name>Accelerated Velocity</author_name>
  <author_url>https://sites.libsyn.com/573960</author_url>
  <html>&lt;iframe title="Libsyn Player" style="border: none" src="//html5-player.libsyn.com/embed/episode/id/37630030/height/90/theme/custom/thumbnail/yes/direction/forward/render-playlist/no/custom-color/88AA3C/" height="90" width="600" scrolling="no"  allowfullscreen webkitallowfullscreen mozallowfullscreen oallowfullscreen msallowfullscreen&gt;&lt;/iframe&gt;</html>
  <thumbnail_url>https://assets.libsyn.com/secure/content/191513575</thumbnail_url>
</oembed>
