Also Freemium
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric

FIRE calculator and financial freedom planner based on income, spending and savings
UntilFire is a financial planning web application designed to help individuals estimate their Financial Independence, Retire Early (FIRE) number and freedom date. It offers a free online calculator that uses income, spending, and savings inputs to project the year when work becomes optional, without requiring a login for basic use. The platform provides decision sliders, city-specific cost-of-living data across multiple global locations, and educational guides on financial independence concepts such as the four percent rule and Coast FIRE. Additionally, it offers a Pro tier with expanded features including bank and brokerage syncing, automated action plans, and progress tracking.
“UntilFire is a FIRE calculator and financial freedom planner that estimates your freedom date based on your income, spending, and savings.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
A language model reading the provided homepage and JSON-LD blocks learns about personal finance concepts centered around the Financial Independence, Retire Early movement. The text covers FIRE number calculations, the mechanics of compound interest over multiple decades, and cost-of-living estimates for various cities globally. Facts that a visitor looks for are fully present in the text, including pricing details for the free and Pro tiers, feature lists, frequently asked questions, and contact support information via email. The embedded JSON-LD schema blocks corroborate the application category, web application details, organization info, and a comprehensive FAQ dataset that aligns with the visible homepage text.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing at least 200 URLs.
Describes itself to machines with schema.org JSON-LD. All 4 pages read pass. The homepage describes itself to machines as WebApplication, Thing, Offer in valid schema.org JSON-LD.
Content is marked up so a reader can find it. 3 of 4 pages read pass; 1 partly. The homepage is partly structured: No <main> element and nothing carrying role="main".
Navigation links expose usable destinations. 5 of 5 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 96 of 96 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 2 of 2 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 101 of 101 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. The homepage has 6 section links, and every one reaches an element on the page.
Serves markdown at its own URL. No /llms-full.txt and no markdown versions linked from llms.txt. +12.5 with its prompt.
llms.txt is present and well formed. No /llms.txt on this site. +11.3 with its prompt.
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.
llms.txt is descriptive, not a bare link list. No usable /llms.txt to judge. +7.5 with its prompt in Pro.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt in Pro.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt in Pro.
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 in Pro.
Earned
The whole readable base above the line, none of the agent layer below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of untilfire.com
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 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing at least 200 URLs.
8.3 of 8.3 points.
All 4 pages read pass. The homepage describes itself to machines as WebApplication, Thing, Offer in valid schema.org JSON-LD.
10 of 10 points.
3 of 4 pages read pass; 1 partly. The homepage is partly structured: No <main> element and nothing carrying role="main".
4.2 of 4.2 points.
96 of 96 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
2 of 2 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
101 of 101 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.
The homepage has 6 section links, and every one reaches an element on the page.
Agent layer
0 / 50
0 of 11.3 points.
No /llms.txt on this site.
0 of 12.5 points.
No /llms-full.txt and no markdown versions linked from llms.txt.
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
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 1286 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 176 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://www.untilfire.com/
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://www.untilfire.com/
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://www.untilfire.com/
https://www.untilfire.com/robots.txt
User-agent: * 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://www.untilfire.com
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://www.untilfire.com/
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://www.untilfire.com/
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://www.untilfire.com/
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://www.untilfire.com/
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://www.untilfire.com/
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://www.untilfire.com/
In its category
The prompts in the owner view would take UntilFire to 84, 7th in its category.
To the prompts →Category average 57. 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 UntilFire:SaaS & Web AppsFintechB2CFreemium
Also Freemium
goodforbots.com
Evaluates website readability for AI crawlers and language models with a scoring rubric
Same category
theflan.app
Budgeting and financial planning app with visual timelines for individuals and couples
Same category
overnightbrief.netlify.app
Compare 2026 US take-home pay between W-2 employment and 1099 self-employment
Same category
dropify.cloud
Aggregates official artist and brand stores with customizable product drop and restock alerts
Same category
quotelyo.online
Free browser-based financial calculators for personal money management
Same category
pressurewasherfix.com
Free browser-based diagnostic tool for consumer pressure washer troubleshooting
Do you run untilfire.com? Open the owner view → Removing the listing is free. Remove →