It generates one WordPress page per row in the outline source. Each page is a real URL with its own title, meta description, schema, and Twig template. The section, subskill, topic name, key concepts, and sample item types all read from that row, so the page is fully populated the moment the row exists in the dataset.

Yes. SleekRank reads CSV, JSON, REST endpoints, and custom post types. Most GMAT prep sites keep the outline JSON in the theme at a path like src/pages/gmat/topics.json, point SleekRank at it, and let the route generate pages. Switching to a CPT later does not change the URLs.

The slug column on each row is the authoritative URL fragment. Most sites combine the section, subskill, and topic name, like di-data-sufficiency-quant-statements. SleekRank does not invent slugs, so GMAC outline labels and URLs stay aligned across rebalances and revisions.

Edit the affected rows or append new ones, then clear the SleekRank item cache. Updated rows rebuild their pages at the next interval with new subskill labels, key concepts, or item types. Removed topics drop their pages and any internal links the related-topic grid had pointing to them.

Each page reads its own row, so title, meta description, Open Graph image, and JSON-LD schema are filled in with the section, subskill, and topic. SleekPixel can render a per-topic OG image with section and subskill burned in, so social previews are distinct for every GMAT topic without manual asset work.

Add a status field to each row and exclude rows where status is deprecated or draft. SleekRank reads the filter on every cache cycle, so disabled rows produce no page, the sitemap drops them, and related-topic grids stop linking to them across the rest of the GMAT archive.

Yes. SleekRank exposes a related entries helper that filters the same dataset by a category or subskill field. Each page can show other topics in the same subskill or section, sourced from row data instead of editor-maintained cross-links across hundreds of GMAT pages.

SleekRank generates real pages in the WordPress page hierarchy, so SEO plugins read them like any other post. Title tags, meta descriptions, canonicals, sitemaps, and JSON-LD all populate from the underlying outline row, and Yoast or Rank Math see the URLs as native theme content.