Open Graph Tag Tester Form
Example Data Table
| Sample URL | OG Title Length | OG Description Length | Required Tags Found | Score | Interpretation |
|---|---|---|---|---|---|
| https://example.com/blog/open-graph-guide | 62 | 154 | 6 / 6 | 100.00 | Excellent markup coverage and quality. |
| https://example.com/product/widget-a | 18 | 52 | 5 / 6 | 67.50 | Missing one required field and short copy. |
| https://example.com/category/tools | 0 | 0 | 2 / 6 | 23.33 | Low share readiness and weak preview control. |
Formula Used
Total Score = Coverage Score + Title Quality + Description Quality + Image Quality + URL Quality
Coverage Score = (Present Required Tags ÷ 6) × 70
Title Quality = 10 points if the OG title length falls inside your selected range. Near-range values receive 5 points.
Description Quality = 10 points if the OG description length falls inside your selected range. Near-range values receive 5 points.
Image Quality = 5 points when the image URL is valid, absolute, and matches the secure-image rule.
URL Quality = 5 points when og:url is a valid absolute web address.
Advisories such as missing og:image:alt, missing Twitter cards, and noindex directives are shown separately to keep the main score easy to compare.
How to Use This Calculator
- Paste the page URL you want to audit.
- Set your preferred title and description length ranges.
- Choose whether secure images, image alt text, locale, and Twitter fallback checks should be enforced.
- Submit the form to fetch the page and parse its metadata.
- Review the score, table, preview card, advisories, and chart.
- Download the final report as CSV or PDF for your workflow.
Frequently Asked Questions
1. What does this tester measure?
It checks required Open Graph fields, title and description length quality, image URL readiness, URL formatting, and several advisory items for better social previews.
2. Which tags are treated as required?
The score uses six core fields: og:title, og:description, og:image, og:url, og:type, and og:site_name. These strongly influence social share appearance.
3. Why can a page score well but still show advisories?
Advisories flag useful enhancements like image alt text, locale markup, or Twitter card fallbacks. They are shown separately so the main score stays consistent.
4. Does the tool fetch redirected pages?
Yes. It follows redirects and reports the final fetched URL. This helps you detect whether the tested page resolves somewhere unexpected.
5. Why might a valid page fail to load?
Some servers block automated requests, require authentication, throttle bots, or return unusual content types. In those cases, the tester may show a fetch error.
6. Why do title and description limits matter?
Balanced copy lengths improve readability in shared previews. Very short text lacks context, while overly long text may truncate or reduce clarity on some platforms.
7. Does this replace platform-specific preview tools?
No. It is a structured audit and scoring tool. Final preview rendering can still vary by network, device, cache state, and platform-specific rules.
8. Can I use the exported files for audits?
Yes. The CSV is useful for spreadsheets and tracking fixes. The PDF is useful for sharing snapshots with teams, clients, or documentation records.