Hi Fabrizio,

If you put 50 in the 'bounce rate greater than box' instead of 0.5 then the table shown below the graph shows the data you want (only bounce rates over 50%, I think that is what you are after right?). I guess the graph cannot be show this filtered data although you can click the 'select a metric' link next to the visits dropdown on the top/left of the graph and add bounce rate to see the average bounce rate by visits/day if that helps with getting a baseline.

HI,

It is checking to see if the visiting user agent contains any of these strings (NC is telling it non case sensitive) and if it does to return a 403 forbidden message.

I dont use something like this myself. I suppose if you are having some problem with bots it might be useful, maybe someone else can chime in if they have some experience with this kind of blocking.

Hi Andrea,

This looks like a drupal issue, not a cpanel issue and I am not that familiar with Drupal.

That being said, are you sure the above htaccess is the complete file that works? If you remove the lines that you say create the issue, you still have this line: RewriteRule ^(.*)$ index.php?q=$1 [L,QSA] which is the one that handles rewriting urls to the form q=admin.

You could try moving the 2 lines of code: 
RewriteCond %{HTTP_HOST} ^www.domain.com$
RewriteRule ^(.*)$ "http://domain.com/$1" [R=301,L]

To immediately below the  'RewriteEngine on' line (and obviously putting your domain in place of domain.com) so that they run first before the rest of the rules. This might work, but to me the above looks like it will be rewriting to q=admin anyway, so maybe this is a drupal setup issue that I am unfamiliar with.

Hi Gal,

Yes as far as i remember this is the process. You do not need to be uploading 10 NEW listings to request the bulk verification feature, you just need to have more than 10 locations in total. The bulk verification happens at the account level, not on an individual location level - if that makes sense.

HI,

This is a good example of when to use the canonical tag. Set it up for the main landing page without any url variables and you should be good to go. Google will know which version of the page to concentrate value on and also which version of the page to index and show in the search results. It is crucial actually, I saw a case once where the url with a partner id in it got indexed and was being shown in the search results.... you can imagine what effect that had on proper tracking when half the organic visits were clicking on a url with a partner id in it!!

Hi Micheal,

I suspect the mobile site might be responsible for the indexed urls issue. Your mobile site has loads of indexed pages with the shorter urls: https://www.google.com/#output=search&sclient=psy-ab&q=site:m.eventective.com&oq=site:m.eventective.com&fp=9861fb8dc6b3e7c

Before the 301 redirects on the mobile site were created, were the rel canonical links pointing to the truncated urls on the main site? Seems to be the case on this random page I grabbed:

view-source:http://webcache.googleusercontent.com/search?q=cache:2AwUe7jXqvMJ:m.eventective.com/Canada/Ontario/Ottawa/569913/

So a kind of odd mixture of 301s on the main site, and a well indexed mobile site saying the rel canonical on the main site is the shorter url. Seems maybe the rel canonical won! Are you sure this is a recent issue? Maybe it has been like this for a while and just not noticed much?

I would think that with the 301s and rel canonicals now properly implemented on the mobile site then the index will slowly sort itself out. I suppose you could put a rel canonical on the main site page also referencing itself, might speed up the process a bit more.

Agree with Jesse that it is not likely a major worry and wouldn't think this alone would cause a ranking issue.

Hi Steve,

htaccess can be tricky! That link above is a good overview of the options. What you want in your case I think is to make sure that the specific individual page url rewrites are before the generic domain rewrite so they are triggered first and the generic redirect is only triggered if none of the individual page urls above it are hit.