Skip to content
Good for Bots

Free CLI, Mac app and MCP server for scheduling posts to X, Bluesky, Mastodon, LinkedIn and Reddit

Good for Bots: Good, 87 of 100Get this badge →

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

Scanned

What is Statuz?

Statuz is a tool for scheduling and publishing posts and threads to X, Bluesky, Mastodon, LinkedIn and Reddit. It has three parts: a Mac menu bar app with a queue, composer and calendar; a command-line tool and MCP server that agents such as Claude Code, Codex and Cursor can drive; and Statuz Cloud, an optional hosted service for always-on publishing and a web composer. The input describes the CLI and Mac app as free to run on your own computer, without an account. It is aimed at people who post to these networks and want to schedule from their desktop, terminal or AI agent. The site links to an install guide, a quick start, a CLI reference and a pricing page, and describes Statuz Cloud as paid per published post with prepaid credits.

Through a bot’s eyes

“Statuz is a free command-line tool and Mac app for scheduling posts and threads to X, Bluesky, Mastodon, LinkedIn and Reddit, with an MCP server that lets AI agents schedule them too. Statuz Cloud is an optional paid hosted version.”

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 model reading this input learns that the page covers scheduling posts from a Mac menu bar app and from a terminal, with a CLI and MCP server for AI agents. Most of the homepage is product copy with sample command output, showing example posts, account listings, status checks and retry behaviour for failed posts. Install steps for Homebrew, npm, Bun and a shell script appear as text, together with the commands to connect accounts and start the daemon. The supported networks are named in plain text, and the homepage states that the CLI and Mac app are free on your own computer. The Markdown version repeats the same sections with the install details spelled out. The llms.txt file adds a short summary and lists documentation pages for accounts, agents, the CLI, scheduling, Cloud and pricing, describing pricing as pay per post with no subscription. The JSON-LD adds per-post Cloud prices, prepaid credits starting at $5, and FAQ answers on sign-in tokens and agent support. The homepage text itself gives no Cloud prices.

What stays hidden

A model reading only this input cannot find who runs Statuz beyond a name in the structured data, or any postal address, company registration or support contact. The homepage text is cut off before its end, and the pricing page and full documentation were not read, so Cloud plan details beyond the per-post figures are not visible. Reddit support is called beta only in the FAQ, and the input gives no information on usage or on any platforms beyond the five listed.

Good for Bots report

Statuz scores 87 of 100: 46 of the 50 base points, 41 of the 50 agent-layer points, no penalties.

Earned

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

87
Penalties0
How scoring works · current methodology →

For the owner of statuz.app

3 prompts, 13 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 30 URLs.

Half passes.

4.2 of 8.3 points.

2 of 4 pages read pass; 2 partly. The page at /docs/cloud declares BreadcrumbList but names none of them, so the markup asserts that something exists without saying what.

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.

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

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

Passes.

2.5 of 2.5 points.

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

41.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 17 links across 10 sections.

Half passes.

3.8 of 7.5 points.

/llms.txt is partly descriptive: it has no summary blockquote under the title.

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`.

Fails.

0 of 5 points.

robots.txt states AI usage preferences, but names no AI crawler individually.

Passes.

2.5 of 2.5 points.

Declares AI usage preferences via Content-Signal (robots.txt): ai-train, ai-input, search.

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 3486 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 113 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.

/auth.md is a markdown document, but not an auth.md: it never addresses an agent and links no OAuth metadata.

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
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://statuz.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://statuz.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://statuz.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://statuz.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://statuz.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

5th of 58 in Developer Tools & APIs

  1. 1Good for Botsgoodforbots.com
  2. 2ProxyJamproxyjam.com
  3. 5Statuz · this reportstatuz.app

The prompts in the owner view would take Statuz to 100, 2nd in its category.

To the prompts →

Category average 63. 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
22 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
891.7 KB
Took
16.5 s
Homepage
113 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/best-times-to-post-art-and-visual-content-on-x-twitter-in-2025article · linked from the homepage · from the sitemap · read
  • /docs/clouddocumentation · linked from the homepage · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read

More like Statuz:Developer Tools & APIsMarketingDevelopersFreemium

Same category

goodforbots.com

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

Same category

volanea.com

Transactional email, campaigns, and automation API with AI agent support

Also Marketing

brivoy.com

Community site where makers launch new products and early adopters discover them

Also Developers

dolaai.pro

AI agent that edits Unreal Engine 5.7 Blueprints, C++ and levels in the open editor

Also Developers

saascubes.com

Curated SaaS directory offering permanent do-follow backlinks for modern software products

Also Marketing

vouchgeo.com

Tracks how AI assistants mention a brand across multi-question buying conversations

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