I have been building a small site for Honor of Kings Global called HOKMeta:
It started from a simple problem: when I looked for hero builds, counters, arcana, and item choices, a lot of content felt either too thin or too far away from how players actually make decisions before a ranked match.
Most searches are not generic. Players search for very specific things:
- Hou Yi build 2026
- best arcana for Hou Yi
- how to counter Angela
- Marco Polo build and counters
- best marksman HOK
So I decided to build the site around those practical questions.
Current build snapshot
The current version is still early, but it is already more than a set of blog posts.
As of the 2026-06-30 production build, the site generated 1,985 static pages.
The data set currently covers:
- 116 hero pages
- 116 hero counter pages
- 105 item pages
- hero guide pages for popular searches like Hou Yi, Angela, Marco Polo, Garo, Luban No.7, Daji, Li Bai, Wukong, Dolia, and Augran
- public JSON endpoints for hero and item data
Example pages:
- Main site: https://hokmeta.com/
- Hou Yi build page: https://hokmeta.com/hero/hou-yi/
- Hou Yi guide: https://hokmeta.com/learn/hou-yi-guide/
- Damage calculator: https://hokmeta.com/tools/damage-calculator/
- Counter picker: https://hokmeta.com/tools/counter-picker/
- Public hero JSON: https://hokmeta.com/api/heroes.json
Why static export
The site is built as a static export because most pages are data-driven and do not need server-side rendering at request time.
For this type of project, static output has a few advantages:
- pages are fast to serve
- hosting is simple
- crawlers can read the content directly
- public JSON files can be generated alongside the site
- content can be refreshed through sync scripts and rebuilt
The tradeoff is that freshness needs to be handled intentionally. If the game patch changes, the data and generated pages need to be updated together.
Why tools, not only content
Content is useful, but for a game like Honor of Kings it gets outdated quickly.
A tier list article can help someone once. A practical tool can bring them back.
That is why I added:
- a damage calculator for testing item builds against target templates
- a build compare tool for checking which build performs better in different matchups
- a counter picker for draft questions
- an item database so item names and stats are easier to check
The goal is not to replace player judgment. The goal is to make common decisions faster:
- Can this build actually kill a tank?
- Is this item core or just situational?
- Who counters this hero?
- What should I build first if I am behind?
The SEO lesson so far
The biggest lesson is that "more pages" is not the same as better coverage.
The pages that matter most are the ones that match a player's exact problem.
A Hou Yi player does not just need a generic hero profile. They need:
- the current build
- arcana and spell choices
- what to do in lane
- what counters them
- when to avoid picking the hero
- a tool to test item decisions
That is why the internal links are built around:
txt
hero page -> guide -> counters -> tools
Top comments (0)