Two patterns work well. Either store an array of image URLs in a JSON column (photos_json) and let SleekRank's list mapping render the grid, or use the WordPress media library and reference attachment IDs from the sheet. The JSON-array pattern is simpler for sites with images already on a CDN; the media-library pattern keeps everything inside WP for backups and search.

Yes. The base template controls rendering, so add native loading="lazy" or an Alpine helper to defer offscreen images. SleekRank only injects the photo list into the matched container; how the container hydrates is up to the template. For galleries with 100+ photos, an intersection-observer-driven loader keeps initial page weight low.

Add columns for license, model_release, location, and capture_date. Map them to selector targets on the page and to JSON-LD structured data so search engines can surface the metadata. For galleries with contractual restrictions, mark a published boolean and filter at the source level so unauthorised collections do not generate URLs.

Yes. Each generated URL is added to the SleekRank-managed sitemap automatically. The base template page is excluded and noindex'd because it is a scaffold, not real content. Submit the sitemap to Search Console after the first deploy and watch the URLs index over a few days.

SleekRank caches data per source for a configurable cacheDuration, typically 86400 seconds (one day) for galleries. Routine edits appear on the next cache cycle. Flush manually via wp db query "DELETE FROM wp_319_sleek_rank_items" for instant updates after a bulk import or a rights review pass.

No. SleekRank uses an existing WordPress page as the template, so any theme, block layout, or page builder works (Bricks, Elementor, Oxygen, blocks, classic editor). The base page is a normal page in every sense, SleekRank only intercepts the URL pattern to render rows. Switch builders later and the galleries survive the migration.

Yes. Run a second page group with a URL pattern like /galleries/theme/{theme}/ that pulls a filtered list of galleries via the list mapping. The same source feeds per-gallery pages and themed roundup pages. Year-based hubs like /galleries/2024/ work the same way using a date column.

Set a published boolean column to false and the row stops generating its URL on the next cache flush. For galleries with inbound links you want to preserve, add a redirected_to column pointing at a related collection, and emit a 301 from the template-side router so visitors land on the closest live URL.