How to Put a Certificate on Your CV

The short version

Certificates go in their own section, headed Certifications, not scattered through Education and not mentioned only in your personal statement. Each entry carries five things: the exact name of the award, the organisation that issued it, the month and year, the credential ID, and the verification link.

Almost everybody writes the first three. The last two are what turn the entry from something you have asserted about yourself into something the reader can settle without asking you, and leaving them off is the single most common way a genuine qualification ends up carrying no more weight than an invented one.

Where it goes on the page

Position follows one question: is this certificate a requirement of the job, or a supplement to it?

If the advert asks for it by name, or the work legally cannot be done without it, it stops being a certificate and becomes a qualification. Put the section directly under your personal statement, above employment history. A reader who has to reach page two to find the thing they screened for may not get there.

If it supports your case rather than making it, the section belongs after employment history and before any interests or referees. Certificates arranged in front of experience read as a substitute for it, which is the opposite of the intended effect.

Keep them out of Education. That section is for awards from institutions whose business is awarding them, and mixing a two-day workshop certificate in beside a degree invites a comparison that does the certificate no favours. A certificate of completion records attendance and finishing; it is not a qualification, and filing it as one is noticed. The same caution applies to a micro-credential, which describes how narrow an award is and says nothing at all about whether anything was assessed.

What one entry should contain

One line per element, or two lines with the detail running on. What matters is that all five are present and none has been improved in transit.

The exact name. Copy it from the certificate. Not the course title, not a tidier version, and above all not a version promoted a grade: "Certificate in Project Management" must not become "Project Management Certification". Those are different things, the reader knows it, and the discrepancy is visible the moment anybody opens your link.

The issuer. The organisation, under the name they actually trade under. If the certificate carries both a training partner and an awarding body, name the awarding body and put the partner in brackets.

The date. Month and year. If it expires, say when in the same line: "Issued March 2026, expires March 2029". An expiring credential with no expiry shown reads as one you have not checked.

The credential ID. The identifier the issuer's own records are keyed on, which is what somebody phoning them will be asked for. What a credential ID is covers where to find yours and what to do when there genuinely is not one.

The verification link. The page that confirms the credential, on the issuer's own domain. Not a link to a PDF in your cloud storage, which looks like verification and proves nothing: anybody can upload a file. A verifiable credential is one that carries its own proof, and the link is how a reader reaches it.

The problem with a link on paper

Every other place you put a certificate assumes a link that can be clicked. A CV frequently cannot: it is printed for an interview panel, or it arrives as a scan, or it is read on a phone by somebody who is not going to type out a forty-character URL.

Start from the assumption that nobody is going to retype it. Most verification links end in a long identifier, because that identifier has to be unguessable: ours are a domain followed by a 36-character UUID, and other issuers are much the same. Shortening it is not an option available to you, since it is your issuer's URL and not yours. So plan around it instead.

• Print the credential ID beside the link. This is the one that matters. The ID is short, it is what the issuer's records are keyed on, and it is what somebody who cannot face the URL will use instead. Two routes to the same record cost you one line.
• Add a QR code if the CV is genuinely going to be handed over on paper. It is the only thing that makes a long URL usable from a printed page. One small code in the certifications section, not one per entry, and worth doing where the certificate is the qualification for the role rather than a supplement to it.
• Keep the link itself intact. Do not trim it to look tidier, and do not run it through a link shortener. A shortened link asks the reader to trust an unfamiliar domain before it hands them to the issuer, which is precisely the instinct you want them to keep.

The same applies to the QR: point it at the credential page itself. And check that it scans from an actual printout before you rely on it, because a code that has been scaled down or printed faintly can look perfectly correct and not read at all.

Writing it so a machine can read it

Many CVs are read by software before a person sees them, and the failure is silent: the certificate is on the page, the parser did not find it, and nobody involved ever learns why. You cannot control which parser, and guidance naming a specific product's behaviour goes out of date quietly. The document-level rules are stable, though, and they are all you need.

• Use a real heading. "Certifications" as text, in the body of the document. Not an image, not a text box, not a header or footer, all of which are commonly skipped.
• Avoid tables and columns for this section. A two-column layout that reads correctly to the eye can interleave into nonsense when flattened to text.
• Write the full name and the abbreviation at least once each. Someone searching for "PMP" and someone searching for "Project Management Professional" should both find you.
• Send a PDF unless a file type is specified, and one generated from a document rather than a scan. A scanned CV is an image of text, and to a parser an image of text is an image.

Which certificates to leave off

A certifications section is stronger for being short. The instinct to list everything you have ever completed produces a page that reads as accumulation rather than expertise, and buries the one credential that mattered among eight that did not.

Steps rather than destinations. If you hold the full qualification, the module certificates that led to it add nothing. List the destination.

Expired credentials, unless the fact that you once held it is genuinely relevant, in which case say so plainly rather than hoping the date is not read.

Anything unrelated to the role. A food hygiene certificate on an application for a back-end engineering job is not a demonstration of breadth.

Certificates you cannot evidence. If the issuer has closed, you have lost the file, and there is no record anywhere, think carefully. You may well be entitled to claim it, and you may also be asked to produce something you no longer have.

When you are asked to prove it

At some point somebody follows up, and where they land depends entirely on what you gave them. With a verification link, the check takes seconds and you are not involved: they open the issuer's page and compare it against your CV. How employers verify certificates sets out the five routes they can take and what each one actually proves, which is worth reading from your side of it.

Without a link, the route is an email to the issuing organisation, and that is where genuine qualifications quietly fail: the request goes to an address nobody monitors, or reaches a body that will not confirm anything to a stranger, or lands with an institution that no longer has records from that year. Nothing has been disproved. It simply could not be confirmed, and the outcome for you is often the same.

If you are asked to bring physical copies, bring them, and bring the link as well. The copy proves you have a document. The link proves the document corresponds to a record.

Does it actually help?

Honestly: less than the effort spent collecting certificates would suggest, and more than nothing, with the gap between those two determined almost entirely by whether the entry is checkable.

Where a credential is a formal requirement, listing it properly is not an advantage but a precondition, and the verification link is what stops the precondition becoming a delay. Where it is one signal among several, it supports a case your experience still has to make. No certificate has ever rescued a thin CV, and a column of nine of them tends to read as a substitute for one substantial thing rather than as evidence of nine.

One thing that is measurable, from our own data rather than from anybody's survey: across one issuer's cohort of 48 credentials, the credential pages were opened far more often than the verification panel on them, and LinkedIn was the largest identifiable source of that traffic. People do follow these links. What they mostly do when they arrive is look, which is an argument for the link being present and correct rather than for anything more elaborate.

The profile version of this exercise is a different job with different fields, and it is covered in adding a certificate to your LinkedIn profile. Sending the credential to somebody, rather than listing it, is different again: sharing a certificate covers what to put in a post and what to send a recruiter who has asked for proof. And if what you need first is the file itself, downloading your certificate covers which format to use where.