Reviewed 3 August 2026
Data methodology
How Palpedia separates installed game data, official card-game data, editorial guidance and experimental calculations—and how every permanent page exposes those limits.
Source classes
| Area | Current source | Coverage | Freshness shown |
|---|---|---|---|
| Pals | Local Palpedia Palworld 1.0 catalog and portrait manifest | 299 entries; 139 include legacy narrative detail and 160 use core stats only | Version and data-status per profile |
| Items | Installed official-game-data extraction | 1,891 records with recipes, stats, unlocks and provenance where present | Dataset generated 2026-08-03; package 1.10.619.0 |
| Structures | Installed official-game-data extraction | 487 records with construction, technology and base fields | Dataset generated 2026-08-03; package 1.10.619.0 |
| TCG | English Palworld Official Card Game catalog | 242 cards and 4 product groups | Retrieved 2026-07-29 |
| Capture Lab | Illustrative local formula configuration | Demo scenarios, not official capture rates | Labelled as a demo on the page and in metadata |
Version policy
A page names a game or package version only when its underlying dataset carries that version. A page is not called “current” merely because it was regenerated today. Search titles use a version only where the page can be updated from a controlled source.
Missing and repeated fields
Missing locations, skill narratives, prices or drop rates are disclosed instead of inferred. Duplicate item names remain separate records with official IDs. Repeated descriptions are supplemented by factual IDs, categories, stats and relationships rather than spun into fabricated prose.
Identity and canonical URLs
Each indexable entity receives one clean URL. Aliases and JavaScript query templates point toward hubs or permanent profiles. TCG record IDs remain part of identity because two catalog records share printed number ESOUL-001.
Structured data policy
Database entities use WebPage or ProfilePage with Thing or CreativeWork facts. Fictional game items are not marked as commercial Product offers. Tools use WebApplication, guides use Article types, and breadcrumbs mirror links visible on the page.
Quality checks
The SEO build checks route counts, unique titles, unique descriptions, unique canonicals, one H1 per generated page, valid JSON-LD, local asset paths and sitemap membership. Broken or thin states stay out of the index until they meet the same contract.
Corrections and updates
Corrections should identify the URL, field, expected value, supporting source and game build. A dataset update is regenerated as a unit so page content, metadata, structured data, internal links and sitemap dates stay consistent.
What this methodology does not claim
Palpedia is an independent fan reference. Installed data can contain unused or internal records, editorial guides can age, and search visibility is never guaranteed. Revenue claims, official status and unavailable facts are not manufactured for SEO.