add to <head>: <link rel="canonical" href="lbry://[channel_ID]/[content_ID]"> #5
Comments
|
Umm do not get it. |
|
Currently rel="canonical" tag points to web content (presumably, it changes based on instance config?). LBRY content is not web content. It is LBRY content. It is not natively hyper-text transport protocol (http://) but is, rather, lbry (lbry://) protocol. The canonical link type tells bots and browsers what is the primary-source of the content. It is also pretty important for things like the AndroidOS "intents" system that allows some link types to be opened in their specialty apps rather than the browser. |
|
madiator.com is web based frontend and it's not using directly P2P protocol. |
|
Right. It is a web-based front-end, and not the authoritative content source. Therefore, it should reference and point to the authoritative content source. |
Is your feature request related to a problem? Please describe.
Is it a problem? Hmm.... no.
Describe the solution you'd like
I want search-engine bots to know that this is not web-first content.
Additional context
Screenshot of Firefox browser developer tools output of a madiator .com content page. Note there is not a rel="canonical" reference. (Also note that the CSS declarations could maybe be cleaned up into a single call to a single CSS file?)
The text was updated successfully, but these errors were encountered: