Title: Document Titles for Repo Plugins Author: Konstantin Obenland Published: June 13, 2018 --- [ ](https://profiles.wordpress.org/obenland/) [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 9:06 am _on_ June 13, 2018 Tags: 3539-meta    # Document Titles for Repo Plugins The Growth Council has submitted [its proposed updates to document titles and meta descriptions](https://docs.google.com/spreadsheets/d/1zX8rCs0lOFasfPgh_sS8DtlReoJczT3asD8oaNYGfVM/edit#gid=394908865) across the WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) network. As part of the update for the PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. Directory, they suggested adding the first two tags of each plugin to the document title: ```notranslate $Plugin_Name, $Tag_Name Plugin | WordPress.org ``` Example: ```notranslate Obenland Media, Gallery Plugin | WordPress.org ``` Before going ahead with that change I wanted to bring it up for discussion here, given the risk of abuse here. How do we weigh the benefit of ease of discoverability on search engines with that risk of abuse? What are your thoughts? Progress on this is tracked in [#3539-meta](https://meta.trac.wordpress.org/ticket/3539). [#3539-meta](https://make.wordpress.org/plugins/tag/3539-meta/) ### Share this: * [ Threads ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=threads) * [ Mastodon ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=bluesky) * [ X ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=x) * [ Facebook ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/plugins/2018/06/13/document-titles-for-repo-plugins/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/3949929f32e0e66f74b59774f3b20e987602c1ead2ff7bd49565702b1e6f0043? s=32&d=mm&r=g) 2. [Ad Inserter](https://profiles.wordpress.org/spacetime/) 9:10 am _on_ June 13, 2018 3. What does `$Tag_Name` mean? 4. * ![](https://secure.gravatar.com/avatar/43e10bdac0c553eccd6b30644312cc245d1d4df3cb04dbc898f44cae8d7d68cf? s=32&d=mm&r=g) * [Konstantin Obenland](https://profiles.wordpress.org/obenland/) 9:13 am _on_ June 13, 2018 * In my example `Gallery` is the name of the tag. So it would be the name of the first (two) tag that are specified in `readme.txt`. 5. ![](https://secure.gravatar.com/avatar/8cf7655071f82970f9635a0c7e7646551756c333b57166083e506a72cad98916? s=32&d=mm&r=g) 6. [David Anderson](https://profiles.wordpress.org/davidanderson/) 9:19 am _on_ June 13, 2018 7. This seems unlikely to work well as a general rule. For lots of plugins, the tag duplicates something in the title. 8. So, picking out of my head the first seven popular plugins I could think of ( all over a million active installs), here are their titles followed by tags: 9. * Contact Form 7: first two tags: contact, form 10. * Yoast SEO: first tag: SEO 11. * JetPack by WordPress.ComWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. [https://wordpress.com/](https://wordpress.com/): first tag: jetpack 12. * UpdraftPlus WordPress Backup PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. : first tag: backup 13. * All in One SEO Pack: SEO, all in one SEO 14. * WooCommerce: ecommerce, e-commerce 15. * Google XML Sitemaps: seo, google 16. It would appear, then, that the proposal basically amounts to doubling up words that are already in the title. 17. ![](https://secure.gravatar.com/avatar/1b8dc77ecf0638ffa4405990f13eee857003536f5e0361fd89a6866aca551ee3? s=32&d=mm&r=g) 18. [Nextendweb](https://profiles.wordpress.org/nextendweb/) 9:32 am _on_ June 13, 2018 19. As an example: [https://plugins.svn.wordpress.org/contact-form-7/trunk/readme.txt](https://plugins.svn.wordpress.org/contact-form-7/trunk/readme.txt) 20. Result with first two tags: Contact Form 7, Contact, Form pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. | WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) Contact Form 7, Contact plugin, Form plugin | WordPress.org 21. [https://plugins.svn.wordpress.org/woocommerce/trunk/readme.txt](https://plugins.svn.wordpress.org/woocommerce/trunk/readme.txt) 22. WooCommerce, Commerce, E-commerce plugin | WordPress.org WooCommerce, commerce plugin, e-commerce plugin | WordPress.org [Google screenshot](https://i.imgur.com/XDj4Cd9.png) 23. Well, I think that as the plugin title in readme.txt affects the page title, there is no reason to add the tags too. 24. Pingback: [gyanpoint | Document Titles for Repo Plugins ⋆ gyanpoint](http://gyanpoint.com/document-titles-for-repo-plugins/) 25. ![](https://secure.gravatar.com/avatar/dbae128ad04471b8a3939757e1b438d262c9cf0e6f90b08a02f31bd29831f872? s=32&d=mm&r=g) 26. [LittleBizzy](https://profiles.wordpress.org/littlebizzy/) 9:39 am _on_ June 13, 2018 27. WIth respect, this is a bad idea. Taking into account the SERP title limits on search engines like Google, much of these keywords would be cut off anyway, as most WordPress pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. titles are already several words long. 28. Keyword stuffing plugin titles would look spammy, and provide little to no benefit to search engine results or end users. 29. A much more useful addition to the WP.org directory would be adding a new headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. called MultisiteMultisite Multisite is a WordPress feature which allows users to create a network of sites on a single WordPress installation. Available since WordPress version 3.0, Multisite is a continuation of WPMU or WordPress Multiuser project. WordPress MultiUser project was discontinued and its features were included into WordPress core. [Advanced Administration Handbook -> Create A Network.](https://developer.wordpress.org/advanced-administration/multisite/create-network/) Support (to complement Requires PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. [https://www.php.net/manual/en/index.php](https://www.php.net/manual/en/index.php)): 30. [https://core.trac.wordpress.org/ticket/44198](https://core.trac.wordpress.org/ticket/44198) 31. ![](https://secure.gravatar.com/avatar/e1a850bca164e3d29c1d8ae8117fa4b341ed150ea4d8ab29a285726c944c453b? s=32&d=mm&r=g) 32. [Marius L. J.](https://profiles.wordpress.org/clorith/) 9:40 am _on_ June 13, 2018 33. I’d say this is a bad idea so long as tags aren’t curated there’s a myriad of tags and you will end up with (as [@nextendweb](https://profiles.wordpress.org/nextendweb/) mentions) sillyness that serves no purpose beyond making the page titles less readable, and look more like what you get when searching up a site that’s been affected by malware (where they do stuff tags into the titles like this). 34. ![](https://secure.gravatar.com/avatar/fe1541ecaf52e528bd94cbb9a112fccddd6c8a1b72a9d4f53277b58298088e75? s=32&d=mm&r=g) 35. [Rene Hermenau](https://profiles.wordpress.org/renehermi/) 9:49 am _on_ June 13, 2018 36. What happens when tags are changed afterwards in the readme.txt. Does that mean that the title of the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. page is going to be changed again? This will lead to a terrible abuse potential. 37. From a SEO a perspective I think it should be prevented (to give the user the capability) to change the page title. This could affect the overall rankings negatively at all. 38. Before this is going definately online please let all plugin developers know in advance so that everyone has a chance to check if the two first tags in the readme.txt are good and does not contain any rudimental data and perfectly suited data. 39. On the other hand if you really need to add the tag into the title why not use the first tag of the tag cloud? See: [http://take.ms/Oja0P](http://take.ms/Oja0P) 40. Its manually added by a WordPress plugin editor and makes abuse impossible. 41. All in all, I don’t like the idea. I could imagine that it will terrible affect a lot of the wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) overall visibility on google serps. 42. Before you go that route please consult someone who knows more about it like [@yoast](https://profiles.wordpress.org/yoast/) 43. ![](https://secure.gravatar.com/avatar/656bc955ff095f76699b2144615fdf0282b990f3033d2275b8a27713eece6fff? s=32&d=mm&r=g) 44. [Yani Iliev](https://profiles.wordpress.org/yaniiliev/) 10:01 am _on_ June 13, 2018 45. What is “**Growth Council**“? I cannot find much information about its members 46. * ![](https://secure.gravatar.com/avatar/656bc955ff095f76699b2144615fdf0282b990f3033d2275b8a27713eece6fff? s=32&d=mm&r=g) * [Yani Iliev](https://profiles.wordpress.org/yaniiliev/) 10:03 am _on_ June 13, 2018 * Also, can you describe the benefits such change is going to have? 47. ![](https://secure.gravatar.com/avatar/ea8b05a71fdd554f4d9b8d4ae4633f11f347dc99b64221166ee22c94d9bdb066? s=32&d=mm&r=g) 48. Anonymous User 10:10 am _on_ June 13, 2018 49. I don’t see a huge benefit to this, especially when considering the risks of a negative impact or abuse. 50. It’s already easy enough to add a meaningful title to the actual pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress. org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., e.g. “PluginName – Contact Form” rather than “PluginName”. For me personally, that’s all the control I need. 51. ![](https://secure.gravatar.com/avatar/250257111d1248c34046552bbcdf6999949ef56b2f992dd5eb39bf45cabeb18a? s=32&d=mm&r=g) 52. [Samuel Wood (Otto)](https://profiles.wordpress.org/otto42/) 12:23 pm _on_ June 13, 2018 53. Massively not okay with using Tags in the title. PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost- based plugin from a third-party. name, sure, okay. Tags: no. 54. ![](https://secure.gravatar.com/avatar/4c89dc1bb610b8fe3109a8f396f71c651bb779f7b0f7c3f2bc6d6f2cc3b41fb9? s=32&d=mm&r=g) 55. [Mahesh Waghmare](https://profiles.wordpress.org/mahesh901122/) 12:51 pm _on_ June 13, 2018 56. IMO, Tags are okay in the title. Because, We could not categorize the plugins. 57. So title should not be `Plugin_Name, Category_Name | WordPress.org` 58. Without tags in the title should be ok. Like `$Plugin_Name | WordPress.org` 59. But, For more descriptive page/htmlHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. titles `` tag We can use the tags in the title like` $Plugin_Name, $Tag1_Name, $Tag2_Name | WordPress.org` 60. ![](https://secure.gravatar.com/avatar/6ae5aac9c9f6b33d57fb70c593808445da3aefe9cc3a250641073a199810414c? s=32&d=mm&r=g) 61. [Paul Gilzow](https://profiles.wordpress.org/gilzow/) 1:05 pm _on_ June 13, 2018 62. What is their reasoning for adding `$Tag_Name` in the title? Is there a particular goal they are trying to accomplish by adding the tag to the title element? 63. Given that I can add any tag I want to my plugins, unless someone is going to be placed in charge of moderating tags moving forward, I don’t see how this won’t be heavily abused. 64. ![](https://secure.gravatar.com/avatar/e4ffab6e721cd0f026a47028900c31121a7257662b07c3788329418b6d1e58d4? s=32&d=mm&r=g) 65. [Gregory Karpinsky (@tivnet)](https://profiles.wordpress.org/tivnet/) 1:33 pm _on_ June 13, 2018 66. 1. Why is everyone talking about abuse? Stuffing keywords in the readme’s body is the same “abuse”. Normal people will put the right words to help Google find their plugins. 67. 2. In my opinion, it’s better to have a separate markup in the readme for the Title instead of building it from the name and tags. 68. 3. The trailing | WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) is just taking space. Does not add anything to Google, because it already knows that the page is on WordPress. 69. 4. There is also a METAMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. DESCRIPTION – what about it? If we do SEO, let’s do it properly. 70. * ![](https://secure.gravatar.com/avatar/6ae5aac9c9f6b33d57fb70c593808445da3aefe9cc3a250641073a199810414c? s=32&d=mm&r=g) * [Paul Gilzow](https://profiles.wordpress.org/gilzow/) 3:46 pm _on_ June 13, 2018 * > Why is everyone talking about abuse? * Because right now when you search for a pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. at your favorite search engine, the tags an author has applied to their plugin do not show up. By adding non- moderated tags to the title element of the page, those will now appear in the title displayed in search results. Page titles affect SEO, hence the concern for abuse. * ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175? s=32&d=mm&r=g) * [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/) 3:54 pm _on_ June 14, 2018 * > Stuffing keywords in the readme’s body is the same “abuse”. * It is and you can get yourself banned from hosting here for it. We regularly send out warnings to people, but it’s a by-hand effort so we miss a lot. * > Normal people will put the right words to help Google find their plugins. * Normal people are fine. Keyword stuffers are not, and we would rather not reward them. 71. ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) 72. [Joy](https://profiles.wordpress.org/joyously/) 3:42 pm _on_ June 13, 2018 73. I don’t think it would provide the “ease of discoverability” that they expect. I don’t see any benefit. I do see detriment. Just ask Yoast – it looks spammy and too long. 74. ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175? s=32&d=mm&r=g) 75. [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/) 4:11 pm _on_ June 13, 2018 76. I’m with Otto here, this is a terrible idea because there are _TWELVE TAGS_. And let’s be clear here, the majority of developers use tags BADLY. 77. You will make the title too long for any SERP benefit. 78. BETTER idea MIGHT be ‘$plugin_title $plugin_SHORT_descroption’ but even then, it strikes me as the same problem. The post title should be short. Like 60 characters short. 79. > If your title is too long, search engines may cut it off by adding an ellipsis(“…”) > and could end up omitting important words. While we generally recommend keeping > your titles under 60 characters long, the exact limit is a bit more complicated > and is based on a 600-pixel container. 80. I vote no 81. ![](https://secure.gravatar.com/avatar/6b6d1c4d29f1b149da0008917c70b019408d5af404a46bca853e4dd33546e1ed? s=32&d=mm&r=g) 82. [Joost de Valk](https://profiles.wordpress.org/joostdevalk/) 7:50 am _on_ June 14, 2018 83. Otto and Mika are clear, and I agree with them. 84. I do think we should improve the titles for plugins, because right now there is absolutely no difference between the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. pages and tag pages, for instance, this is the title for the tag page GDPR: 85. **GDPR | WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)** 86. and this is the title for the GDPR _plugin_: 87. **GDPR | WordPress.org** 88. If you can’t find the difference that’s because there isn’t one. 89. My proposal is that we make the title tag for the tag pages like: 90. **$tag_name plugins | Browse them on WordPress.org** 91. and for plugins: 92. **$plugin_name | WordPress plugin | WordPress.org** 93. On top of that, to improve the readability of all our titles, I’d suggest replacing the pipe ( | ) everywhere with a better separator. 94. * ![](https://secure.gravatar.com/avatar/e2f5cdfaa31c9d539c55861f832b36b07fbfbf98fbbf5075042d136331e81a42? s=32&d=mm&r=g) * [jonoaldersonwp](https://profiles.wordpress.org/jonoaldersonwp/) 10:11 am _on_ June 14, 2018 * Minor tweak. I’d suggest: `$plugin_name - WordPress plugin | WordPress.org` * Happy to change the hyphen to an arbitrary symbol, too – just need to avoid the use of two pipes to avoid confusion. - ![](https://secure.gravatar.com/avatar/3949929f32e0e66f74b59774f3b20e987602c1ead2ff7bd49565702b1e6f0043? s=32&d=mm&r=g) - [Ad Inserter](https://profiles.wordpress.org/spacetime/) 12:30 pm _on_ June 14, 2018 - > $plugin_name – WordPress pluginPlugin A plugin is a piece of software > containing a group of functions that can be added to a WordPress website. > They can extend functionality or add new features to your WordPress websites. > WordPress plugins are written in the PHP programming language and integrate > seamlessly with WordPress. These can be free in the WordPress.org Plugin > Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party. - I would prefer without ` | WordPress.org`: - ```notranslate $plugin_name - WordPress plugin ``` - ![](https://secure.gravatar.com/avatar/6ae5aac9c9f6b33d57fb70c593808445da3aefe9cc3a250641073a199810414c? s=32&d=mm&r=g) - [Paul Gilzow](https://profiles.wordpress.org/gilzow/) 2:13 pm _on_ June 14, 2018 - Excellent point, [@joostdevalk](https://profiles.wordpress.org/joostdevalk/) about the page vs pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.. And I’ll second [@jonoaldersonwp](https://profiles.wordpress.org/jonoaldersonwp/). If there’s a strong attachment to the pipe segmentation, then do we need the “WordPress” in “Wordpress Plugin” since we would have it in “WordPress. orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)”? - **GDPR | Plugin | WordPress.org** - vs - **GDPR | WordPress Plugin | WordPress.org** - If it’s at WordPress.org it’s going to be a _WordPress_ plugin. * ![](https://secure.gravatar.com/avatar/27180c82524020e7339e2b30818b6d8ab004c54f730f12b1434b1e365be0e175? s=32&d=mm&r=g) * [Ipstenu (Mika Epstein)](https://profiles.wordpress.org/ipstenu/) 3:52 pm _on_ June 14, 2018 * Wouldn’t having “WordPress PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.” _AND_ “WordPress.orgWordPress. org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)” be incredibly redundant? * What about …. * > List of $tag_name plugins | Browse them on WordPress.org * and * > $plugin_name| Plugin for WordPress.org - ![](https://secure.gravatar.com/avatar/6a97b9fdf799797b7e29604f11d3c6ba1da31e57f4fdb9f76dba09cb052770b1? s=32&d=mm&r=g) - [Joy](https://profiles.wordpress.org/joyously/) 11:40 pm _on_ June 27, 2018 - I prefer - > List: $tag_name plugins – WordPress.orgWordPress.org The community site > where WordPress code is created and shared by the users. This is where > you can download the source code for WordPress core, plugins and themes > as well as the central location for community conversations and organization. > [https://wordpress.org/](https://wordpress.org/) - and - > $plugin_name pluginPlugin A plugin is a piece of software containing > a group of functions that can be added to a WordPress website. They can > extend functionality or add new features to your WordPress websites. > WordPress plugins are written in the PHP programming language and integrate > seamlessly with WordPress. These can be free in the WordPress.org Plugin > Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party. – WordPress.org 95. ![](https://secure.gravatar.com/avatar/4a3351856434c5e326a8d7502a7fb24814ff084b0b74805d31f1ffe7baf54d01? s=32&d=mm&r=g) 96. [Daniel James](https://profiles.wordpress.org/danieltj/) 3:48 pm _on_ June 24, 2018 97. Big no from me. Most of the time the tags wouldn’t make sense anyway as others have already pointed out. As an example with the Dark Mode pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party., you’d have: 98. Dark Mode, Admin Dark Plugin | WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) 99. Where `admin` and `dark` are two separate tag names. It doesn’t make sense and would add a lot of ‘fluff’ to the title where it’s not needed. Plugins already rank fairly high in Google for plugins with sensible names. 100. ![](https://secure.gravatar.com/avatar/ad54fee87b0057de02d3b3f5af8638dd50aece094c8c5b3da65415df11c092df? s=32&d=mm&r=g) 101. [ilovewpcom](https://profiles.wordpress.org/ilovewpcom/) 2:12 pm _on_ July 7, 2018 102. Just automatically adding the “pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.” and “theme” words respectively should make so much more sense. 103. GDPR Plugin | WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) Telegraph Theme | WordPress.org Telegraph WordPress Theme | WordPress.org 104. With generic words it becomes pretty useful or you end up with pages like: Customization | WordPress.org Consulting | WordPress.org Podcast | WordPress.org 105. So my vote is for adding the logical identifiers for plugins and themes. 106. * ![](https://secure.gravatar.com/avatar/6e229b77c35eff460257711220922038ed5f8551600366c661745c5806865171? s=32&d=mm&r=g) * [LewisCowles](https://profiles.wordpress.org/lewiscowles/) 9:02 am _on_ July 9, 2018 * so much this, but also using micro-format and schema.org data to denote tags so that search engines can free-associate the tags with the plugins & themes without the overhead of mangling headers and titles. 107. ![](https://secure.gravatar.com/avatar/f35b9fb3b4afef01e3c3733a23e362a12a7122cbe6e78db2dc9af01336f55be8? s=32&d=mm&r=g) 108. [Dominik Schilling (ocean90)](https://profiles.wordpress.org/ocean90/) 4:02 pm _on_ July 11, 2018 109. > Just automatically adding the “pluginPlugin A plugin is a piece of software > containing a group of functions that can be added to a WordPress website. They > can extend functionality or add new features to your WordPress websites. WordPress > plugins are written in the PHP programming language and integrate seamlessly > with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) > or can be cost-based plugin from a third-party.” and “theme” words respectively 110. This doesn’t work well when thinking about translations. 111. My suggestion would be `$plugin_name| Plugins on WordPress.org`. And the same should be done for themes: `$theme_name | Themes on WordPress.org`. 112. ![](https://secure.gravatar.com/avatar/9a8fcdd6349cc4a6a946017bd9e0161a6f99b1b6e385d5076a59e074e80bab35? s=32&d=mm&r=g) 113. [todd-inmotion](https://profiles.wordpress.org/todd-inmotion/) 5:59 am _on_ July 16, 2018 114. Thanks for all the background information and sorry about the delay in adding into this thread with a bit more thoughts. First, just in case anyone is not familiar yet as to why myself or someone else might be stirring the pot here – traffic has been falling to wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/) in the last couple years and part of the fall is a drop in search traffic. So, my apologies for putting extra work out there and please feel free to guide me to do a better job here. 115. For plugins, to get the concepts going my initial thought was to be $Plugin_Name, $Main_Plugin_Category PluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party. | WordPress.org . The goal of bringing the $Main_Plugin_Category was to have a general phrase that Google and the visitor can see is related to their search without that being in the name of the plugin. As I learned, there is not any order or precedence to the tags and so $Main_Plugin_Category is out unless something is introduced to do this. Next was my not so clearly thought out idea of $plugin_name, $tag1, $tag2 – not so wise. 116. In addition, with the free form nature of the tags there are 60k tags as well, many with only a single plugin in that tag. For example, [https://wordpress.org/plugins/tags/guide-book/](https://wordpress.org/plugins/tags/guide-book/)– these are somewhat an issue, but something for later. There are some tags that are great though and form a logical categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. with numerous appropriate plugins. These are really good pages and with a few tweaks should be targeted by google for traffic. 117. The reason to bring in the “| WordPress.org” is to have a standardized ending to all titles on the overall site so that in a SERP it is clear to the visitor this is the official WordPress.org site. As you all know there is a lot of variation of endings currently depending on the section. As for a pipe or a dash, tends to be a religious discussion so I will bow out if I can! 118. I was hoping to avoid variable endings like | Plugins on WordPress.org – harder to recognize quickly in a SERP and hard to apply to the main top level pages. 119. So if we can solve translation related issues is the following agreeable? 120. > plugin – $plugin_name Plugin | WordPress.org > tag – $tag Plugins | WordPress. > org 121. For clarity of title for the visitor clicking on the SERP and general SEO wise, I think this is the best – the exact match of a normal search like “security plugins” is ideal. 122. Next, and not sure of SEO effect of putting in the extra dash, but if we can not solve translation issues then: 123. > plugin – $plugin_name – Plugin | WordPress.org > tag – $tag – Plugins | WordPress. > org 124. Thoughts? 125. * ![](https://secure.gravatar.com/avatar/6ae5aac9c9f6b33d57fb70c593808445da3aefe9cc3a250641073a199810414c? s=32&d=mm&r=g) * [Paul Gilzow](https://profiles.wordpress.org/gilzow/) 4:55 pm _on_ July 17, 2018 * so you want the word “pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory [https://wordpress.org/plugins/](https://wordpress.org/plugins/) or can be cost-based plugin from a third-party.” to show up before **and** after the the plugin’s name? Can you explain the logic for both before and after? What about plugins whose name includes the word “plugin”? As an example, BackWPup would become: * `plugin – BackWPup – WordPress Backup Plugin – Plugin | WordPress.orgWordPress. org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. [https://wordpress.org/](https://wordpress.org/)` Comments are closed. # Post navigation [← WP 4.9.6, Privacy, Hooks, and You](https://make.wordpress.org/plugins/2018/05/17/wp-4-9-6-privacy-hooks-and-you/) [Reminder: Check your Boilerplates →](https://make.wordpress.org/plugins/2018/06/27/reminder-check-your-boilerplates/)