<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Julien Rousseau</title>
    <description>The latest articles on DEV Community by Julien Rousseau (@julien_rousseau_29172bb6c).</description>
    <link>https://dev.to/julien_rousseau_29172bb6c</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2799232%2F8cd2374a-1c12-4b71-b154-7e84b2fb6035.png</url>
      <title>DEV Community: Julien Rousseau</title>
      <link>https://dev.to/julien_rousseau_29172bb6c</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/julien_rousseau_29172bb6c"/>
    <language>en</language>
    <item>
      <title>Why your OpenGraph tags break on LinkedIn (and how to actually fix it)</title>
      <dc:creator>Julien Rousseau</dc:creator>
      <pubDate>Sat, 12 Sep 2026 15:11:47 +0000</pubDate>
      <link>https://dev.to/julien_rousseau_29172bb6c/why-your-opengraph-tags-break-on-linkedin-and-how-to-actually-fix-it-32gf</link>
      <guid>https://dev.to/julien_rousseau_29172bb6c/why-your-opengraph-tags-break-on-linkedin-and-how-to-actually-fix-it-32gf</guid>
      <description>&lt;p&gt;Last week someone asked me why their React app showed an empty card when shared on LinkedIn, even though their tags were right there in the code.&lt;/p&gt;

&lt;p&gt;The reason is simple: social scrapers don’t execute client-side JavaScript.&lt;/p&gt;

&lt;p&gt;Twitterbot, LinkedInBot, and Slackbot aren't full browsers. They run a quick &lt;code&gt;GET&lt;/code&gt; request, look at the raw HTML coming from your server, grab whatever is inside &lt;code&gt;&amp;lt;head&amp;gt;&lt;/code&gt;, and close the connection.&lt;/p&gt;

&lt;p&gt;If you use pure React or Vite without SSR, the bot only gets this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="cp"&gt;&amp;lt;!DOCTYPE html&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;html&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;head&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;title&amp;gt;&lt;/span&gt;My App&lt;span class="nt"&gt;&amp;lt;/title&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/head&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;body&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;id=&lt;/span&gt;&lt;span class="s"&gt;"root"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/div&amp;gt;&lt;/span&gt;
    &lt;span class="nt"&gt;&amp;lt;script &lt;/span&gt;&lt;span class="na"&gt;src=&lt;/span&gt;&lt;span class="s"&gt;"/src/main.jsx"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&amp;lt;/script&amp;gt;&lt;/span&gt;
  &lt;span class="nt"&gt;&amp;lt;/body&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;/html&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;blockquote&gt;
&lt;p&gt;The tags are injected after client hydration. By that time, the crawler is already gone.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  How to fix it
&lt;/h2&gt;

&lt;p&gt;First, your meta tags need to be in the initial HTML (using Next.js, Remix, Astro, or static prerendering).&lt;/p&gt;

&lt;p&gt;Second, you need the actual dynamic image. Doing Figma exports for every blog post or product page gets old fast, and maintaining a headless Puppeteer instance on your backend to screenshot HTML is heavy and slow.&lt;/p&gt;

&lt;p&gt;To solve this for my own projects, I built &lt;a href="https://dev.tourl"&gt;ogcraft.dev&lt;/a&gt;, focusing on two things:&lt;/p&gt;

&lt;p&gt;A raw HTML visualizer: A free tool that scrapes strictly the raw initial HTML (no client-side JS) so you can preview exactly what Twitter and LinkedIn see before sharing.&lt;/p&gt;

&lt;p&gt;A crawl-back image engine: Instead of passing huge encoded payloads or spinning up browser instances, you just drop a single tag on your page:&lt;/p&gt;

&lt;p&gt;HTML&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;meta&lt;/span&gt; &lt;span class="na"&gt;property=&lt;/span&gt;&lt;span class="s"&gt;"og:image"&lt;/span&gt; &lt;span class="na"&gt;content=&lt;/span&gt;&lt;span class="s"&gt;"https://api.ogcraft.dev/api/v1/extract?template=modern-blog&amp;amp;url=https://mysite.com/blog/my-post"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The API visits your page, extracts your existing tags (&lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt;, description, author), and renders an optimized dynamic card on the fly with CDN caching.&lt;/p&gt;

&lt;p&gt;How do you guys usually handle dynamic OG images? Do you spin up Puppeteer/Satori in serverless functions, or use dedicated image APIs?&lt;/p&gt;

</description>
      <category>frontend</category>
      <category>javascript</category>
      <category>react</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
