Feature #90327
closedSitemap Generation on Root-Level with a Multilang Site (Seo Extension)
0%
Description
TYPO3 seo extension should feature the functionality to create a sitemap index file on root level.
Example configuration for a page with 2 languages:
https://www.mydomain.com/de/
https://www.mydomain.com/en/
Both have a sitemap:
https://www.mydomain.com/de/sitemap.xml or https://www.mydomain.com/de/?type=1533906435
https://www.mydomain.com/en/sitemap.xml or https://www.mydomain.com/en/?type=1533906435
rootPageId: 1 base: 'https://www.mydomain.com/' languages: - title: German enabled: true languageId: '0' base: /de/ typo3Language: de locale: de_DE.UTF-8 iso-639-1: de navigationTitle: Deutsch hreflang: de direction: ltr flag: de solr_core_read: '%env(SOLR_CORE_DE)%' - title: English enabled: true languageId: '1' base: /en/ typo3Language: default locale: en_GB.UTF-8 iso-639-1: en navigationTitle: English hreflang: en direction: ltr fallbackType: strict fallbacks: '' flag: gb solr_core_read: '%env(SOLR_CORE_EN)%' errorHandling: - errorCode: '404' errorHandler: Page errorContentSource: 't3://page?uid=20' routes: { } routeEnhancers: PageTypeSuffix: type: PageType default: / suffix: / index: / map: /: 0 sitemap.xml: 1533906435
What i cant do:
https://www.mydomain.com/sitemap.xml or https://www.mydomain.com/?type=1533906435
Call this page (because there is no configuration for /) and get a sitemap index file containing the path to both language sitemaps. Why cant i configure this? Because the path is for languages only. And i have configurated my languages already on /de/ and /en/.
Whats the problem:
Google Indexer will look at domain/sitemap.xml to improve page indexing.
Google Indexer will loot at robots.txt if there are any rows with "Sitemap: path/to/sitemap.xml" definitions
- Generate a robots.txt by typoscript to tell google where to find the sitemaps = faild to same reasons
- Let my default language listen to / and the english version on /en/, but then the index sitemap would only contain sitemaps in default language.
Versions:
TYPO3: 9.5.13
Am i missing something, or is this a needed feature to maintain the current and future sitemap pool for all domain/language combinations without static htaccess redirects?
Updated by Nico Poggenburg almost 5 years ago
- Tags changed from Sitemap Seo to Sitemap, Seo, TYPO3 9, Multilanguage
Updated by Richard Haeser almost 4 years ago
- Status changed from New to Rejected
First of all, I do advice you to submit your XML sitemap(s) in Google Search Console. That way, you also have a bit more control and you can see what is going on with the pages in the sitemap as well. By submitting your sitemaps directly to Google, you don't have to be afraid anymore Google can't find your sitemaps. Same for Bing Webmaster Tools.
If you want to create robots.txt files, you can create a staticText route (TYPO3 v10) for the robots.txt and add you content there. Please know that it is not needed to have those files if you have already submitted your sitemaps to Google Search Console or Bing Webmaster Tools.
Nevertheless, we are checking if we want to have a multi-language sitemap file, but that is only if you have translations of your pages and not separate roots. Most of the time those are really different websites and therefor should have their own sitemap.