Same category
vouchgeo.com
Tracks how AI assistants mention a brand across multi-question buying conversations

Free search tool to check if you have been posted on the Tea dating app
Tea App Checker is an online tool designed to help men find out if they have been posted on the Tea app, a dating safety platform built for women where men cannot create accounts to search for themselves. The site allows users to run a search for free by entering a first name, city, and age, or by uploading an optional face photo. Results are typically displayed in about ten seconds, showing potential matches with details such as the photo, name, age, city, post date, and comment or flag counts. While searching and viewing match summaries is free, users must pay a one-time fee per post if they wish to unlock and read the full text and comments.
“Tea App Checker is a free search tool that lets men check if they have been posted on the Tea dating app by entering their name, city and age, or a photo.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading this input learns that Tea App Checker provides external search capabilities for content hosted on the Tea dating safety application. The text covers how the search mechanism works using names, locations, ages, and optional facial recognition, alongside privacy practices like encrypted photo storage and third-party payment processing through Stripe. The homepage and llms.txt provide comprehensive details on what is included in free match results versus unlocked posts, step-by-step guides, policies, and contact information via [email protected]. The provided JSON-LD structured data and llms.txt reiterate the site purpose and supply an FAQ section answering common questions about search duration, privacy, and payment methods. Exact monetary prices for unlocking posts are not explicitly stated in numerical terms on the page, though the text clarifies that prices appear on the unlock button prior to purchase.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 2 user-agent groups.
Sitemap is present and parses. Sitemap declared in robots.txt, listing 13 URLs.
Describes itself to machines with schema.org JSON-LD. 3 of 4 pages read pass. The page at /biometric-notice/ publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 11 of 11 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 94 of 94 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 110 of 110 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. All 4 pages read pass. The homepage has 8 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 13 links across 3 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 100% of links.
Serves markdown at its own URL. /llms-full.txt serves the site's content as markdown (25 KB).
States a position on AI crawlers. States a position on 16 AI crawlers, across 3 purposes (training, search, user-fetch).
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt.
Earned
The whole readable base above the line, 36 of the 50 agent-layer points below it.
3 prompts away
For the owner of teaappchecker.app
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
50 / 50
3.3 of 3.3 points.
robots.txt is valid, with 2 user-agent groups.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing 13 URLs.
8.3 of 8.3 points.
3 of 4 pages read pass. The page at /biometric-notice/ publishes no structured data at all: no JSON-LD, no microdata, no RDFa.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
94 of 94 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
3 of 3 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
110 of 110 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
All 4 pages read pass. The homepage has 8 section links, and every one reaches an element on the page.
Agent layer
36.3 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 13 links across 3 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 100% of links.
12.5 of 12.5 points.
/llms-full.txt serves the site's content as markdown (25 KB).
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
5 of 5 points.
States a position on 16 AI crawlers, across 3 purposes (training, search, user-fetch).
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 1919 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 140 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
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.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://teaappchecker.app/
No matching refusal for this URL was found for the listed identities.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://teaappchecker.app/
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://teaappchecker.app/
https://teaappchecker.app/robots.txt
User-agent: * allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
Declared allow · robots.txt
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://teaappchecker.app/
https://teaappchecker.app/robots.txt
User-agent: googlebot User-agent: googlebot-image User-agent: bingbot User-agent: applebot User-agent: duckduckbot User-agent: gptbot User-agent: oai-searchbot User-agent: chatgpt-user User-agent: claudebot User-agent: claude-user User-agent: claude-searchbot User-agent: anthropic-ai User-agent: claude-web User-agent: perplexitybot User-agent: perplexity-user User-agent: google-extended User-agent: applebot-extended User-agent: meta-externalagent User-agent: meta-externalfetcher User-agent: amazonbot User-agent: ccbot User-agent: bytespider User-agent: mistralai-user User-agent: cohere-ai User-agent: duckassistbot User-agent: youbot allow: /
robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers
GoodForBotsBot received HTTP 200 via a direct request.
Observed · Direct request
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://teaappchecker.app
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://teaappchecker.app/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://teaappchecker.app/
No snippet restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No snippet restriction was observed in the supported homepage directives.
homepage response
https://teaappchecker.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://teaappchecker.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://teaappchecker.app/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://teaappchecker.app/
In its category
The prompts in the owner view would take Tea App Checker to 100, first in its category.
To the prompts →Category average 58. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
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.
More like Tea App Checker:SaaS & Web AppsSecurity & PrivacyB2C
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 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 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
Do you run teaappchecker.app? Open the owner view → Removing the listing is free. Remove →