Yes. Configure a rest_api source pointing at the public endpoint, cache the response with a long cacheDuration like 604800 (a week) since structured country data rarely changes, then map fields like name.common, capital, currencies, and languages into the template via selector or tag mappings. SleekRank handles the JSON traversal so you can address nested fields directly.

Add an image_url column or use the REST Countries flags.png field, then map it via selector mapping to the relevant img tag's src attribute. For meta og:image, use a meta mapping. To brand the previews automatically, pair with SleekPixel and a templated suffix so /countries/japan/ gets its own branded social card.

SleekRank does not translate copy. Either run separate page groups per locale, each pointed at a localized data source like countries-en.json and countries-de.json with their own urlPatterns, or carry locale-specific columns like intro_en and intro_de and use selector mappings keyed off the current locale to switch copy. The first pattern is simpler at scale.

Yes. Add a related_slugs column with pipe-separated values like "south-korea\|china\|taiwan" and map it to a list of internal links targeting /countries/{slug}/. Each entry renders as an anchor; if you carry the country name alongside the slug, the link text reads naturally without an additional lookup.

Removing a row stops the URL from resolving on the next cache flush — the page returns a 404. If the URL had backlinks worth preserving, set up a 301 redirect via your host or a redirect plugin to a related country or a regional index. Soft-deleting via a status column is safer than hard removal during editorial reorganizations.

Each source has its own cacheDuration. Pages serve from the items cache between fetches, and you can flush manually with wp db query "DELETE FROM wp_319_sleek_rank_items" after a big update. For REST Countries, weekly caches are usually plenty; for an editorial sheet you maintain daily, set a shorter duration or flush after each editorial pass.

Yes. Add the JSON-LD block to the base template and inject country name, currency, and language via selector or meta mappings. For breadcrumbs, render a static "Home > Countries > {country}" pattern in the template and pull the country name from the row. Each /countries/{slug}/ ships valid structured data sourced from its row.

Carry both the canonical name and a display name column, plus a regions array if a country has dependencies you cover separately. Map display name into headings and og:title, but keep the canonical slug stable for URL integrity. Disputed regions can run on their own page group with explicit editorial framing on the base template.