Skip to content
Good for Bots

ModelSnap

modelsnap.app

AI tool that turns clothing product photos into on-model listing images for online sellers

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

ModelSnap scores 56 of 100: the whole readable base, 6 of the 50 agent-layer points, no penalties.

Earned

The whole readable base above the line, 6 of the 50 agent-layer points below it.

56

3 prompts away

Copy them below ↓

30

Still open

Behind the checks below, with prompts in Pro.

14
Penalties0
How scoring works · current methodology →

Through a bot’s eyes

“ModelSnap is an AI fashion model generator that turns clothing product photos, such as flat lays or ghost mannequin shots, into images of AI models wearing the garment for Amazon, Etsy and Shopify listings.”

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 product workflow: uploading a flat lay, mannequin or product photo, choosing a model and scene, output formats such as 3:4, 1:1 and 3:2, and a gallery of 24 AI models. It states the pricing tiers with monthly prices and credit allowances, the free allowance, and that failed images are not charged. Its FAQ answers which photos can be uploaded, whether garment details are preserved, commercial use, and that files are kept for up to 90 days. The text ends mid-sentence in a closing call to action, so the page as received is incomplete. The llms.txt adds marketplace export sizes, a five-step workflow, a cost comparison with traditional photography, documentation links and a support email address, and gives the model library as 12+ models rather than 24. The JSON-LD repeats the description, provides the FAQ answers as structured data, gives a free-trial offer at price 0, and gives a founding year of 2026 for the organization.

What stays hidden

A model reading only this input cannot tell what annual plans cost, since the homepage mentions annual billing with two months free but gives no figures. It cannot see the actual output images, only illustrative examples described in text. The input gives no company location, legal entity or team details, and the only contact address is the support email in llms.txt. Whether the 24 models on the homepage or the 12+ in llms.txt is the current number is not settled by the input.

What is ModelSnap?

ModelSnap is an AI fashion model generator for clothing sellers. Users upload a flat lay, ghost mannequin or clean product photo, choose an AI model and scene, and receive product images showing the garment on a model, for listings on Amazon, Etsy and Shopify.

Read more →

The homepage says it is aimed at independent brands, online boutiques and marketplace sellers. The input lists a free tier of 30 shared credits and paid monthly plans at $19, $49 and $99, with ten credits per finished image.

3 prompts, 30 points

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

+12.5score from 56 to 68

Serve Markdown at its own URL

No /llms-full.txt and no markdown versions linked from llms.txt.

Read prompt

+10score from 68 to 78

Serve Markdown when asked for it

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

Read prompt

+7.5score from 78 to 86

Add descriptions to llms.txt

/llms.txt lists no links, so there is nothing to describe.

Read prompt

Pro

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

Ready-made files

Pro drafts these for this site.

Pro

A ready-made llms.txt and robots.txt

Pro drafts both files for ModelSnap from its scan, keeps only links and rules our parsers can verify, and hands them over ready to review and publish. It never changes the score.

See Pro

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

Readable base

50 / 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 28 URLs.

Passes.

8.3 of 8.3 points.

All 4 pages read pass. The homepage describes itself to machines as SoftwareApplication, Offer, FAQPage in valid schema.org JSON-LD.

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.

41 of 41 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Passes.

2.5 of 2.5 points.

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

5.6 / 50

Half passes.

5.6 of 11.3 points.

/llms.txt has a title but lists no links to follow.

Prompt in Pro →
Fails.

0 of 7.5 points.

/llms.txt lists no links, so there is nothing to describe.

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 1238 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 93 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.

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

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

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

    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

52nd of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 52ModelSnap · this reportmodelsnap.app

The prompts above would take ModelSnap to 86, 8th in its category.

To the prompts ↑

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

Scanned

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.

Scan details

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

Scanned
14 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
4.1 MB
Took
20.6 s
Homepage
93 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/how-to-photograph-clothes-for-salearticle · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · read
  • /clothing-photographylinked from the homepage · from the sitemap · read