If you search "venn digital" then the correct meta description is pulled through, but if you search "venndigital" then it pulls through our twitter feed from the bottom of the page.

My only suggestion is that it is doing it because there is no mention of " Venn Digital" in the body of the copy, so it is going to the twitter feed at the bottom of the page where Venn Digital is mentioned to pull this info through.

I've just taken a look at the optical express site, assuming this is the site you're referring to.

If if it was my client I'd remove the nofollows from the flags in the footer. I don't see any reason why you'd be penalised for linking together a set of multinational domains for a brand, and removing the nofollows will help the link juice flow around the sites.

I wouldn't nofollow these links personally, that isn't what the nofollow tag was designed for.

The nofollow tag would stop google from passing link juice through the links, but it wouldn't stop google actually following the links and figuring out the sites are connected.

If you want users to see you have international sites (which makes complete sense), include the links. But, why not make them more prominent with a country selection page similar to ikea.com or apple.com? Don't be afraid of linking together a legitimate network of sites that sit under a single brand.

Hi Amod,

There are my thoughts:

1. Yes, of course Google we re-index the page. With or without 'good linking', next time it crawls the page (and it'll do that regardless of any new link building activity) it will see the tag has changed and include it in the index again.

2. No, it will be aware of the age of the page.

3. No, Google has already indexed all of the links pointing to your site. It won't suddenly forget that just because you added a noindex to your page. They're 2 seperate entities.

4. The rankings will come back, but it will take time. I've read blog posts about this in the past, perhaps someone else here could give an estimate? I'd imagine it depends on the strength of the page.

Thanks,

Matt

That works perfectly, thank you very much

Thanks for the response Alan.

However, the problem is with the old URL's, so where they have a trailing slash I cannot get them to redirect to any URL's of the new structure (with a trailing slash or otherwise.).

To simplify the ask, how do I put in place a 301 redirect from 'http://www.example.com/example_folder/' to some other URL?

I'm having real trouble with getting working redirects in place to use on a site we're re-launching with a modified url structure.

Old URL: http://www.example.com/example_folder/

New URL: http://www.example.com/example-of-new-folder/

Now, where the old URL's have a trailing slash the web.config simply will not accept it. It says the URL can start with a slash, but not end with a slash. However, many of my URL's do end with a slash so I need a workaround.

These are the rules I'm putting in place:

<location path="example_folder/"></location>

Thanks