SnapPChart

snappchart.app

AI chart analysis tool that grades trade setups from uploaded screenshots

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

SnapPChart scores 80 of 100: 44 of the 50 base points, 36 of the 50 agent-layer points, no penalties.

Earned

44 of the 50 base points above the line, 36 of the 50 agent-layer points below it.

3 prompts away

Copy them below ↓

Still open

Behind the checks below, with prompts in Pro.

Penalties0

How scoring works · current methodology →

Through a bot’s eyes

“SnapPChart is an AI chart analysis tool that grades stock, forex, and crypto chart screenshots, providing trade entry, stop loss, and target levels.”

Simulated from the response GoodForBotsBot received on 3 Oct 2026, not a live answer from any AI assistant.

What it can read, and what stays hidden →

What a bot can read

A language model reading this input learns about SnapPChart's features, target audience, pricing models, and core functionality. The homepage markdown details how the tool works in three steps, explaining its support for PNG, JPG, and WebP screenshots, pattern detection, and personalized trading profiles. It also presents user testimonials and pricing tiers of $4.99 per week, $19.99 per month, and $199.99 per year. The provided llms.txt file adds extensive technical context regarding its multimodal vision models, free calculator tools, and specific documentation links, while the JSON-LD schema supplies structured organization data, founding details, and exact offer pricing.

What is SnapPChart?

SnapPChart is an AI-powered chart analysis tool designed for stock, forex, crypto, and futures traders. It provides automated technical analysis by evaluating uploaded chart screenshots from platforms like TradingView, Webull, and MetaTrader.

The platform grades trade setups on a scale from A+ to F, and supplies entries, stop losses, risk-to-reward ratios, and profit targets based on price action and indicators such as EMAs, RSI, and volume. Users can personalize the AI through a trading profile that adapts to their specific style, market, and bias. SnapPChart offers a free tier alongside weekly, monthly, and yearly subscription plans.

3 prompts, 18 points

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

+10

Serve Markdown when asked for it

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

Read prompt

My website snappchart.app scored 80/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: serve markdown through content negotiation on all public HTML routes.

The check it fails is "Serves markdown when asked for it", worth 10 points. What the scanner saw: None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.

The scan checked a sample of 4 pages. It does not establish which other pages have the same issues. Use the findings below to locate the responsible templates, components or configuration, and apply the fix wherever the same issue occurs. Pages in the sample with findings:
- https://www.snappchart.app/: Asking the homepage for markdown still returns text/html.
- https://www.snappchart.app/blog/ai-chart-analysis/ai-after-hours-analysis: Asking the page at /blog/ai-chart-analysis/ai-after-hours-analysis for markdown still returns text/html.
- https://www.snappchart.app/blog: Asking the page at /blog for markdown still returns text/html.
- https://www.snappchart.app/pricing: Asking the page at /pricing for markdown still returns text/html.

Implement content negotiation across all public HTML routes, including page types
outside the scan's sample. Put it in the shared response handling or the handlers
for each page type, so new pages receive it too. Agents need the content of any
page they follow, including pages the report did not name.

When a request arrives with `text/markdown` in its `Accept` header, the same URL that
serves HTML to a browser should return a markdown rendering of that page's content.
Requests without that header must keep getting the HTML exactly as they do now.

The response must:

- set `Content-Type: text/markdown; charset=utf-8`;
- include `Accept` in the `Vary` header, so shared caches never serve the markdown to a
  browser or the HTML to an agent (RFC 9110 says a server SHOULD send `Vary` whenever
  the representation depends on a request header);
- contain real markdown, not HTML with a different header on it;
- drop `ETag` and `Last-Modified` for the converted response, since a conditional request
  cannot be honoured against a body generated on the fly.

Work out how to do this in whatever stack this project uses. If the site is behind
Cloudflare on a paid plan, the "Markdown for Agents" zone setting does all of the above
and is the least invasive option. Otherwise implement it in the framework: middleware
inspecting the `Accept` header, a route handler that returns the markdown source, or
whatever fits the architecture here.

