How to Build an Expo Booth Landing Page That Actually Converts (2026 Guide)

Most expo booth pages are an afterthought. Someone snaps a logo, drops in a date, and calls it done. Then the booth gets traffic from a QR code and nobody knows what to do next. I’ve rebuilt enough of these to know the difference between a page that sits there and one that fills a follow-up list.

Here’s the thing: an expo landing page has one job. It’s not a brochure. It’s a handshake that has to work in about eight seconds, on a phone, on a convention center Wi-Fi network that’s fighting ten thousand other devices.

Start With the One Thing You Want People to Do

Before you touch a design tool, decide the single action. For most booths it’s one of these:

• Scan a QR code and land on a page where they book a call
• Join an email list for a specific follow-up (not a generic newsletter)
• Grab a demo link or a downloadable spec sheet
• Find your booth number and the show floor map

Pick one. Two is fine if they’re related. Four is a page that converts on none of them. If you’re working with a custom web development setup rather than a template builder, you have full control over this, which matters more than people think.

Make It Fast on Bad Wi-Fi

Convention center connectivity is the real constraint. A page that loads in 4 seconds on your office fiber will take 12 seconds on the show floor, and half the people will bounce before your hero image finishes.

The fixes are boring and they work:

• Serve images as WebP or AVIF, sized to the actual display dimensions
• Skip web fonts if you can, or subset them and use font-display: swap
• No autoplay video in the hero. Ever.
• Inline critical CSS so the top of the page paints immediately
• Deploy to a CDN with edge nodes near the venue

Here’s a lightweight lazy-load pattern that won’t tank your LCP:

<img
 src="/images/booth-hero-800.avif"
 srcset="/images/booth-hero-400.avif 400w,
 /images/booth-hero-800.avif 800w,
 /images/booth-hero-1600.avif 1600w"
 sizes="(max-width: 600px) 100vw, 800px"
 width="800" height="450"
 alt="Our booth at the 2026 show, hall C"
 fetchpriority="high"
 decoding="async">

Note the fetchpriority="high" on the hero and nothing on the rest. That one attribute does more for perceived speed than most optimization plugins.

Answer the Four Questions in the First Screen

Someone scanning your QR code has four questions, in this order:

1. Where am I?
2. What do you do?
3. Why should I care right now?
4. What do I do next?

If any of those takes scrolling, you lose people. Put the booth number and hall in the top bar. Put a one-line description under it. Put the button above the fold. That’s it.

A Header That Does the Work

<header class="booth-header">
 <p class="booth-location">Booth C-412 · Hall C · Javits Center</p>
 <h1>We build custom web apps for trade show teams</h1>
 <p class="sub">Stop losing leads to a clipboard. Scan, capture, follow up.</p>
 <a class="cta" href="#book">Book a 15-minute slot</a>
</header>

Three elements. Location, promise, action. No stock photo of people shaking hands.

Capture Leads Without a Form That Feels Like a Form

The old advice was a five-field form. In 2026 that’s a bounce machine. Ask for the minimum you need to follow up, and give them a reason to give it to you.

Two fields is the sweet spot:

<form action="/api/lead" method="post" class="lead-form">
 <label for="email">Work email</label>
 <input type="email" id="email" name="email"
 autocomplete="email" required>

 <label for="interest">What are you here for?</label>
 <select id="interest" name="interest">
 <option>A demo</option>
 <option>Pricing</option>
 <option>Just staying in touch</option>
 </select>

 <button type="submit">Send me the follow-up</button>
</form>

That dropdown is doing quiet work. It tells you how to route the lead later, and it gives the person a sense they’re getting something specific, not a newsletter blast.

One more thing: use inputmode and autocomplete properly. On a phone, autofill cuts form completion time in half.

Track the Scan, Not Just the Click

If you can’t tell which booth, which day, and which QR code a lead came from, you’re guessing. Append UTM parameters to the URL behind each QR code.

https://yoursite.com/expo?utm_source=booth
 &utm_medium=qr
 &utm_campaign=2026-spring-show
 &utm_content=hall-c-banner

Generate a separate QR per placement: the banner, the table card, the badge lanyard, the slide deck. They cost nothing and the data pays for itself.

Don’t Forget the Day After

The show ends and everyone goes home. That’s when the page should change. Two options:

• Swap the hero for a “Thanks for stopping by” message with the same booking link
• Redirect to a permanent page that keeps the content but drops the booth number

Either way, don’t leave a dead page with a date that’s now in the past. It looks abandoned, and it wastes whatever SEO value the page built.

If you’re local and doing a show around Long Island or the city, the same rules apply. The venue changes, the Wi-Fi is still bad, and people still scan while walking.

FAQ

Do I need a separate page for every show?

No. Use one page with a URL parameter or a subpath for each event. You keep the SEO juice in one place and avoid a graveyard of orphaned pages.

What’s the fastest way to make a slow expo page faster?

Convert your hero to AVIF, set explicit width and height, and add fetchpriority="high" to it. That’s usually a 40 to 60 percent LCP improvement on its own, before you touch anything else.

Should the QR code go to my homepage or the booth page?

The booth page, always. A homepage makes people hunt for what they just saw on the banner. Send them to the page that has the booth number, the promise, and the button.