58 | | '''Regular Expression''' |
59 | | Please, master regular expression in Perl syntax |
| 61 | * '''Define the types''' Select meta types to be explored. Choose the content types in the field “Define the types” they want to be displayed in their Sitemap. (As a rule, Document is set as the default content type for the Plone Google Sitemap. However, it would be much better for the Google to see some other content types in your Plone Google Sitemap, like Folder or !FormMailer). |
| 62 | * '''Review status''' The objects with the given state will be displayed. Select the state of the objects to be visible in the Sitemap. |
| 63 | * '''Blackout entries''' The objects with the given Short Names will be removed from the Sitemap. Make some objects invisible in the Sitemap by entering their Short Names. |
| 64 | * '''URL processing Regular Expression''' Please, master regular expression in Perl syntax. |
| 65 | * '''Additional URLs''' Add URLs that are not objects to enable the desired objects to be shown even though their content type was not chosen in the field “Meta Types to dig” |
64 | | |
65 | | === “Settings” functinality === |
66 | | Due to the tab '''“Settings”''' in ''Plone Google Sitemap configuration'' users can manage their Sitemap. They can do the following: |
67 | | * choose the content types in the field '''“Meta Types to dig”''' they want to be displayed in their Sitemap. (As a rule, '''Page''' is set as the default content type of the Plone Google Sitemap. However, it would be much better for the Google to see some other content types in your Plone Google Sitemap, like '''Folder''' or '''FormMailer'''.) |
68 | | * select the state of the objects to be visible in the Sitemap (using the field '''“State”''') |
69 | | * make some objects invisible in the Sitemap by entering their Short Names in the field '''“Blackout Entries”''' |
70 | | * c(by entering their Short Names in the field '''“Additional URLs”''') |
71 | | == “Settings” Note: == |
72 | | It is essential to avoid the situation when there are two objects with the same content in the Sitemap, e.g. a folder and its default page. Various methods can be applied in such cases. One can either forbid ids of these objects by entering them in the field '''“Blackout entries”''' or make sure the default pages are not published unlike folders. |
73 | | |
74 | | |
75 | | == The tab '''“Pinging”''' in Plone Google Sitemap configuration == |
76 | | By pressing '''"Ping Google"''' button you inform Google that it should reread your sitemap as you did some modification on the site. Google usually rereads your sitemap with it's own schedule but you have possibility to hint it about best time to do that. |
77 | | Below this button you have five workflow lists, which give you the opportunity to let Google know about the changes in your Plone site workflow. |
78 | | |
79 | | http://quintagroup.com/services/plone-development/products/google-sitemaps/images/ploneworkflow.png |
80 | | |
81 | | http://quintagroup.com/services/plone-development/products/google-sitemaps/images/folder.png |
82 | | |
83 | | |
84 | | |
| 69 | It is essential to avoid the situation when there are two objects with the same content in the Sitemap, e.g. a folder and its default page. Various methods can be applied in such cases. One can either forbid ids of these objects by entering them in the field “Blackout entries” or make sure the default pages are not published unlike folders. |