Strip navigation, headers, footers and cookie banners from the markdown. The point is the
content, without the page furniture around it.

Verify HTML and Markdown responses for each public page type, including URLs
outside the reported sample. Check that each Markdown response contains that
page's content and that ordinary browser requests still receive HTML.

The whole report, as markdown, is at https://goodforbots.com/r/snappchart.app.md?scan=cmusm311d02u401o08gveb4ks. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

Mark up content so a reader can find it

2 of 4 pages read pass; 2 partly. The page at /blog is partly structured: 2 visible content roots, where the standard allows one.

Read prompt

My website snappchart.app scored 80/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: mark the content up so a parser can find it.

The check it only partly passes is "Content is marked up so a reader can find it", with 5 points of it still on the table. What the scanner saw: 2 of 4 pages read pass; 2 partly. The page at /blog is partly structured: 2 visible content roots, where the standard allows one.

The scan checked a sample of 4 pages. It does not establish which other pages have the same issues. Use the findings below to locate the responsible templates, components or configuration, and apply the fix wherever the same issue occurs. Pages in the sample with findings:
- https://www.snappchart.app/blog: The page at /blog is partly structured: 2 visible content roots, where the standard allows one.
- https://www.snappchart.app/pricing: The page at /pricing is partly structured: No <main> element and nothing carrying role="main".

Review the site's public page templates and shared layout components. Fix missing
content roots, heading structure and landmarks wherever they occur, including
templates outside the reported sample. Check the server's HTML response from each
page type: a shared layout fix can introduce a second `<main>` on pages that
already have one.

Semantic elements help a reader of raw HTML find the page's content and distinguish
it from navigation and other surrounding material.

Three things, all from the HTML standard. Change the markup; do not change what the page
looks like.

**1. One content root.** Wrap the page's dominant content in a single `<main>`.

```html
<body>
  <header>…site header…</header>
  <main>…the article, the docs page, the product copy…</main>
  <footer>…site footer…</footer>
</body>
```

The standard allows exactly one `<main>` per document that is not marked `hidden`, and
its ancestors may only be `<html>`, `<body>`, `<div>`, an unnamed `<form>` or a custom
element, which makes a `<main>` inside `<section>` or `<article>` invalid. Put the real
content inside it: a `<main>` that holds a sliver of the page while the article sits in a
sibling `<div>` marks nothing. If a framework template makes the element impossible,
`role="main"` on the wrapper is an acceptable substitute.

**2. A heading outline that holds together.** Exactly one idea per level, starting at
`<h1>`, and never skipping a level on the way down.

```html
<h1>What this page is about</h1>
  <h2>First section</h2>
    <h3>A detail</h3>
  <h2>Second section</h2>
```

`<h1>` → `<h3>` is invalid; `<h3>` → `<h2>` on the way back up is fine. Use heading
elements for headings and CSS for size: a `<div class="text-2xl">` is invisible to the
outline. If a heading is an image or an icon, give it real text and hide it visually
rather than leaving the element empty.

**3. Landmarks around the content.** At least two of these, outside `<main>`:

```html
<header>   <!-- the site header: becomes the banner landmark -->
<nav>      <!-- navigation -->
<footer>   <!-- the site footer: becomes contentinfo -->
<aside>    <!-- related content -->
<search>   <!-- a search form -->
```

Two rules that surprise people. `<header>` and `<footer>` only count as the page's banner
and contentinfo when they are children of `<body>`; inside `<article>` or `<section>` they
are that section's own header and footer and are not landmarks at all. And a `<form>` is
only a landmark when it has an accessible name, so give a search form
`aria-label="Search"`.

Do not add landmarks that describe nothing: five unlabelled `<nav>` elements are worse
than one. And do not wrap the whole body in `<main>`: that puts the header and footer
inside the content root, which removes the landmarks this asks for.

