Do not duplicate SEO meta data when duplicating a product

[Zyles]

Description (*)

When you duplicate a product in the database a new product is created with the SEO data being the same.

99.9999999999999999999999999999999% of the time when you duplicate a product you do it because you want to use the same attributes for the next product, since it is usually a similar product.

What you do not want (usually) when duplicating is the same product name, the same SKU, and possibility not the same description or the same URL key as the previous product.

What happens is after you duplicate the product the SEO data stays the same. And unless you click down the hidden header you may forget to update that information, and your new duplicated product will have the same SEO meta data as your old product.

This adds extra useless work to empty this data every time you duplicate a product.

Expected behavior (*)

A better solution would be to empty that data on duplication and save the new information on save.

Fields to be emptied/not duplicated:

• URL key
• Meta title
• Meta keywords
• Meta description

Benefits

1. Less work.
2. Less problems.
3. Less duplicate meta tags.
4. Better user experience.
5. Better SEO experience.
6. Better SEO rankings.

Additional information

When you duplicate a product in the database a new product is created with the SEO data being the same.

If you disagree, please state in what use case you want duplicate SEO content.

[m2-assistant]

Hi @Zyles. 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.

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

• yes
• no

---

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

[m2-assistant]

Hi @krishprakash. 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]

@krishprakash Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

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

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

[m2-assistant]

Hi @dasharath-wagento. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[m2-assistant]

Hi @dharmendra-wagento. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if you want to validate it one more time, please, go though the following instruction:

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

• 2. 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!

• 3. If the issue is not relevant or is not reproducible any more, feel free to close it.

---

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

[magento-engcom-team]

Hi @Zyles. Thank you for your report.
The issue has been fixed in #26659 by @dasharath-wagento in 2.4-develop branch
Related commit(s):

• 1f96b873283229aa6892444244475d9992c0d8f2
• 89b0a9d4edd2380672ee813d812fe8fbf715eb61
• 99383fcdef11a034118bb44b7f6f35ec3a8ae546
• 2d19477ebf398f066930ac413e6e4ebec6ce1830
• 5aea4acf70bbf52d5c6f4f2d76e5698f3d8b2fb8
• dbf39249c537519dd3d97fd116110c454847e736

The fix will be available with the upcoming 2.4.0 release.