Picking a conference theme with speaker profiles is usually treated as a box to tick on a feature list. It deserves more attention than that, because on most event sites the speakers page is the second page a visitor opens after the homepage and the last one they read before deciding whether the ticket is worth it. A schedule tells somebody what is happening. The speakers page is what tells them whether it is any good.

This is a build guide for that page: what belongs in a profile, how to wire profiles to sessions in both directions, and the photography rules that stop a carefully designed grid from falling apart. It assumes WordPress, and that you would rather not commission a custom post type.

Why the speakers page drives ticket sales

A delegate deciding on a ticket is answering one question: will the people in the room be better than the people I already talk to? Nothing on the site answers that except the speakers page. The programme page answers a different question — what is on — and the venue and sponsor pages answer none of it.

Three practical consequences follow, and they are the reason this page gets its own build rather than a shared template.

It has to work before the line-up is complete. Most conferences announce speakers in waves over two or three months, and the page is live from the first wave onward. A design that only looks right with twenty-four faces in a grid looks broken with five, so settle what five, nine and twenty-four all look like before you commit to a layout.

It is the page speakers share. Every speaker you confirm will post their own profile URL to their followers, which makes each profile a separate landing page arriving from a social referral with no other context. That argues for individual profile pages with real URLs rather than modal pop-ups, which have nothing to share and nothing to index.

It is a reusable asset. A maintained event speaker directory accumulates across editions. By the third year it is a credible record of who has spoken, and it is the single best argument you can make to a speaker you are still trying to book.

What a speaker profile must contain

A conference speaker bio page carries more weight than a team-page entry, so it needs more than a name and a job title. The nine fields below are the working set; the first five are non-negotiable.

  • Name as they want it written, collected from the speaker rather than inferred from an email address, including diacritics and the order they use.
  • Role and organisation at the time of the event, with the organisation left unlinked or marked rel="nofollow" so the page does not become a link farm as the directory grows.
  • A headshot at the dimensions in the next section but one.
  • A two-sentence bio and a longer one. The short version goes in the grid and in the schedule; the long one goes on the profile page. Asking a speaker for “a bio” gets you one of indeterminate length that fits neither slot, so ask for both and give a word count for each.
  • Their sessions, linked, with times. This is the field that turns the page from a credits list into something a delegate can act on.
  • One or two social or portfolio links, and only the ones they actually use. Five greyed-out icons read as neglect.
  • Pronouns, if the speaker supplies them — useful for the person introducing them on stage as well as for delegates.
  • A one-line “talk to them about”, written by you rather than by them. It is the most-read line on the page and the thing that starts conversations in the break.
  • Accessibility and language notes where they apply: the language the session is delivered in, whether slides will be shared, whether captioning is provided.

Collect all nine in one structured form rather than over email. Contact Form 7 is adequate for this and is already a companion plugin on most event themes. One field worth adding that nobody thinks of: a checkbox confirming the speaker is happy for the headshot and bio to stay published after the event, which is what makes the archive in the final section defensible.

Mark each profile up with schema.org Person structured data, and the sessions with schema.org Event, so the relationship between a person and a dated session is machine-readable rather than only visually implied by a layout.

Linking speakers to sessions

The single most common defect on event sites is a one-way link: the schedule names the speaker but the profile never mentions the session, or the reverse. Both directions have to exist, because the two pages serve opposite journeys. Somebody who knows the name arrives at the profile and wants to know when; somebody scanning the grid arrives at a slot and wants to know who.

Decide early how to handle the cases that break a naive one-to-one model; retrofitting them after fifty profiles are live is painful:

  • One session, several speakers — panels, paired talks, co-hosted workshops. The session page needs a list, not a field.
  • One speaker, several sessions — a keynote plus a workshop is a common ask, and the profile has to show both with their times.
  • Non-speaking roles — hosts, facilitators, critics on a live-crit panel. Give them a role label rather than inventing a session for them.
  • Late changes. When a speaker drops out, the profile URL should stay alive with a short note, not 404. Every link anybody shared points at it.

Be realistic about the mechanism. Unless you are building custom fields, cross-linking profiles and sessions is editorial work done by hand — a link in the profile body and a link in the session body. That is workable for thirty speakers, but write it into the checklist for each announcement wave rather than trusting it to happen.

Building the page in a conference theme with speaker profiles

Our YOY event and conference theme ships the page templates this needs: it is built around tickets, event venues, speakers, sessions and sponsors, and includes a dedicated Speakers page alongside Schedule templates, Venue and Clients pages, eight homepage layouts and the usual Service, About and Contact ones. The included Event Scheduler plugin builds the schedule itself, pages are laid out with the WPBakery Page Builder, and Google Maps and Contact Form 7 are the named companions for the venue and for forms. Other options sit in the events theme archive. The build order below is the same whichever of them you use.

  1. Import the demo, then strip it. The one-click importer gives you the Speakers and Schedule page structure populated with placeholder people. Delete the placeholders before you add anybody real, or you will ship a site with a fictional keynote on it.
  2. Build one profile completely — all nine fields, final headshot, real bio — and get it signed off before building the rest. Every layout problem you have shows up on the first one.
  3. Fix the grid rules. Decide the order (alphabetical by surname is the only one nobody argues with, and it avoids implying a hierarchy), what the card shows, and what happens on the last row when the count is not divisible by your column count.
  4. Build the schedule in Event Scheduler, then add the cross-links in both directions as described above, session by session.
  5. Check it at phone width with the longest name and the longest job title you have. Two-line names and forty-character titles are what break speaker grids, not the photography.
  6. Add the structured data and the page metadata — a hand-written title and description on the speakers index itself, which is a page people search for by event name plus the word “speakers”.

Two caveats that apply to any pre-built theme. A one-click demo import gives you structure, not a finished site: every bio, headshot, session and time is still yours to write, and on a speakers page that writing is the whole job. And the photography in a theme demo is licensed for the demo only — it is not included with a purchase, so the headshots have to be real from day one.

Photo and headshot standards

A speaker grid is twenty photographs taken by twenty different people. Left alone it will mix a studio portrait, a cropped wedding photo and a webcam still, and the page will look amateur no matter how good the layout is. The fix is a short, enforced spec sent with the invitation.

  • One aspect ratio for everybody, square or 4:5, decided before the first ask. This matters more than resolution.
  • A minimum long edge of around 1,200 pixels so the image survives a retina display, and a responsive image set so phones are not downloading the full file.
  • Head and shoulders, eyes on roughly the same line across the set. This single rule does most of the work of making mixed sources look deliberate.
  • A plain or quiet background, or a consistent treatment — a duotone or a uniform crop — applied to all of them, which is the standard trick for rescuing an inconsistent set.
  • Real alt text describing the person, not the keyword: “Headshot of Ana Oliveira, product designer”. The W3C guidance on image alternatives is the reference if you are deciding what counts as informative.
  • A fallback, because two speakers will never send one. A plain initials tile in your brand colours is better than an empty frame or a stock silhouette.

Compress everything before upload rather than relying on the theme to do it; a wordpress speaker profile page with twenty-four uncompressed portraits on it is a heavy page, and the images are the only part of it you control completely.

Keeping it current after the event

Most event sites are abandoned the week after the event, throwing away the one asset that was expensive to build. Four things to do instead, in the fortnight while you still care:

  1. Add the outputs to each profile — slides, recording, the notes somebody took. A profile with a recording attached keeps earning search traffic; one without it stops the day the event ends.
  2. Date the edition, do not delete it. Move the 2026 speakers to an archive URL and keep it indexed rather than overwriting it for next year. Those pages hold whatever links and rankings the event earned.
  3. Freeze the roles. A profile says what somebody’s job was at the time. Trying to keep job titles current across three editions is unwinnable; add the year instead.
  4. Honour removal requests promptly, which is the other half of the consent checkbox in section two.

Then point the archive at next year. The speakers page sells the ticket, but it is the programme that justifies it — our thirty conference session formats covers what to put in those slots, and eighteen formats built for design and agency audiences covers the case where the room is full of practitioners who will judge the format as hard as the line-up.