It generates one WordPress page per row in the PT bank. Each page is a real URL with its own title, meta description, schema, and Twig template. The stimulus, five choices, correct response, question type tag, and teach-back explanation all read from that row, so the page is fully populated the moment the row exists.

Yes. SleekRank reads CSV, JSON, REST endpoints, and custom post types. Most LSAT prep sites keep the released-items JSON in the theme at a path like src/pages/lsat/items.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 PT number, section, type, and item index, like pt-87-lr-assumption-q14. SleekRank does not auto-generate slugs, so item ids and URLs stay consistent across the entire PT archive.

Edit the row or remove it from the source, then clear the SleekRank item cache. Updated rows rebuild their page at the next interval with the new explanation or tags. Removed rows drop their page and any related-items grid links that pointed to them.

Each page reads its own row, so title, meta description, Open Graph image, and JSON-LD schema are filled in with the PT, section, and question type. SleekPixel can render a per-item OG image with the PT number and type burned in, so social previews look distinct without manual asset work.

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

Yes. SleekRank exposes a related entries helper that filters the same dataset by a category or type field. Each page can show other items of the same type, or items from the same PT, sourced from row data instead of editor-maintained cross-links.

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 PT row, and Yoast or Rank Math see the URLs as native theme content.