Event website SEO checklist: rank for the queries that matter

Event websites have an SEO problem that most static-site SEO advice doesn't account for: they go out of date. Last year's page becomes a 404 or a "this event has ended" dead-end, and any link equity built up over months evaporates the day the event ends. A good event SEO setup builds equity that compounds across years, not just within a campaign.

This guide is the practical checklist — what to ship, what to schema, and how to handle the year-over-year transition.

The four queries an event SEO strategy targets

Stop optimising for "{event name}" alone — you'll rank for that no matter what. Build for these four query types:

1. Branded — "{event name} 2026," "{event name} agenda"
2. Branded + intent — "{event name} tickets," "{event name} discount code"
3. Category — "RevOps conference 2026," "marketing conference Singapore"
4. Long-tail — "best fintech conferences in EMEA 2026"

Branded queries are easy. The category and long-tail queries are where compounding actually happens.

Page structure that ranks

For a recurring event, run three types of pages:

• Evergreen homepage — / or /conference/ — never changes URL, updated yearly.
• Year-specific landing pages — /2026/ — the campaign page that converts.
• Topic / track / vertical pages — /2026/devops-track/, /2026/financial-services/ — long-tail magnets.

The crucial detail: the evergreen page accumulates equity year after year. Don't roll it over to a new URL each cycle. Internal-link the year-specific pages from it.

Schema markup that matters

The schema types that meaningfully impact event SEO:

{
  "@context": "https://schema.org",
  "@type": "Event",
  "name": "WebMobi Summit 2026",
  "startDate": "2026-09-15T09:00:00+05:30",
  "endDate": "2026-09-17T18:00:00+05:30",
  "eventStatus": "https://schema.org/EventScheduled",
  "eventAttendanceMode": "https://schema.org/MixedEventAttendanceMode",
  "location": {...},
  "organizer": {...},
  "offers": {...},
  "performer": [{...}, {...}]
}

A few specific notes:

• eventAttendanceMode matters for hybrid events. Don't lie — Google penalises misuse.
• performer should list speakers. Each Person schema entry helps build authority for both the speaker and your event.
• offers should reflect current ticket pricing. Stale price schema is worse than no schema.

For a sponsor-laden conference, also add Sponsor markup linking to sponsor sites — clean trade-offs and a small E-E-A-T win.

URL structure decisions you will regret reversing

A few URL choices to make early and stick with:

• /{eventslug}/{year}/ — clean, easy to roll. Avoid /{year}/{eventslug}/ — harder to maintain navigation.
• Speaker pages at /speakers/{firstname}-{lastname}/. Year-agnostic; the page evolves as the speaker comes back to future events.
• Session pages at /{year}/sessions/{sessionslug}/. Year-specific because session content changes.

Once URLs are public, changing them costs you 6–12 months of link equity. Decide carefully.

Internal linking — the underrated lever

Most event sites have terrible internal linking. The fixes are simple:

• Every speaker page links to all their sessions.
• Every session page links to all its speakers.
• Every track page links to all its sessions and all its speakers.
• The agenda page links to every session.
• Every year's landing page links to the prior year's recap page (which links forward).

Done well, this creates a tightly interlinked sub-graph that ranks far better than the sum of its individual pages.

The year-over-year strategy

Past-year event pages are an asset, not garbage. Treat them right:

• Don't 404 them. Don't redirect them to the new year's page. Both lose equity.
• Update the page header to "WebMobi Summit 2025 (past event) — see the recap" with a link to the recap.
• Add session recordings, photos, and a "register interest for 2026" CTA.
• Schema-update the eventStatus to EventCompleted and the previousStartDate.

Done this way, past-year pages continue to bring search traffic that converts at 4–9% to the next year's registrations.

Recap content that ranks

A post-event recap blog or page should include:

• One paragraph summary, including the year, city, and headline numbers.
• Top 5 sessions with one quote each.
• Photo grid (image alt-text matters — describe the room, the topic).
• Embedded short video.
• "What's next" CTA.

These pages often rank for "{event name} recap," "{event name} highlights," and long-tail "{topic} conference {city}" queries that drive year-round traffic.

Common SEO mistakes for event sites

1. Single-page-app-only pages. If your registration page renders only with JS, Google may not index it cleanly. Use SSR or static generation.
2. No canonical tags. Multiple URLs serving the same content is the most common event-site SEO failure.
3. Aggressive "this event has ended" gating. Pushes search traffic away. Better to convert it.
4. Thin city / track pages. A 200-word "Marketing track" page won't rank. Either invest in 800+ words or roll the content into the agenda.
5. Speaker pages that are just photos and bios. Add the speaker's session abstracts, video clips, and quotes. Each speaker page is a topic page in disguise.

A minimum viable on-page checklist

For each year-specific landing page:

• [ ] Title tag: "{Event} {Year}: {1-line tagline}" (60 chars max)
• [ ] Meta description: dates, city, and one specific reason to attend (155 chars)
• [ ] H1 matching the title
• [ ] H2s for: agenda, speakers, sponsors, FAQ, register
• [ ] Event schema (above)
• [ ] BreadcrumbList schema
• [ ] FAQ schema (uses your existing FAQ section)
• [ ] OG and Twitter card with a clean header image
• [ ] Canonical tag
• [ ] Mobile-friendly (95+ Lighthouse mobile score)
• [ ] Fast (LCP < 2.5s)

Skip the title-tag and meta-description on the recap page until you know what queries you actually rank for — write the meta-description against the queries you see in Search Console, not a guess.

FAQ

How long does event SEO take to compound? For a first-year event, treat SEO as a 12–18 month investment. Branded queries rank fast; category queries take 2–3 cycles to climb.

Should I block search engines from past-year landing pages? No. Update the content and let them continue ranking. They drive future-year registrations.

Is structured data mandatory for event SEO? For events specifically, yes — Google's Event search results lean heavily on Event schema. Without it you miss most of the rich-result placements.

Should I have a separate domain for the conference? Almost never. Sub-folders on the main domain (webmobi.com/summit/) compound the parent site's authority. Sub-domains start from zero.

Related guides

• How to promote a conference
• Event registration optimization
• Post-event content repurposing