An IT provider's partner designations and certificates, stated as issued

A retired program name is a stale fact with your name on it

Vendors rename and retire their partner programs, and a website keeps the badge and the sentence it was built with until someone changes them. Microsoft's program is a clear case. Its partner program overview on Microsoft Learn, read on September 25, 2026, lists the legacy Gold and Silver benefits packages as "no longer available as of January 22, 2025", with renewal not possible, and recommends that legacy Gold partners explore the Partner Success Expanded Benefits package and the Solutions Partner designation in the Microsoft AI Cloud Partner Program instead.

A footer that still reads "Microsoft Gold Partner" therefore names something Microsoft's own page now lists only as a legacy package, no longer available. A text fetch of that footer returns the sentence, and an older copy of the page may already sit in a model's training data; either way, an answer has a dated claim it can repeat as if it were current. A buyer who checks the vendor's directory finds another name or none, and the claim fails the one test the buyer can run.

An old badge image is the same fact in pixels: a person reads it, a text fetch reads nothing, and neither learns the date. None of this depends on the vendor. Microsoft's page warns that its program information is subject to change without notice, and the only current source for any designation's name is the vendor's own page on the day you check. Where the vendor's pages do not confirm a current name, use the wording your partner portal or agreement shows today, or leave the designation off.

How to write a partner designation a buyer can check

Give each designation one sentence and one link. The sentence names the vendor, the program and the designation exactly as the vendor's current page or your partner agreement spells them, the date you were awarded it, and the company that holds it. The link goes to your entry in the vendor's public partner directory, where the vendor keeps one. The table takes the sentence apart.

The registered name matters more than it looks. After an acquisition or a rebrand, the company that holds a vendor agreement may not carry the name on your homepage, and a buyer searching the vendor's directory searches for one of the two. In our audit of 9,483 small business websites (40 trades, 90 metros, late August to early September 2026), 43.1% were inconsistent about who and where they are across their own three main pages; the figure is sample-wide, and we publish no IT-only cut. Write the registered name beside the trading name wherever a designation appears.

Two limits keep the sentence honest. State the designation, not what it proves: Microsoft's page says a reference to Solutions Partner should not be read as an endorsement, guarantee or warranty on Microsoft's part, so "endorsed by Microsoft" claims more than Microsoft does. And leave a program's requirements to the vendor. What a tier asks of a partner is the vendor's to publish and to change, and a summary on your page goes stale the day the vendor edits its own.

A certificate is stated with its scope, its issuer and its dates

A certificate from an independent body, such as an ISO/IEC 27001 certificate, is written from the certificate itself: the standard and its edition year exactly as printed, the scope in the certificate's own words, the certification body that issued it, the certificate number, and the dates it is valid from and until. If the certification body lets anyone check a certificate by its number, link that lookup.

Certified to ISO/IEC 27001:[edition year] for [the scope, as worded on the certificate].
Certification body: [name]. Certificate number: [number].
Valid from [date] until [date]. Check it at: [the certification body's lookup, if it has one].

The scope is where a claim can outgrow the certificate. If the certificate covers [the managed services delivered from one office], the page says so, and the badge stays off pages about services the scope does not name. "We are ISO 27001 certified" on the homepage of a group whose certificate covers one office states more than the certificate does, and an answer that repeats the homepage repeats the overstatement.

The page reports what you hold and leaves the standard alone. What ISO/IEC 27001 requires, and what your audit examined, are for the standard and your certification body to say; the credentials page repeats the certificate and nothing more.

Say what you do not hold

A buyer's question can name a certificate or a partner status outright ("msp with iso 27001", "it company that is a [vendor] partner"), and the article on MSP shortlists collects more of the questions IT buyers bring. An answer can state where your firm stands only if a sentence states it, and a page that lists what you hold and is silent about the rest leaves the question open. A plain negative closes it: "We are not certified to ISO/IEC 27001." "We do not hold [vendor]'s [designation]; we support [product] through [the arrangement you have]."

Leave out the phrases that sound like a certificate without being one. "ISO 27001 aligned" or "built on ISO 27001 principles" hands an answer a sentence it can repeat as certification. If you follow parts of a standard without a certificate, name the parts as a fact about your own practice, and say in the same sentence that you are not certified. If an audit is booked, say that it is booked and with whom, and leave the finish date off until the certificate exists.

Staff certifications, one credentials page, and the markup

An engineer's vendor certification belongs to the engineer. Put it on that person's profile with its name as the issuer writes it, the date, and the verification link where the issuer keeps a numbered, public record. A line such as "[n] of our engineers hold [certification]" is fine while it is true and the names behind it are on the site; "certified team" with nobody named gives a buyer nothing to check.

Keep one credentials page as the source for every other mention: each designation and certificate with its dates, linked from the footer, the about page and each service page it supports. Review it on every renewal date and whenever a vendor announces a program change. If the history matters, keep a dated line instead of the old badge: "From [year] to [year] we held [vendor]'s [former designation], which [vendor] retired on [date]." The IT service providers overview places this page among the others a provider's site carries.

In markup, a certificate the company holds is a hasCertification on the firm's LocalBusiness or Organization node, whose value is a Certification: issuedBy for the certification body, certificationIdentification for the certificate number, certificationStatus, validFrom, expires and a url for the public lookup. schema.org's own definition of the type gives an ISO-certified organization as its example. An engineer's certification can take the same shape on a Person node where the issuer keeps a numbered, checkable record. A partner designation is the vendor's statement about you rather than an independent body's, so it stays in the text.

{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "[Trading name]",
  "legalName": "[Registered name that holds the certificate]",
  "hasCertification": {
    "@type": "Certification",
    "name": "ISO/IEC 27001:[edition year]",
    "description": "[The scope, as worded on the certificate]",
    "issuedBy": { "@type": "Organization", "name": "[Certification body]" },
    "certificationIdentification": "[Certificate number]",
    "certificationStatus": "https://schema.org/CertificationActive",
    "validFrom": "[YYYY-MM-DD]",
    "expires": "[YYYY-MM-DD]",
    "url": "[The certification body's public lookup for this certificate]"
  }
}

Mark up only what the page shows, and change the markup on the day the page changes. Google's general structured data guidelines ask for up-to-date information and nothing a reader cannot see, and a lapsed certificate left in the markup fails the first. The field-by-field reasoning is in the changelog and trust center article, written for software companies and just as true for a provider.