-
Notifications
You must be signed in to change notification settings - Fork 295
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
setting for separator #331
Comments
Where SEO is concerned it's important to have some leeway here IMO so not all pages look the same on SERPS. https://perishablepress.com/choosing-the-best-title-separators/ |
This issue has been automatically marked as stale because it has not been commented on for at least two months. The resources of the Jekyll team are limited, and so we are asking for your help. If this is a bug and you can still reproduce this error on the If this is a feature request, please consider whether it can be accomplished in another way. If it cannot, please elaborate on why it is core to this project and why you feel more than 80% of users would find this beneficial. This issue will automatically be closed in two months if no further activity occurs. Thank you for all your contributions. |
(below response copied from here) Disappointing to see the default pipe e.g. https://support.google.com/google-ads/answer/6349091?hl=en ...uses: Pipes have been mentioned several times as meaning something closer to "or" for Google, so usually it makes sense to reserve usage for the homepage only. E.g. It shouldn't really be used in the way Jekyll SEO Tag is currently using it, to delimit sitename suffix. Seems like an easy win to allow customization or go with the vastly more common dash... |
Any chance this will get traction? Would love the ability to configure this. |
SEO titles have a limited size in google search result page. I think this is the main reason we prefer "|" A agree to say that this is the same :) (sorry for my english) |
@tabasko78 The vast majority of websites are using dashes |
@tabasko78 Use the following - |
@pixelicous Big thanks ! It works !!! |
I second the feature request, I’d like to be able to use a · |
If people are willing to set aside the visual stylistic differences of the separator, and they should, the more important matter to consider is accessibility. > “Page title vertical line site name” ☝🏻 That's how most screen readers will announce it with the pipe character. Not great. Using a standard right-there-on-the-keyboard hyphen is the most accessible solution. “But why, Phil?” Glad you asked! Because screen readers will treat this as a small pause, rather than reading it out in any way at all — which is what we want. > “Page title [pause] site name” ☝🏻 That's a much better experience for our screen reader-using friends and neighbours. It's a tiny improvement, but it matters. It makes things better than they were yesterday, and that's what we should aim for each day. |
a similar issue was previously raised, except it changed from "allow changing
the separator" to "change the separator".
i want my separator to be
-
(hyphen). im not proposing to change the defaultas the default was already hyphen and it was changed away from that. instead
im proposing what the previous issue initially proposed: to allow users the
option.
Personally, i prefer the hyphen because that is what Firefox uses:
here is a workaround:
The text was updated successfully, but these errors were encountered: