How to Share a Certificate on LinkedIn

The short version

Share the verification link, and attach the certificate image to it. On LinkedIn that means a post containing both, with the issuing organisation tagged. Sending it to one person means the same link in a message, with a sentence saying what it is.

The link is the part that does the work. An image of a certificate is a picture of a claim, and everyone reading it knows that pictures can be made. The link is the only version of your certificate that a sceptical reader can do anything with.

Sharing is not adding it to your profile

These are two different jobs and doing one does not do the other. A post is a moment: it appears in feeds for a day or two, reaches the people who happen to be looking, and then is effectively gone. A profile entry is permanent, appears to everybody who visits you afterwards, and is what recruiters filter and search on.

The profile entry is the one that matters more, and it is a separate exercise with its own fields to fill in correctly. Adding a certificate to your LinkedIn profile covers that form, including the two fields most people leave empty. Do that first. Then, if you want to, post about it.

The image or the link

Most people share the image, because it is the thing that looks like a certificate. It is worth being precise about what each one hands to the person receiving it.

None of this makes the image a mistake. Attach it: a post with a picture is more likely to be looked at than a bare line of text, and the certificate is the obvious picture. The error is attaching only the image, which is what turns a genuine achievement into something indistinguishable from a template someone filled in. What the link adds is that the thing on the other end is a verifiable credential, carrying proof of its own rather than asking to be believed.

One thing to avoid entirely: a screenshot of the verification page. It carries all of the weaknesses of an image and adds the false impression that verification has happened. Anybody being asked to trust a screenshot of a check is being asked to trust the person who took it.

Writing the post

The pattern that works is short and specific, and it is mostly a matter of avoiding the version everyone has learned to scroll past.

• Say what the programme involved. "Delighted to share that I have completed" carries no information. What you can now do that you could not do in January is information.
• Tag the issuing organisation. It reaches their audience, they are generally pleased to see it, and it associates your post with an account that has a history rather than with a name in plain text.
• Put the verification link in the post itself, not in the first comment. A link somebody has to go looking for is a link nobody opens.
• Attach the image as well. Both, in one post.
• Thank people by name if you mean it, and not otherwise. A list of tagged colleagues added for reach is visible as exactly that.

Post once. Five posts about five modules of the same programme is the most reliable way to make a real qualification look like content.

Sending it to one person

This is the version that actually changes outcomes, and almost nobody does it. A recruiter asking whether you hold a qualification wants the answer settled, not asserted.

Send the link with one sentence of context: what the award is, who issued it, and that the page confirms it. Do not attach a PDF unless they asked for a file. A PDF puts them back in the position of deciding whether to believe a document, which is the position the link exists to get them out of.

If they have asked for evidence formally, give them the link and the credential ID together. Different organisations check in different ways, and how employers verify certificates sets out the five routes they might take. The link serves the fastest of them; the ID serves the slower ones.

Everywhere that is not LinkedIn

The same link works in every other place a certificate comes up, and the considerations barely change.

In an application form. Where there is a field for a credential URL, use it. Where there is not, put it beside the qualification in the free-text box. Putting a certificate on your CV covers the printed case, which has its own problem: a link on paper cannot be clicked.

In an email signature. Reasonable for a licence that is central to your work, and clutter for anything else. One line, not a row of badges.

On WhatsApp or a group chat. The link previews, which is usually the point. Be aware that forwarding is frictionless and that whatever you send may travel further than intended, which matters more than it sounds given the next section.

Where somebody has asked for a file. Some application systems accept an upload and nothing else. Send the PDF in that case and put the link in whatever free-text field exists; downloading your certificate covers which of the two files you want and why the file on its own settles less than the link does.

If your certificate has no link

Most certificates in circulation have none. There is no way to manufacture one, and the honest options are limited.

Ask the issuer whether they offer a verification page, a public register, or a confirmation letter on request. Many training providers have one and never mention it. If they do not, share the image and be straightforward about what it is, quote the credential ID if there is one, and offer to put the issuer in touch directly. That is a weaker position than a link, and pretending otherwise helps nobody, but it is honest and it is what an employer expects when a credential predates all of this.

What not to do is upload the PDF to cloud storage and share that as though it were verification. A file you control proves nothing about who issued it, and a reader who realises the link goes to your own drive has learned something you did not intend to tell them.

What you are also sharing

A verification page is public by design. That is the entire point: a credential nobody can open is a credential nobody can check. It does mean deciding, once, that you are comfortable with the page being reachable by anyone who has the link.

What is on it is the same information as on the certificate itself: your name, the award, the issuing organisation, and the date. Worth knowing, and not obvious, is that on our own credential pages the page's underlying data also contains the email address the credential was issued to. It is not displayed anywhere on the page, and it is there for a specific reason: the signature covers it, and the check runs in the visitor's own browser rather than on a server, so the browser needs every signed field to reproduce the check. Somebody who looks at the page source can read it. If that matters for a particular credential, that is a reason to send the link to named people rather than posting it publicly.

A credential page can also be taken out of search results without being taken down, which is a distinction worth knowing: the page keeps working for anyone you send it to, while stopping it turning up when somebody searches your name. Ask your issuer, who can set that per credential.

When not to share it at all

Not every certificate is worth a post, and the judgement is easier than it looks. If it is a step towards something rather than the thing itself, wait and share the thing itself. If you would be uncomfortable seeing it quoted back to you in an interview, that discomfort is information. If you have posted about three certificates this quarter, the fourth post is no longer about the certificates.

The profile entry costs nobody anything and asks for no one's attention. It is available in every one of these cases, and it is the one that is still working for you in two years.