-
-
Notifications
You must be signed in to change notification settings - Fork 71
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
Set character limits on other title and description fields #1265
Comments
Would it be acceptable if they used the same settings from the SEO Title & SEO Description length settings? Currently it's setting the defaults to what Twitter & Facebook say are the length limits. |
https://capture.dropbox.com/xAZ6dVfXYVoOFcKn Same here. It becomes a mess depending on the length of data and fieldtype. |
@EmptyStreets I'm not understanding the context here, that field seems to be populated with a whole lot of characters that shouldn't be there? I also never got an answer from @milesjbland ? |
Sorry. I mean that schema.org description doesn't follow the character limit defined in the plugin setting nor there's any additional option(s) to specify this for schema json. Can be an issue in terms of SEO (looks really spammy) and adds additional overhead to the page size. |
@EmptyStreets would you be ok with the proposal I mentioned above? That all titles and descriptions are truncated to the limit set for titles and descriptions? |
Sounds logical to me. It couldn't be easier. |
@khalwat Sorry for the delay in getting back to you! Happy with the proposed solution. |
Is your feature request related to a problem? Please describe.
Currently, in Plugin Settings > Titles, you are able to set the character limits for the SEO Title and SEO Description fields. But, you can't set them for Twitter Title/Description or Facebook OpenGraph Title/Description.
Describe the solution you would like
It would be nice if we had additional fields in the settings to add optional character limits to these fields.
Describe alternatives you have considered
We can add our own text field with a character limit and use that to populate these, but we'd prefer to use the native SEO field.
Additional context
N/A
The text was updated successfully, but these errors were encountered: