Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a marketer, I'd like each bounty URL to have a canonical URL included, so that our SEO is improved and we are not penalized for duplicate content on bounties. #4503

Closed
danlipert opened this issue May 28, 2019 · 7 comments · Fixed by #4579
Labels

Comments

@danlipert
Copy link
Contributor

User Story

As a marketer, I'd like each bounty URL to have a canonical URL included, so that our SEO is improved and we are not penalized for duplicate content on bounties.

Why Is this Needed

Currently, each version of each bounty gets a unique URL - often 3 or 4 versions per bounty. Search engines will penalize us for the duplicate content, but adding a canonical URL to each version that points at the latest version will remove this penalty.

Description

Type: Feature

Current Behavior

No Canonical URL

Expected Behavior

Added canonical URL that points to the latest version.

Definition of Done

The template for bounty details is updated to contain a valid canonical URL pointing at the current version of the bounty detail page.

Data Requirements

This should increase organic search traffic

@gitcoinbot
Copy link
Member

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


This issue now has a funding of 0.3 ETH (78.28 USD @ $260.92/ETH) attached to it.

@gitcoinbot
Copy link
Member

gitcoinbot commented May 31, 2019

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 11 months, 2 weeks from now.
Please review their action plans below:

1) drslowpokephd has applied to start work (Funders only: approve worker | reject worker).

In order to fix this problem, I will create an additional link that is continuously searching for a link that matches a certain unique id/keywords related to the bounty itself. That link will then point to the most recent of those links collected.
2) tommycox has been approved to start work.

I'll essentially follow this (https://www.dev2qa.com/how-to-create-canonical-url-in-django/) to add a canonical URL to the bounty details template.
3) codeblcks has applied to start work (Funders only: approve worker | reject worker).

Make the required changes in HTML and Python code for adding a canonical URL.

Learn more on the Gitcoin Issue Details page.

@proofoftom
Copy link
Contributor

Quick update, will be able to tackle this today!

@gitcoinbot
Copy link
Member

@TommyCox Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • reminder (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@proofoftom
Copy link
Contributor

Ready for review

@gitcoinbot
Copy link
Member

Navigator ⚡️ A *Navigator* Kudos has been sent to @TommyCox for this issue from @danlipert. ⚡️

The sender had the following public comments:

Great job Tommy - appreciate the thoroughness!

Nice work @TommyCox!
Your Kudos has automatically been sent in the ETH address we have on file.

@gitcoinbot
Copy link
Member

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


The funding of 0.3 ETH (80.14 USD @ $267.12/ETH) attached to this issue has been approved & issued to @TommyCox.

danlipert pushed a commit that referenced this issue Jun 18, 2019
* Add canonical URL to Bounty Details template

* Add test for canonical_url property

* Use absolute path for canonical URL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants