Social URL
Pages can declare the official web address platforms should use when the page is shared. Silktide checks that each page declares this address and that it is clean and consistent - the page's own address, without tracking codes or surprises.
The sharing address is set with an tag in the page's :
<!-- The clean, official address for this page -->
<meta property="og:url" content="https://www.example.com/courses/biology" />
Why this matters
Social platforms use this address to identify the page being shared, and they aggregate likes, comments, and share counts against it. If different copies of the same page declare different sharing addresses - or the address carries campaign tracking codes - that engagement gets split across several versions instead of accumulating on one. An address pointing at a different domain or path can also send visitors somewhere you did not intend.
How to fix it
- In your , find where the social URL is set - most
CMSs and SEO plugins generate
og:urlautomatically from the page's , which is the right behavior. - Make sure the address is the full, public address of the page itself: starting
with
https://(orhttp://), on the same domain as the page, and matching the page's canonical URL where one is set. - Remove tracking parameters such as
utm_source,utm_campaign,gclid, orfbclid- tracking codes belong on links pointing to the page, never in the page's own declared address.
How Silktide tests this
- Test each page that could be shared - pages search engines and platforms are allowed to index.
- Read the page's
og:urltag. If it is missing, report the page. - Report the address unless all of the following hold:
- It is a full web address using
httporhttps. - It is on the same domain as the page.
- It carries no common tracking parameters (
utm_*,gclid,fbclid,mc_cid,mc_eid). - It matches the page's canonical URL where one is declared, or the page's own address otherwise. The comparison ignores capitalization and trailing slashes.
- It is a full web address using
Troubleshooting
My social URL differs from the page address on purpose
The one legitimate case is pointing at the canonical version of a duplicated page, and that passes - the check compares against the canonical URL first. A social URL pointing at a genuinely different page or domain splits engagement and is worth fixing. If you are confident your setup is intentional, the finding.