SEO and Calendar Pro

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
6/28/2012 3:28:02 AM
Gravatar
Total Posts 167

SEO and Calendar Pro

I've just run the search optimization tool in IIS manager against one of my sites that uses Calendar (pro) and it has returned 1000's of violations.

Mainly this is due to <h1>, description and multiple canocical formats in each of the calendar pages. Is there anyway of reducing these?

i.e :

can I add a header to calendar that will apply to every day/week/month

Can the description be set to apply to every day, week, month

each calendar page (in day view)  seams to share the same canonical format as the next day - The page with URL "http://www.smartcowmarketing.com/Events/DayView.aspx?pageid=7&mid=6&date=2012-06-14T00:00:00" can also be accessed by using URL "http://www.smartcowmarketing.com/Events/DayView.aspx?pageid=7&mid=6&date=2012-06-15T00:00:00".

I don't know if these issues apply to the normal calendar or just pro. Could partly the issue be due to adding a repeating event and then removing it?

Any suggestions?

6/29/2012 11:49:36 AM
Gravatar
Total Posts 18439

Re: SEO and Calendar Pro

I will do some testing on my local machine with the IIS SEO toolkit and try to resolve some of these for the next release of Event Calendar Pro.

Probably some of the solution is going to involve adding noindex/follow meta tags on some of the view pages like week view and day view  so that search engines won't try to index them.

The reason these things give violations is because they appear to have the same content on different urls anf this is what causes the canonical warnings. For example the content on day view and week view is identical for every empty day or empty week. Since these views really just provide links to the details they have no seo value for them to be indexed, really you only want the detail views indexed.

You definitely do not want multiple pages to have the same meta description (that would produce more warnings) and don't really need meta descriptions at all on the pages that don't need to be indexed such as week view and dayview and monthview. Only the detail pages need descriptions and the main page where ECP is loaded you can put meta description in page settings. On the event details you can already add meta descriptions but they should be unique for each event.

Best,

Joe

7/3/2012 6:27:45 AM
Gravatar
Total Posts 167

Re: SEO and Calendar Pro

Cheers,

So Can I update the robots.txt file now or will this require to wait for an update.

Would adding the following to Robots.txt work

Disallow: /Events/

and how would I get this to work in sub sites within an installation (is there something in the web or Robots config that can allow each subsite have its own Robot.txt)

 

7/3/2012 10:07:08 AM
Gravatar
Total Posts 18439

Re: SEO and Calendar Pro

You could do that since the detail pages use friendly urls.

robots.txt will only be read from the root of the web site. If its multiple sites based on host name they will all work the same. If its folder based child sites you could update the robots.txt file in the root for each site like

Disallow: /foldername/Events/

Keep in mind that if you are customizing robots.txt you need to be careful during upgrades because we ship a robots.txt file that would overwrite your custom one. So you would want to remove ours from the package before upgrading.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.