Tier list maker methodology

Tier List Maker Methodology and Source Review

Every public template needs an exact question, a checked roster, complete image coverage, and an update boundary a reader can verify.

Query and scope

One page owns one search intent and states exactly what the roster includes.

Roster check

Stable item IDs, counts, groups, and exclusions must agree before publication.

Image review

Every item needs a working image, source record, dimensions, and rights state.

Static release

Only reviewed pages enter the sitemap and receive a substantive update date.

Source and roster review

A template begins with a narrow user question. The Pokemon starter tier list maker asks users to compare 27 released base starters from Gen 1-9. The Pokemon starter evolution tier list maker asks a different question and includes all 81 released base, middle, and final species.

Counts, generation groups, National Dex identifiers, inclusions, and exclusions must agree. Announced characters stay outside a released roster until the launch state and usable assets have been reviewed.

Editable templates and personal rankings

Template pages provide named image collections and an empty board. A user's ranking is an expression of preference, not an objective claim. Local drafts are not treated as published content or search pages.

Editorial references are labeled opinions

An optional reference board is an editorial starting argument with a date and stated criteria. It is never called community consensus, a live ranking, or a scientific result without a real auditable dataset.

Discovery, sources, and freshness

Candidate discovery may monitor permitted public sitemaps, RSS feeds, and official announcements. A new URL or sitemap timestamp is only a signal to review. It does not prove a roster change, ranking, image right, or release status.

Verified content is stored in reviewable local data and published as static HTML. Cloudflare Pages serves the finished files; the production page does not fetch source data or generate SEO copy at request time.

Correction and update handling

A substantive correction updates the affected roster, source note, scope copy, and page date together. A changed roster receives a new template revision so older share links are not silently interpreted against different items.