Mobile app version of vmapp.org
Login or Join
Cugini213

: Canonical URL to refer to other page, although it is not exactly duplicate content? We are hosting recurring events, and when you search in Google for that event, you always get an ealier installment

@Cugini213

Posted in: #DuplicateContent #RelCanonical #Seo

We are hosting recurring events, and when you search in Google for that event, you always get an ealier installment of it that tops the list. This is of course obvious, as every time the new event starts from scratch, collecting media attention. Eventually it will top the list.

As these events are mostly the same each year, would it be a solution to add a canonical URL to the new event? And if so, do we run the risk to trigger some Google penalty as the events are not duplicate content strictly speaking?

301 redirects are not really an option because we need these pages accessible in our archives.

10.02% popularity Vote Up Vote Down


Login to follow query

More posts by @Cugini213

2 Comments

Sorted by latest first Latest Oldest Best

 

@Mendez628

I guess the solution to your page is not rel=canonical because even when this might acomplish you goal, this may confuse Googlebot and result on lower ranking of the entire site based on the vague idea of "I don't understand this page" (plus, Google treats rel=canonical as a signal, not an order). In your case, I would add two things (both) to your HTML (adding only one -any of them- should solve the problem, but the more info we give to Google, the better they understand the site and this is better for us):


Schema Event Markup:


This was not created to solve your problem, but it could. Also it may makes your event appears in the Google Knowledge Graph. Please, note the endDate part.

<script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "Event",
"name": "Miami Heat at Philadelphia 76ers - Game 3 (Home Game 1)",
"location": {
"@type": "Place",
"address": {
"@type": "PostalAddress",
"addressLocality": "Philadelphia",
"addressRegion": "PA"
},
"url": "wells-fargo-center.html"
},
"offers": {
"@type": "AggregateOffer",
"lowPrice": "",
"offerCount": "1938"
},
"startDate": "2016-04-21T20:00",
"endDate": "2016-04-21T21:30", // This is the part yyou are looking for
"url": "nba-miami-philidelphia-game3.html"
}
</script>



"Unavailabe After" Meta Tag:


If you are shy about Schema Markup, is too hard for you or you want to give the more information to Google to ensure the result, there is a Meta Tag created exactly for what you are looking for:

<META NAME=”GOOGLEBOT” CONTENT=”unavailable_after: 23-Jul-2016 18:00:00 EST”>

10% popularity Vote Up Vote Down


 

@BetL925

Treating recurrent events is indeed not so easy. To avoid duplicate content issues, the best option is to use the same page each year (same URL), especially if the content is very similar. For this, think about not to use the date in the URL.

With this solution, you can take benefits of the old page SEO and you'll be sure to rank first the new event in the search engines. From my opinion, it is a pity to lose all the SEO work of the events each year but if you don't care about it, you can put the rel="canonical" tag on the old event page with the reference of the new event page URL (not the opposite!). Not sure the old event page will disappear from search engines but you're safe regarding duplicate content issues.

If you want to keep the old event page available for your users, think about change the URL and not to index it in the search engines anymore (by using the no-index meta tag and add the URL in your robots.txt for instance).

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme