What is the best way to deal with an event calendar

[categorycode]

I have an event calendar that has multiple repeating items into the future. They are classes that typically all have the same titles but will occasionally have different information. I don't know what is the best way to deal with them and am open to suggestions.

Currently Moz anayltics is showing multiple errors (duplicate page titles, descriptions and overly dynamic urls). I'm assuming that it's showing duplicate elements way into the future.

I thought of having the calendar no followed at all but the content for the classes seems valuable.

Thanks,

[FedeEinhorn]

Are the same classes in the future link to the same page? are you using canonical tags correctly? Your URL should help diagnose the problem and guide you better,

[Martijn_Scheijbeler]

Besides this, take a look at the schema markup for Events it might help you mark up the page better so Google will understand what the page/ event is about: http://schema.org/Event

[BlueprintMarketing]

is this the all-in-one event calendar for WordPress?

If so I can give you the information or you can just Google CPU Max WordPress

essentially you have to change the robots.txt file so the crawlers don't have huge issues as they do now with it.

Get flywheel has that built into their robots.txt file if that is your issue I can go in and grab it for you.

Sincerely,

Thomas

[evolvingSEO]

Hi Landon

I had a client with a similar situation. Here's what I feel is the best goal;

Calendar pages (weeks/months/days etc) - don't crawl, don't index

Specific event pages - crawl and index

Most likely the calendar URLs have not been indexed, but you can check with some site: searches. Assuming the have not been indexed, the best solution was to block crawling to certain URLs with robots.txt - calendars can go off into infinity, and you don't want to send the crawlers off into a black hole as it's not good for crawl budget, or for directing them to your actual content.

[BlueprintMarketing]

I got the robots.txt file I hope this will help you.

This is built into every GetFlywheel.com website they are a managed WordPress only hosting company

website the reason they did this was the same reason Dan as described above.

I'm not saying this is a perfect fix however after speaking with the founder of GetFlywheel I know they place this in the robots.txt file for every website that they host in order to try get rid of the crawling issue.

This is an exact copy of any default robots.txt file from getflywheel.com

Default Flywheel robots file

User-agent: *
Disallow: /wp-admin/
Disallow: /wp-includes/

Disallow: /calendar/action:posterboard/
Disallow: /calendar/action:agenda/
Disallow: /calendar/action:oneday/
Disallow: /calendar/action:month/
Disallow: /calendar/action:week/
Disallow: /calendar/action:map/

As found on a brand-new website. If you Google "Max CPU All in one calendar" you will see more about this issue.

I hope this is of help to you,

Thomas

PS

here is what

The maker of the all in one event calendar has listed on their site as a fix

http://support.time.ly/limiting-excessive-google-crawls/

[BlueprintMarketing]

A great completely and this is a good example of the type of difference changing the robots.txt file could make

I would read all the information you can on it as it seems to be constantly updating.

I used this info below as an example of a happy ending but to see the problems I would read all the stories you will see if you check out this link.

_http://wordpress.org/support/topic/max-cpu-usage/page/2_

CPU usage from over 90% to less than 15%. Memory usage dropped by almost half, from 1.95 GB to 1.1 GB including cache/buffers.

My setup is as follows:

Linode 2GB VPS
Nginx 1.41
Percona SQL Server using XtraDB
PHP-FPM 5.4 with APC caching db requests and opcode via W3 Total Cache
Wordpress 3.52
All in One Event Calendar 1.11

All the Best,

Thomas

[BlueprintMarketing]

Sorry for all the posts however maybe this will help you as well that get rid of the dynamic uRLs

http://www.webconfs.com/url-rewriting-tool.php

Thomas