Hi,

At first glance it seems you have a rel canonical issue. All of your blog posts have a rel canonical pointing to: <link <span class="webkit-html-attribute-name">rel="canonical" href="http://www.hilden.co.uk/bed-linen.html" /></link <span>

Probably not what you had in mind!

Hi,

It i probably google deciding to rewrite the titles for you, Yoast himself makes a mention of it here: http://yoast.com/google-page-title/ In short, not much you can do about it.

Hi

This should do it, you place the robots.txt in the root directory of your site.

User-agent: * Disallow: /product-category/

You can check out some more examples here: http://www.seomoz.org/learn-seo/robotstxt

As for the multiple urls linking to the same pages, you will just need to check all possible variants and make sure you have them covered in the robots.txt file.

Google webmaster tools has a page where you can use to check if the robots.txt file is doing what you expect it to do (under Health -> Blocked Urls).

It might be easier to block the pages with a meta tag as described in the link above if you are running a plugin allowing this, that should take care of all the different url structures also.

Hope that helps!

Hey Dan,

Its a bit confusing and has been for a while! See: https://moz.com/community/q/uk-and-gb-when-selecting-targeted-engines-in-campaign-management. Results should be the same between them anyway but Moz is saying that GB is the mistake and is due to be phased out.

Hi,

This happens quite often if redirects are not implemented with adwords in mind. You can either ask your developers to tweak the redirect code so that url parameters are passed on during the redirect or alternatively change the relevant adwords urls to go directly to the redirected url which will bypass the redirect completely and should preserve the gclid parameters. Depends a bit on how temporary or permanent the redirect is (you say you are using a 302 temporary redirect currently but this would normally be a 301 if the change is permanent).

Hi,

The new(ish) business.facebook.com is pretty much the MCC equivalent. It can be a bit difficult to figure out in the beginning but it is a lot better than the situation you describe! Check out the official faq page here.

Hi Bridget,

There is no alt attribute in css, so no you cannot add it there,

There are a couple of things you can do.

1. Optimizing your image file names will at least give an indication of what the image is about and

2. Rethink your css and the use of background images. Specifically you could get the same effect as you have now without background images using a combination of absolutely and relatively positioned divs. This way you can have the same layout as now but with the image in the html rather than the css and alt tags will be available for them.

Check the link here for some demo code: http://stackoverflow.com/questions/8708945/how-to-position-text-over-an-image-in-css

Hope that helps!

Hi,

I believe the limit on local listings per account is 100, not 10 (see here), so you will be ok for a while yet. Since you are not eligible for bulk upload/verification the only option at the moment is to input your local listings individually as usual and verify them individually also. You can then add new locations as they become available and once you are over the 10 locations limit you can initiate the bulk verification request following the instructions here.  There is no disadvantage in this process, you don't 'lose' anything starting out with less than 10 locations and then moving above that number and bulk verifying so nothing to worry about!

Hi Tim,

Did you ever get to the bottom of the issue mentioned in this question? It is almost certainly the same problem.

Have a look at this page and try either turning of the sh404SEF anti flooding feature or else boosting the max number of requests allowed. http://forum.joomla.org/viewtopic.php?p=1368937

The anti flooding part of this component is basically blocking requests for pages if it thinks someone is trying to do a dos attack on your site. The current setup seems to be too sensitive and is bloocking screaming frog after the first few requests, quite possibly blocking the google bots, maybe blocking the moz crawler also, so certainly something you should address.