Skip to content
Good for Bots

Wonderlist

wonderlist.co

Mobile travel marketplace for curated packages, custom trip requests and chat with travel agencies

Good for Bots: Fair, 69 of 100Get this badge →

On your homepage, it turns this report’s link to wonderlist.co dofollow.

Scanned

What is Wonderlist?

Wonderlist is a mobile-first travel marketplace, offered as an app for iOS and Android and as a web app. According to the input, it brings curated travel packages, custom trip requests and conversations with travel agencies into one place. Verified local agencies publish packages with prices and dates, and travelers can save trips, post a request describing dates, budget and vibe, and receive agency proposals. The meta description and llms.txt say the service focuses on Umrah packages and tours from Pakistani agencies. The homepage text itself does not name Pakistan or Umrah. The service is aimed at travelers planning trips, and the input describes the app as free to download.

Through a bot’s eyes

“Wonderlist is a mobile-first travel marketplace where travelers find curated packages from verified agencies, post custom trip requests and chat with agencies, mainly through its free iOS and Android app.”

Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A model reading this input learns that Wonderlist is a travel marketplace with a traveler-facing app and a community. The homepage text covers published agency packages, custom trip requests, chat with agencies, bucketlists, shoutouts, trip buddies, and a four-step path from discovery to payment. It gives figures such as 2,400+ packages, 84 agencies, a 4 minute average first reply and 47 destinations, plus sample prices of $640 for seven days and $1,240 for five days. Download links for iOS and Android appear, with the app described as free. The llms.txt file adds a page list: Umrah packages with prices in PKR, Pakistan tours, international packages, an agency directory, travel guides, Urdu pages on Umrah steps, visas and weather, a help center, terms and a privacy policy. It states that booking and chat sit behind sign-in in the web app and mobile apps. The JSON-LD repeats the description in organization, website and mobile application entries and adds social profile links. No contact email, phone number or postal address appears in the input.

What stays hidden

A model reading this input cannot find the actual price of any package beyond the sample figures on the homepage, nor the full list of destinations or agencies. It cannot learn cancellation, refund or payment terms, since those pages appear only as titles. The homepage does not say which countries the service covers, and no direct contact email, phone number or address appears. The text does not state whether posting a custom trip request costs anything.

Good for Bots report

Wonderlist scores 69 of 100: the whole readable base, 19 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 19 of the 50 agent-layer points below it.

69

Still open

Behind the checks below, with prompts in Pro.

3
Penalties0
How scoring works · current methodology →

For the owner of wonderlist.co

3 prompts, 27 points

They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.

Open the owner view →

Select a check to see what we found and how it is graded.

Readable base

50 / 50

Passes.

3.5 of 3.5 points.

robots.txt is valid, with 1 user-agent group.

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 192 URLs.

Passes.

8.8 of 8.8 points.

3 of 4 pages read pass; 1 partly. The page at /about declares BreadcrumbList but names none of them, so the markup asserts that something exists without saying what.

Passes.

10.5 of 10.5 points.

All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.

Passes.

8.8 of 8.8 points.

9 of 9 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

57 of 57 assessed homepage links and buttons have a nonempty accessible name.

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Passes.

2.6 of 2.6 points.

57 of 57 assessed homepage controls and role declarations meet the static role, state and relationship checks.

Passes.

1.8 of 1.8 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

18.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 202 links across 6 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Fails.

0 of 12.5 points.

No /llms-full.txt and no markdown versions linked from llms.txt.

Fails.

0 of 10 points.

None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

Fails.

0 of 5 points.

robots.txt names no AI crawlers, so every operator has to guess.

Fails.

0 of 2.5 points.

No usage declaration found in robots.txt or the final successful homepage response header.

Prompt in Pro →

Penalties

− 0

Passes.

Penalty: 0 of 15 points.

Our crawler reaches the page without being challenged.

Passes.

Penalty: 0 of 20 points.

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Passes.

Penalty: 0 of 25 points.

The captured homepage HTML contains 718 content words; completeness is not assessed.

Passes.

Penalty: 0 of 25 points.

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Passes.

Penalty: 0 of 10 points.

The homepage is served over HTTPS and returns HTTP 200.

Passes.

Penalty: 0 of 3 points.

The homepage provides both a non-empty title and meta description.

Passes.

Penalty: 0 of 3 points.

The homepage is reached in 0 redirects.

Passes.

Penalty: 0 of 3 points.

The homepage reached a plain crawler in 325 ms.

Agent capabilities

0 of 11 · no points

