Skip to content
Good for Bots

GatherMango

gathermango.com

Free Secret Santa, white elephant and group availability poll tools that need no sign-up

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

On your homepage, it turns this report’s link to gathermango.com dofollow.

Scanned

What is GatherMango?

GatherMango is a website of free tools for groups planning gatherings. Its main tools are a Secret Santa generator that draws names with couples kept apart and gives each person a private link, a white elephant game that draws the turn order and tracks gifts, and an availability poll where people tap the times they are free. The site also offers sign-up sheets, RSVP pages, meal trains, potluck sheets and random name and team draws, along with guides on gift ideas, rules and potluck dishes. The input says the tools work on phones and that nobody invited has to sign up. Organizers receive a share link and a private link for changing a draw or poll. Draws and polls are deleted 90 days after anyone last uses them. The site is aimed at people organising office gift exchanges, family events and group schedules.

Through a bot’s eyes

“GatherMango is a free website with tools for group plans, including a Secret Santa generator, a white elephant game tracker and a group availability poll, none of which require the organizer or invitees to sign up.”

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 homepage learns that the site offers tools for group plans: Secret Santa and white elephant gift exchanges, availability polls, sign-up sheets, RSVP pages and meal trains. It also sees lists of related guides on gift ideas, game rules, potluck dishes and the meaning of RSVP, a comparison section naming other scheduling tools such as When2meet, Doodle and Calendly, and a short section on accounts, email and deletion after 90 days. The homepage text does not give the price of any tool, and it does not say who the site is for beyond gatherings and groups. The llms.txt file adds a fuller list of the tools, each with a one-line description, and a contact address, [email protected]. It also lists the polls and draws as private and not indexed. The JSON-LD blocks describe the organization and the website, with the name, alternate name, URL, language and the same email address, but no description of the services.

What stays hidden

A model reading only this input cannot tell what any tool costs beyond the word free in the title and description, or whether any paid option exists. It cannot tell how many groups use the tools or how long the service has existed. It also cannot tell which ad network the site uses or what the analytics consent options cover in practice, beyond the short notice in the page text.

Good for Bots report

GatherMango scores 71 of 100: the whole readable base, 21 of the 50 agent-layer points, no penalties.

Earned

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

71

Still open

Behind the checks below, with prompts in Pro.

1
Penalties0
How scoring works · current methodology →

For the owner of gathermango.com

3 prompts, 28 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 42 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.

5 of 5 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

98 of 98 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.

99 of 99 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

21.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 40 links across 5 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 98% 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 states AI usage preferences, but names no AI crawler individually.

Passes.

2.5 of 2.5 points.

Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.

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 617 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 57 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.

No API catalog published.

Not applicable.

Adds +1 to the badge when found.

No /auth.md published.

Not applicable.

Adds +1 to the badge when found.

No AI Catalog published, so no MCP server card can be discovered.

Not applicable.

Adds +1 to the badge when found.

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

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.

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Not applicable.

Adds +1 to the badge when found.

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Not applicable.

Adds +1 to the badge when found.

No ACP discovery declaration established at /.well-known/acp.json.

Not applicable.

Adds +1 to the badge when found.

No UCP discovery declaration established at /.well-known/ucp.

Not applicable.

Adds +1 to the badge when found.

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

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://gathermango.com/

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://gathermango.com/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://gathermango.com/

    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://gathermango.com

    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://gathermango.com/

    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

25th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 25GatherMango · this reportgathermango.com

The prompts in the owner view would take GatherMango to 99, first in its category.

To the prompts →

Category average 58. 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
19 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
1.2 MB
Took
13 s
Homepage
57 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
  • /secret-santa-questionnairearticle · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read
  • /across-time-zoneslinked from the homepage · from the sitemap · read

More like GatherMango:SaaS & Web AppsProductivity

Same category

vouchgeo.com

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

Same category

talhabashir.com

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

Also Fair

volanea.com

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

saascubes.com

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

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also Fair

submityourstartup.now

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

Do you run gathermango.com? Open the owner view → Removing the listing is free. Remove →