No. SleekRank does not generate asteroid content. You provide the sheet, number, name, diameter, orbit class, and so on, and SleekRank renders one page per row. Editorial responsibility for orbital and physical accuracy stays with you. SleekRank's role is the rendering and routing layer between the dataset and the live site.

Yes. Add an image_url column to the sheet and map it via a tag or selector mapping that injects an . For Open Graph cards, pair SleekRank with SleekPixel for dynamic OG images that take the slug as a parameter and render a branded card with the number and diameter.

Add an orbit_class column (Apollo, Aten, Amor, Main Belt, Trojan) and render it via a selector mapping. The same template can handle every class; pages just show different orbital parameters, and NEOs carry close-approach arrays while Trojans carry libration points.

Store close approaches as an array column with date, distance in lunar distances, and relative velocity per row, then render via a list mapping. The dataset carries the records, the template carries the formatting.

SleekRank caches the source per cacheDuration set in seconds. Edit the sheet, clear the SleekRank cache via WP-CLI or admin, and the next request rebuilds the page with new data. For asteroid catalogs (a slow-changing domain) set cacheDuration high so the sheet is not constantly refetched.

Yes. Each generated URL is a real WordPress page included in the sitemap. The base template is excluded automatically so the scaffolding does not compete with real asteroid pages. Run a rewrite flush after adding new slugs so the routes resolve immediately on production.

Yes, but that's a hub page rather than the per-asteroid URL. Build /asteroids/ as a filter page that pulls from the same dataset and filters by orbit class, diameter range, or spectral type. SleekRank handles the per-asteroid detail pages; the hub uses the same source as the single point of truth.

Pick a canonical slug (usually the name once one is assigned, otherwise the provisional designation), and store the number and provisional designation as separate columns. Add redirects from old provisional-slug URLs so external citations resolve to the current page.