No, the JS layer on the base WordPress page does. SleekRank delivers the questions, options, and correct-answer flags as DOM data attributes or a JSON blob. Your script reads that data, handles selection, calculates the score, and reveals explanations. Common patterns are Alpine.js for simple quizzes or a small custom script for more complex flows. The plugin's job is the content layer; interactivity stays yours.

Yes, in the JS layer on the base page. SleekRank renders questions in source order; your script can shuffle them on page load. For larger pools where each visit shows ten of fifty questions, render the full bank to a hidden element and let the script sample. The data layer makes the full bank addressable; the interaction layer decides what the user sees.

Carry an explanation per question, either as a parallel pipe-separated column or a nested JSON field. List mapping renders each explanation alongside its question in a hidden div. The JS reveals the relevant explanation when the user picks an answer. Both correct and incorrect choices can carry distinct explanations if you carry per-option explanations as a deeper nested array.

SleekRank handles the page rendering, not user accounts. For score persistence, integrate your existing membership plugin or a serverless function on the base page that posts the score to your CRM after the user submits an email. The interaction owns the data flow; SleekRank just provides the canonical question bank that drives every quiz consistently.

Add a category column with values like code, geography, business. Render category pills via selector mapping, run a /quiz/ index page filtered by category, or run multiple page groups under /quiz/code/{slug}/ and /quiz/business/{slug}/ for separate URL trees per category if your information architecture calls for it.

Yes, that is the JSON-file source pattern. Check a quiz-bank.json file into the theme repo. Adding or editing questions becomes a pull request, reviewed for accuracy before going live. Engineering teams who treat course content as code prefer this; editorial teams who prefer Sheets or Notion can use those instead with the same mappings.

No. SleekRank only places existing content into the template. Question authoring stays with subject-matter experts. Pair with SleekAI to draft initial banks, but a human should always review for factual accuracy and pedagogical fit before adding rows. The plugin's value is removing the publishing friction, not generating substantive educational content.

Yes. Add Quiz JSON-LD to the base page, with hasPart entries for each Question. Selector and list mappings populate the questions and answers from the same columns the visible quiz reads. Validate with the Rich Results Test once. Schema and visible content stay locked together because they share the source, eliminating the consistency problems that hand-authored quizzes accumulate over time.