OG URL Match
SkillDev toolsog-url-match is a skill for auditing Open Graph tags on pages that have both a canonical-url and an og:url tag. It checks whether the two URLs match exactly and explains how mismatches split social share counts across URL variants, making share counts appear lower than they are.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a page that contains both a canonical-url tag and an og:url meta tag.
Then ask your AI: use the OG URL Match skill
What your AI can do with it
- Compare og:url with the canonical tag value character-for-character
- Flag mismatches in protocol, domain, path, or query string
- Detect http vs https, www vs non-www, and trailing slash inconsistencies
- Identify UTM parameters, session IDs, or tracking tokens in og:url
- Guide fixes: set og:url to the canonical absolute HTTPS URL
- Advise adding a canonical tag when none exists
Getting started
- Have a page that contains both a canonical-url tag and an og:url meta tag.
- Invoke the skill when auditing Open Graph tags or investigating low social share counts.
- Compare the og:url value with the canonical href; both must be identical absolute HTTPS URLs.
- Fix mismatches by setting og:url to the exact canonical URL and removing tracking parameters.
- Consult references/rule.md for full implementation details and framework-specific guidance.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/og-url-match/SKILL.md and read by ahel’s review.
When og:url doesn't match the canonical URL, social platforms track share counts separately for each URL variant—published share counts get split across multiple URLs and appear lower than they actually are.
Quick Reference
- og:url must exactly match the URL
- Use absolute HTTPS URLs for both og:url and canonical-url
- Mismatched URLs cause social platforms to aggregate share counts on the wrong URL
- og:url should be the clean canonical URL without tracking parameters
Check
Compare the og:url meta tag value with the href value. Both must be identical absolute HTTPS URLs. Flag any page where they differ, either in protocol, domain, path, or query string.
Fix
Set og:url to exactly the same absolute HTTPS URL as the canonical tag. Remove any UTM parameters, session IDs, or tracking tokens from og:url. If no canonical tag exists, add one and set og:url to match it.
Explain
Social platforms use og:url as the canonical identifier for aggregating share counts and comments. If og:url differs from the canonical tag, shares on the page URL and shares of the og:url accumulate separately, making your content appear less popular than it is and creating attribution confusion.
Code Review
Compare the value of with the value of . They must be identical character-for-character. Check for: different protocols (http vs https), www vs non-www mismatch, query string differences, trailing slash inconsistencies. Flag any page where the two values differ.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/og-url-match
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should this skill be used?
- Use it when auditing Open Graph tags or investigating why social share counts appear low. It applies to any page with both canonical-url and og:url tags.
- Why do social share counts appear low?
- When og:url doesn't match the canonical URL, social platforms track share counts separately for each URL variant, splitting published share counts across multiple URLs.
- What counts as a mismatch?
- Any difference between og:url and the canonical tag: protocol (http vs https), www vs non-www, path, query string, or trailing slash inconsistencies.
Advanced
- Item type
- skill
- Key
og-url-match- Source
- github.com/thedaviddias/front-end-checklist