Skip to content
Good for Bots

PayoutPeek

payoutpeek.com

Financial statement analyzer for Etsy and TikTok Shop sellers

Good for Bots: Poor, 37 of 100Get this badge →

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

Scanned

What is PayoutPeek?

PayoutPeek is a web tool designed for Etsy and TikTok Shop sellers to analyze their monthly financial statements and understand their real take-home earnings, fees, and product profitability. It targets online merchants who want to untangle lump-sum deposits, transaction fees, shipping label costs, and offsite ad charges without sharing bank login credentials or Etsy passwords. The platform processes exported statement files directly within the user browser to ensure privacy. It offers a free tier for basic statement previews alongside paid Pro and Multi subscription plans that include per-product profit calculations, multi-month combinations, and side-by-side platform comparisons.

Through a bot’s eyes

“PayoutPeek is a browser-based analysis tool for Etsy and TikTok Shop sellers that calculates real take-home pay, fee breakdowns, and product profitability from uploaded statement files without requiring bank logins.”

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

A language model reading this input learns that PayoutPeek is a browser-based analysis tool for Etsy and TikTok Shop sellers. The text covers how the tool processes monthly statements locally without requiring bank logins or account creation. It provides details on what the free preview and paid plans offer, including fee breakdowns, deposit explanations, profit per product, and red flag detection. Pricing information is explicitly stated, with a Free tier at zero dollars, a Pro plan at eight dollars per month or sixty-nine dollars per year, a waitlist founding member rate at five dollars per month, and a Multi plan at fourteen dollars per month or one hundred nineteen dollars per year. The input also details step-by-step instructions on how users download and drop in their statement files. No JSON-LD blocks, separate llms.txt files, or separate Markdown versions were provided in the input.

What stays hidden

The input does not provide information on support channels, contact details, terms of service, or technical system requirements beyond running in a browser.

Good for Bots report

PayoutPeek scores 37 of 100: 37 of the 50 base points, none of the agent layer, no penalties.

Earned

37 of the 50 base points above the line, none of the agent layer below it.

37

Still open

Behind the checks below, with prompts in Pro.

29
Penalties0
How scoring works · current methodology →

For the owner of payoutpeek.com

3 prompts, 33 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

36.7 / 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 30 URLs.

Fails.

0 of 8.3 points.

1 of 4 pages read pass. The homepage publishes no structured data at all: no JSON-LD, no microdata, no RDFa.

Prompt in Pro →
Half passes.

5 of 10 points.

2 of 4 pages read pass; 2 partly. The page at /pricing is partly structured: No <h1>, so nothing says what the page is about.

Prompt in Pro →
Passes.

8.3 of 8.3 points.

5 of 5 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

125 of 125 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.

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

0 / 50

Fails.

0 of 11.3 points.

/llms.txt returns an HTML page rather than markdown.

Fails.

0 of 7.5 points.

No usable /llms.txt to judge.

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 names no AI crawlers, so every operator has to guess.

Prompt in Pro →
Fails.

0 of 2.5 points.

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

Prompt in Pro →

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 1004 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 69 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.

/.well-known/api-catalog answers with a web page, the way a site answers a path it does not implement, so no API catalog is established.

Not applicable.

Adds +1 to the badge when found.

/auth.md returns an HTML page rather than a markdown document.

Not applicable.

Adds +1 to the badge when found.

/.well-known/ai-catalog.json returns an HTML page rather than an AI Catalog.

Not applicable.

Adds +1 to the badge when found.

/.well-known/agent-card.json returns an HTML page rather than an A2A Agent Card.

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.

/.well-known/http-message-signatures-directory returns an HTML page rather than a key directory.

Not applicable.

Adds +1 to the badge when found.

/.well-known/x402 returns an HTML page rather than an x402 manifest, and no 402 payment challenge was seen.

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://payoutpeek.com/

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://payoutpeek.com/

    robots.txt is present and valid

  • Declared allow · robots.txt

    • 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)

    No matching refusal for this URL in the applicable robots group. This is a declaration, not an access test.

    Acquisition of https://payoutpeek.com/

    https://payoutpeek.com/robots.txt

    User-agent: *
    allow: /

    robots.txt is present and validStates a position on AI crawlersAllows search and user-fetch crawlers

Observed access

GoodForBotsBot received HTTP 200 via a direct request.

Sources and scope: observed access
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

103rd of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 103PayoutPeek · this reportpayoutpeek.com

The prompts in the owner view would take PayoutPeek to 70, 27th in its category.

To the prompts →

Category average 58. 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
4 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
637.1 KB
Took
13.3 s
Homepage
69 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
  • /guides/etsy-fee-changes-2026article · from the sitemap · read
  • /pricingpricing · from the sitemap · read
  • /guides/collection · linked from the homepage · from the sitemap · read

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