Add a cfpDeadline column with ISO dates and filter the /conferences/cfp/ page to rows where the deadline is in the future. SleekRank serves whatever the cached row contains, so set cacheDuration to a few hours during peak CFP season and let expired calls drop off automatically. Some sites add a manual cfpOpen flag for finer control when deadlines extend.

Yes. Route 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, and switch to approved manually before the next cache flush. Confs.tech, the canonical community conference list, runs this pattern with GitHub pull requests instead of forms.

If the conference exposes them, scrape or import via REST. Otherwise keep a speakers column with comma-separated names and link them out to a separate /speakers/{slug}/ page group if you want individual speaker pages. Most aggregator sites do not maintain per-speaker pages because the editorial cost is high and the SEO upside is concentrated in topic plus city searches.

Add a format column with values like in-person, virtual, hybrid and surface it via tag mapping. Event JSON-LD includes an eventAttendanceMode field that accepts these values, so Google rich results show the format clearly. Virtual-only events skip the location.address fields but still include organizer and offers.

Yes. Either run one row per year with year-suffixed slugs like /conferences/kubecon-europe-2026/, /conferences/kubecon-europe-2027/, or maintain a single evergreen page per series with the next edition as columns. Per-year slugs preserve historical SEO; evergreen consolidates link equity. Most sites pick per-year for major conferences and evergreen for smaller series.

Add an earlyBird, regular, and lateBird column or a single ticketTiers column with structured data. Render as a small pricing table via list mapping. Event JSON-LD offers field accepts an array of priceSpecification items, so multiple tiers show in rich results.

Add a coverageUrl column linking to your editorial post or recap article. Surface it as a related link on the conference page via selector mapping. Trade publications often use this to weave their reporting into the conference database without duplicating content into the database itself.

KubeCon hosts dozens of co-located days. Either run them as separate rows linked via a parentEvent column, or list them inline on the parent conference page via list mapping. Both approaches have SEO trade-offs: separate rows index more pages, inline list keeps link equity on the parent.