#3940 closed enhancement (fixed)
https://wordpress.org/ homepage should include open graph + twitter tags
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | Priority: | low | |
| Component: | General | Keywords: | seo |
| Cc: |
Description
We should aim to best control how WordPress is represented when shared on social platforms. Without open graph tags, we're at the whim of how Facebook etc decide to parse and present our messaging.
This has lead to significant issues in the past where, e.g., an ill-fitting WordCamp promotional image has been sourced as the primary image to represent the page/product/brand.
Add the following tags to the <head>.
<meta property="og:type" content="website" /> <meta property="og:title" content="Blog Tool, Publishing Platform, and CMS - WordPress" /> <meta property="og:description" content="Open source software which you can use to easily create a beautiful website, blog, or app. " /> <meta property="og:url" content="https://wordpress.org/" /> <meta property="og:site_name" content="WordPress" /> <meta property="og:image" content="https://s.w.org/images/home/screen-themes.png" /> <meta name="twitter:card" content="summary_large_image" /> <meta name="twitter:creator" content="@WordPress" />
Note that, the description and image can (and probably should) be refined by the marketing team - but this shouldn't hold up deployment.
Change History (6)
#2
@
6 years ago
What domains and paths is this intended to cover? I'm assuming only wordpress.org/?
Can you also provide an updated list of what we should have on rosetta domains? ie. https://de.wordpress.org/
$ curl -s https://de.wordpress.org/ | grep -e '\(twitter\|og\):' <meta property="og:type" content="website" /> <meta property="og:title" content="Deutsch" /> <meta property="og:description" content="WordPress auf Deutsch" /> <meta property="og:url" content="https://de.wordpress.org/" /> <meta property="og:site_name" content="Deutsch" /> <meta property="og:image" content="https://s.w.org/images/backgrounds/wordpress-bg-medblue.png" /> <meta property="og:locale" content="de_DE" /> <meta name="twitter:site" content="@WordPress" /> <meta name="twitter:text:title" content="Startseite" /> <meta name="twitter:card" content="summary" />
(I believe these may be added by a certain popular plugin, but we can change the data)
#3
@
6 years ago
The tags from the ticket have been added in [dotorg-14595]. Leaving open for refinement.
#4
@
6 years ago
Code was only intended for the wordpress.org homepage.
For Rosetta domain homepages, I would make some minor tweaks:
- Append
- CCto theog:site_name(e.g.,WordPress - DE). - Translate the English
og:descriptionandog:title(with some sensible compromises where necessary). - Set the URL to the appropriate homepage.
- Set the
og:localeas appropriate (eg., de_DE). - Alter the image to a translated/localised version, if available.
Note that JetPack appears to be active and outputting og tags on these sites, but that they're painfully wrong. We should disable/overwrite/correct those values on homepage of those sites.
For the sake of clarity, this is a quick fix, and a bit of a fudge. Ideally, we'd have a combination of default logic and specific controls to manage og tags and similar (including additional tags which I've not included here), on every single url on the site(s).
This is an mvp, quick win; not a complete or long-term solution.