-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin names use a kind of keyword stuffing. #91
Comments
I've asked plugin developers to shorten their plugin names as well. Some even only have the description and the actual name is at the end of that, but gets cut off in certain places, so it's missing the name altogether. Some plugin developers listen and adjust the name, but most of them think it's better for them to stuff it with keywords to get higher in the search results. As this is totally not useful for users, I'd like to see that this is made clear in guideline 9, where keyword stuffing is already mentioned. Maybe it's already enough to take action against these plugins. |
A few more examples: |
FYI: We as the german polyglots team decided to keep all plugins names untranslated. Period, |
Hi, I think keyword stuffing is a bit of a subjective topic, there will be specific cases where few people think it's keyword stuffing and cases where most people would agree. I think in the end it's something where common sense has to prevail, I don't think it's a subject where you can specify exactly in the guidelines a formula by which you can do this in an exhaustive, mathematical and reproducible way. Anyway, guidelines already give a hint in the 12 about what keyword stuffing is.
But we know that keyword stuffing is not only that. So regarding that I think it's clear that "My Forms Plugin - Beautiful forms, GDPR forms, Spam Free forms" can be considered keyword stuffing. While "My Forms Plugin - Beautiful, GDPR and Spam free forms" although it is technically a rather long title, I think it is open to opinion regarding keyword stuffing. |
Looks like there's a trend of 'keyword stuffing' the plugin names, like in:
Jetpack – WP Security, Backup, Speed, & Growth
WPForms – Easy Form Builder for WordPress – Contact Forms, Payment Forms, Surveys, & More
Tablesome – Form DB & Automation – WPForms, Contact Form 7, Elementor, Forminator, Fluent, Gravity
Popup Maker – Boost Sales, Conversions, Optins, Subscribers with the Ultimate WP Popups Builder
etc.
Besides the question if this is good practice I have another question. the german team doesn't translate Plugin names usually. But I see more and more translation of those additional phrases, like in
Jetpack – Sicherheit, Backups, Geschwindigkeit und Wachstum für WordPress (translated by translationsbyautomattic)
Following our rules I would need to reject this translation.
So in general, what do you think, is this a route we should follow or should it be restricted in any way? Has there been some discussion/decision from your side?
I first raised this question on Slack and after there was some discussion I got redirected here
The text was updated successfully, but these errors were encountered: