What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Build a URL inventory from your sitemap, fetch each page, and check both its Open Graph tags and its image responses. A useful audit records redirects and HTTP errors as well as metadata: otherwise, a failed fetch can look like a page with missing tags. Group findings by template, fix shared causes, then recrawl the affected URLs.
What a sitemap-based Open Graph audit checks
The sitemap defines the URLs in scope; it does not prove that those URLs are crawlable, indexed, or even currently returning the intended page. Google says sitemap inclusion does not guarantee crawling or indexing (Google Search Central). Keep the audit’s scope explicit: list the sitemap files used, URL count, exclusions, and the date of the crawl.
As an Amazon Associate I earn from qualifying purchases.
Open Graph’s four required basic properties are og:title, og:type, og:image, and og:url (Open Graph Protocol). Also inspect optional fields such as og:description, og:site_name, and og:locale. A presence check alone is not enough: values may be blank, duplicated, inappropriate for the page, or point to an unavailable image.
Google describes a small site in this context as about 500 pages or fewer; that is a sitemap discussion rule of thumb, not a cutoff for whether an Open Graph audit is useful (Google Search Central).
#1 Best Overall
1. Build and document the URL inventory
- Locate the sitemap. Check
robots.txt, your CMS settings, or the site’s documented sitemap URL. - Expand sitemap indexes. If the entry is an index, recursively collect each child sitemap before extracting its
<loc>URLs. - Preserve useful context. Store the source sitemap for each URL and any
<lastmod>value. Normalize URLs consistently and deduplicate them, but retain notes when a URL appears in multiple sitemap files. - Choose scope. Decide whether to audit every listed URL or a defined set of page types. Record that decision and any exclusions so the report does not imply coverage it did not achieve.
Sitemaps are discovery aids, particularly on large or complex sites, but membership is not a crawl or indexing guarantee.
2. Fetch pages and preserve the outcome
For every URL, retain the requested URL, HTTP status, redirect chain, final URL, content type, and fetch time. Mark errors, unexpected redirects, and non-HTML responses separately from successful HTML pages with missing metadata. Use a conservative request rate and respect site rate limits, especially on production systems.
Rank #2
- Features Over 160 Latin Songs
- Arranged for C Instruments
- Standard Notation
- 48 Pages
Keep the raw HTML or a reproducible source snapshot for pages with findings. This makes it possible to distinguish a genuinely absent property from a malformed value, a duplicate, or a value generated by a shared template. General crawlers can combine response and redirect checks with metadata extraction; choose one that supports the sitemap structure, crawl pacing, and export format your audit needs (Screaming Frog SEO Spider).
3. Extract tags without hiding duplicates
Capture at least the four required properties, plus useful optional and image fields:
Rank #3
og:title,og:type,og:image, andog:url.og:description,og:site_name, andog:locale.- When present,
og:image:width,og:image:height, andog:image:alt.
Store all occurrences of each property in source order. The Open Graph Protocol says the first value is preferred when consumers encounter conflicting values; silently collapsing duplicates can therefore conceal which value a consumer may use (Open Graph Protocol). Save the source location or raw markup for each occurrence if your extraction system can provide it.
4. Validate values and image responses
Check page identity and tag quality
- Flag missing and blank values, repeated properties, and values that do not describe the individual page.
- Compare
og:urlwith the intended canonical page identity. A redirect destination and an Open Graph identity URL are related evidence, but do not assume they must match in every implementation; define the expected policy for your site. - Resolve relative image URLs against the final page URL. Flag relative URLs for review if your intended consumer or implementation requires absolute addresses, and document that policy rather than assuming every platform treats them identically.
- Compare the title, description, and image with the actual page content and intended social preview.
Request and inspect every image
For each og:image, record whether the request succeeds, its content type, and its dimensions. Check the actual crop and aspect ratio as well as reachability; a valid image response can still make a poor card. OpenGraph.io recommends 1200×630 for preview quality, but that is its recommendation, not a requirement in the Open Graph Protocol (OpenGraph.io documentation). Treat declared og:image:width and og:image:height as metadata to compare with the fetched file, not proof of its real dimensions.
5. Find shared template and CMS causes
Group results by URL pattern, content type, and repeated tag value. If many pages share an identical title, description, or image, inspect the template, SEO plugin, and site-wide fallbacks before editing pages one by one.
For example, Yoast documents Open Graph values that can be derived from social templates, SEO fields, excerpts, or page content; image selection can fall back through page-specific, featured, content, template, and site-default choices (Yoast: Customize the Facebook share image and description). This is one concrete example of how a tag visible in rendered HTML may be generated rather than authored directly in the page body.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.6. Prioritize fixes and verify the result
- Sort by impact. Prioritize broken primary images, missing required properties, incorrect identity URLs, and errors on high-value landing pages. Include the number of affected pages for each issue.
- Fix clustered issues at their source. When findings share a pattern, correct the template, plugin configuration, or content source first; reserve page-by-page edits for page-specific problems.
- Recrawl affected URLs. Compare before-and-after values and image responses for the changed pages and representative pages using the same rules.
- Check important rendered previews. For campaign-critical pages, use the relevant platform’s preview or debugging workflow. Extracting correct HTML does not guarantee every consumer renders an identical card.
- Use Search Console for a separate question. Its sitemap filter can help examine submitted URLs, but its example URL list is limited and may not be exhaustive. It is a diagnostic view of Google’s indexing, not a replacement for the audit’s complete sitemap-derived metadata inventory (Google Search Console URL Inspection tool).
What to put in the audit report
Keep one row per URL and retain enough evidence to reproduce the finding:
- Requested URL, final URL, status, redirect notes, content type, and fetch timestamp.
- Originating sitemap, extracted values, duplicate counts, and page type or template.
- Image request result, content type, dimensions, and preview or crop notes.
- Rule violations, severity, suggested owner, and recheck result.
Add rollups for missing or invalid fields, image failures, repeated values, redirects, non-HTML responses, and patterns that point to a shared template. State the tested URL count and exclusions alongside the results.
Choosing an audit method
A general-purpose crawler is a fit when you want Open Graph extraction alongside broader technical checks and control over crawl settings and exports. An OG-focused audit service may make social-preview summaries and card previews easier to review. Compare sitemap-index handling, JavaScript rendering, crawl pacing, image checks, issue grouping, repeatability, and cost against your actual needs; documented tool capabilities alone do not establish which performs best for a particular site. An Open Graph audit complements a technical SEO crawl rather than replacing checks such as backlinks, Core Web Vitals, crawl depth, or indexing status (OpenGraph.io documentation).
Recommended Free Tools
Or skip the browser setup
If you also need clean screenshots of audited pages for review or reporting, ScreenshotNeo can return an image or PDF through one GET request. Its cookie/consent-banner handling and removal of 60+ known consent platforms, newsletter popups, and chat widgets run before capture, and each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed; response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.
Example cURL request (replace the target URL as needed):
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 setup and options. Sign up free for 1,000 screenshots a month with no card.
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.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
