Recommended Free Tools
To audit Open Graph tags across a sitemap, turn the sitemap URLs into a page inventory, fetch each page, and check the returned HTML, redirects, tag values, and image URLs—not just whether a tag exists. Group recurring faults by page template, fix their shared cause, then recrawl the affected URLs.
Define the audit scope from your sitemap
Find the sitemap URL in robots.txt, your CMS, or your site’s documented sitemap address. If it is a sitemap index, recursively collect its child sitemaps. Parse each <loc> into a URL inventory, retaining the source sitemap and any useful <lastmod> value. Deduplicate URLs, but keep a note of URLs listed by more than one sitemap.
Decide whether the audit covers every listed URL or selected page classes, such as product pages, articles, or campaign landing pages. Record the scope and exclusions in the final report. A sitemap defines a useful audit boundary; it does not guarantee that search engines will crawl or index every listed URL. Google describes a small site as about 500 pages or fewer in its discussion of whether a sitemap is needed; that is context, not a cutoff for whether an Open Graph audit is worthwhile. Google Search Central’s sitemap overview
Fetch every URL and preserve what happened
For each URL, record the requested address, HTTP status, redirect chain, final URL, content type, and fetch time. Flag errors, unexpected redirects, and non-HTML responses separately from valid HTML pages with missing metadata. Respect site rate limits and use a conservative crawl pace, particularly on a production site.
#1 Best Overall
Keep the raw HTML or a reproducible source snapshot for pages with findings. That evidence helps distinguish absent tags from malformed values, duplicate properties, or metadata generated by a CMS template. A crawl result is not a valid tag audit if the page could not be fetched successfully.
Extract the required and useful properties
The Open Graph Protocol specifies four required basic properties for every page: og:title, og:type, og:image, and og:url. Also collect the useful optional properties og:description, og:site_name, and og:locale, plus available image properties such as og:image:width, og:image:height, and og:image:alt. Open Graph Protocol specification
Rank #2
- Features Over 160 Latin Songs
- Arranged for C Instruments
- Standard Notation
- 48 Pages
Preserve every occurrence and its order when a property is repeated; do not silently collapse duplicates into one value. The protocol says the first value is preferred when consumers encounter conflicting values. Keep both the raw values and the extracted result so reviewers can see what a platform may encounter.
Validate values and preview images
- Presence and content: flag missing or blank required properties, unexpected duplicates, and values that do not describe the specific page.
- Page identity: compare
og:urlwith the page’s intended canonical identity. Investigate mismatches, especially when the fetched URL redirects. - Image resolution: resolve a relative
og:imageagainst the final page URL, then request it and record its response status, content type, and dimensions. If your audit requires absolute image URLs, state that policy explicitly rather than assuming every consumer handles relative values the same way. - Image suitability: review the image itself and its crop, not just whether it loads. OpenGraph.io recommends 1200×630 for preview quality; that is the vendor’s recommendation, not a protocol requirement. OpenGraph.io
A reachable image can still produce a poor card if its subject is cropped badly or it is irrelevant to the page. For important pages, check the rendering with the destination platform’s preview or debugging workflow as a separate step: successful HTML extraction does not prove every consumer will render the same card.
Rank #3
Trace repeated problems to their source
Group findings by URL pattern, CMS content type, and repeated tag value. If unrelated pages share one title, description, or image, inspect the common template, SEO plugin settings, and site-wide fallback before editing individual pages.
For example, Yoast documents that Open Graph titles and descriptions may inherit from social templates, SEO fields, excerpts, or page content. Its image selection can fall back through page-specific, featured, content, template, and site-default choices. This illustrates why a tag visible in page source may have been generated by a shared rule rather than manually added to each page. Yoast’s Open Graph documentation
Prioritize fixes and verify the result
- Prioritize high-value landing pages, broken primary images, missing required properties, incorrect identity URLs, and errors affecting many pages.
- When findings cluster around one page family, correct the shared template, plugin configuration, or data source first.
- Recrawl the affected URL set after deployment and compare results with the saved baseline. Recheck representative pages from each affected template as well as specifically important URLs.
- Use platform preview tools for critical campaigns when needed. Consult Search Console separately for Google’s indexing view; it answers a different question from whether the page’s Open Graph metadata is correct.
Search Console’s sitemap filter can help examine submitted URLs, but its example URL list is limited and may not be exhaustive. Treat it as a diagnostic aid, not a substitute for a complete page-by-page inventory. Google Search Console URL Inspection tool
Keep a report that can be acted on
Retain one row per audited URL, with enough context to reproduce and assign each finding:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall- Requested URL, final URL, status, redirect notes, content type, and fetch timestamp.
- Source sitemap and any retained
lastmodvalue. - Extracted Open Graph values, duplicate counts, and the source snapshot location.
- Image request status, content type, dimensions, and preview or crop notes.
- Rule violations, page type or template, severity, suggested owner, and recheck result.
Add rollups for missing or invalid fields, image failures, duplicate values, redirects, non-HTML responses, and patterns that point to a shared template. State how many URLs were tested and what was excluded so the report does not overstate its coverage as site-wide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose an audit method that fits your site
A general-purpose crawler with custom extraction can keep the Open Graph audit alongside broader technical checks. An Open Graph-focused audit service may make social-preview summaries and card previews easier to review. Compare candidates on the details that affect your workflow:
- Sitemap and sitemap-index coverage, including URL deduplication and export options.
- Control over extraction rules, source evidence, and repeatable reports.
- Support for JavaScript-rendered pages, crawl pacing, and image-fetch checks.
- Issue grouping by template or repeated values, and whether preview rendering is included.
- Cost for the URL volume and recrawl frequency you need.
Published product descriptions establish capabilities, not an independent head-to-head result. Test a candidate against representative pages from your own site before relying on it for a full audit. An Open Graph-focused audit also differs from a full technical SEO crawl: it may center on social metadata and preview cards rather than backlinks, Core Web Vitals, crawl depth, or indexing status.
Or skip the browser setup
If you need screenshots of audited pages or previews without building a browser-capture setup, ScreenshotNeo offers a screenshot API and MCP server. One GET request can return a screenshot or PDF. Cookie banners are accepted and removed along with supported consent banners, newsletter popups, and chat widgets before the shot; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, with the outcome reported in response headers. AI agents can use its MCP tools to take screenshots, get page information, and capture PDFs.
For a screenshot of a target page, replace the example URL with the page you want to inspect:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. One thousand screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
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.
