Yes. Use a brands array on the row with a list mapping for one URL covering every brand the shop stocks, or duplicate the row per brand so the urlPattern emits a separate URL per brand-shop combination. Row duplication wins on long-tail "Lindberg dealer San Francisco" queries because each brand gets its own title and meta.

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

Add an exam-schedule column listing available days. A selector mapping renders the schedule in the page, and a JSON feed source layered on top can update the next-week schedule on a one-hour cache. Patients see accurate availability without the shop owner maintaining a separate page.

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

Yes. Add an image URL column and configure a meta mapping for og:image targeting it. For dynamic cards combining brand badge, city, and shop name, pair SleekRank with SleekPixel and reference the generated image URL via the same meta mapping path.

Edit the brands column to remove the dropped brand, then clear the SleekRank cache. The shop URL keeps accumulated link equity since the slug stays the same. The hub for the dropped brand auto-removes the shop on the next render. No stale claims linger.

Yes. Conditional blocks on the base page show or hide based on row values. A shop without an on-site optometrist hides the exam block. A shop with a kids-frames specialty renders an extra section. The base page handles every shape and the row decides what shows.

Yes. SleekRank supports multiple sources per page group. Layer a Google Sheet of shop basics (24 hour cache) with a CSV of insurance plans accepted (12 hour cache), and both render on each shop page. Sources merge by shop slug, so insurance updates do not touch the basics.