No. The lookup math runs in your existing lookup widget, whether that is a JavaScript block that reads a JSON table or an iframe pointing at a hosted service. SleekRank only generates the test-specific landing page around the widget. It reads test rows from your sheet and renders the intro, score range explanation, test-specific FAQs, and related-test links, then drops your existing embed into the same place on every page.

Yes. Pass the percentile_table reference and min and max scores through query string or data attributes via a selector mapping. Each /percentile/{test}/ loads the lookup with that test's range and table already configured. A visitor enters a score and gets a percentile back without any selector or test-picker UI on the page itself.

Annually for most tests. College Board updates SAT percentiles each fall based on the prior cohort; ACT does similarly. LSAC publishes a three-year averaged percentile table that updates as each new year is added. Set the SleekRank cacheDuration to 86400 seconds and run a scheduled refresh after each test maker's update cycle to keep tables aligned with the current cohort.

Each test row carries distinct intro copy, test-specific FAQs, related-test pointers, and at least three unique entries on retakes, superscoring, or score-choice rules. SAT and ACT both target college admissions but have different score scales, section structures, and audience profiles. Avoid generic intros that would read identically across rows in the test catalog.

Yes. Add a subtests column that stores a list of subtest rows for that test. List mapping renders subtest lookups beneath the composite lookup. /percentile/sat/ shows EBRW and Math subscore lookups alongside the total; /percentile/gre/ shows Verbal, Quantitative, and Analytical Writing lookups. Each subtest carries its own range and percentile table within the same row.

Add a year column or a cohort_window column flagged with the years the percentile table covers. The test page intro explains which cohort the displayed table represents, so a visitor sees the current published percentile table and can read about how the cohort window is defined. Tables refresh through scheduled imports as the test maker publishes new windows.

Yes. Add a country column and let the urlPattern carry it: /percentile/{country}/{test}/. Score scales, percentile table structures, and audience profiles differ enough that each country gets its own slug namespace. The shared lookup widget handles any percentile table the row points to as long as the format matches the widget's expected schema.

Hide or remove the row, flush the SleekRank cache, and the /percentile/{test}/ stops resolving. Set up a 301 to the successor test or a parent category page if the retired URL had meaningful backlinks. A status column flagged active or archived makes the audit straightforward once the catalog spans every test you cover across admissions tiers and professional licensing exams.