Skip to content

Set og:type to article so Pinterest's Rich Pin validator finds one - #123

Merged
Robbie1977 merged 1 commit into
mainfrom
fix/pinterest-rich-pin-og-type
Sep 22, 2026
Merged

Robbie1977 merged 1 commit into
mainfrom
fix/pinterest-rich-pin-og-type

Conversation

@Robbie1977

Copy link
Copy Markdown
Contributor

Pinterest only recognises og:type "article" or "blog" as Rich-Pin eligible; the preview page was sending "website", which Pinterest never treats as a Rich Pin no matter what other og:/twitter: tags are present — that's why the validator said "We were not able to find a Rich Pin!" even though the ordinary preview (title/description/image) was already working everywhere else (Slack, Facebook, Discord, Bluesky don't gate on og:type the same way).

Also adds article:section (the term kind — class/individual/template/term), which Pinterest lists as optional-but-useful and costs nothing to include. og:site_name was already present and is the other tag Pinterest strongly recommends.

New test added (test_page_qualifies_for_pinterest_article_rich_pin); all 39 tests pass.

Pinterest only recognises og:type "article" or "blog" as Rich-Pin
eligible; the preview page was sending "website", which Pinterest
never treats as a Rich Pin regardless of what other og:/twitter: tags
are present -- every other unfurler (Slack, Facebook, Discord, Bluesky)
was already unaffected since they don't gate on og:type the same way.

Also adds article:section (the term kind -- class/individual/template/
term) since it's free to provide and Pinterest lists it as optional-
but-useful; og:site_name was already present and is Pinterest's other
strongly-recommended tag.
@Robbie1977
Robbie1977 merged commit 327b0f1 into main Sep 22, 2026
3 of 5 checks passed
@github-actions

Copy link
Copy Markdown

⚠️ 162 test(s) skipped — an upstream data source was unreachable

The full suite ran, but 162 test(s) were skipped because an upstream data source (VFB's Neo4j / SOLR / Owlery, or FlyBase's Chado) did not answer during this run.

These are not failures and not a problem with this branch — but those queries went unverified, so a green check here is an incomplete run.

To re-run: open this workflow run and click Re-run all jobs once the data sources are healthy (re-running the “Run completeness” check itself does nothing — it has no job behind it).

1 failed, 726 passed, 162 skipped, 338 warnings in 830.60s (0:13:50)

Posted automatically. This comment is removed once a run completes with zero skips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants