Skip to content
Good for Bots

TimerPanda

timerpanda.com

Free Pomodoro focus timer with a task list, session stats and streaks, plus themed timers

Click badge to copy

Changed your site? Run a new scan.

Claim to rescan

Claiming is free. Verify ownership to request a rescan after deploying your changes.

Unclaimed listings are checked automatically every 90 days.

Good for Bots report

TimerPanda scores 68 of 100: the whole readable base, 18 of the 50 agent-layer points, no penalties.

Earned

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

68

3 prompts away

Copy them below ↓

28

Still open

Behind the checks below, with prompts in Pro.

4
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“TimerPanda is a free Pomodoro focus timer with a task list, daily stats and streaks, plus themed timers for eggs, workouts, exams and holiday countdowns.”

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

The homepage text covers the Pomodoro method and how the focus timer, tasks, progress panel, streaks, background sounds, themes and full-screen mode work. A short FAQ answers questions about background tabs, data storage and phone use. The page also lists dozens of other pages: timers for workouts, talks and exams, themed timers, timers by length, holiday and date countdowns, and pet vaccination schedules and lifespans. The homepage body does not state a price, a sign-up requirement or contact details, though the meta description calls the timer free. The llms.txt file repeats the summary in a curated link list, adds the phrase no account or sign-up, and gives the contact address [email protected]. The JSON-LD blocks describe an Organization and a WebApplication, stating a price of 0 USD, a logo and the same email address. No Markdown version of the homepage was received.

What stays hidden

A model reading only this input cannot tell who runs TimerPanda beyond a name and an email address, or whether a postal address exists. The timers themselves are described in text but cannot be seen, and the input gives no detail on how the pet schedules or lifespan figures were compiled beyond one line in llms.txt.

What is TimerPanda?

TimerPanda is a website offering a free Pomodoro focus timer. The timer runs 25-minute work sessions with short breaks, and includes a task list where each finished session counts towards a chosen task, a progress panel with daily sessions and minutes, and a streak of consecutive days with at least one finished focus session.

Read more →

Tasks, stats and settings are saved in the browser on the same device, and no account is needed. The site also offers many other timers and countdowns, including bomb, egg, race, classroom, interval, exam and noise meter timers, holiday and birthday countdowns, and pet vaccination and lifespan pages. The input does not state a specific audience beyond these uses.

3 prompts, 27 points

For Claude Code, Cursor or Codex. The score moves after the next scan.

+12.5score from 68 to 80

Serve Markdown at its own URL

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

Read prompt

+10score from 80 to 90

Serve Markdown when asked for it

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

Read prompt

+5score from 90 to 95

State a position on AI crawlers

robots.txt states AI usage preferences, but names no AI crawler individually.

Read prompt

Pro

13 more prompts in Pro

Pro shows a prompt for every fix and drafts your llms.txt and robots.txt. It never changes the score.

$9 once, per listingSee Pro

Deployed your fixes? Rescan to update your score →

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for TimerPanda from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

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

Readable base

50 / 50

Passes.

3.3 of 3.3 points.

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

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 72 URLs.

Passes.

8.3 of 8.3 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 of 10 points.

3 of 4 pages read pass; 1 partly. The page at /kitten-vaccination-schedule is partly structured: The outline jumps from h1 to h3, which the standard forbids.

Passes.

8.3 of 8.3 points.

7 of 7 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

20 of 20 assessed homepage form fields meet the static naming and field-semantics checks.

Passes.

2.5 of 2.5 points.

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

Passes.

1.7 of 1.7 points.

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

Agent layer

17.5 / 50

Passes.

11.3 of 11.3 points.

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

Half passes.

3.8 of 7.5 points.

/llms.txt is partly descriptive: only 40% of links carry a description.

Prompt in Pro →
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 1176 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 52 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.

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://timerpanda.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://timerpanda.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://timerpanda.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://timerpanda.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://timerpanda.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

31st of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 31TimerPanda · this reporttimerpanda.com

The prompts above would take TimerPanda to 95, 3rd in its category.

To the prompts ↑

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

Scanned

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.

Scan details

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

Scanned
19 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
658.7 KB
Took
13.1 s
Homepage
52 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
  • /kitten-vaccination-schedulearticle · linked from the homepage · from the sitemap · read
  • /aboutabout · linked from the homepage · from the sitemap · read
  • /1-minute-timerlinked from the homepage · from the sitemap · read