I did a search for this topic, which is a comment on CodingHorror’s March 2017 post
https://blog.codinghorror.com/thunderbolting-your-video-card/
The first link Google points to, is the blogpost and the second one to the forum/comment discussion/post.
something about the google indexing here is weird. the canonical on that page is:
<link rel="canonical" href="https://discourse.codinghorror.com/t/thunderbolting-your-video-card/5157?page=2">
so I am not even sure how that is showing up there.
My google results from your link are in this order
https://blog.codinghorror.com/thunderbolting-your-video-card/https://discourse.codinghorror.com/t/thunderbolting-your-video-card/5157/9https://discourse.codinghorror.com/t/thunderbolting-your-video-card/5157/21https://discourse.codinghorror.com/t/thunderbolting-your-video-card/5157The actual correct result would be post number 12…
https://discourse.codinghorror.com/t/thunderbolting-your-video-card/5157/12
… so 9 and 21 are a bit off but certainly “on the same page” ish.
Still it is odd to search for a whole quoted paragraph plus, verbatim. in Google.
For your specific case I wonder if canonical should be the parent blog at least for all the comments that render on parent blog.
I also wonder about adding an option to redirect crawlers to the correct page vs canonical.
For a 100% embedded case you want the search to always hit the parent blog except for super rare cases
The actual search in this case is a bit bizarre so I am not cnfortable basing an entire philosophy on a sample size of one.
I saw this bug on another forum and wanted an example to showcase, hence the search by a paragraph.
Please don’t change the current functionality to a blogpost canonical. Here’s the reason:
https://meta.discourse.org/t/how-can-i-get-google-to-index-all-responses-and-comments-as-new-url-endpoints-or-pages/?source_topic_id=61443