Connect a Google Form to the same sheet with required columns. Add a status column that defaults to pending so unreviewed entries do not auto-publish, then flip to approved manually before the next cache flush. Most communities pair this with a simple curation rule like minimum prize amount or required organizer affiliation.

Add a format column with in-person, virtual, hybrid and surface it via tag mapping. Event JSON-LD includes eventAttendanceMode for these values. Virtual events skip address fields but still include organizer and the streaming URL via selector mapping.

Add a pastWinners column or a separate winners sheet keyed by event slug. Render the most recent winners as a card list on the event page via list mapping. This is high-signal for founders deciding whether the event aligns with their company, and it pulls in backlinks from winners linking back to their pitch night.

Add an access column with values like open, application, invite-only and surface it as a pill. Invite-only events still benefit from a public page because they pull in founder applications via search, and the page itself signals the organizer's network.

Use a free-text prize column that accepts equity, office space, customer intros, or cloud credits. The structured field is useful for sorting and filtering, but the content can be anything. Some sites split into prizeAmount and prizePerks columns for sharper filtering.

No. SleekRank handles SEO landing pages and per-event URLs. RSVP and ticketing run on Lu.ma, Eventbrite, or your own form via deep-link from the page. The point is to capture organic search traffic that platform pages do not rank for, and route it to whatever RSVP system the organizer already uses.

Add a sponsors column with comma-separated logos or names and render as a list mapping. The sponsor list is high-signal for founders evaluating fit, and sponsors get backlinks to their own pages from the event listing.

Run them as a parent event with /pitch-competitions/{slug}/ and child rounds under /pitch-competitions/{slug}/round-{n}/. Each round has its own date and shortlist; the parent page aggregates winners across rounds. Event JSON-LD subEvent field handles the parent-child relationship.