If eBird exposes a JSON or REST endpoint your site can read — there's a public API with rate limits — SleekRank can use it as a source. SleekRank doesn't have a built-in eBird integration, so you wire the endpoint as a REST data source with the appropriate auth header. Cache duration prevents hammering the API. Check eBird's terms of service before publishing derived data.

Not by itself. With a REST source connected to eBird or a similar feed, sightings refresh at the configured cache interval — 1 hour, 6 hours, daily — they aren't streamed live. For real-time alerts on rare species, embed the eBird Recent Notable widget on the base page and let SleekRank handle the static spot info around it.

Pick a single naming convention in the sheet — usually common name with scientific binomial in parentheses, in eBird taxonomic order — and the list mapping renders the same format everywhere. A data validation rule on the column or a controlled vocabulary lookup prevents editors from mixing styles. Consistency matters more than which convention you pick.

Yes. Add a parking column to the sheet, add a tag or selector mapping pointing to a target element on the base page, flush the cache, and every spot page picks up the new field — no per-page editing. This is exactly where manual directories collapse and data-driven setups shine.

SleekRank doesn't generate maps. Inject latitude and longitude from the row into a static-map URL (Google Static Maps, Mapbox Static, OpenStreetMap tiles) or a map embed iframe via selector mappings. Most sites use a static-map image with a click-through to a full interactive map for routing.

Yes. SleekRank registers every generated URL with the sitemap and noindexes the base template page so only per-spot URLs get crawled. New spots added to the sheet appear in the sitemap on the next cache refresh — useful when documenting a newly opened reserve or a recently public spot.

Yes. Store species as a structured array with each entry carrying a season field (spring, summer, fall, winter) — a list mapping with conditional logic in the base page renders four sections, one per season. Or split into spring_species, fall_species, etc. columns and use four list mappings on different page sections.

Add a sensitivity column (public, permit-required, private-by-invitation) and use a meta mapping to set robots=noindex on sensitive spots, plus a conditional in the base template to hide coordinates and show a contact-the-society note. Some birding clubs deliberately keep nesting raptor spots out of public listings; the column controls visibility.