To audit Open Graph (OG) tags across a website, first build a complete list of URLs to check, then crawl each page, extract and validate its metadata, test every referenced image, group errors by shared template, and retest the fixes. A crawl alone is not proof of complete coverage: compare its results with your sitemap and a deliberate list of important pages.
What a site-wide Open Graph audit should check
Open Graph metadata is commonly placed in a page’s <head>. The Open Graph Protocol identifies four foundational properties for each page: og:title, og:type, og:image, and og:url. It describes og:url as the object’s canonical URL and permanent graph identifier. The protocol also describes og:description and og:site_name as optional, generally recommended properties. When a page specifies og:image, the protocol recommends specifying og:image:alt as well. See the Open Graph Protocol.
As an Amazon Associate I earn from qualifying purchases.
Check these properties separately for presence, correctness, duplication, and consistency across page types. A tag’s presence does not establish that an external crawler can fetch the image or that a social platform will display a newly updated card.
1. Define scope and build the URL inventory
Decide which parts of the site are in scope before crawling. Include relevant subdomains, language or region variants, and page types such as product pages, categories, articles, campaigns, and landing pages. Gather URLs from the XML sitemap and internal links, then compare them with a manually maintained list of priority pages.
- Identify URLs found in the sitemap but not through internal links. They may be intentionally unlinked, or they may be stale or orphaned.
- Check whether important pages are missing from both the crawl and sitemap, and add them explicitly to the audit list.
- Record redirects and final destinations so that a URL’s declared
og:urlcan be compared with the intended canonical URL.
A general crawler typically discovers pages through links in HTML and offers crawl configuration. Some tools also offer JavaScript rendering, which can help when links or metadata are generated client-side. A rendered crawl does not prove that every social platform’s crawler executes JavaScript in the same way.
2. Choose a crawl and extraction method
| Approach | Best for | Strengths | Limits |
|---|---|---|---|
| General crawler such as Screaming Frog SEO Spider | Technical teams that need a broad site crawl and flexible extraction | Crawl configuration, source search, custom HTML extraction, exports, optional JavaScript rendering, and crawl comparison | OG-specific reporting may require custom extraction. The vendor’s product page, accessed in 2026, lists a free limit of 500 URLs per crawl and a £199 annual license to remove the limit and unlock advanced features; pricing and limits can change. See Screaming Frog SEO Spider. |
| Specialized audit such as OpenGraph.io Site Audit | Teams focused on OG checks, image previews, and issue reporting | Page-level OG checks, image and canonical checks, preview cards, issue rollups, and reports; documented discovery via sitemap and internal links or an exact URL list | The vendor says the tool is not a replacement for a full technical SEO crawler. Its documentation describes paid monitoring as weekly or monthly. See OpenGraph.io Site Audit. |
| Manual source inspection plus a single-URL checker | Small sites and spot checks | Quickly inspect fetched tags and a preview for an individual URL | It does not establish whole-site coverage unless every URL is inventoried and checked. See Facebook Sharing Debugger and LinkedIn Post Inspector. |
Choose based on URL coverage, discovery controls, custom extraction, whether JavaScript rendering is needed, image-fetch checks, preview simulation, export and reporting options, repeatability, and crawl limits. A specialized audit may package OG-specific findings; a general crawler may offer broader technical crawl data but require custom extraction to produce the report you need.
3. Extract fields into a page-by-page report
Create one row per URL. A useful audit spreadsheet or export includes:
- Requested URL, HTTP status, and final URL after redirects.
- HTML title and canonical link for context.
og:title,og:type,og:image, andog:url.og:descriptionandog:site_name.og:image:altwhen an image is declared.- Duplicate instances of important properties, rather than just the first matching value.
- Image response status and basic dimensions, if your method can fetch and inspect the asset.
- Page type or template, plus an issue or notes column.
These are recommended audit columns, not a promise that every crawler reports them by default. Screaming Frog documents custom HTML extraction and export; its extraction options include XPath, CSS selectors, and regex. Consult its custom extraction guidance for configuration. A specialized audit vendor describes explicit OG-field and image checks in its Site Audit documentation.
Rank #2
4. Validate presence, values, and consistency
Separate protocol requirements from recommendations
Flag missing og:title, og:type, og:image, or og:url as missing foundational properties under the protocol. Track og:description and og:site_name separately: they are optional, although generally recommended. When og:image is present, check for og:image:alt as recommended by the protocol.
Check page-specific metadata and canonical intent
Verify that each page’s og:url matches the canonical URL strategy you intend to publish. Look for generic titles, descriptions, or images repeated across unrelated pages. A value repeated across a consistent series may be deliberate; a product page inheriting an unrelated campaign image is more likely a template or content error.
Look for duplicate and conflicting output
More than one component can emit a property—for example, a CMS template and a plugin. Flag duplicates and inspect the page source or rendered HTML to identify which template, plugin, or component owns the output. Resolve the shared source rather than applying one-off patches to every affected page.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Do not treat display advice as protocol law
Do not apply a universal character limit for titles or image dimensions as though the Open Graph Protocol requires it. Platform rendering and cropping can differ. A vendor may publish platform-oriented recommendations, but test actual previews for the services you target and label any such figures as recommendations. For example, OpenGraph.io’s current audit documentation accessed in 2026 presents 1200×630 as a recommendation its image checks compare against—not a formal protocol requirement. See its Site Audit documentation.
5. Verify each OG image independently
For each og:image, check the asset itself, not just the tag that points to it. Resolve the URL and inspect whether it is publicly retrievable, whether it redirects unexpectedly, and whether the response contains a usable image. A file opening in your logged-in browser does not prove that an unauthenticated external crawler can retrieve it.
- Confirm that the image URL resolves correctly and is absolute where required by your implementation.
- Check for access restrictions, unexpected redirects, a non-success response, the wrong content type, or a malformed file.
- Record dimensions and aspect ratio as practical preview checks, not universal protocol requirements.
- If a preview is stale, distinguish the image or page’s current response from any separate preview-cache behavior.
Third-party checker guidance discusses separate page and image fetching and common issues such as blocked images, relative paths, and caching. See OpenGraph Check.
6. Group findings, fix shared causes, and rerun
Sort issues by property, template, CMS or plugin, and number of affected URLs. A single template defect can account for many page-level failures, so fix shared generation logic before editing individual content records.
- Group repeated failures—for example, missing
og:imageacross every article page, or one genericog:titleacross a product category. - Inspect the shared template, CMS settings, plugin output, or component responsible for those fields.
- Correct the common cause, then review exceptional pages that intentionally use different metadata.
- Rerun the same URL inventory and compare the output with the initial crawl to verify the fix and spot regressions.
Crawler vendors document exporting crawl data and comparing crawls; the specialized audit documentation describes issue rollups and monitoring comparisons. See Screaming Frog SEO Spider and OpenGraph.io Site Audit.
7. Preview representative pages on the target platforms
Choose representative URLs for each template and page type. Inspect their extracted metadata and use a relevant platform debugger or preview inspector if a displayed card disagrees with the page output. Facebook Sharing Debugger and LinkedIn Post Inspector are examples of platform-specific tools described by third-party checker guidance: Facebook Sharing Debugger and LinkedIn Post Inspector.
Use the current platform tool to check a page after a metadata change, and account for the possibility that its displayed preview is cached separately from your page. The exact refresh steps and caching behavior vary; do not assume one platform’s process applies to another.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Common audit problems and fixes
The crawler extract is missing tags
Inspect the page source and rendered HTML. Confirm that your extraction targets the actual meta elements and their property attributes. If tags are added after the initial HTML, check whether your crawler is reading raw HTML by default and whether its JavaScript-rendering option is appropriate. A rendered result still does not establish how a social crawler will process the page.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThe same page’s values appear on many URLs
Group affected URLs by template, then inspect shared metadata-generation logic, CMS settings, and plugins for duplicated or inherited output. Fix the shared cause and rerun that URL group.
Best Value
- Features Over 160 Latin Songs
- Arranged for C Instruments
- Standard Notation
- 48 Pages
The image tag exists, but the preview has no image
Test the image as an unauthenticated external request. Check its response, redirects, access controls, content, and file validity. Then inspect the page with the target platform’s current preview or debugger tool.
The crawler sees updated tags, but the platform card is old
Use that platform’s current debugger or inspector workflow and allow for separate preview caching. Cache behavior and refresh steps differ; verify them in the platform’s current documentation rather than assuming the crawler extract guarantees an immediate preview update.
Important URLs are missing from the report
Compare the crawl output against the XML sitemap and your explicit priority list. Add known important URLs directly or adjust discovery and crawl configuration; do not treat an automatically discovered set as complete without checking it.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Or skip the browser setup
If you need a clean screenshot of a page while investigating how it appears, ScreenshotNeo can return a screenshot or PDF from one GET request. A screenshot is useful visual evidence, but it does not replace extracting and validating the OG tags or testing a target platform’s own preview.
For parameters and response details, see the ScreenshotNeo documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpCookie banners are accepted and removed before the shot, as are known newsletter popups and chat widgets; each step can be turned off. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response identifies the page verdict and billing status. An MCP server gives AI agents tools for taking screenshots, getting page information, and capturing PDFs. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
Sign up for 1,000 free screenshots a month—no card required.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
