Page groups with 5,000+ generated URLs run on a single base template without issue. The data layer is cached and rendering re-uses your existing WordPress page, so the practical ceiling is your hosting plan and your sitemap budget. Most tribal art catalogues top out well below the technical limit because Google's crawl budget for new pages slows past a few thousand.

Yes. Edit your Google Sheet, push to your inventory REST endpoint, or update the CSV in the theme. SleekRank refreshes on the next cache cycle, and you can clear the cache manually from the admin or via WP-CLI. No theme deploy, no static site build, no engineering ticket.

Yes. SleekRank uses your existing base WordPress page as the template. Whatever theme, blocks, page builder, or custom CSS rendered that page renders every generated URL identically. Bricks, Elementor, Gutenberg, Oxygen, and classic themes all work because SleekRank operates on the rendered HTML.

Yes. They are real WordPress URLs with full HTML, sitemap inclusion, and per-page meta tag mappings for title, description, canonical, and og:image. The base template page is excluded from the sitemap and marked noindex automatically so it never competes with the generated listings.

Yes. You can branch a mapping based on a form column, or run multiple page groups against subsets of the data. A common pattern: /native-american-art/{slug}/ for pottery with a richer template, /native-american-art/textiles/{slug}/ for weavings with a leaner one.

On the next cache refresh the URL stops resolving and returns 404. The sitemap is regenerated automatically so search engines drop the URL cleanly. If you would rather redirect a sold piece to a similar example by the same maker, point the slug at a wildcard rule in your normal WordPress redirects plugin before deleting the row.

Make the data carry the difference. Maker hallmarks, period, dye history, stone provenance, conservation notes, and photographs at five angles all vary per row. Avoid copy-paste paragraphs that swap only the tribe. The richer the per-piece data, the lower the duplicate-content risk.

Yes. A URL pattern like /{tribe}/{form}/ produces /navajo/blankets/, /san-ildefonso/ollas/, /hopi/katsinas/ from a combined data set or two joined sheets. Use a tribe sheet and a form sheet, then run mappings against the cross-product.