The report's content and navigation breakdown is diagnostic. It measures extracted
text in marked regions, not content quality. Keep useful navigation; do not remove
links or add filler to change a percentage. If much of the text is labelled "other",
check whether the real main content has a meaningful wrapper. The reported start of
main text follows HTML order, which can differ from the visual layout.

The whole report, as markdown, is at https://goodforbots.com/r/snappchart.app.md?scan=cmusm311d02u401o08gveb4ks. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

+2.5

Declare AI usage preferences

No usage declaration found in robots.txt or the final successful homepage response header.

Read prompt

My website snappchart.app scored 80/100 on Good for Bots (Good). Good for Bots measures one thing: whether a language model can read a site and cite it.

I need you to: declare the site's AI usage preferences in robots.txt or HTTP headers.

The check it fails is "Declares AI usage preferences", worth 2.5 points. What the scanner saw: No usage declaration found in robots.txt or the final successful homepage response header.

Blocking a crawler says who may fetch a page. This says what may be done with the
content afterwards (trained on, indexed, quoted in an answer), which is a different
question, and one a site can answer without blocking anybody.

There are two vocabularies for it and either is fine. Cloudflare's `Content-Signal` is
deployed at scale; the IETF AIPREF working group's `Content-Usage` is the standards-track
version. Pick one.

Cloudflare's, placed inside a user-agent group:

```
User-agent: *
Content-Signal: ai-train=no, search=yes, ai-input=yes
Allow: /
```

The three categories are `ai-train` (training or fine-tuning models), `search` (building
a search index that links back here) and `ai-input` (feeding the content to a model at
answer time, such as retrieval-augmented generation). Each takes `yes` or `no`.

The IETF version, with reversed naming for the training category and single-letter
values:

```
User-agent: *
Content-Usage: train-ai=n, search=y, ai-use=y
Allow: /
```

Alternatively, send the same IETF preference as an HTTP response header:

```http
Content-Usage: train-ai=n, search=y, ai-use=y
```

Configure it on the content responses it is meant to cover, including the final
homepage response after redirects. A header applies only to that response's content;
it is not a site-wide declaration. Do not put a robots.txt path prefix in it.
The scanner samples the final successful homepage response and awards this check
once even when both robots.txt and the header declare preferences.

Use lowercase category labels and the unquoted tokens `y` or `n`. Parameters are
ignored. Repeated HTTP fields form one dictionary: a duplicate category keeps its
last value. Keep that distinct from conflicts between separate applicable AIPREF
statements, where disallow takes precedence over allow by default. Keep the
carriers consistent with the intended policy; a header does not automatically
override robots.txt.

Decide what this project wants. A common position is to refuse training while
allowing search and grounding, so the site stays citable without feeding a model.
Omitting a category is allowed and means "unstated", not "allowed".

One caution: nothing compels a crawler to honour either directive. This is a stated
preference, not an enforcement mechanism. The standards-track vocabulary is also a draft
that can still change under you.

The whole report, as markdown, is at https://goodforbots.com/r/snappchart.app.md?scan=cmusm311d02u401o08gveb4ks. Read it first: this prompt covers one finding, and the report has everything the scan saw.

When you are done, summarise what you changed and how to check it against a running instance. Do not try to run the Good for Bots scan yourself: it only sees what is already deployed, it is rate-limited, and re-running it is the site owner's call once the change ships.

Pro

12 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 →

All 35 checks

Evidence for each, in Markdown →

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

Readable base

43.8 / 50

3.3 of 3.3 points.

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

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 Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.

5 of 10 points.

2 of 4 pages read pass; 2 partly. The page at /blog is partly structured: 2 visible content roots, where the standard allows one.

4.2 of 4.2 points.

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

2.5 of 2.5 points.

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

1.3 of 2.5 points.

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

