Implement programmatic or settings changes that can be made to /plugins/ and /themes/

[mtobar]

Implement programmatic or settings changes that can be made to /plugins/ and /themes/ to allow for individual theme or plugin pages to conform to the SEO Standards. Examples of this format will be:

(1) /themes/

• Title - ? (For example, $Theme_Name, Free $Main_Theme_Category Theme - WordPress)
• H1 - ?
• Meta Description
• ? (of note, we can not do all of the standards, we must start with the most important)

(2) /plugins/

• Title - ? - $Plugin_Name, $Main_Plugin_Category Plugin - WordPress
• H1 - ?
• Meta Description
• ?

More information on this can be found here:
​https://docs.google.com/document/d/13YxtyPNIz8798EpZT-AXh1SW2QNLGm9PBhtDJo7O16o/edit?usp=sharing

[netweb]

See ​https://wordpress.slack.com/archives/C9GG77GRJ/p1522706611000049 in #council-ops in Slack

[obenland]

#3657 was marked as a duplicate.

[obenland]

Updated ​Download, ​Hosting, and ​Mobile in ​https://dotorg.trac.wordpress.org/changeset/14199.

[obenland]

In 7286:

Plugins: Update doc title and front page description

Also add Open Graph data for the front page.

See #3539.

[obenland]

@todd-inmotion The About pages were just rewritten a month ago, I assume the current H1 is good to stay? What should the title/descriptions look like for its subpages? NVM, they already have titles and descriptions :)

[obenland]

In 7287:

WPorg: Update document title separator.

See #3539.

[obenland]

In 7288:

Support: Update site titles and add description.

See #3539.

[obenland]

In 7290:

Showcase: Update site titles and add description.

See #3539.

[obenland]

In 7298:

Main: Update About page title & desc

See #3539.

[obenland]

In 7299:

Themes: Update document title structure.

Also adds Open Graph tags and meta descriptions.

See #3539.

[coffee2code]

I'm really not a fan of having most of the details of this request being separately presented in an access-by-permission document.

What is left to be done?

And what's the justification for what was already done? For instance, related commits here changed the title separator from a dash (—) to a vertical bar (|), though this had already been explicitly discussed and the dash was chosen and used--and the vertical bar rejected as an option--back in #1105.

[obenland]

I'm really not a fan of having most of the details of this request being separately presented in an access-by-permission document.

Agreed, when this ticket was opened it was public, I don't know why it's not anymore. It wasn't my favorite way of conveying these details either.

What is left to be done?

Probably not much. Since the document is not public anymore I assume the ticket can be closed.

And what's the justification for what was already done?

It was pretty much a mandate from the Growth Council at the time. ​I asked for community feedback for some of the changes , but the title separator did not seem to be part of it.

[coffee2code]

Since the document is no longer public and there have been no follow-up inquiries, I'm closing this as fixed.

The recent and ongoing SEO effort covers the same sort of scope.