= Plone Google Sitemaps = [[PageOutline]] [[Image(quintagroup.plonegooglesitemaps-160-120.jpg, nolink)]] '''Plone Google Sitemaps (quintagroup.plonegooglesitemaps''', former '''qPloneGoogleSitemaps)''' is a Plone product developed by Quintagroup that allows you to enable different kinds of Google Sitemaps on your Plone website. Such Sitemaps help Google to identify site URLs and the data under each site section. With Google Sitemaps enabled, search engines could track the URLs faster and more efficiently, optimizing their search by placing all the information on one page. More about [wiki:qPloneGoogleSitemaps/why Why create Sitemaps for Google]. == Links == * Home page - http://quintagroup.com/services/plone-development/products/google-sitemaps * Repository - http://svn.quintagroup.com/products/quintagroup.plonegooglesitemaps/ * Releases - http://plone.org/products/qplonegooglesitemaps/releases * Watch [http://quintagroup.com/cms/screencasts/qplonegooglesitemaps Plone Google Sitemaps Screencast] to learn how to install and configure sitemaps on your Plone instance, how to let Google know about your sitemaps. == Introduction == Plone Google Sitemaps allows you to make your Plone site Google Sitemaps enabled. You can enable the following sitemap types on your website: * '''content sitemap''' - is a list of the pages on your website. Creating and submitting a Sitemap helps make sure that Google knows about all the pages on your site, including URLs that may not be discoverable by Google's normal crawling process. * '''mobile sitemap''' - is a specific type of Sitemap, that indexes all site URLs that serve content for mobile devices. By submitting such Sitemap into Google mobile index, you expand the coverage of the mobile web and speed up the discovery and addition of pages to Google mobile index. * '''[wiki:qPloneGoogleSitemaps/news-sitemap news sitemap]''' - is different from regular Sitemaps, it is specific to Google News only. It uses the Sitemap protocol, with additional News-specific tags, defined by Google. The package brings additional Google Sitempas tab to News Item content type for defining !NewsSitemap-specific meta tags. Different Sitemap types index their content and are independent from each other. Google Sitemap looks approximately this way: [[Image(content-sitemap.png, nolink)]] == Installation == See [wiki:qPloneGoogleSitemaps/install Instatallation instructions] for different product versions. == Migration == See [wiki:qPloneGoogleSitemaps/migration migration instructions] for migrating from previous quintagroup.plonegooglesitemaps package version to the new one; and from Products.qPloneGoogleSitemaps to quintagroup.plonegooglesitemaps. == Configuration == Here is description of the [wiki:qPloneGoogleSitemaps/config Google Sitemap Configuration] area (can be reached after successful Plone Google Sitemaps installation at Add-ons Configuraion -> Google Sitemaps). == Usage == === Step 1 - Create Sitemap === Add Sitemap(s) at Google Sitemap ''[http://projects.quintagroup.com/products/wiki/qPloneGoogleSitemaps/config#Settingstab Settings]'' tab (Add-on Products Configuration -> Google Sitemaps). You can add any of the Sitemap types: content, mobile or news. [[Image(add-sitemap.png, nolink)]] Define what content should be added to the sitemap by setting necessary parameters on [http://projects.quintagroup.com/products/wiki/qPloneGoogleSitemaps/config#Editsitemap Sitemap Edit Form]. === Step 2 - Verify your Site ownership in Google Webmaster tools === * Sign into [http://www.google.com/webmasters/sitemaps/ Google Sitemaps] with your [http://www.google.com/accounts/ManageAccount/ Google Account] * Add your Plone site to your Google account, e.g. ''!http://www.plone-site.com'' [[Image(add-site.png, nolink)]] * Verify your ownership by carrying out one of the suggested verification methods: uploading an HTML file with a name they specify, or adding a META tag to your site's index file. We recommend you to choose '''Upload an HTML file''' method as it is the most convenient and not so time-consuming as the second one. [[Image(verify.png, nolink)]] * Download the verification file * Go to your Plone '''Site Setup''' -> '''Add-on Product Configuration''' -> '''Google Sitemaps''' * Select the '''Verification''' tab * Upload the verification file in the field provided [[Image(upload-file-plone4.jpeg, nolink)]] * Go back to Google's site verification page and press "Check Status" * Google will verify that the file exists in the specified location. If it does, it'll show a status of VERIFIED and provide a link to your site statistics. You can view your statistics at any time after your site is verified by clicking the site link on the My Sites page. If Google can't access the file, it'll give you information about the error it encountered. Once this problem is resolved, try to verify your site again. === Step 3 - Let Google know about your Sitemap === After verification is completed: * Navigate to '''Site Configuration -> Sitemaps''' [[Image(submit-sitemap.png, nolink)]] * Click the '''Submit a Sitemap''' button * Type the URL to your Sitemap location in the provided field. Make sure you include the entire URL, such as ''!http://www.plone-site.com/google-sitemaps'' * Click '''Submit Sitemap"'''. * After you added a Sitemap, its status is displayed as '''Pending'''. Once Google processes your Sitemap (which may take several hours), this status will change to either OK or to an error. If you receive an error, click on it to view additional information. == FAQs == === 1 === ''Question:'' Why the generated sitemap.xml displays URLs with the IP address like this: ''999.999.999.999:8080/myplonesite'' instead of the URL ''www.plonesite.com''? ''Answer:'' quintagroup.plonegooglesitemaps uses 'canonical_url' catalog metadata field while building the sitemap.xml. You might get wrong values cataloged when creating sitemap through internal URL. To fix this - login to your Plone site via your site's real URL (''www.plonesite.com'') and update portal_catalog to fix the cataloged values. Also, to fix the above-mentioned issue - insert the following line into '''URL processing Regular Expressions''' on a sitemap edit form: {{{ s/[you_site\/internal\/path]/[domain]/ }}} where ''[you_site\/internal\/path]'' - is URL via which you edit your site, and ''[domain]'' - is site production URL. For example, for our site ''http://quintagroup.com'' we use ''!http://www.quinta.qg:8080/www/www URL'', so, to configure right sitemap URLs we insert: {{{ s/www.quinta.qg:8080\/www\/www/quintagroup.com/ }}}