Skip to content
Good for Bots

Schedules video and posts across 15 social networks, with a REST API and MCP server for agents

Good for Bots: Excellent, 92 of 100Get this badge →

On your homepage, it turns this report’s link to reeling.app dofollow.

Scanned

What is Reeling?

Reeling is a social media scheduling and publishing product that lets users plan content, prepare video ads and schedule posts across 15 social networks from one workspace. The input describes AI caption and script drafting, a monthly calendar with bulk visibility settings, a pre-publish spam check for Reddit, Quora and Medium, and a REST API and MCP server for tools such as Claude, Cursor and OpenClaw. It is described as aimed at short-form video creators, technical founders, growth marketers and AI agent developers. Plans are listed from $2.99 per month: Starter at $2.99, Creator at $5.99 with API and MCP access, and Agency at $19.99. The contact address given is [email protected].

Through a bot’s eyes

“Reeling is a social media scheduler and AI video studio that publishes across 15 networks, with a spam check for Reddit, Quora and Medium and an MCP server and REST API for AI agents. Paid plans start at $2.99 per month.”

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 scheduling across 15 networks, per-channel permissions, bulk calendar settings, a spam shield for Reddit, Quora and Medium, and MCP and REST API automation. It states a starting price of $2.99 per month and says the API and MCP features are on Creator and Agency plans. The platform list and use cases are present as text, but the homepage is cut off partway through its feature list and does not show the full plan tiers. The Markdown version adds a product overview, a pricing table with monthly and yearly prices for Starter, Creator and Agency, and a table of supported networks with file limits and feature notes. The llms.txt file lists core pages such as pricing, about and developer documentation with short descriptions, and repeats the company summary and contact address. The JSON-LD blocks add organization contact details, a software application entry with three monthly prices, and FAQ answers about supported platforms and the browser extension.

What stays hidden

A model reading only the homepage cannot find the price of the Creator and Agency plans, which appears only in the Markdown version, llms.txt and JSON-LD. It cannot tell how the Reeling Companion browser extension works in practice or what the spam shield checks beyond the listed examples, because the homepage cuts off before the full feature list. Signup terms, free trial availability and the company location are not given.

Good for Bots report

Reeling scores 92 of 100: 45 of the 50 base points, 48 of the 50 agent-layer points, no penalties.

Earned

45 of the 50 base points above the line, 48 of the 50 agent-layer points below it.

92

Taken back

Earned, then taken back by penalties.

1
Penalties0
How scoring works · current methodology →

For the owner of reeling.app

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

44.7 / 50

Passes.

3.5 of 3.5 points.

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

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 96 URLs.

Passes.

8.8 of 8.8 points.

All 4 pages read pass. The homepage describes itself to machines as Organization, ContactPoint, WebSite in valid schema.org JSON-LD.

Half passes.

5.3 of 10.5 points.

2 of 4 pages read pass; 1 partly. The page at /pricing is barely structured: No <main> element and nothing carrying role="main".

Passes.

8.8 of 8.8 points.

83 of 83 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

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

Not applicable.

0 of 0 points.

No applicable form fields were observed in the homepage HTML.

Passes.

2.6 of 2.6 points.

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

Passes.

1.8 of 1.8 points.

All 4 pages read pass. The homepage declares itself as its canonical URL.

Agent layer

47.5 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 104 links across 7 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 100% of links.

Passes.

12.5 of 12.5 points.

/llms-full.txt serves the site's content as markdown (at least 64 KB).

Passes.

10 of 10 points.

All 4 pages read pass. The homepage serves markdown on `Accept: text/markdown`.

Passes.

5 of 5 points.

States a position on 11 AI crawlers, across 3 purposes (search, user-fetch, training).

Fails.

0 of 2.5 points.

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

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 2766 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 42 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 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.

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://reeling.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
1
CCBot. Refusing training never changes 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 searchAllowedNoneUser-agent: oai-searchbot Allow: /
Claude-SearchBotAnthropicAI searchAllowedNoneUser-agent: claude-searchbot Allow: /
PerplexityBotPerplexityAI searchAllowedNoneUser-agent: perplexitybot Allow: /
GooglebotGoogleSearchAllowedNot scoredUser-agent: googlebot Allow: /
, all allowed
Fetches a person asked for
ChatGPT-UserOpenAIUser fetchAllowedNoneUser-agent: chatgpt-user Allow: /
Claude-UserAnthropicUser fetchAllowedNoneUser-agent: claude-user Allow: /
Perplexity-UserPerplexityUser fetchAllowedNoneUser-agent: perplexity-user Allow: /
, all allowed
Model training, never scored
GPTBotOpenAIAI trainingAllowedNoneUser-agent: gptbot Allow: /
ClaudeBotAnthropicAI trainingAllowedNoneUser-agent: claudebot Allow: /
Applebot-ExtendedAppleAI trainingAllowedNoneUser-agent: applebot-extended Allow: /
Google-ExtendedGoogleAI training, GroundingAllowedNoneUser-agent: google-extended Allow: /
CCBotCommon CrawlOpen dataset, AI trainingRefusedNone: training opt-outs are neutralUser-agent: ccbot Disallow: /
, all allowed
Agents, extraction and others
bytespiderUnspecifiedNot establishedRefusedNot scoredUser-agent: bytespider Disallow: /
googlebot-imageUnspecifiedNot establishedAllowedNot scoredUser-agent: googlebot-image
, all allowed

The robots.txt groups behind this table

User-agent: oai-searchbot
Allow: /

User-agent: claude-searchbot
Allow: /

User-agent: perplexitybot
Allow: /

User-agent: gptbot
Allow: /

User-agent: claudebot
Allow: /

User-agent: applebot-extended
Allow: /

User-agent: chatgpt-user
Allow: /

User-agent: claude-user
Allow: /

User-agent: perplexity-user
Allow: /

User-agent: google-extended
Allow: /

User-agent: ccbot
Disallow: /

User-agent: googlebot
Allow: /

User-agent: bytespider
Disallow: /

User-agent: googlebot-image

User-agent: *
Allow: /

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

3rd of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 3Reeling · this reportreeling.app

The prompts in the owner view would take Reeling to 100, first 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
13 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
602.6 KB
Took
12.9 s
Homepage
42 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/reddit-quora-medium-spam-filter-rules-pre-publish-detectorarticle · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read

Do you run reeling.app? Open the owner view → Removing the listing is free. Remove →