Prompt in Pro →

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 3 pages read pass. The homepage has 4 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: 512 links across 13 sections.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 99% of links. 501 of 506 descriptions follow the link with something other than ":", the separator the format specifies (`- [name](url): notes`).

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (at least 64 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 14 AI crawlers, across 3 purposes (search, user-fetch, training).

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.

Prompt in Pro →

Penalties

− 0

Penalty: 0 of 15 points.

Penalty: 0 of 20 points.

Penalty: 0 of 25 points.

Penalty: 0 of 10 points.

Penalty: 0 of 3 points.

Agent capabilities

0 of 10 · no points

Each one found adds +1 to the badge.

Adds +1 to the badge when found.

What we found

2 of 4 pages read pass; 2 partly. The page at /blog is partly structured: 2 visible content roots, where the standard allows one.

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

Passes: Homepage
The homepage marks its content root, its heading outline and its landmarks.
Passes: /blog/ai-chart-analysis/ai-after-hours-analysis
The page at /blog/ai-chart-analysis/ai-after-hours-analysis marks its content root, its heading outline and its landmarks.
Half passes: /blog
The page at /blog is partly structured: 2 visible content roots, where the standard allows one.
Half passes: /pricing
The page at /pricing is partly structured: No <main> element and nothing carrying role="main".

Extracted words: 1,804
Headings: 22
H1 headings: 1

Content and navigation

Share of extracted homepage words by marked region. Navigation inside a header, footer or main region is counted once, under navigation.

Extracted words and their share by page region
Region	Words	Share
Main region	1,621	89.86%
Navigation	14	0.78%
Page header	0	0%
Page footer	169	9.37%
Other text	0	0%

14 words appear before the first main-region text in HTML order.

Diagnostic only; it does not affect the score. Recognised hidden text and script payloads are excluded. Stylesheet visibility and repetition across pages are unknown. A large menu is not necessarily a problem.

Heading outline · first 4

H1Know if your trade setup isworth taking before you risk real money.
H2Try it now. Upload your chart.
H2Screenshot → trade plan in three steps.
H3Drop your screenshot

18 more headings recorded

Page landmarks

contentinfo
navigation
region

How to fix

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "gaps": [],
  "pages": [
    {
      "url": "https://www.snappchart.app/",
      "reason": "structured",
      "status": "pass",
      "summary": "The homepage marks its content root, its heading outline and its landmarks.",
      "homepage": true
    },
    {
      "url": "https://www.snappchart.app/blog/ai-chart-analysis/ai-after-hours-analysis",
      "reason": "structured",
      "status": "pass",
      "summary": "The page at /blog/ai-chart-analysis/ai-after-hours-analysis marks its content root, its heading outline and its landmarks.",
      "homepage": false
    },
    {
      "url": "https://www.snappchart.app/blog",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /blog is partly structured: 2 visible content roots, where the standard allows one.",
      "homepage": false
    },
    {
      "url": "https://www.snappchart.app/pricing",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /pricing is partly structured: No <main> element and nothing carrying role=\"main\".",
      "homepage": false
    }
  ],
  "roots": [
    {
      "words": 1895,
      "source": "element",
      "hierarchicallyCorrect": true
    }
  ],
  "reason": "partly-structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "Know if your trade setup isworth taking before you risk real money.",
      "empty": false,
      "level": 1
    },
    {
      "text": "Try it now. Upload your chart.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Screenshot → trade plan in three steps.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Drop your screenshot",
      "empty": false,
      "level": 3
    },
    {
      "text": "AI agents analyze the setup",
      "empty": false,
      "level": 3
    },
    {
      "text": "Get a graded plan",
      "empty": false,
      "level": 3
    },
    {
      "text": "A second opinion that pushes back.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Bullish flag breaking out above 9/20 EMA with rising volume.",
      "empty": false,
      "level": 3
    },
    {
      "text": "The AI grades the way you trade.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Grade every setup before you risk a dollar.",
      "empty": false,
      "level": 2
    },
    {
      "text": "Weekly",
      "empty": false,
      "level": 3
    },
    {
      "text": "Monthly",
      "empty": false,
      "level": 3
    },
    "… 10 more items"
  ],
  "bodyWords": 2129,
  "landmarks": [
    {
      "role": "navigation",
      "named": false,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "contentinfo",
      "named": false,
      "source": "native",
      "element": "footer"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    }
  ],
  "textRatio": 0.0156,
  "truncated": false,
  "articleCount": 8,
  "contentWords": 1895,
  "headingCount": 22,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": true,
    "headingOutline": true
  },
  "landmarkRoles": [
    "contentinfo",
    "navigation",
    "region"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 1621,
      "other": 0,
      "footer": 169,
      "header": 0,
      "navigation": 14
    },
    "shares": {
      "main": 0.8985587583148559,
      "other": 0,
      "footer": 0.09368070953436806,
      "header": 0,
      "navigation": 0.007760532150776054
    },
    "version": 1,
    "truncated": false,
    "totalWords": 1804,
    "analysisLimited": false,
    "mainRegionCount": 1,
    "wordsBeforeMain": 14
  },
  "emptyHeadingCount": 0,
  "misnestedMainCount": 0
}

