Customer only pages sessions being indexed, Magento 2.x

[winterk80]

Preconditions (*)

All Magento 2.2.x versions

Steps to reproduce (*)

1. Customer only pages such as the login page, cart, etc are set to index by Magento. This is a concern that session data is indexed for both SEO and security reasons. Also creates a larger server load from bots following sessions.
2. What happens in sessions are captured by google resulting in thousands of indexed pages that are customer sessions in their index. Example, this url is allowed to be indexed: customer/account/login/referer/aHa0cHM6Ly93d3cuaG9tZXdldGJhci5jb20vc2t1bGwtb2YtZG9vbS1iZWVyLXN0ZWluLXAtMjg4Mi5odG1s/
3. The reason it is allowed to be indexed is because Magento universally applies the to all pages, even pages that are customer only pages such as the cart and login pages that should not be indexed.
4. Magento incorrectly attempts to remedy this by allowing the cart and login to be blocked in robots.txt. However since the meta tag on the page directly conflicts this, Google is ignoring the robots.txt
5. Google states this is expected behavior when the meta tag and robots conflict. Magento must fix the meta tag to resolve the issue. More details from Google here: https://support.google.com/webmasters/answer/7440203#indexed_though_blocked_by_robots_txt
6. Solution is for Magento to allow a separate noindex meta tag for customer only pages as follows

Expected result (*)

1. Customer login, cart pages (and any other customer only pages) should have a separate meta applied to them, than the meta tag for rest of the site. That meta for customer only pages should be

Actual result (*)

1. Customer only pages are coded to display the same tag as the rest of the site:
2. This causes customer sessions to be indexed. Leading to thousands of duplicate pages, one for each session. This is a concern that session date is indexed for both SEO and security reasons. Also creates a larger server load from bots following sessions.

[magento-engcom-team]

Hi @winterk80. 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-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@winterk80 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[orlangur]

@winterk80 oh, great finding! Probably it was tied somehow to cacheable/non-cacheable pages.

[magento-engcom-team]

Hi @engcom-backlog-nazar. 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[magento-engcom-team]

@engcom-backlog-nazar Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96300, MAGETWO-96301 were created

[epiblue]

Is there any temporal fix for this? Untill it will be added to official version?