Skip to content
Good for Bots

Deals Copier

dc.flasktoken.com

Chrome extension that turns marketplace product pages into affiliate deal posts for social apps

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

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

Scanned

What is Deals Copier?

Deals Copier is a Chrome extension that turns a product page from Amazon, eBay, Walmart, Woot! or Flipkart into a ready-to-publish affiliate post. According to the input, one click captures the deal data, adds the user's affiliate tag, writes the copy with AI and formats it for Telegram, WhatsApp, Reddit, X or Facebook. It is aimed at people who share deals with affiliate links. The free tier includes 10 AI calls a month, and the Pro version, listed in the llms.txt file at a one-time 4.99 USD, unlocks unlimited AI writing and translation.

Through a bot’s eyes

“Deals Copier is a Chrome extension that turns an Amazon, eBay, Walmart, Woot! or Flipkart product page into a ready-to-publish affiliate post with AI-written copy for Telegram, WhatsApp, Reddit, X and Facebook.”

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 Chrome extension, the five output platforms, the 30 supported storefronts listed by domain, a four-step usage flow, the affiliate networks, image and video output, and the free tier with 10 AI calls a month. It states that deal data is read in the browser and not sent to the company's servers. It links to the Chrome Web Store and a sideload page but gives no Pro price. The llms.txt file adds the Pro price of 4.99 USD as a one-time payment, browser support, a privacy summary and a list of site pages. The JSON-LD repeats the description and adds structured offers with the same prices, a SoftwareApplication entry and a feature list. Together the sources state what is offered, for whom and at what cost, but no contact address or company details appear.

What stays hidden

A model reading only this input cannot learn who operates the extension, what contact address or support channel exists, or what the FAQ, changelog and terms pages contain, since they appear only as links. It also cannot see the screenshots or demo, and it does not learn how users obtain their affiliate tracking IDs or which affiliate program terms apply.

Good for Bots report

Deals Copier scores 65 of 100: 46 of the 50 base points, 19 of the 50 agent-layer points, no penalties.

Earned

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

65

Still open

Behind the checks below, with prompts in Pro.

7
Penalties0
How scoring works · current methodology →

For the owner of dc.flasktoken.com

3 prompts, 27 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 14 URLs.

Half passes.

4.2 of 8.3 points.

1 of 4 pages read pass; 3 partly. The page at /guides/amazon-affiliate-link-automatically/ 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.

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

Passes.

8.3 of 8.3 points.

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

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

Passes.

2.5 of 2.5 points.

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

18.8 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 8 links across 1 section.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% 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 names no AI crawlers, so every operator has to guess.

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 574 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 73 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
Detected
A sign-in or sign-up link
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://dc.flasktoken.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://dc.flasktoken.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://dc.flasktoken.com/

    https://dc.flasktoken.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

38th of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 38Deals Copier · this reportdc.flasktoken.com

The prompts in the owner view would take Deals Copier to 92, 3rd 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
9 Nov 2026
Rubric
0.9.0
Requests
24
Fetched
494.5 KB
Took
15.8 s
Homepage
73 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/amazon-affiliate-link-automatically/article · from the sitemap · read
  • /featuresservice · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read

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