Skip to content
Good for Bots

Records days spent in each country on iPhone and counts them under visa, residence and tax rules

Good for Bots: Good, 89 of 100Get this badge →

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

Scanned
Category
Other

What is Geostay?

Geostay is a country days tracker for iPhone, according to the input. It records the days a person spends in each country and counts them the way visa, residence and tax rules count them. The homepage names rules it counts, including Schengen's 90 days in any rolling 180-day period, the UK Statutory Residence Test, the US Substantial Presence Test and 183-day tax lines for some countries and US states. It states that visa rules are included for 40 countries and tax residency tests for 184 countries, and that the app requires iOS 18 and has no account. The llms.txt names the developer as Mehmet Ali Kısacık, an independent developer in Istanbul. The input does not state a price.

Through a bot’s eyes

“Geostay is a country days tracker for iPhone that records the days spent in each country and counts them under visa, residence and tax rules, keeping the travel history on the device.”

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 Geostay is an iPhone app that records country days and counts them against Schengen, UK, US and other visa, residence and tax rules. The text explains that each card shows one number and warns before a limit, that location is recorded with the app closed, that past trips can be rebuilt from photos, and that travel data stays on the device. A question-and-answer section covers which rules are counted, offline behaviour, photo import, visa coverage, data storage and legal status, and links to the privacy policy. Several visitor facts are present as text: iOS 18, no account, no ads in the app, and the App Store link. The llms.txt adds a page inventory of calculators, comparison pages and usage guides, plus a support email address and the developer's name and location, which the homepage does not show. The JSON-LD adds organization, person and app records, a feature list and a publication date of 2026-11-05.

What stays hidden

A model reading only this input cannot find the price of the app or of any subscription, although the text mentions purchase details for a subscription. It does not learn which of the 40 visa-rule countries are covered beyond the few examples named, or which of the 184 tax-test countries are included. Platform support is limited to iOS 18, with no statement about iPad, Mac or other systems.

Good for Bots report

Geostay scores 89 of 100: the whole readable base, 39 of the 50 agent-layer points, no penalties.

Earned

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

89
Penalties0
How scoring works · current methodology →

For the owner of getgeostay.com

3 prompts, 11 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.6 of 3.6 points.

robots.txt is valid, with 13 user-agent groups.

Passes.

8.9 of 8.9 points.

Sitemap declared in robots.txt, listing 18 URLs.

Passes.

8.9 of 8.9 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, ImageObject, Thing in valid schema.org JSON-LD.

Passes.

10.7 of 10.7 points.

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

Passes.

8.9 of 8.9 points.

10 of 10 assessed homepage navigation links expose usable destinations.

Passes.

4.5 of 4.5 points.

29 of 29 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.7 of 2.7 points.

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

38.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 18 links across 7 sections.

Passes.

7.5 of 7.5 points.

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

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (6 KB).

Fails.

0 of 10 points.

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

Passes.

5 of 5 points.

States a position on 9 AI crawlers, across 3 purposes (training, search, user-fetch).

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 1243 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://getgeostay.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 searchAllowedNoneUser-agent: oai-searchbot Allow: /
Claude-SearchBotAnthropicAI searchAllowedNoneNot named; User-agent: * applies
PerplexityBotPerplexityAI searchAllowedNoneUser-agent: perplexitybot Allow: /
GooglebotGoogleSearchAllowedNot scoredNot named; User-agent: * applies
BingbotMicrosoftSearchAllowedNot scoredUser-agent: bingbot Allow: /
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneUser-agent: chatgpt-user Allow: /
Claude-UserAnthropicUser fetchAllowedNoneNot named; User-agent: * applies
Perplexity-UserPerplexityUser fetchAllowedNoneNot named; User-agent: * applies
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneUser-agent: gptbot Allow: /
ClaudeBotAnthropicAI trainingAllowedNoneUser-agent: claudebot Allow: /
Applebot-ExtendedAppleAI trainingAllowedNoneUser-agent: applebot-extended Allow: /
Google-ExtendedGoogleAI training, GroundingAllowedNoneUser-agent: google-extended Allow: /
AmazonbotAmazonAI training, Product improvementAllowedNoneUser-agent: amazonbot Allow: /
CCBotCommon CrawlOpen dataset, AI trainingAllowedNoneUser-agent: ccbot Allow: /
, all allowed
Agents, extraction and others
bytespiderUnspecifiedNot establishedAllowedNot scoredUser-agent: bytespider Allow: /
coccocbotUnspecifiedNot establishedAllowedNot scoredUser-agent: coccocbot Allow: /
, all allowed

The robots.txt groups behind this table

User-agent: oai-searchbot
Allow: /

User-agent: perplexitybot
Allow: /

User-agent: gptbot
Allow: /

User-agent: claudebot
Allow: /

User-agent: applebot-extended
Allow: /

User-agent: chatgpt-user
Allow: /

User-agent: google-extended
Allow: /

User-agent: amazonbot
Allow: /

User-agent: ccbot
Allow: /

User-agent: bingbot
Allow: /

User-agent: bytespider
Allow: /

User-agent: coccocbot
Allow: /

User-agent: *
Allow: /

https://getgeostay.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://getgeostay.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://getgeostay.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://getgeostay.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

1st of 9 in Other

  1. 1Geostay · this reportgetgeostay.com
  2. 2Log Cam: RAW 4K Video Cameralogcamvideo.com
  3. 3chong-zhen.comchong-zhen.com

Category average 66. 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
24
Fetched
419.3 KB
Took
14.5 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
  • /about/about · linked from the homepage · from the sitemap · read
  • /contact/contact · linked from the homepage · from the sitemap · read
  • /compare/linked from the homepage · from the sitemap · read

More like Geostay:OtherTravel & HospitalitySecurity & PrivacyMobile

Also Good

saascubes.com

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

Also Good

dolaai.pro

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

Also Good

vouchgeo.com

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

contentspilot.com

AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style

goodforbots.com

Evaluates website readability for AI crawlers and language models with a scoring rubric

brivoy.com

Community site where makers launch new products and early adopters discover them

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