Chess.com on any website.

Chess.com is a closed-source commercial platform, but the company maintains a free, well-documented Public Data API at chess.com/news/view/published-data-api covering everything a third party needs to embed a player profile. The API base is api.chess.com/pub, and the endpoints include player profile (api.chess.com/pub/player/{username}), stats across every time control (api.chess.com/pub/player/{username}/stats), monthly game archives in PGN format (api.chess.com/pub/player/{username}/games/{YYYY}/{MM}), club details (api.chess.com/pub/club/{url-id}), country leaderboards (api.chess.com/pub/country/{iso}), title-holder lists (api.chess.com/pub/titled/{title}), and Daily Puzzle of the day (api.chess.com/pub/puzzle). All endpoints accept unauthenticated GET requests, return JSON, and are rate-limited generously enough for any normal third-party embed use. There is no OAuth flow, no developer console, no quota application form. This matters because chess.com's main-site UI changes regularly (the live board, the home feed, the rating histogram have all been redesigned in the last three years), and any widget built on web scraping breaks every redesign. The Public API stays stable. Poper queries it directly, caches at the CDN edge, and re-fetches on the configured sync interval. The result is a widget that keeps showing your latest games and ratings even when chess.com is shipping a new front-end weekly.

The Netflix series The Queen's Gambit aired in October 2020 and triggered the largest sustained surge in chess interest since the Bobby Fischer era. Chess.com's monthly sign-ups jumped roughly five-fold in the months that followed, and the platform crossed 100 million accounts in late 2022, then 150 million in 2025. The boom never really cooled down because it merged with the parallel rise of the chess streamer economy on Twitch and YouTube. Hikaru Nakamura, GothamChess, BotezLive, Anna Cramling, Eric Rosen, and dozens of other streamers built audiences in the millions playing Chess.com games on stream, and their viewers signed up to play themselves. By 2026 chess streaming is a measurable subgenre with consistent top-100 channels on Twitch in the Chess directory. For any of those streamers, having a live Chess.com rating banner on the personal site or sponsorship page is table stakes. A coach who picks up new students from stream traffic, a content creator who runs Patreon tiers around playing improvement, or a tournament organizer running over-the-board events with Chess.com qualifiers all need the same thing: a single embed that always shows current rating across time controls, recent games, and tournament wins. The widget audience is large enough now that Chess.com itself ships official widgets for the Daily Puzzle and a single Game of the Day, and the absence of a full profile widget from chess.com itself is the gap third-party widgets like this one fill.

Magnus Carlsen's relationship with chess.com has been the most-discussed governance story in chess since 2023. Carlsen vacated his classical World Champion title in 2023 partly in protest of the existing championship cycle, then launched his own platform Take Take Take and became the public face of the Champions Chess Tour run on chess.com. Persistent rumors have circulated that chess.com is in acquisition talks with Take Take Take or with Carlsen's broader Magnus Group portfolio, none of which the parties have confirmed publicly as of 2026. Whatever the corporate outcome, the practical effect for embed widgets is that Chess.com remains the dominant commercial chess platform, the Public API remains free and unauthenticated, and the player base keeps growing. A widget that depends only on the Public API surface keeps working through any ownership changes because the API contract is open and stable, while a widget that depends on undocumented internal endpoints breaks every redesign. The right architectural choice for a third-party Chess.com widget in 2026 is also the only choice that survives the next five years of platform evolution: query the Public API, cache at the CDN edge, and never touch internal endpoints. Poper takes that approach and is committed to it as long as the Public API remains the Chess.com developer surface.

Chess.com and Lichess are the two platforms serious chess players actually use. Chess.com is the commercial market leader with roughly 150 million accounts, video lessons from top GMs, a tournament prize pool, Opening Explorer with master-game data, and a coaching marketplace. Lichess is the free, open-source, donation-funded alternative with about 12 million accounts, a culture of openness, the standout Studies feature for shareable annotated analysis, and serious variant play (Atomic, Crazyhouse, King of the Hill, Antichess) that chess.com supports more lightly. Many serious players run accounts on both and have different ratings on each because the rating pools are independent. For a widget audience, this matters in three ways. First, a Chess.com widget should not pretend Lichess does not exist. The right pattern is to make it easy to run a Chess.com widget and a Lichess widget side by side on the same page, so a coach who plays on both shows ratings from both. Poper supports exactly this: ship the chess-feed widget for the chess.com half and the lichess-feed widget for the Lichess half, both pulling from their respective free public APIs, both styled to match. Second, Chess.com features that Lichess does not have (chess.com Diamond and Premium subscriptions, prize-pool tournaments, the official Daily Puzzle, the Opening Explorer with master-game data) should be visible on the widget so a Diamond subscriber's investment shows up. Third, the variant rating pools are different on each platform. If you play Bughouse seriously, that is a chess.com surface. If you play Crazyhouse seriously, that is a Lichess surface. The widget should honor the pool a player actually uses rather than averaging across platforms. Poper renders Chess.com Bullet, Blitz, Rapid, Daily, and the chess.com-specific variants natively while leaving the Lichess variants to the Lichess widget.

The single most common SEO mistake when embedding any profile-based widget is duplicating personal-brand content without a canonical reference. Search engines see the same name, country, and rating data on chess.com and on yoursite.com, treat one as the original, and either suppress the other from rankings entirely or split ranking signal between the two URLs. The fix is to emit Schema.org Person structured data with a canonical URL pointing back to the original chess.com profile, telling Google explicitly that yoursite.com is republishing public profile data and chess.com is the authoritative source. Poper handles this automatically. Every embedded Chess.com profile emits Person JSON-LD with name, image, country (mapped from the chess.com country field), URL set to the canonical chess.com profile URL, and a sameAs array pointing to the chess.com source. Tournament result blocks emit additional Event JSON-LD where applicable, and the Daily Puzzle block emits its own canonical reference to the chess.com puzzle URL. Visitors browsing your site see the profile rendered inside your design, but search engines see a clear signal that chess.com remains the canonical source of the underlying data. Your chess.com profile keeps its rating-page ranking for queries like 'GMHikaru chess.com' or 'your-username Elo', and your site receives the SEO benefit of a rich, content-heavy profile block without competing against your chess.com profile for the same query. Combined with the asynchronous loading and global CDN edge caching that keeps the widget under 40KB gzipped and lazy-loaded below the fold, the performance and SEO posture of a Chess.com feed widget is among the cleanest of any embeddable profile widget on the market in 2026.