Skip to content
Good for Bots

Invoicing and estimates for freelancers, with payment tracking and automatic reminders

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

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

Scanned

What is Incusia?

Incusia is a web application for creating invoices and estimates, sending them to clients and tracking whether they are paid. The llms.txt file says it is aimed at solo freelancers and independent contractors. The homepage lists a Starter plan at $9 a month with unlimited invoices and clients, a Pro plan at $29 a month that adds recurring invoices, time tracking, a client portal and a cash forecast, and a one-time Lifetime payment of $99. A 7-day trial needs no card. Other features mentioned include automatic payment reminders, invoices in more than 30 currencies, and payment by card, Apple Pay or bank transfer.

Through a bot’s eyes

“Incusia is an invoicing web app for freelancers and independent contractors, used to create invoices and estimates, send them and track whether they are paid. Plans start at $9 a month, with a 7-day free trial that needs no card.”

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 is mostly product marketing. It contains a sample invoice and feature sections on invoices, estimates, multi-currency billing, recurring payments, receipts, time tracking, a client portal, payment reminders, late fees and cash forecasting, along with statements about pricing and cancellation. Plan names, monthly prices, included features and trial terms appear as plain text, so a model reading it learns what is offered and at what price. The FAQ section shows its ten questions without answers, and the page gives no contact details beyond a sample email address in the invoice mockup. The llms.txt file restates the offer in a short summary, adds the pricing rules and data export, lists pages for pricing, features and alternatives to QuickBooks, FreshBooks and Invoice Simple, and gives a contact email and an X link. The JSON-LD blocks name the organisation and its founder, link a LinkedIn page, give a support email and state an offer range from $9 to $99.

What stays hidden

A model reading only this input cannot learn the answers to the FAQ questions, such as how cancellation, data export, ads or an acquisition would be handled. The Founder Playbook and Rate Setter named in the Lifetime plan are not explained. The homepage gives no business address or company registration details.

Good for Bots report

Incusia scores 63 of 100: 43 of the 50 base points, 20 of the 50 agent-layer points, no penalties.

Earned

43 of the 50 base points above the line, 20 of the 50 agent-layer points below it.

63

Still open

Behind the checks below, with prompts in Pro.

10
Penalties0
How scoring works · current methodology →

For the owner of incusia.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

43.4 / 50

Passes.

3.5 of 3.5 points.

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

Passes.

8.8 of 8.8 points.

Sitemap declared in robots.txt, listing 166 URLs.

Passes.

8.8 of 8.8 points.

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

Passes.

10.5 of 10.5 points.

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

Half passes.

4.4 of 8.8 points.

32 of 33 assessed homepage navigation links expose usable destinations.

Passes.

4.4 of 4.4 points.

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

Half passes.

1.3 of 2.6 points.

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

Prompt in Pro →
Passes.

1.8 of 1.8 points.

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

Agent layer

20 / 50

Passes.

11.3 of 11.3 points.

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

Half passes.

3.8 of 7.5 points.

/llms.txt is partly descriptive: only 57% of links carry a description.

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.

Passes.

5 of 5 points.

States a position on 7 AI crawlers, across 2 purposes (training, search).

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 1040 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 444 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://incusia.com/

Declared crawling rules

No matching refusal for this URL was found for the listed identities.

Sources and scope: declared crawling rules

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

43rd of 111 in SaaS & Web Apps

  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 43Incusia · this reportincusia.com

The prompts in the owner view would take Incusia to 90, 5th 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
10 Nov 2026
Rubric
0.9.0
Requests
23
Fetched
1.9 MB
Took
17.4 s
Homepage
444 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/can-i-charge-interest-on-late-invoicearticle · from the sitemap · read
  • /blogcollection · linked from the homepage · from the sitemap · read
  • /pricingpricing · linked from the homepage · from the sitemap · read

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