Skip to content
Good for Bots

BirthChartGod

birthchartgod.com

Free natal chart calculator showing planets in signs and houses, calculated in the browser

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

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

Scanned
Category
Other

What is BirthChartGod?

BirthChartGod is a free birth chart calculator. A visitor enters a birth date, time and place, and the calculator, running in the browser, produces a natal chart showing the zodiac wheel, the planets in their signs and houses, and the aspects between them. It offers Placidus and whole sign house systems, with saved charts kept in the browser and share links. The input describes ten tools, including Moon, rising, Venus and Mars sign calculators, Saturn and Jupiter return dates, progressed charts, a North Node calculator and a synastry comparison, plus pages on planet placements and birthstones by month. It is aimed at people interested in astrology who want a chart of their own. The input states no price beyond the free offer.

Through a bot’s eyes

“BirthChartGod is a free birth chart calculator. It works out a natal chart from a birth date, time and place in the visitor's browser, showing planets in signs and houses and the aspects between them.”

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 explains how to read a birth chart: the zodiac ring, planets in signs, houses starting from the ascendant, and aspects such as trines, squares and conjunctions. It says what a visitor must supply (date, time and town of birth), notes that the time can be left out, and explains the Placidus and whole sign house options. It also covers accuracy, citing the astronomy-engine library and NASA's JPL ephemeris, and the privacy arrangements, including that details stay on the device. The date range from 1800 to 2100 is stated. The calculator form and the chart it produces are not present as text, because they need JavaScript. The llms.txt file adds a structured list of the ten calculators, the placement pages and the about, privacy and contact pages, with the contact email [email protected]. The JSON-LD blocks add the organisation and web application records, the email address, and a free offer in USD.

What stays hidden

A model reading only this input cannot see the chart output, so it cannot say what a finished chart shows for a given birth. The text of the placement readings, which the site says exist for every planet in every sign and house, is not included, so the meaning given to any placement is unknown. Whether the site has an account system, or any cost beyond the free offer, is not stated.

Good for Bots report

BirthChartGod scores 67 of 100: 46 of the 50 base points, 21 of the 50 agent-layer points, no penalties.

Earned

46 of the 50 base points above the line, 21 of the 50 agent-layer points below it.

67

Still open

Behind the checks below, with prompts in Pro.

5
Penalties0
How scoring works · current methodology →

For the owner of birthchartgod.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

45.8 / 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 at least 200 URLs.

Half passes.

4.2 of 8.3 points.

1 of 4 pages read pass; 3 partly. The page at /about declares BreadcrumbList but names none of them, so the markup asserts that something exists without saying what.

Prompt in Pro →
Passes.

10 of 10 points.

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

Passes.

8.3 of 8.3 points.

7 of 7 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

2.5 of 2.5 points.

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

21.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 21 links across 3 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 81% 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 852 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 61 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://birthchartgod.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://birthchartgod.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://birthchartgod.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://birthchartgod.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://birthchartgod.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

4th of 9 in Other

  1. 1Geostaygetgeostay.com
  2. 2Log Cam: RAW 4K Video Cameralogcamvideo.com
  3. 4BirthChartGod · this reportbirthchartgod.com

The prompts in the owner view would take BirthChartGod to 95, first in its category.

To the prompts →

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
19 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
612.3 KB
Took
12.9 s
Homepage
61 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
  • /aboutabout · linked from the homepage · read
  • /birth-monthslinked from the homepage · from the sitemap · read
  • /contactcontact · linked from the homepage · read

More like BirthChartGod:Other

Also Fair

volanea.com

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

Also Fair

submityourstartup.now

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

Also Fair

talhabashir.com

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

Also Fair

interviewace.online

Real-time AI answer suggestions for job candidates during live video interviews

vouchgeo.com

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

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