amiibo Games Use Map: How to Structure “amiibo Works With…” Pages

Instead of one giant list that becomes outdated, build a structured map: a master index plus repeatable per-game pages. That scales, stays clean, and is easy to update.

The Target Structure (Simple and Scalable)

• 1) Master page: “amiibo Compatibility Map” (the hub).
• 2) Per-game pages: “amiibo in {Game}” with consistent sections.
• 3) Per-series pages (optional): “amiibo for Zelda / Smash / Splatoon…”
• 4) Per-figure pages (optional later): “{Figure} — Works With…”

Master Page: What It Should Contain

1. A short explanation of how amiibo works (NFC → game-defined features).
2. A filtered table concept (later): game → platform → effect types.
3. Quick links to per-game pages (alphabetical + by franchise).
4. A note about updates/reprints and that effects can differ by game version.

Per-Game Page Template (Copy/Paste Standard)

• What amiibo do in this game (summary).
• Effect types: unlocks, cosmetics, items, daily bonuses, training/saves.
• Which amiibo work: list by series/character (with notes).
• How to use: where to scan, how often, restrictions.
• Is it worth it?: play value rating (for your audience).
• Collector note: editions/figures most relevant for the game.

Effect Taxonomy (Stable Labels)

• Unlock (content opens).
• Cosmetic (skins/costumes).
• Boost (items/consumables).
• Daily (once per day bonuses).
• Training (learning/AI data).
• Save/Custom (stores settings or loadouts).

Internal Linking Rules (So SEO Stays Clean)

1. Master page links to every per-game page.
2. Per-game pages link back to master + relevant series pages.
3. amiibo care/storage and editions pages are linked in a “Collector Notes” section.
4. Avoid duplicate pages: one canonical per game, then update over time.

This structure turns a messy list into a maintainable library. Start with 10–20 top games, then expand steadily.