Each one found adds +1 to the badge.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/api-catalog, so the API catalog could not be verified.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/ai-catalog.json, so MCP server card discovery could not be verified.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/agent-card.json and /.well-known/ai-catalog.json, so A2A Agent Card discovery could not be verified.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking https://wonderlist.co/.well-known/agent-skills/index.json, https://wonderlist.co/.well-known/skills/index.json and /.well-known/ai-catalog.json, so Agent Skills discovery could not be verified.

Not applicable.

Adds +1 to the badge when found.

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/http-message-signatures-directory, so the Web Bot Auth key directory could not be verified.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/x402, and no 402 payment challenge was seen.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/acp.json, so ACP discovery is unknown.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from checking /.well-known/ucp, so UCP discovery is unknown.

Not applicable.

Adds +1 to the badge when found.

robots.txt disallows our crawler from reading /.well-known/agent.json; no usable AMP extension was found in the collected cards.

Site profile

Login
Not established
API
Not established
Commerce
Not established

It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.

Access & usage policy

Who can read this page, and for what purpose?

GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.

Sampled URL: https://wonderlist.co/

Measured, our crawler
HTTP 200
GoodForBotsBot received HTTP 200 via a direct request.
Search and user-fetch crawlers refused
0 of 20
robots.txt refuses none of them.
Training crawlers refused
0
Refusing training would not change the score.

Crawlers and what robots.txt declares for them

Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.

Crawlers and what robots.txt declares for them on the sampled URL
CrawlerPurposeDeclared accessScore effectRule that applies
Our crawler, measured
GoodForBotsBotGood for BotsSite diagnosticsFetchedHTTP 200, directNot scoredrobots.txt admitted our crawler
Search and AI answers
OAI-SearchBotOpenAIAI searchAllowedNoneNot named; User-agent: * applies
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneNot named; User-agent: * applies
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneNot named; User-agent: * applies
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneNot named; User-agent: * applies
ClaudeBotAnthropicAI trainingAllowedNoneNot named; User-agent: * applies
Google-ExtendedGoogleAI training, GroundingAllowedNoneNot named; User-agent: * applies
, all allowed
Agents, extraction and others
, all allowed

The robots.txt groups behind this table

User-agent: *
Allow: /

https://wonderlist.co/robots.txt

How to read this table

Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.

Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.

Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
  • Declared allow · Scan admission

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    The recorded robots admission decision allowed our crawler to proceed.

    GoodForBotsBot admission along the homepage request chain

    https://wonderlist.co/

    robots.txt is present and valid

  • Observed · Direct request

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    Our request received HTTP 200. A status alone does not identify a WAF.

    Our recorded direct transport attempt; intermediate attempt URLs are not retained

    https://wonderlist.co

    HTTP 200

    Serves the homepage over HTTPS with HTTP 200

  • Observed · Final homepage response

    • GoodForBotsBot/1.0 (+https://goodforbots.com/bot)

    GoodForBotsBot received HTTP 200 via a direct request.

    homepage response

    https://wonderlist.co/

    HTTP 200
    Transport: direct

    Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge

Coverage and interpretation
  • Crawler coverage includes the registered identities and up to 50 user-agent entries from robots.txt. Source excerpts and detail groups are bounded; omissions are labelled.
  • Observed access describes GoodForBotsBot only. Other crawler entries describe declared rules, not tests of those operators' access.
  • Coverage is the sampled homepage response and collected robots.txt files. No indexing or citation is guaranteed. Usage preferences are declarations, not a legal determination of permission.
  • This explanation adds no points or penalties. Any score effects belong to the linked checks.
  • AIPREF and Content Signals keep their own definitions. AIPREF search can include processing used exclusively for search; training preferences are not a blanket ruling on every search process.

In its category

1st of 2 in Marketplaces & Booking

  1. 1Wonderlist · this reportwonderlist.co
  2. 2Growth Bountiesgrowthbounties.com

Category average 52. The percentile appears once the catalogue holds a few hundred sites.

Scan details

Every scan is kept. Pro draws the history as a chart →

Scanned
13 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
754.5 KB
Took
9.9 s
Homepage
325 ms · direct
Pages read
4
robots.txt
allowed
Which pages the scan read

The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.

  • Homepagealways read
  • /guides/azerbaijan-visaarticle · from the sitemap · read
  • /guidescollection · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read

More like Wonderlist:Marketplaces & BookingTravel & HospitalityMobileB2C

Also Fair

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Also B2C

submityourstartup.now

Free weekly launch directory where early-stage founders list startups and are ranked by votes

Also B2C

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

Also Fair

talhabashir.com

Free online calculators and tools for US taxes, mortgages, business and personal finance

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Do you run wonderlist.co? Open the owner view → Removing the listing is free. Remove →