Yes. Use a scales array on the row with a list mapping for one URL covering every gauge the shop stocks, or split the row per scale so the urlPattern emits a separate URL per scale-shop combination. Row duplication wins on long-tail "HO scale Denver" queries because each scale gets its own title and meta description.

Not directly. SleekRank reads JSON, CSV, Google Sheets, Notion, or a REST API on the configured cacheDuration and renders whatever sits in the source. If your shop platform exposes a stock JSON feed, point a data source at it with a short cache. There is no native integration with specific model train inventory systems.

Duplicate the row per location so each storefront gets its own slug, city, and hours. The shared shop name and brand list stay identical across rows. Per-location URLs rank for city-specific searches like "M.B. Klein Baltimore" while a parent listing under /model-train-shops/m-b-klein/ can roll all locations together.

Yes. SleekRank renders through your existing base WordPress page, whatever builder created it. Tag, selector, and list mappings target real DOM IDs and classes on the page, so Bricks, Elementor, Gutenberg, Oxygen, or a classic theme all work without rewriting the template.

The base page is noindexed automatically. Generated URLs are indexable and each carries its own meta title, description, h1, and og:image driven by row data, which keeps the pages distinct enough to avoid duplicate-content penalties. The data-shape variance across shops (scales, brands, hours, layout space) does most of the differentiation work.

Delete the row, clear the SleekRank cache, and the URL returns a clean 404 on the next render. The slug drops out of the XML sitemap automatically. If you want the page to redirect instead, add a redirect column to the sheet and handle that in a small filter on the base page, or set up a 301 in your WordPress redirect plugin.

Yes. Conditional blocks on the base page show or hide based on row values. A shop with a layout-space column reading zero hides the layout block. A shop with a member-program field renders an extra section. The base page covers every case and the row data decides what shows.

Yes. SleekRank supports multiple sources per page group. Layer a Google Sheet of shop basics with a JSON feed of current event nights, and the page renders both. Cache durations are set per source so the slow-moving roster refreshes daily while the event feed refreshes hourly.