Currently if website A publishes an article they can pitch to a collection which is their own. That's all good.
If website B is added to the article as an additional website, but the article is not updated in Composer (no website_url generated for website B), website B can still pitch the article to a collection they own. This unfortunately then includes an article with no website_url in website B's collection which culminates in a headline and other display elements depending on the specific PageBuilder setup not having any "link"... is not clickable.
Ideally, website B would get an error message when pitching to the websked collection noting the article is not published to their website, no website_url available.
Clay McNeill
Hi Clay, we are planning to build multisite collections, that will solve for this issue. Thanks for submitting your idea!