Only use the canonical / permanent URL #184

Closed
opened 2017-10-03 22:23:50 +02:00 by kauffj · 2 comments
kauffj commented 2017-10-03 22:23:50 +02:00 (Migrated from github.com)

For SEO purposes, each discrete piece of content should only have a single canonical URL. Currently, in spee.ch, a piece of content can exist on up to 4 URLs:

  • /file
  • /claim/file
  • /channel/file
  • /channel:claim/file

All 4 of these pages should include a <link rel="canonical"> tag to a single URL. That URL should be the one described by lbryio/lbry#958

More on these tags here: https://en.wikipedia.org/wiki/Canonical_link_element

Additionally, we ought to consider if an outright redirect (or JS based updating of the location bar) so that users are encouraged to use one URL over another. In particular, if content is published via a channel, we probably want to encourage users to use channel based URLs.

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
For SEO purposes, each discrete piece of content should only have a single canonical URL. Currently, in spee.ch, a piece of content can exist on up to 4 URLs: - /file - /claim/file - /channel/file - /channel:claim/file All 4 of these pages should include a `<link rel="canonical">` tag to a single URL. That URL should be the one described by lbryio/lbry#958 More on these tags here: https://en.wikipedia.org/wiki/Canonical_link_element Additionally, we ought to consider if an outright redirect (or JS based updating of the location bar) so that users are encouraged to use one URL over another. In particular, if content is published via a channel, we probably want to encourage users to use channel based URLs. ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed
kauffj commented 2018-08-06 15:26:29 +02:00 (Migrated from github.com)

The URLs described by lbryio/lbry#958 are the only URLs that the app should directly send a user to and are the URLs that should be shown in all embed/share codes.

Additional URLs can resolve, but should include the canonical URL tag.

The URLs described by lbryio/lbry#958 are the _only_ URLs that the app should directly send a user to and are the URLs that should be shown in all embed/share codes. Additional URLs can resolve, but should include the canonical URL tag.
daovist commented 2018-11-05 20:39:06 +01:00 (Migrated from github.com)

Most of this is done and live on spee.ch. Publishes are not yet using this feature. That will be part of the update-abandon PR upon which this ticket will be closed.

Most of this is done and live on spee.ch. Publishes are not yet using this feature. That will be part of the update-abandon PR upon which this ticket will be closed.
This discussion has been locked. Commenting is limited to contributors.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/spee.ch#184
No description provided.