Sitemap in robots.txt not store specific

[medialoungeml]

Preconditions (*)

1. Magento CE 2.3.3
   Magento 2.4 and 2.3.5-p1

Steps to reproduce (*)

1. Create Second Web Site, Store and Store View
2. Go to Stores -> Configuration -> General -> Web
3. Set "Add Store Code to Urls" = "Yes" -> Save
4. Go to Stores -> Configuration -> Catalog -> XML Sitemap
5. Expand "Generation Settings" section
6. Set "Enabled" = "Yes"
7. Expand "Search Engine Submission Settings" section
8. Set "Enable Submission to Robots.txt" = "Yes" -> Save
9. Run php bin/magento cron:run and php bin/magento c:f
10. Go to Marketing -> Site Map
11. Create 2 Site Maps (one for Default site and another one for second with different "Filename"
    
12. Save & Generate
13. Run php bin/magento cron:run and php bin/magento c:f
14. Go to store view and open Default store (http://youredomain.local/robots.txt)
15. Then in new tab open Second store (http://youredomain.local/de/robots.txt)

Expected result (*)

Site Maps should be different (because of different Filename)
The Sitemap: property should be retrieved within the context of the store

Actual result (*)

Site Maps are the same

Proposed Solution

The Sitemap value is retrieved in Magento\Sitemap\Block\Robots::_toHtml() and within this function the \Magento\Store\Model\StoreManagerInterface::getDefaultStoreView() is called to get the list of store ids to generate the sitemap for, this results in the value for the default store only ever being returned.
Here is comment with posible fix the issue

Note In Content -> Design -> Configuration you can configure the file settings robots.txt

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [ X ] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @medialoungeml. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[alex-james]

For anyone who encounters this issue, the workaround I have used is here: https://github.com/cogensoft-uk/magento-siite-specific-sitemap/tree/master/Cogensoft/Sitemap

[m2-assistant]

Hi @engcom-Lima. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

❌ Something went wrong. Cannot update Jira issue (https://jira.corp.magento.com/browse/MC-35674).

[magento-engcom-team]

✅ Confirmed by @engcom-Lima
Thank you for verifying the issue. Based on the provided information internal tickets MC-35674 were created

Issue Available: @engcom-Lima, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.