None of those fields are anything to do with SEO

None of those fields are anything to do with SEO

Metadata comes under seo

You should look at how the data is used. None of those fields are used for seo

@brianteeman

so, according to you this should be in separate section because of meta description part?

See discussion #15833

@Quy I have read the discussion but not seeing any end-up of discussion , some people says it's good , some not, if you all are ok with this then I will create pr for every component, otherwise I will close this, Thanks :)

I don't see the point of moving just 3 fields to its own tab especially if they are not updated often.
What is your rationale to justify its own tab?
Why not do a text override to "Publishing/SEO" in your installation?

I don't see the point of moving just 3 fields to its own tab especially if they are not updated often. What is your rationale to justify its own tab? Why not do a text override to "Publishing/SEO" in your installation?

For example if I will have to add the meta description or keywords so first thing which comes in mind that there will be an separate SEO section where I can find the all functionality for SEO, how will I know that it will come under publishing

It may not be obvious at first, but once you know where these settings are under Publishing then I don't see the issue. Create a language override if you need a reminder.

This pull requests has been automatically converted to the PSR-12 coding standard.

This pull request has been automatically rebased to 5.0-dev.

I have tested this item ✅ successfully on 1e8b03b

Thank you for the PR. Closing for now for reason stated. When there are additional SEO settings added, we will revisit this.