Google Site Map Generator
Google Sitemaps are the single best way for ensuring your website is being properly and fully indexed by Google. Clever Technology has been playing with the Mura plugin architecture for quite a while now, and our first release is something that has already proven popular: automating Google Sitemap creation in Mura CMS.
To install the Google Sitemaps (GSM) plugin you'll need a version of Sava/Mura Mura CMS that supports plugins. If you don't find the "Installed Plugins" page mentioned below, you'll have to do it the old fashioned way or update your Mura install.
To install the plugin:
download the plugin (ctGoogleSitemaps_v1.zip) file
(Note: you don't need to unzip the file; this is the format Mura CMS Plugins come in).
login to Mura CMS
click on Site Settings (top-right on yellow bar)
click on the Installed Plugins tab
click on Browse and choose the ctGoogleSitemaps.zip file.
click on Deploy
The plugin is now installed. The configuration page will let you choose default settings for the way the GSM plugin deals with individual pages & portals. The most important setting is the one at the bottom: make sure you check off every site you want to have a sitemap for.
The actual sitemap.xml file is located in the root Mura web directory for each site. Remember that for your sitemap.xml file to serve any purpose, it must be registered. See Google's Webmaster/Site owner tools for details on how to do this.
You can configure the sitemap settings for a particular page or portal's Change Frequency and Priority under Site Manager » (page) » Extended Attributes » Google Site Maps. For more information regarding these settings, I recommend you visit Google's Sitemaps information page.
Inheritance and include/exclude settings are also found on the Extended Attributes page.
Depending upon how you configured your GSM plugin, all pages/portals are either included or excluded in your sitemap.xml file by default. If you chose to not include all pages and/or portals by default, then you have to include them manually. The reverse is also true if you chose to include all pages by default (in this case, you would have to manually exclude them). Inheritance can also be set, in which case the page will follow up the chain of "parent" pages until it finds an "include me" or "exclude me" setting.
Sitemaps are generated according to the settings you chose when installing/configuring the GSM plugin (Update Frequency).
For Daily/Weekly/Monthly updates, only loading this page will refresh the sitemap.xml file more frequently.
If you choose Every Update as your update frequency, the entire sitemap is regenerated every time you publish or delete a page or portal. This can be task intensive for large websites, so it is not recommended in those cases. Besides, you can force an update any time by clicking on one of the above buttons.
When you add a new site to Mura, you must update your GSM plugin to include it. The list of sites that the GSM plugin will be available to is found at the bottom of the plugin's configuration page.
This plugin should be compatible for both earlier versions of Sava when plugins were first added, as well as the latest versions of Mura CMS. This being said, we obviously haven't tested every version of Sava and Mura that's been released, so the safest bet is to update to the lastest version of Mura CMS.
Please contact the developer for support.
- July 15, 2009, 2:00 PM
- Michael Dinowitz said:
While registering a sitemap with Google is a good idea, it is not required as long as it is 'announced'. This is done by putting a reference to the sitemap in the robots.txt.
- July 21, 2009, 12:14 PM
- Richard Nugen said:
This is a great plug in! Solved a huge management issue for me.
- October 21, 2009, 3:42 PM
- Phillip Molaro said:
I have installed this plugin. It generates the sitemap.xml file in the site directory (my case the "default" directory as I made that my actual site.). When I go to Plugins -> Google Site Maps (GSM) Plugin and click on the "the sitemap" link the url is correct but the file isn't found. If I move the file to the wwwroot folder, then you instruction page finds it. However, the "Update All" script just regenerates the XML file back in the default directory. So if the link on the instruction page broken, or is the file generated in the wrong place? (seems like the link is broken). Bare in mind that like many others, we have set up our site to hide the "/default/" directory in the SES URLs.
- October 21, 2009, 3:50 PM
- Phillip Molaro said:
Found the issue. I needed to enter "/default" in the "Package (Base of Install Directory)" during the setup (or by editing the plugin config). Hope this helps others.
- October 23, 2009, 10:22 AM
- Hugo Ahlenius said:
One minor bug that triggered my OpenBD installation - cfc/ctGoogleSiteMapBean.cfc - on line 19, the cfset is not closed properly (an extra space).
But - I have more problems - I can't seem to view the extended attributes properly - when I try I see the Google Sitemaps attributes repeated three times, and then "default" times three on the bottom.
- November 30, 2009, 3:04 AM
- Hugo Ahlenius said:
I can just add to my last comment - it seems to work fine now!
- June 14, 2010, 8:03 PM
- Tim said:
The "frequency" doesn't seem to work for me. Even though I have everything set to weekly. The XML file shows monthly. It's really great though.