Editorial sitemap
Every public editorial route published by the Lvlup desk. Coverage is grouped by editorial desk (hubs) and by brand-intent (Brand SERP). An XML mirror is at /sitemap.xml.
Eight editorial desks
Tournaments
APAC Major, EMEA Championship, Americas Open, Global Finals.
Matches
Live fixtures, broadcast schedules and editorial previews.
Teams
Verified rosters, region tags and active sponsorships.
Players
Role dossiers, signature plays and role-meter spread.
Games
Five chapters across 15 active titles — strategy context and patch-watch.
Guides
Beginner, bracket-follower and coach / analyst reading paths.
News
Roster moves, broadcast deals, format and patches.
Esports overview
The cross-title map of the scene.
Fourteen canonical brand-intent pages
Login
App
Download
APK direct
Referral code
Bonus code
Editorial review
How-to-play
Customer care
Is Lvlup legal
Owner & company
Delete account
Official website
Wallet & KYC
Trust, contact and editorial
How to read the sitemap
The editorial sitemap is grouped by coverage desk. Below is the working method for reading the sitemap.
Coverage desks — eight entries
The eight coverage desks are the homepage, tournaments, matches, teams, players, games, guides, news, esports. The homepage is the newsroom's front page; the remaining eight desks are the newsroom's editorial map.
Brand SERP cluster — fourteen entries
The fourteen canonical brand-intent pages are the Brand SERP cluster. The cluster covers the editorial questions a reader asks about Lvlup itself.
Utility — six entries
The six utility pages are trust and contact surfaces. The utility covers the editorial standard, the corrections log, the responsible-play boundary, the privacy policy and the terms.
How a reader can use the sitemap
Below is the desk's working method for using the editorial sitemap. The method is published on this page for editorial transparency.
Use one — find a coverage desk
A reader who wants to follow a coverage desk uses the editorial sitemap to find the desk's entries. The entries map to the eight coverage desks.
Use two — find a brand-intent page
A reader who wants a brand-intent page uses the editorial sitemap to find the page in the Brand SERP cluster. The cluster covers fourteen canonical brand-intent pages.
Use three — find a utility page
A reader who wants a utility page uses the editorial sitemap to find the page in the utility section. The utility section covers six trust and contact surfaces.
Use four — find an archive entry
A reader who wants an archive entry uses the corrections log; the editorial sitemap lists the public archive entry as a utility entry. The reader who wants the deeper archive uses the corrections log search.
Where the editorial sitemap is updated
The editorial sitemap is updated whenever the desk publishes a new page. The XML sitemap is updated at the same time.
Reader questions on the editorial sitemap
Below is the desk's working method for the most common reader questions on the editorial sitemap.
Why does the sitemap list 30 entries?
The editorial sitemap is grouped by coverage desk (8 entries + homepage), Brand SERP cluster (14 entries) and utility (6 entries). The total is 30.
How do I find a page not on the sitemap?
A reader who wants a page not on the sitemap searches the editorial archive; pages that are retired are in the archive.
How do I find the XML sitemap?
The XML sitemap lives at /sitemap.xml. The editorial sitemap (this page) is the reader-facing version of the same route map.
How do I download the sitemap?
The XML sitemap is downloadable. A reader can save the XML file locally and re-walk the route map offline.
How do I check whether a page is retired?
A retired page is filed in the editorial archive. A reader can check the editorial colophon for the retired entry.
How do I request a sitemap entry for a new page?
A new page request is sent to the corrections inbox. The desk reviews the request within 14 hours and adds the entry on the next sitemap update.
How do I report a sitemap error?
A sitemap error is sent to the corrections inbox. The desk walks the error within 14 hours and publishes a corrections log entry where the error is confirmed.
Working method — how the desk handles a reader sitemap request
Below is the desk's working method for a reader sitemap request. The method is published on this page for editorial transparency.
Step one — request lands
A reader sends a sitemap request to the corrections inbox. The sitemap editor receives the request.
Step two — editor reviews the request
The editor reviews the request against the editorial sitemap and the editorial archive. The editor identifies the requested page.
Step three — editor publishes the entry
Where the entry is missing, the editor publishes the entry on the editorial sitemap within 14 hours. The entry is also added to the XML sitemap.
Step four — editor pushes the entry
The editor pushes the entry to the reader via the desk's alert channel. The push happens within 14 hours.
Step five — editor updates the editorial colophon
The editor updates the editorial colophon with the new entry. The colophon carries the latest editorial route map.
Step six — editor files the entry under the editorial archive
The editor files the entry under the editorial archive at the end of the editorial cycle.
What the editor does not do
The editor does not run a public dispute on the sitemap.
The editor does not publish an entry on the sitemap that is not yet verified against the live source ladder.
The editor does not publish a sitemap entry that disagrees with the publisher's published feed.