Not directly. SleekRank renders from your data source. If your sheet has a script that pulls a service's quote API or scrapes its calculator, those numbers flow through on the cache cycle. The import layer lives upstream of SleekRank, which is responsible for rendering whatever is current in the source.

Both page groups read from the same services sheet. The pairs group joins two rows at render time using a slug pair from a pairs sheet. A change to a service row updates every page that references the service, including per-service, pair, and any category roll-ups, after the cache window expires.

Define another page group with a different URL pattern, source from a corridors sheet, and join to the services sheet. A /money-transfer/usd-to-inr/ landing page becomes its own SEO target, with the matching services rendered from the matrix.

Yes. Store the schedule as a JSON column keyed by send-amount band. List mapping renders the correct lineup per page. A comparison template can show fees for a $1,000 send on one tab and a $10,000 send on another, all from the same row.

Yes. The pairs sheet has its own verdict column. The per-service verdicts handle solo pages, and the pair verdict drives head-to-heads. If a pair row's verdict is empty, the template can fall back to a templated summary built from the two service rows' verdict snippets.

Update the owner and brand columns in the sheet. Every page that references the service reflects the new ownership after the cache window. Add a 301 from the old slug to the new slug if the brand name changes the URL, so backlinks keep their value.

Yes. Map an image URL column to og:image with the meta type, so each per-service page renders its own social card. Pairing with SleekPixel lets the OG image render on the fly from the row data, overlaying service name, headline margin, and a sample corridor on a styled background.

Drop the corridor from the supported_corridors JSON column and flush the cache. The corridor-specific pages stop rendering that service in their service list, and any per-corridor page falls back to the remaining options. If an entire service shuts down, set a discontinued flag and add a 301 to the successor.