Related checks

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://www.snappchart.app/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules

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://www.snappchart.app/
robots.txt is present and valid
Declared allow · robots.txt
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- mistralai-index (ai-search)
- kimi-searchbot (ai-search)
- amzn-searchbot (ai-search)
- meta-webindexer (ai-search)
- exasearchbot (ai-search)
- aiwebindex (ai-search)
- shapbot (ai-search)
- yandexadditional (ai-search)
- yandexadditionalbot (ai-search)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- webzio-extended (ai-training)
- perplexity-user (user-fetch)
- kimi-user (user-fetch)
- amzn-user (user-fetch)
- diffbot-user (user-fetch)
- firecrawlagent (extraction)
- webzio (extraction)
- meta-externalfetcher (user-fetch, agent)
- googlebot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: *
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- oai-searchbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: oai-searchbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claude-searchbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: claude-searchbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- perplexitybot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: perplexitybot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- duckassistbot (ai-search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: duckassistbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- gptbot (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: gptbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claudebot (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: claudebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- applebot-extended (ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: applebot-extended
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- chatgpt-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: chatgpt-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claude-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: claude-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- mistralai-user (user-fetch)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: mistralai-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- google-extended (ai-training, grounding)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: google-extended
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- meta-externalagent (ai-training, product-improvement)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: meta-externalagent
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- amazonbot (ai-training, product-improvement)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: amazonbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- ccbot (open-dataset, ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: ccbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- bingbot (search)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: bingbot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- anthropic-ai (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: anthropic-ai
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- claude-web (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: claude-web
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- cohere-ai (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: cohere-ai
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- applebot (search, ai-training)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: applebot
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- perplexitybot-user (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: perplexitybot-user
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers
Declared allow · robots.txt
- mistral-ai (Unknown)
No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.
Acquisition of https://www.snappchart.app/
https://www.snappchart.app/robots.txt
```
User-agent: mistral-ai
allow: /
```
robots.txt is present and valid States a position on AI crawlers Allows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access

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://www.snappchart.app
```
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://www.snappchart.app/
```
HTTP 200
Transport: direct
```
Serves the homepage over HTTPS with HTTP 200 Serves our crawler without a challenge

Indexing directives

No indexing restriction was observed in the supported homepage directives.

Sources and scope: indexing directives

Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://www.snappchart.app/
The homepage does not block indexing or snippets

Search snippets

Scoped instructions were recorded; see their values and recipient support below.

Sources and scope: search snippets

Observed · Meta robots
- googlebot (search)
This declares a snippet instruction for the named recipients. The value is not a claim about citation by every AI operator.
This response only
https://www.snappchart.app/
```
max-snippet: -1
```
The homepage does not block indexing or snippets

Search usage

No applicable preference for this use was established.

Sources and scope: search usage

Unstated · AIPREF Content-Usage
- goodforbotsbot (Site diagnostics)
- * (Default robots group)
- oai-searchbot (ai-search)
- claude-searchbot (ai-search)
- perplexitybot (ai-search)
- mistralai-index (ai-search)
- kimi-searchbot (ai-search)
- amzn-searchbot (ai-search)
- meta-webindexer (ai-search)
- exasearchbot (ai-search)
- aiwebindex (ai-search)
- duckassistbot (ai-search)
- shapbot (ai-search)
- yandexadditional (ai-search)
- yandexadditionalbot (ai-search)
- gptbot (ai-training)
- claudebot (ai-training)
- mistralai-training (ai-training)
- kimibot (ai-training)
- ai2bot (Unknown)
- applebot-extended (ai-training)
- webzio-extended (ai-training)
- chatgpt-user (user-fetch)
- claude-user (user-fetch)
- perplexity-user (user-fetch)
- mistralai-user (user-fetch)
- kimi-user (user-fetch)
- amzn-user (user-fetch)
- diffbot-user (user-fetch)
- firecrawlagent (extraction)
- webzio (extraction)
- meta-externalfetcher (user-fetch, agent)
- google-extended (ai-training, grounding)
- meta-externalagent (ai-training, product-improvement)
- amazonbot (ai-training, product-improvement)
- ccbot (open-dataset, ai-training)
- googlebot (search)
- bingbot (search)
- anthropic-ai (Unknown)
- claude-web (Unknown)
- cohere-ai (Unknown)
- applebot (search, ai-training)
- perplexitybot-user (Unknown)
- mistral-ai (Unknown)
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://www.snappchart.app/
Declares AI usage preferences

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

2nd of 20 in AI Products & Agents

Whole category →

1Pathnovopathnovo.com
2Picturesque AIaipicturesque.com
2SnapPChart · this reportsnappchart.app

The prompts above would take SnapPChart to 98, first in its category.

To the prompts ↑

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

Scanned: 3 Oct 2026
Category: AI Products & Agents
Tags: FintechAI & Machine LearningFreemium

Site profile

Login: Detected; A sign-in button in the page header
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.

Read this report as Markdown

Removing it is free. Remove →

Scan details

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

Scanned: 3 Oct 2026
Rubric: 0.9.0
Requests: 22
Fetched: 6.3 MB
Took: 19.3 s
Homepage: 774 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
/blog/ai-chart-analysis/ai-after-hours-analysisarticle · from the sitemap · read
/blogcollection · linked from the homepage · from the sitemap · read
/pricingpricing · linked from the homepage · read

Similar reports

The whole directory →

More like SnapPChart:AI Products & Agents Fintech AI & Machine Learning Freemium

Also AI & Machine Learning

Good for Bots

goodforbots.com

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

Same category

Picturesque AI

aipicturesque.com

Freemium AI creative studio combining image, video, audio, and motion models in one workspace

Same category

Pathnovo

pathnovo.com

AI agents that parse engineering documents into structured data for enterprise systems

Same category

Pic2VideoAI

pic2videoai.com

Browser-based image-to-video tool to turn still photos into animated clips

Same category

ScriptureSide

scriptureside.app

AI Bible study and prayer companion for daily quiet time and reflection

Same category

Peak Answer

peakanswer.com

Tracks AI search visibility, finds competitor gaps, and closes them with automated content and outreach

SnapPChart

Changed your site? Run a new scan.

SnapPChart scores 80 of 100: 44 of the 50 base points, 36 of the 50 agent-layer points, no penalties.

Through a bot’s eyes

What a bot can read

What is SnapPChart?

3 prompts, 18 points

Serve Markdown when asked for it

Mark up content so a reader can find it

Declare AI usage preferences

12 more prompts in Pro

All 35 checks

Who can read this page, and for what purpose?

Declared crawling rules

Observed access

Indexing directives

Search snippets

Search usage

AI input and use

AI training

2nd of 20 in AI Products & Agents

Site profile

Scan details

Similar reports

Good for Bots

Picturesque AI

Pathnovo

Pic2VideoAI

ScriptureSide

Peak Answer