TYPO3 Core

I doubt the usefulness of inheriting SEO-related fields.
Just so I understand:
Say you have a tree structure like this:

Home [Shortcut to first subpage]
  - About us
  - Contact

Now you want to add meta keywords and a description to Home and inherit that down onto both About us and Contact?

Mathias Schreiber wrote:

I doubt the usefulness of inheriting SEO-related fields.

I doubt the usefulness of SEO-related fields in general, but at least for keywords, this is what many sites are doing.
The keywords-example is taken from the typoscript reference:
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Meta/Index.html?highlight=keywords

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55805

Raphael Graf wrote:

Mathias Schreiber wrote:

I doubt the usefulness of inheriting SEO-related fields.

I doubt the usefulness of SEO-related fields in general, but at least for keywords, this is what many sites are doing.

That doesn't make it right however:

1. Keywords are pointless unless used for internal purposes
2. Descriptions must be unique for every single URL

So just like Mathias I don't see a use for this change.

The keywords-example is taken from the typoscript reference:
https://docs.typo3.org/typo3cms/TyposcriptReference/Setup/Meta/Index.html?highlight=keywords

Technically this example is correct, logically it's useless. ;-)

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55805

Mathias Brodala wrote:

1. Keywords are pointless unless used for internal purposes
2. Descriptions must be unique for every single URL

I don't know about a reason for multiple pages share the same description. But there may be use cases where a non-specific description is better than no description at all.
Keywords may be pointless for google & co but as you said they could be used to tag pages for whatever reason. ('internal purpose' is a reason, don't you think? ;-))

It will not hurt to have the fields available in the backend. It is easy to hide them by tsconfig anyway.

same as possible to hide those via tsconfig it is such easy to add those fields to shortcut doktype. therefore I am for rejecting this issue