Emailed Author: There are issues with your plugin code. Please read this ENTIRE email, address all listed issues, and reply to this email with your corrected code attached. It is required for you to read and reply to these emails, and failure to do so will result in significant delays with your plugin being accepted.
## Too Many Tags
Your plugin is using too many tags. We ask that users limit tags in their plugins to no more than 12, with some exceptions. Any time your plugin has a high number of tags, you’re seen as trying to game the system.
Remove any ‘common misspellings’ from your tag list (as they aren’t beneficial), as well as any duplicates. Duplicate words do not help your results in our search engine, as it only considers them once. As much as some people like to think, “tags” are not the same as “search terms” in our system, so including lots of them doesn’t really benefit you much.
If you’re looking to improve your search rankings, we suggest improving the parts of the readme intended for human beings to read. The short and long descriptions should be clear and useful. Addressing common problems in the “FAQ” section helps too. The entire contents of the readme file is considered for the search, and tags are really only a small part of that. Removing irrelevant pieces such as lists of languages (like links) or feature bullet points may help a lot as well, to reduce the overall length and to help eliminate irrelevant information about the plugin.
Make the readme for people, not for machines, and it will help you rank higher in the search results. People actually search for solutions to their problems, not simply for keywords.
## Phoning Home
We do not permit plugins to phone home to your own server unless they’re acting as a service.
For example, a plugin like Akismet is processing spam on their own servers, and passing the data back to the users via an API. This is a service.
On the other hand, a plugin that simply validates a license and ‘unlocks’ functionality that’s already in the plugin is not a service.
Similarly, if you have your plugin send an email or message to your own servers when the plugin is installed and/or uininstalled, this is patently nor permitted.
This is explained in more detail in our guidelines ( https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/ ) under “Serviceware”
Please remove any calls back to your own server from the plugin. Alternately, you may provide more information as to how you are providing a service. Remember. The service needs to be running from an external server.
Why? This is not mentioned as a requirement in your readme. And we STRONGLY discourage you from making yourself a service endpoint for Facebook. It’s a lot of work and legally problematic for some people.
Please make sure you’ve addressed ALL issues brought up in this email. When you’ve corrected your code, reply to this email with the updated code attached as a zip, or provide a link to the new code for us to review. If you have questions, concerns, or need clarification, please reply to this email and just ask us.
(While we have tried to make this review as exhaustive as possible we, like you, are humans and may have missed things. As such, we will re-review the ENTIRE plugin when you send it back to us. We appreciate your patience and understanding in this.)