# GGEMU Full Discovery

> Detailed machine-readable guidance for crawling and retrieving public game information from GGEMU.

## Site Scope

- Public retro game catalog with individual game pages.
- Public collection pages containing curated groups of games.
- Public blog posts and discovery-oriented library pages.
- Multilingual localized routes for the main public site.

## Crawl Priority

1. https://ggemu.com/llms.txt
2. https://ggemu.com/llms-full.txt
3. https://ggemu.com/sitemap.xml
4. https://ggemu.com/.well-known/api-catalog
5. https://ggemu.com/.well-known/openapi.json
6. https://ggemu.com/docs/api

## Supported Locales

- en, zh-CN, zh-HK, hi, es, fr, de, ru, pt, ja, ko, vi, it, th, tr
- Public content is available under locale-prefixed routes such as /en, /zh-CN, /ja, /fr, and similar.
- If only one localized page is needed as a canonical crawl baseline, prefer /en URLs from the sitemap.

## Important Public URL Patterns

- Home: https://ggemu.com/{locale}
- Game detail: https://ggemu.com/{locale}/game/{url_slug_or_id}
- Collections index: https://ggemu.com/{locale}/collections
- Collection detail: https://ggemu.com/{locale}/collections/{id}
- Blog index: https://ggemu.com/{locale}/blog
- Blog detail: https://ggemu.com/{locale}/blog/{slug}
- Game library: https://ggemu.com/{locale}/library/games
- Platform library: https://ggemu.com/{locale}/library/platforms and https://ggemu.com/{locale}/library/platforms/{platform}
- Genre library: https://ggemu.com/{locale}/library/genres and https://ggemu.com/{locale}/library/genres/{category}
- Developer library: https://ggemu.com/{locale}/library/developers and https://ggemu.com/{locale}/library/developers/{developer}

## Structured Discovery Files

- LLMs.txt: https://ggemu.com/llms.txt
- LLMs full: https://ggemu.com/llms-full.txt
- API catalog: https://ggemu.com/.well-known/api-catalog
- OpenAPI: https://ggemu.com/.well-known/openapi.json
- API docs: https://ggemu.com/docs/api
- Agent skills index: https://ggemu.com/.well-known/agent-skills/index.json
- Sitemap: https://ggemu.com/sitemap.xml

## Public API Endpoints

- Health: https://ggemu.com/api/health
- Active live rooms: https://ggemu.com/api/live/rooms?limit=20&page=1&sort=popular
- Search games: https://ggemu.com/api/games/search?query=mario&limit=20&page=1&sort=popular
- Game detail: https://ggemu.com/api/game/detail?id={url_slug_or_id}
- Search collections: https://ggemu.com/api/collections?query=capcom&limit=12&page=1
- Collection detail: https://ggemu.com/api/collections/{id}?limit=20&page=1
- Search blog posts: https://ggemu.com/api/blog-posts?keyword=arcade&limit=12&page=1
- Blog post detail: https://ggemu.com/api/blog-posts/{id_or_slug}
- Search API useful query parameters include query, keyword, platform, category, language, page, limit, and sort.
- Detail API returns a sanitized public game record and may include session-aware like state when a valid session cookie is present.

## Recommended Retrieval Workflow

- Discover candidates from sitemap, library pages, or the search APIs.
- Use /api/games/search for keyword or taxonomy filtering.
- Use /api/game/detail for one exact game by url_slug or id.
- Use the localized game page or markdown representation to capture richer descriptive text and related links.

## Public Game Data You Can Expect

- Core identifiers: _id, url_slug, slug, name.
- Descriptive metadata: description, how_to_play, developer, released_year, keywords.
- Taxonomy: platform, categories, languages.
- Gameplay metadata: players, net_play, live_mode, play_online, leaderboard, age_rating.
- Engagement metrics: likes_count, comments_count, views_count, plays_count.
- Media fields may include game_cover, game_video, and promotional_media.

## Markdown Support

- Send 'Accept: text/markdown' to supported public pages to receive markdown instead of HTML.
- Supported markdown pages: https://ggemu.com/, https://ggemu.com/en, https://ggemu.com/en/game/{url_slug_or_id}, https://ggemu.com/en/collections, https://ggemu.com/en/collections/{id}, https://ggemu.com/en/blog, https://ggemu.com/en/blog/{slug}

## Public Indexing Boundaries

- Public indexing should stay on public site pages, public discovery files, and the allowlisted public game APIs.
- Do not rely on private, admin, authenticated-only, or account-specific routes.
- Non-public areas commonly include /api/ private endpoints, locale-specific /admin, /account, and /login routes.

## Freshness Guidance

- Sitemap and discovery APIs are suitable for recurring recrawls.
- Game popularity and new-arrival sections can change more often than static blog and policy pages.
- When exact current catalog data matters, prefer the public APIs over cached assumptions.