4

I suggest installing the Views Data Export module. It will allow you to create XML pages from your taxonomy and as many as you want. I would create one view and 4 page displays with the varying filters to generate your pages. Then change the output to XML. I looked over the XML Sitemap, and the error you are experiencing seems to be something they are ...


4

This could either happen because it's node/add/article is included within a menu that's indexed by XML Sitemap or a custom path that was added. In either case, a drush command can update the path flag for exclusion & rebuild the sitemap so that it's no longer there. drush sqlq "UPDATE xmlsitemap SET status = 0 WHERE loc = 'node/add/article'" drush ...


3

The base function you call is xmlsitemap_link_save. I am unaware of any docs on how to use this, but nodes get added to the sitemap via xmlsitemap_node_nodeapi which in turn calls xmlsitemap_node_create_link. The code for that should provide some guidance on how to build $link.


3

Some more troubleshooting ideas: Do the spaces only appear on the RSS page, or also on other pages? That could tell you whether the problem is in a central place or a template/include-file that is only loaded for the RSS feed. You can use var_dump(get_included_files()) (ideally in the template, just before the XML is generated) to see a list of all PHP ...


3

There is a setting in the XMLSitemap admin configuration that lets you set the base domain. Update that value, clear cache, and regenerate the sitemap.


2

You can do the same with xmlsitemap modules Enable XML sitemap node, XML sitemap taxonomy submodules. After that you will get these options.


2

If you are using Drupal 7, it will show that your sitemaps have been submitted in your log messages at Admin > Reports > Recent Log Messages (/admin/reports/dblog) Click on "Filter log messages" and select "xmlsitemap" If you do this, it will show when the last sitemap was generated and when it was submitted the the search engines that you have configured ...


2

There doesn't seem to be hook anymore to return links for further processing, but adding and deleting links is done with calls to xmlsitemap_link_save and xmlsitemap_link_delete(_multiple) I implemented a hook_xmlsitemap_index_links, which normally is only called when the command drush xmlsitemap-index is issued: function my_xmlsitemap_index_links($limit) ...


2

For news there's the Google News sitemap module The Google News module generates a Google news compatible sitemap feed from your Drupal site's content. I don't think there are existing modules for images/video (I've looked for the same thing before myself and ended up hacking something together). There's a feature request in the XMLSitemap module's ...


2

Please visit the feature request about "Remove duplicate links when using both menu and node sitemap". It has a patch which works fine.


2

There is no harm in adding both by menu and by content type (I have tested this before). In my experience, paths will not be duplicated. If you also add by content type, then that priority will be used, even if it is lower than the one you have set for the menu. Also, the last modification date will be used; it doesn't get used when you add by menu. The ...


2

You'll need to bootstrap the Drupal environment in your PHP script to do this. There are many ways to do this, probably the easiest is Drush's php-script command: drush php-script my_custom_script.php This will let you execute any arbitrary PHP script in a bootstrapped Drupal environment. Once you have your script running your Drupal environment, you can ...


2

Yes, that's normal behaviour. xmlsitemap_menu() includes a route for /sitemap.xml specifically.


1

There are 2 aspects: SEO - if one node is always seen under one address, or you properly set canonical, it's no problem. HTML structure - you need to make sure there are no duplicated IDs on links when you output them twice, as it can sometimes mess Drupal's (and contrib) javascript operating on links. And of course it prevents your site from validating ...


1

Drupal 6 Option 1: Enable the 6.x-2.x XML sitemap custom sub-module. Manually add the links to your views at admin/settings/xmlsitemap/custom Option 2: Enable the 6.x-2.x XML sitemap menu sub-module. Create a new menu at admin/build/menu/add with the menu name xmlsitemap and title XML sitemap. Make sure that the 'Include this menu in the sitemap.' ...


1

