Award Markup With Structured Data

When you hang a trophy on a wall, people see it. When you publish an award on a web page, people see it and so do machines: search engines, assistants and software that tries to summarise who you are and what you have done. Whatever those machines understand about your award, they will repeat.

Structured data is the way to tell them plainly. It is a small, careful addition to a page that labels facts in a form software can read. This guide explains how awards fit into structured data, what to mark up, what to leave alone and how to keep the markup honest.

What structured data is

Structured data is information on a web page labelled in a standard vocabulary, so that machines can interpret it. The most widely used vocabulary is Schema.org, a shared set of types and properties for describing things such as organisations, products, people, events and creative works.

Google's introduction to structured data explains that search engines use it to understand the content of a page and to show richer results in some cases. It is not a magic switch. It does not guarantee anything about rankings or appearance. It is a courtesy to the machines and a precision aid for you.

The award property

Schema.org defines a property called award. In its own description, an award is an award won by or for an item, with a text value. It can be used on several types, including organisations, people, products, services and creative works.

In plain terms: if your organisation, product or a person on your team has won an award, you can say so in a way that software can understand. The value is text, so you describe the award in words: its name, perhaps the category and the year.

An older form of the property name, "awards" in the plural, has been superseded by the singular.

Why bother

There are good reasons to add it, and some limits.

Reasons:

• It makes your claim explicit and consistent across your pages.
• It helps machines associate the award with the right entity, your organisation or your product, rather than guessing from the surrounding text.
• It encourages you to be precise, since you must write the facts in a few words.
• It is useful for directories and platforms that read pages automatically.

Limits:

• It does not make search engines show anything in particular.
• It will not make an unimportant award important.
• It does not replace the visible page.

Mark up what is true and visible

The first rule of structured data is that it must match the page. Google's guidance is clear that markup should describe content that is visible to users, and that misleading markup, such as marking up information that is not on the page, can be treated as a violation. Its spam policies cover structured data that is deceptive.

For awards, that means:

• Only mark up awards that are on the page, visible to readers.
• Only mark up awards actually won. The property is for awards won. If you were shortlisted, say so in the visible text, and do not mark it as a win.
• Be accurate about the entity. If the award was for a product, attach it to the product, not the whole company, and the reverse.
• Keep the wording the same as in the visible text.
• Do not inflate. "Winner" means winner.
• Keep it current. Remove or update items that no longer apply.

What to include in the text

Because the value is text, give it enough detail to be unambiguous.

A good award value includes:

• The name of the award, as the organiser writes it.
• The category, if there is one.
• The year.
• The organiser, in the text or in a related link.

For example, in words: "Software Product of the Year, small business category, 2024, run by a named trade body." Keep it factual and consistent with the page.

If you have several awards, list each as a separate value.

Where to place it

Mark up the award on the entity it belongs to.

• An organisation's award goes on the organisation, typically on the about page or home page.
• A product's award goes on the product page.
• A person's award goes on their profile page.

Do not copy every award to every page. A site with fifty pages repeating the same trophy list looks like decoration. Put it where it belongs and link to your cabinet page for the full list.

Format

Structured data can be written in several syntaxes. The recommended one for most sites is a small block of JSON-LD in the page, which keeps markup separate from visible text. Your content management system or a plugin may do this for you. If someone else builds your site, ask them to include the award property from the visible information.

You do not need to write code to benefit: even a clear visible list with proper headings and plain text helps machines. The markup adds precision.

Test it

After adding markup, check it.

1. Use a structured data testing tool to validate syntax and see what is detected.
2. Compare with the page. Every fact in the markup should be on the page.
3. Check dates and names.
4. View the page as a visitor. Is the award easy to see?
5. Recheck after any redesign.

Many content systems break markup quietly when themes change. Put a recheck in your calendar.

Accuracy beyond the markup

Structured data is only as good as your claim. Before you publish it:

• Confirm the award, with the organiser's own results page or letter.
• Check the wording they use for the name and category.
• Check the year.
• Check the permitted use. Some organisers set rules for how winners may describe themselves.
• Keep the evidence on file.

Advertising rules in many places require that objective claims, such as winning an award, be capable of substantiation. Markup that states a win you cannot evidence is a claim on a machine's behalf, and it is likely to be repeated.

Awards you give

If you run an awards programme, structured data can help you too. Pages that list winners can label them with the award property for each winner's page, and pages for the programme can describe the event. Be careful to keep winners' pages and your results page consistent, and to update when results change.

Keep it modest

You do not need elaborate structures. A neat, accurate award entry on the right entity is enough. Complexity breeds errors.

Avoid:

• Marking up everything. A badge you like, a ranking you scored well in, a certification and a membership are different things from an award.
• Using the property for self-given titles. "Our best product" is not an award.
• Adding ratings or review markup to awards. They are different.
• Hidden text.

Machines are one audience

Never forget the humans. Visible clarity matters more than code.

• Show the award with its name, category, year and organiser in plain text.
• Link to the organiser's results page if it exists.
• Add alt text to any trophy or badge image.
• Make sure the information is accessible: real text, proper headings, good contrast.

Markup serves the page, not the other way round.

A short worked example

A small software company won a category award from a trade body in 2024. On its about page, it publishes a short paragraph: the award's name, category, year and organiser, with a link to the organiser's results page. A badge image has alt text with the same details. In the page's structured data, the organisation's award property carries a text value with the award name, category and year, matching the paragraph exactly.

It runs the testing tool, which reads the data correctly, and puts a reminder in its calendar to recheck after the next redesign. When another award arrives the following year, it adds a second value, with a different name and year. When the 2024 award ages, it keeps it, because it is still true, and the dates keep the record clear.

On this site

The launches page shows how achievements and dates appear to readers, the developers page describes the free API and MCP server for reading listing data and the submit page lets you add recognition to your entry. The categories page helps you place your product, and the blog has more guides in this series.

A short checklist before you publish

Ask five questions. Is the award on the visible page? Was it actually won, not merely shortlisted? Are the name, category and year identical in the markup and the text? Is the markup attached to the right entity, the company, the product or the person? Have you saved evidence of the result? If the answer to all five is yes, publish. If not, fix the page first, and let the markup follow. Markup is a mirror, and it should reflect only what is really there.

When your site is built by someone else

If a developer or agency maintains your site, give them a short written brief: the exact award wording, the entity it belongs to, the year and the link to the official result. Ask them to add the structured data from the visible text and to test it. Ask for a note in the site's documentation saying where the markup lives, so that it is not lost in a redesign.

The short version

Structured data labels facts on a page for machines. Schema.org's award property records an award won by an organisation, person, product or work, as text. Mark up only awards actually won and visible on the page, put them on the right entity, include name, category and year, validate the markup, keep it in step with the visible text and keep evidence on file. Markup helps machines repeat your claims, so make sure the claims are true.