City residents search community garden Brooklyn waitlist, allotment near me Chicago, Berlin community garden membership, and Portland P-Patch availability. The intent splits along city, neighborhood, plot availability, annual fee tier, water access, organic-only policy, and waitlist length. Municipal park sites produce inconsistent garden information across departments, and per-garden details often live in volunteer-maintained spreadsheets that never make it to indexable pages.

SleekRank reads a curated feed of gardens and renders one /community-gardens/{slug}/ page per garden plus /community-gardens/neighborhood/{slug}/ and /community-gardens/city/{slug}/ collection pages from the same source. Each row defines name, neighborhood, city, plot count, available plots, annual fee, water access, founded year, organic policy, and signup URL via tag, selector, list, and meta mappings.

Closed gardens move to a /community-gardens/closed/ archive for backlink continuity. Open Graph cards via SleekPixel pair neighborhood plus city plus available plots so social shares preview opportunity. Cache duration sits at one week since plot turnover happens seasonally, and the XML sitemap picks up every new garden automatically.

Community garden search is hyper-local and seasonal: residents want a garden in their specific neighborhood with current plot availability, not a citywide list of every garden with stale availability data from last year's update. Municipal park sites produce inconsistent garden coverage because community gardens often span overlapping departments (parks, sustainability, food policy) and individual gardens depend on volunteer coordinators whose contact info changes annually. Garden coalitions and urban agriculture nonprofits have the structural advantage on per-garden coverage but lose it operationally when manual maintenance falls behind seasonal plot turnover.

Programmatic per-garden pages from a feed solve both problems: the curation is structured at the data layer and the freshness comes from coordinator updates to a single shared sheet. Per-neighborhood indexes capture the geo-intent that drives garden discovery, and per-feature indexes (water access, organic-only, accepting-plots) capture preference-driven intent that converts well because gardeners searching at that intent are ready to apply. Closed-garden archives hold backlinks across closures so years of community building references survive.

The data layer becomes the urban agriculture SEO surface, and the coalition curates by approving rows rather than rebuilding pages for every seasonal cycle.