No. SleekRank reads only from sources you control: Google Sheets, CSV, JSON, Notion, or REST API. Keep pricing in a sheet you maintain, and update it as carriers change. Carrier APIs for plan data don't exist publicly, so most operators rely on a manual or partial-scrape workflow upstream of the sheet.

Yes. Define two page groups against the same data: one with urlPattern /carriers/{slug}/ pulling from the carriers tab, another with /phone-plans/{slug}/ pulling from plans. Each has its own base template, but cross-links between them stay consistent because they share the underlying sheet.

Use list mapping for perks — Apple TV+, Netflix, hotspot bonuses — and selector mapping for legal copy or footnotes that vary per plan. Carriers have wildly different fine print on deprioritization thresholds, so selector mapping per plan keeps the right caveat on the right page.

Pages refresh on the cacheDuration you set. For immediate updates after a major edit, flush manually with wp db query "DELETE FROM wp_PREFIX_sleek_rank_items" and run wp rewrite flush --hard if slugs are new. Most editorial teams flush after planned price changes and let cache expire naturally otherwise.

Yes. The base WordPress page stays as your template, regardless of theme or builder — Bricks, Elementor, Oxygen, GenerateBlocks, or native blocks all work the same way. SleekRank's mappings target the markup you already have; nothing about your design needs to change.

Map an OG image URL via meta mapping for static carrier-branded images. Pair with SleekPixel to generate dynamic OG images per plan that include the plan name, price, and data tier. Dynamic OG matters more for plans because the share preview is the only signal Twitter and Slack cards show.

For mid-month price tweaks, edit the cell and flush cache. For full rebrands like T-Mobile dropping Magenta for Go5G, change the slug column to redirect old URLs and add new rows for the new plan names. Set up 301s for the deprecated slugs in WordPress redirect plugins; SleekRank does not auto-redirect renamed rows.

Yes, if your data carries coverage. Add a regions column with comma-separated ZIPs or state codes per plan, and use selector mapping to render coverage notes. Visible and prepaid plans on T-Mobile have different coverage than postpaid, and selector mapping lets you say so on the right pages.