Replacing a site map

[NeilTompkins]

We are in the process of changing our folder/url structure.  Currently we have about 5 sitemaps submitted to Google.

How is it best to deal with these site maps in terms of either (a) replacing the old URLs with the new ones in the site map and (b) what affect should we have if we removed the site map submission from the Google Webmaster Tools console.

Basically we have in the region of 20,000 urls to redirect to the new format, and to update in the site map.

[RyanKent]

A sitemap should be a link representation of your site. It should contain a link to every page you wish to be included in Google's index.

How is it best to deal with these site maps in terms of either (a) replacing the old URLs with the new ones in the site map

Just make the switch. If a page no longer exists on your site, remove the link. If you create a new page on your site, add the link.

what affect should we have if we removed the site map submission from the Google Webmaster Tools console

For the most part, none. During the next crawl Google would look for your sitemap at your root address: www.mydomain.com/sitemap.xml. Google will also check your robots.txt file for a path to your sitemap file. If a sitemap is not located, it will crawl your site normally.

The primary purpose of a sitemap is to allow Google to become aware about new pages on your site it otherwise might not find. If your site offers solid navigation, a site map is not necessary at all.

[THB]

Big question: are you changing folder/url structure for aesthetics or functionality?  Often times it's not worth making such a large change in hopes of getting some SEO-friendly URL's, as the weight on SEO-friendly URL's isn't what it once was.  And the headache involved, as well as the inevitable loss in traffic, is quite often not worth it at all.

With that said, refresh your entire sitemap with the new URL's once they are made.  Remove all old urls.

IMPORTANT: setup 301 redirects, either using .htaccess or PHP (or whatever language your site uses), to redirect all old urls to the respective new urls.  You will lose a fair chunk of PR during this change, but if you feel your site will benefit greatly from a structure change, then you will be willing to take the hit.

Don't leave any redirect un-turned.  Then, you'll just have to wait it out while Google re-indexes your entire site trying to figure out your new url structure.  Could take a week, could take months.  All depends on what Google has valued your site as.  For example, if CNN changed their entire URL structure, they probably would miss a beat.  Smaller websites tend to take much larger hits in the SERP's.

So, just be sure it's a necessary action, trust me.  And don't ever remove those 301's from your .htaccess as you never know what Google still has in their index for your site.

[NeilTompkins]

We are changing our site structure for two main reasons

1. Ease of functionality, and having the ability to target friendly URLs suitable for SEO

2. Plus we've a new CMS, that allows this custom written URLs

The current structure has too many folders that are too deep, and is becoming too un-manageable.  The new CMS gives us totally control from one control panel.

I understand that we will loose some PR, but below it will be for the better of the site and user experience.

[NeilTompkins]

We are changing our site structure for two main reasons

1. Ease of functionality, and having the ability to target friendly URLs suitable for SEO

2. Plus we've a new CMS, that allows this custom written URLs

The current structure has too many folders that are too deep, and is becoming too un-manageable.  The new CMS gives us totally control from one control panel.

I understand that we will loose some PR, but believe it will be for the better of the site and user experience.

[NeilTompkins]

Perfect thanks. Just one final question, since the site has over 10,000 pages we need to make sure all redirects etc are set-up before we go live with the new URLs ?

What is the best way to go forward with regards launching the site ?

Should we launch the new pages and then go through the URLs redirecting them ?

Thoughts please ??

[RyanKent]

since the site has over 10,000 pages we need to make sure all redirects etc are set-up before we go live with the new URLs ?

Whether your site has 10 pages or a million pages you should ensure all internal links work without the need for redirection. Any old external links should be redirected to the correct page on your site if one exists. Otherwise you can allow the URL to 404 if there is not a current equivalent page.

Set up your site's 404 page so users are offered a basic "page not found" message along with your site's navigation and a search function. You should set up a log to track which URLs are generating 404 errors.

Prior to launching the site run a crawl diagnostic to help ensure nothing has been missed.

[NeilTompkins]

Another thought might be to place a noindex on the new pages to start with and as we migrate and 301 redirect the old to the new remove the noindex on the new pages ?

Thoughts ??

[RyanKent]

Another thought might be to place a noindex on the new pages to start with and as we migrate and 301 redirect the old to the new remove the noindex on the new pages ?

That can work but it's not an approach i would use. It seems like a lot of extra work, you run the risk of forgetting to remove the noindex tag on some pages, and also you may wind up not having pages properly indexed for a month.

If you publish a page today, Google may crawl the new page and see the noindex tag. You can then remove the noindex tag but Google may not recrawl the page for some time leaving your site without an indexed page.

As part of the process of publishing the page, I would 301 the old URL to the new URL immediately.