-
Notifications
You must be signed in to change notification settings - Fork 891
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
Linkedin No publication date found #18627
Comments
We have been trying to add support for this but have no luck due to LinkedIn's lack of documentation. Once we find more information about this, we'll add it in the plugin. |
I wanted to create a new issue regarding this but saw that @yogeshbeniwal beat me to it. |
It seems LinkedIn wants a time tag that is missing. Having read several web posts and checked my page settings, I believe this could be solved by adding element |
Not really, I just tested it but no luck 🥱 |
I am also experiencing this issue with the latest WP and Yoast versions. |
I have the same issue and contacted LinkedIn support. Here's their answer: Member can change the date accordingly :
or by time element : |
doesn't work on my end |
Same issue here. |
Same here |
I checked LinkedIn Help and noticed there still need details from LinkedIn on how to add the Publish date. If anyone notices any official guidelines from LinkedIn about this, share them with us so we can take a closer look. Moreover, even though the LinkedIn inspector shows a message about a missing publish date, the sharing on LinkedIn works fine. |
|
The meta tag < |
Is your feature request related to a problem? Please describe.
Linkedin post inspector is throwing an error for Publish date: No publication date found
Describe the solution you'd like
Similar to adding meta author, add relevant details to page to resolve this error
Why do you think this feature is something we should consider for the Yoast SEO plugins?
To keep all schema related information at one place
Additional context
The text was updated successfully, but these errors were encountered: