Google、Facebook抓取源码与浏览器显示不一致，OG标签缺失求助

算力阿峰

2026-5-22

Troubleshooting: Missing Tags (Including OG Tags) in Facebook Debugger vs. Browser View Source

Hey there, let's break down why the Facebook Debugger is pulling a stripped-down version of your page while your browser shows the full source—including those critical OG tags. Here are the most actionable fixes to investigate:

Check for User-Agent based content serving
Facebook's crawler uses a specific User-Agent string (facebookexternalhit/1.1). It’s common for servers, CDNs, or CMS plugins to serve different content to crawlers vs. regular browsers. Test this by simulating the crawler’s request locally with curl:
```
curl -A "facebookexternalhit/1.1" https://justdoc.com/medicine/surfaz-sn-cream
```
If the output is missing tags, you’ll need to adjust your server/CDN rules to ensure Facebook’s crawler gets the full, unmodified HTML.
Rule out client-side rendering issues
If your page uses client-side frameworks (React, Vue, etc.) that render content via JavaScript, the initial HTML sent to the server won’t include dynamic content (like OG tags). Browsers execute JS to build the full DOM, but Facebook’s crawler doesn’t run JS by default. Fix this by implementing server-side rendering (SSR), static site generation (SSG), or using a pre-rendering tool to serve fully rendered HTML to crawlers.
Audit CDN/security tool blocking
Tools like Cloudflare, WordPress security plugins, or firewalls might flag Facebook’s crawler as a bot and restrict access. Check your CDN’s firewall rules or security plugin settings to whitelist Facebook’s crawler IP ranges or its User-Agent string.
Validate OG tag placement and syntax
Even if your browser sees the OG tags, double-check they’re properly placed inside the <head> section and follow Open Graph guidelines (correct property names, valid values). A tiny syntax error could make the debugger ignore them, even if they show up in view source.
Force a fresh scrape in the debugger
Facebook’s tool caches previous results aggressively. After making changes, click the "Scrape Again" button in the debugger to pull the latest version of your page—don’t rely on cached data!