My basic apprach for 7.x-2.x is (assume the module is called mymodule_xmlsitemap). /** * Implements hook_cron(). */ function mymodule_xmlsitemap_cron() { mymodule_xmlsitemap_xmlsitemap_index_links(xmlsitemap_var('batch_limit')); } /** * Implements hook_xmlsitemap_index_links(). */ function mymodule_xmlsitemap_xmlsitemap_index_links($limit) { ...


1

Is there a way I can assign uniform frequency to all my content pages? or edit individual page frequencies? Not through the UI as far as I know, but it's possible in code using hook_xmlsitemap_link_alter(): function MYMODULE_xmlsitemap_link_alter(&$link) { if ($link['type'] == 'node' && $link['subtype'] == 'article') { $link['changefreq']...


1

There's now the module to do that: XML Sitemap per node type The XML Sitemap Per Node Type module provides the additional context for XML sitemap module that allows creating sitemaps per content type.


1

For Taxonomy terms you can use Disable Term Node Listings module (https://www.drupal.org/project/disable_term_node_listings) There is also a great write up on drupal.org about similar issues: https://www.drupal.org/node/345620 In short use robots.txt to disallow paths like ones you specified above. This will prevent google from indexing those pages in ...


1

No, or at least not, with XML Sitemap & Views module. There is no Views integration with the XML Sitemap module. Given how both these modules work (a view being defined by base table & XML sitemap trying to generate a list of all indexable site paths), I think you'd be better off looking for another solution to embed all your site paths into the site....


1

If you don't mind a programmatic approach, then follow these steps: Ensure that XML Sitemap module is installed & enabled Create/use a custom module (say, MYMODULE) & use the following hook: function MYMODULE_xmlsitemap_element_alter(&$element, $link, $sitemap) { // Some logic to generate datetime // or hardcoded value $element['...


1

There is an XML Sitemap Custom submodule in the XML Sitemap module You can use this to set Page Views' paths for inclusion in the XML Sitemap You might also check this module out: https://www.drupal.org/project/xmlsitemap_aliases From the project page: "Anything with a path in the aliases table can now be included in your XMLsitemap by the click of a ...


1

Did you define base_url in settings.php file? Try to set your current website address for base_url, then clear cache and run cron to generate sitemap. If this doesn't work, backup your database and run SQL query as: UPDATE variable SET value='s:99:"http://example.com";' WHERE name='xmlsitemap_base_url'; Where the 99 is the length of your domain (including ...


1

Excluding the node manually, isn't really the long term solution. The actual problem resides with the module. There is currently a patch that claims to handle this issue and that's the best place to start. See this: https://www.drupal.org/node/2266933


1

I think you have a setting wrong. Browse to the XML Sitemap settings page (admin/config/search/xmlsitemap/settings). Expand the Advanced Settings section. Check/set the Default Base URL. Typically, I set this to make sure the default base URL gets used, as rebuilding from drush won't set it properly if you don't $uri set in your site alias.


1

Your D7 may not remain unchanged forever. When it change, you will want its sitemap to change in concert with the site. In other words, you need something like XML Sitemap on your site. You should therefore install the XML Sitemap module (as you suggest yourself). The module actually has an upgrade path if you used the D6 version of the module to generate ...


1

To make sure you have the content types that you want in your sitemap, you can enable xmlsitemap_node. After enabling, visit each content types configuration page and select "Include" under the xmlsitemap tab. After setting each content type, you can check the Included/Excluded status for all content types under the xmlsitemap module config page. Once ...


1

When using i18n xml sitemap, and when you have a menu set to be included in a sitemap (using xmlsitemap menu), even if that menu is set to display only for one language (localized to Japanese or English in my case using i18n_menu), it will still get added to the sitemap for both languages. So, in this case, one solution is to avoid using xmlsitemap_menu and ...


1

You can separate you sitemap.xml into several sitemaps. Each of this maps will be a smaller than one big sitemap. Go to admin/config/search/xmlsitemap/settings, in Advanced settings in Number of links in each sitemap page choose, for example, 1000 and regenerate you sitemap.


Only top voted, non community-wiki answers of a minimum length are eligible