-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Missing dash in TITLE metadata #1188
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
Comments
The other similar problem we're facing is the casing in the filenames. |
@juanpablojofre your comments about casing are in reference to #1175, is that accurate? |
It seems, this issue was part of the migration process. |
oops.... this impacts at LEAST psget as well. @juanpablojofre would you mind re-running your amazing script against the different directories? we should also keep an eye out for underscores in page title. |
I think we need define better our reference strategy for the Gallery. |
@JKeithB please take a look at above concern. I agree with @juanpablojofre to unify the PowerShellGet content under single location. |
Updating Title metadata tag as requested by @zjalexander |
Fixed |
Originally reported by Chrissy LeMaire:
I find it disconcerting that searching for PowerShell commands returns pages with titles that are missing the dash.
For example:

The page itself has a proper title
Can this be fixed? The reason it's an issue is because I initially scan over it. I assume others may too. My brain is trained to look for the dash, otherwise, it lumps the result in with ads or rando blog posts.
In the end, I end up having to fight my natural response that tells me to click on SS64.com.
If you look at the raw markdown, you will see a bunch of tags, including:
title: Get AuthenticodeSignature
That title tag is what we use to generate the page title, which is what search engines pick up, and it is missing the dash.
So, not an infrastructure problem! Just a metadata problem that we need to fix. Now we need to see how many items are missing the dash in the title….
The text was updated successfully, but these errors were encountered: