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 phonograph catalogues top out below the technical limit because the supply of original-condition machines is small.

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 maker column, or run multiple page groups against subsets of the data. A common pattern: /phonographs/{slug}/ for Edison and Victor machines with a richer template, /phonographs/european/{slug}/ for Pathe and Columbia issues with a leaner one keyed off the same sheet.

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 machine to a similar model, point the slug at a wildcard rule in your normal WordPress redirects plugin before deleting the row.

Make the data carry the difference. Serial numbers, horn types, case woods, motor specs, restoration notes, and reproducer types all vary per row. Avoid copy-paste paragraphs that swap only the model letter. The richer the per-machine data, the lower the duplicate-content risk.

Yes. A URL pattern like /{maker}/{model}/ produces /edison/standard-model-a/, /edison/amberola-30/, /victor/victor-vi/ from a combined data set or two joined sheets. Use a maker sheet and a models sheet, then run mappings against the cross-product.