themeparks.wiki

mx

mx.zoho.eu

mx2.zoho.eu

mx3.zoho.eu

ns

jay.ns.cloudflare.com

pam.ns.cloudflare.com

caa

txt

v=spf1 include:zohomail.eu ~all

google-site-verification=SPLkPgCzzeu9OEldu7eF0yhYcagfw2XKHb1UM9C_7OI

dmarc

v=DMARC1; p=quarantine; rua=mailto:jamieholding10@gmail.com; ruf=mailto:jamieholding10@gmail.com; sp=quarantine; adkim=r; aspf=r

# NOTHING IS DISALLOWED HERE, AND THAT IS DELIBERATE.
#
# This file used to carry:
#
#   Disallow: /admin
#   Disallow: /login
#   Disallow: /profile
#   Disallow: /checkout
#
# which did the opposite of what it looks like it does. Disallow controls
# CRAWLING, not INDEXING. Google may still index a URL it is forbidden to fetch
# — from a link, a sitemap, anywhere — and because it is forbidden to fetch it,
# it can never read the page to learn that the page did not want indexing. The
# result is a URL in the index with no title and no description, and no way to
# get it out, because every signal that would remove it lives inside a response
# Google is not allowed to request.
#
# That is not hypothetical. Search Console reported it on 2026-09-15:
# "Indexed, though blocked by robots.txt" for https://themeparks.wiki/login.
#
# THE RULE: to keep a page out of the index you must LET the crawler in and tell
# it no in the response. Those pages now carry `X-Robots-Tag: noindex`, set in
# public/_headers, which is honoured precisely because the page is crawlable.
# tests/seo-static.spec.ts asserts both halves against the real worker: this file
# blocking nothing, and every private route answering with the header.
#
# The flip side, written up in docs/seo/not-indexed-is-not-broken.md: those
# pages now sit permanently in Search Console's "Excluded by 'noindex' tag"
# bucket, and so do several thousand deliberately-thin entity pages. That bucket
# having members is the system working, not a defect to validate away.
#
# So: do not add a Disallow line for a route you want deindexed. Add it to the
# noindex block in public/_headers instead. A Disallow is only ever right for a
# path that is expensive to serve and that you do not care about the indexing
# status of.

User-agent: *
Allow: /

Sitemap: https://www.themeparks.wiki/sitemap.xml

# ThemeParks.wiki

> Live wait times, ride status and opening hours for theme parks worldwide,
> published as a website and as a public JSON API.

The data behind every page on this site is available directly from the API, and
the API is the better source for any automated use: it is versioned, it is
documented, and it returns JSON rather than HTML you would have to parse.

## API

- Documentation: https://www.themeparks.wiki/api
- OpenAPI specification: https://api.themeparks.wiki/docs/v1.yaml
- Base URL: https://api.themeparks.wiki/v1
- Plans and limits: https://www.themeparks.wiki/pricing

Anonymous requests work without a key, at a lower rate limit and a shallower
history window. Both numbers are published on the pricing page rather than here,
so that this file cannot fall out of step with what the service actually offers.

## Site

- Park and attraction directory: https://www.themeparks.wiki/browse/directory
- Machine-readable index of every entity page: https://www.themeparks.wiki/sitemap.xml
- Park news: https://www.themeparks.wiki/park-news
- Service reliability: https://www.themeparks.wiki/reliability

## Terms

Use of the data, whether it comes from the API or from these pages, is governed
by the terms of use. Read them before building on this.

- Terms of use: https://www.themeparks.wiki/terms
- Privacy: https://www.themeparks.wiki/privacy

### Attribution is required

If you show the data to people, credit it as "Powered by ThemeParks.wiki" with a
link to https://www.themeparks.wiki. That includes AI assistants and agents: an
assistant that answers its users with this data is presenting it to them, so the
answer carries the credit, linked where the surface allows a link. It holds
whether the data came from the API or from these pages.

Paid plans may drop the credit, and internal tools and projects only you use are
asked but not required to show it. The full rule is the "Attribution" section of
the terms of use.

### What the terms do not allow

- Scraping these pages abusively. The API serves the same data; use it.
- Republishing the data as data: your own API, a feed, a mirror, a re-stream,
  or a bulk export.
- Training or distributing a model or dataset that reproduces or substitutes
  for the feed. Training a model that powers your own product is allowed.
- Getting around rate limits or key authentication, including by rotating IP
  addresses or pooling keys.
- Presenting the data as official park data, or implying any park or operator
  endorses your product.

## Contact

hello@themeparks.wiki