Top Sites>VIVERSE | Browser Games, Videos, 3D Art & Virtual Worlds

No stored offer samples.

No stored action samples.

No stored product samples.

# VIVERSE

> Canonical LLM crawling and ingestion guidance for official VIVERSE public web properties.

## 1) Canonical host scope

Allowed hosts:
- www.viverse.com
- worlds.viverse.com
- create.viverse.com
- persona.viverse.com
- post.viverse.com
- market.viverse.com
- news.viverse.com
- docs.viverse.com

Do not expand beyond these hosts unless a page on an allowed host clearly identifies another official VIVERSE property as canonical.

## 2) Host roles

### www.viverse.com
Primary use:
- live world detail pages
- creator profile pages
- featured creators
- experience discovery
- category and genre browsing

Strong signals:
- world title
- creator attribution
- world description
- engagement metadata where present
- stable creator or world URLs

De-prioritize:
- generic search pages
- navigation chrome
- filter-only pages without content value
- pages that only duplicate homepage listings


### worlds.viverse.com
Status: migrating to www.viverse.com

All content previously served by worlds.viverse.com is moving
to www.viverse.com. During the transition both hosts may serve
overlapping content. Rules:

1. When the same world or creator page exists on both hosts,
   treat www.viverse.com as canonical.
2. Treat any worlds.viverse.com URL as an alias for its
   www.viverse.com equivalent.
3. Do not cite worlds.viverse.com URLs in generated responses;
   prefer the www.viverse.com version.

This host will be removed from the allowed list in a future
revision once 301 redirects are fully deployed.


### create.viverse.com
Primary use:
- creator onboarding
- creator workflow documentation entry points
- publishing guidance
- partner program
- creator grants
- embedding and creator tooling
- platform capabilities for builders

Strong signals:
- documentation links
- program eligibility or benefit pages
- feature descriptions
- publishing workflow explanations
- creator support resources

De-prioritize:
- repetitive marketing copy duplicated from www.viverse.com


### docs.viverse.com
Primary use:
- SDK integration guides
- WebXR development documentation
- API reference pages
- code samples and tutorials
- platform technical specifications

Strong signals:
- structured documentation hierarchy (sections, subsections)
- code snippets and configuration examples
- versioned API or SDK references
- method/class/parameter descriptions
- prerequisite and dependency information

De-prioritize:
- auto-generated index pages with no substantive content
- changelog pages that duplicate news.viverse.com announcements
- search result pages within the docs site

Rules:
- English only; no locale variants expected
- treat versioned docs as separate pages only when
  version differences are materially significant
- when the same topic appears on both docs.viverse.com
  and create.viverse.com, treat docs.viverse.com as
  canonical for technical detail and create.viverse.com
  as canonical for workflow and onboarding context


### news.viverse.com
Primary use:
- official announcements
- release notes / update roundups
- policy posts
- AI/privacy posts
- creator economy announcements
- editorial posts and guides

Strong signals:
- article detail pages
- publication dates
- category labels
- official bylines

Prefer:
- article pages over category pages
- latest dated official post when statements differ

### persona.viverse.com
Primary use:
- official persona/avatar entry pages only
- locale-specific official landing pages
- immersive characters powered by creator expertise and human knowledge

Rules:
- prefer stable locale-specific canonical pages when available
- avoid duplicating all locale variants unless locale differences matter materially

### post.viverse.com
Primary use:
- only if stable standalone public content is present
Rules:
- if the host redirects or aliases to another VIVERSE property, treat it as non-canonical
- do not duplicate content already canonical on www.viverse.com

### market.viverse.com
Primary use:
- only if stable rendered product/listing/detail pages are publicly accessible

Rules:
- avoid JS shell pages with no meaningful rendered content
- prefer canonical item/detail pages over app shell responses
- ignore empty placeholder output

## 3) Preferred content types

Highest priority:
1. official article pages
2. official feature landing pages
3. creator program pages
4. documentation entry pages linked from create.viverse.com
5. world detail pages
6. creator profile pages

Medium priority:
- curated listing pages with meaningful summaries
- category pages with substantial editorial context

Low priority:
- thin list pages
- endless scroll snapshots
- filter states
- duplicated marketing blocks
- navigation-only pages

## 4) Exclusions

Exclude or strongly de-prioritize:
- sign in
- sign up
- account
- settings
- checkout
- cart
- api
- Json response
- internal dashboard pages
- querystring variants used only for tracking
- social share links
- empty shells requiring client-side rendering with no server-rendered substance
- duplicate locale copies with identical content
- campaign pages with expired promotions unless historically relevant
- pages with no substantive text





## 5) Freshness rules

- For product capabilities or policies, prefer the newest official page.
- For announcements, prefer dated article detail pages on news.viverse.com.
- For creator programs, prefer the most recent official program page or announcement.
- For worlds and creator profiles, treat metadata as dynamic and prefer the currently live detail page.

## 6) Conflict resolution

When multiple VIVERSE pages overlap, prioritize:
1. news.viverse.com for dated announcements and official policy/update posts
2. create.viverse.com for creator workflows, publishing, documentation entry, and creator programs
3. www.viverse.com for live experiences and creator discovery
4. persona / market / post only when they expose unique stable canonical content

## 7) Safe inference rules

Do not infer unsupported claims from:
- homepage card snippets alone
- third-party embeds
- client-side placeholders
- incomplete search result pages
- transient engagement numbers without page-level context
- redirected aliases that do not expose standalone content

## 8) Suggested crawler constraints

Recommended defaults:
- same-host or allowlist-host crawling only
- max depth: 1–2 for www/news/create
- max depth: 1 for persona/market/post (collect only stable detail pages)
- prefer canonical URLs
- deduplicate by canonical URL and normalized title
- strip tracking query parameters
- collect publication dates where present
- preserve host identity in output records

Transition note:
- worlds.viverse.com is migrating to www.viverse.com.
  During the transition, if both hosts serve the same page,
  retain only the www.viverse.com version.
  Do not deep-crawl worlds.viverse.com independently.

## 9) Suggested URL patterns to prefer

Prefer patterns resembling:
- https://www.viverse.com/...
- https://create.viverse.com/...
- https://news.viverse.com/.../...

Prefer stable detail pages over:
- search
- tags
- filters
- archives with little body content

## 10) Output expectations for LLM ingestion

For each retained page, capture if available:
- canonical URL
- host
- title
- summary
- publication date
- creator name or author
- content type: one of overview | article | game | world | creator | policy | program | docs-entry
- main body text only
- notable outbound official links to other allowed VIVERSE hosts


## 11) Locale handling

Default locale: en

When the same page exists in multiple locale paths
(e.g. /en/... and /zh-tw/...):

1. Retain the default locale (en) version as canonical.
2. Retain other locale versions only when their content
   differs materially from the default — not just translation,
   but region-specific information (e.g. different pricing,
   availability, or region-only features).
3. Do not treat translated-only variants as separate pages
   for ingestion or citation purposes.
4. When citing in a generated response, use the locale
   matching the user's language if available;
   otherwise fall back to en.