Both expose REST APIs that SleekRank reads via the REST API data source type. Meetup.com requires OAuth or API key auth depending on the endpoint; Luma uses bearer token auth. Cache duration sits at four to six hours during typical weeks and drops to one hour during event week so RSVP counts and venue changes propagate quickly.

Add recording_url and slides_url columns populated after the meetup. Selector mapping injects them into a recordings block per page. The post-event page becomes the canonical resource for that talk's recording, which captures search like react server components berlin meetup recording for years after the event.

Maintain a speakers sheet with one row per speaker (name, bio, photo, GitHub, Twitter, talks given). Reference speaker IDs from the meetup row via a comma-separated speakers column and pull bios via cross-source lookup on render. The same speaker bio shows up on every meetup they speak at, no per-event re-typing required.

Yes. Event schema supports offers with price 0 for free meetups, and Google's event rich results show free as a price label in SERP. Paid workshops within a meetup series (occasional hands-on workshops with a fee) map to offers with the actual price and currency.

Either add one row per occurrence with a unique slug per month, or use a single evergreen page per recurring group with next_date column for the upcoming event. Per-occurrence rows are better for SEO because each gets its own URL and rich result eligibility; evergreen is better for groups where attendees primarily care about the next event.

If your source (Meetup.com, Luma, custom) exposes RSVP count, pull it into the feed and render as a tag mapping with capacity status (open, limited, waitlist). RSVP momentum is a strong signal for attendees deciding whether to show; surfacing it as a pill drives conversion to the RSVP click.

No, per-tech pages canonicalize to themselves and link out to canonical per-meetup pages. Per-tech pages aggregate link equity for the technology facet across cities without competing with per-meetup detail pages for SERP positions on local searches.

Maintain a unified sheet pulled from Meetup.com API, Luma API, and manual community contributions, or run separate data sources per region in the same page group. Column normalization lets a Meetup.com API response and a manual community sheet write into the same template fields with consistent rendering.