TechCompare LogoTechCompare
Showing centimeters. Press to switch to inches.Showing inches. Press to switch to centimeters.

How to check the Open Graph tags on every page of a site

By TechCompare · Updated · How we check

Run your sitemap through batch mode after every template change, not just at launch. Fix missing images first, because they change the card the most. Repeated titles usually come from one template bug, so one fix can clear many rows at once. Download the CSV when you want to track the fixes in a spreadsheet.

Checking one link preview is easy, but a single template bug can break the cards on every page that uses it. A blog template that never got an og:image, a shop that copies one description onto every product, or a new section without a twitter:card all look fine in the browser. Nobody notices until the link gets shared.

Batch mode in the Open Graph Viewer reads a sitemap or a list of URLs and checks up to 100 pages from one site in a single run. You get a table with each page's title, description and image, and the problems sit right next to the page they belong to.

Platform or focus
Best Practices
OG tag strategy and tooling
Topic detail
Bulk OG tag audit
bulk-audit
Check a whole site in batch mode. Paste a sitemap URL or up to 100 page URLs from one site.
Edit in the full tool

How this is calculated

Paste a sitemap URL or a list of page URLs, one per line. Most sites keep their sitemap at /sitemap.xml, and robots.txt usually names it. The checker reads the first 100 pages. When the sitemap is an index that points to other sitemaps, it opens up to three of them and still stops at 100 pages in total. Gzipped sitemaps (.xml.gz) aren't supported, so use the plain XML version or paste the URLs.

Every page gets the same checks:

  • No og:title, og:description, og:image or twitter:card.
  • An og:image under 1200x630, shown with its real size.
  • An og:image that doesn't load at all.
  • A title over 60 characters or a description over 160.
  • The same title or description on more than one page.

Pages are fetched about one a second, so a full batch takes about two minutes. A batch covers one site, and www and the bare domain count as the same site. URLs from other hosts are skipped and listed under the results. That keeps the load on any single server low, so the site has no reason to block the checks.

Verdict

Batch mode is the fast way to catch template bugs across a site: missing og:image tags, images under 1200x630, and titles or descriptions repeated on many pages. It checks up to 100 pages from one site per run, at about a page a second, and follows a sitemap index one level down. For a bigger site, paste each child sitemap on its own, or paste one page from every template.

More OG scenarios

OG image dimensions
The de facto standard Open Graph image size is 1200x630 pixels, a 1.91:1 aspect ratio.
View details
Twitter Card types
Twitter Cards control how your URL appears when shared on X (formerly Twitter).
View details
Facebook vs Twitter tags
Open Graph (og:) tags are the standard, originated by Facebook and now supported by LinkedIn, Discord, Slack, WhatsApp, and most other platforms.
View details

Related guides

OG debugger tools
Platform debuggers for the pages the batch flags.
View guide
OG image dimensions
Why the batch flags images under 1200x630.
View guide

Frequently asked questions

How many pages can I check at once?
Up to 100 per batch, all from one site. A sitemap index works too. The checker opens up to three of its child sitemaps and stops at 100 pages in total. For a bigger site, paste one child sitemap at a time, or paste a short list with one page from each template, since pages that share a template usually share its bugs. If you run batch after batch, an hourly limit kicks in, and the tool tells you when you can go on.
Why does my browser load every og:image?
To measure it. The page's HTML only says where the image lives, not how big it is, so your browser downloads each og:image and reads its real width and height. That means the image host sees a normal visit from your browser. TechCompare's server fetches the pages themselves. The results only live in your browser tab, so they're gone when you leave, and they never go in the link.
Why does the checker flag titles over 60 characters?
Google cuts titles by pixel width, not by a character count, and titles past about 60 characters often get cut on desktop. Descriptions get cut at about 155 to 160 characters. Treat these as warnings rather than errors. A long og:title still works, but the end of it may be hidden in search results and in some share cards.
Why were some of my URLs skipped?
A batch only checks one site, picked from the first URL you paste or from the sitemap's own address. URLs on other hosts get skipped and listed under the results, so you can check them in a separate batch. The www and bare versions of a domain count as one site, and a sitemap that redirects to a new domain gets its pages on that domain checked.

Related tools

JSON Formatter

Validate, format, and minify JSON. Browse it as a tree, run JSONPath queries, compare two documents, or validate against a JSON Schema.

Use tool

Text Encoding Converter

Convert text to Base64, binary, hex, URL encoding and HTML entities, and back again.

Use tool

Color Picker

Pick colors, convert between HEX, RGB, HSL, HSV, OKLCH and CMYK, and find the nearest CSS and Tailwind color.

Use tool