Skip to content
Good for Bots

Invoiceize

invoiceize.com

Free online generator for invoices, receipts, quotes, and pay stubs with PDF export

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

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

Scanned
Category
SaaS & Web Apps
Tags
Finance & AccountingProductivityB2B
Markdown
Read this report

What is Invoiceize?

Invoiceize is a free online document generator that provides tools to create invoices, receipts, quotations, and pay stubs. Designed for freelancers, hourly workers, consultants, and contractors who want to avoid complex accounting software, the platform allows users to fill in business and client details, add line items with automatic calculations, and download clean PDF documents without watermarks. Users can choose from Classic, Modern, and Minimal layouts, customize labels, upload logos, and apply brand colors. Documents are saved automatically in the user's browser local storage, with an optional free account available for cloud synchronization across devices.

Through a bot’s eyes

“Invoiceize is a free online generator for invoices, receipts, quotes, and pay stubs that allows users to create and download water-mark-free PDFs directly in the browser.”

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 language model reading the provided homepage text, llms.txt, and JSON-LD blocks learns that Invoiceize is a browser-based financial document generator offering free PDF creation for invoices, receipts, quotes, and pay stubs. The text covers step-by-step instructions on making an invoice, structural components of complete invoices, template categories for different professions, and frequently asked questions regarding cost, data privacy, and account requirements. The llms.txt and JSON-LD files supplement the homepage by providing explicit data about pricing (free), support email addresses, optional AI scan and fill features, browser versus cloud storage specifications, and structured schema organization data. Specific contact details, guides, and template links are clearly detailed throughout the text.

Good for Bots report

Invoiceize scores 70 of 100: 44 of the 50 base points, 26 of the 50 agent-layer points, no penalties.

Earned

44 of the 50 base points above the line, 26 of the 50 agent-layer points below it.

70
28

Still open

Behind the checks below, with prompts in Pro.

2
Penalties0
How scoring works · current methodology →

For the owner of invoiceize.com

3 prompts, 28 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 →

All 36 checks

Evidence for each, in Markdown →

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

Readable base

43.8 / 50

Passes.

3.3 of 3.3 points.

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

Passes.

8.3 of 8.3 points.

Sitemap declared in robots.txt, listing 66 URLs.

Passes.

8.3 of 8.3 points.

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

Half passes.

5 of 10 points.

None of the 4 pages read pass fully; 4 partly. The homepage is partly structured: No <main> element and nothing carrying role="main".

Passes.

8.3 of 8.3 points.

6 of 6 assessed homepage navigation links expose usable destinations.

Passes.

4.2 of 4.2 points.

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

Passes.

2.5 of 2.5 points.

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

Half passes.

1.3 of 2.5 points.

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

Prompt in Pro →
Passes.

1.7 of 1.7 points.

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

Agent layer

26.3 / 50

Passes.

11.3 of 11.3 points.

/llms.txt is well formed: 12 links across 4 sections.

Passes.

7.5 of 7.5 points.

/llms.txt is descriptive: a summary plus descriptions on 75% 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.

Passes.

5 of 5 points.

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

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 1708 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 198 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.

Readable base · invoiceize.com

robots.txt

robots.txt is present and valid

Passes3.3 of 3.3 points

What we found

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

Crawler groups
16
Directives
34
Sitemap declarations
1

Parser findings

No parser errors recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "errors": [],
  "groups": 16,
  "sitemaps": 1,
  "directives": 34
}

Related checks

See sites that pass robots.txt →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Readable base · invoiceize.com

Sitemap

Sitemap is present and parses

Passes8.3 of 8.3 points

What we found

Sitemap declared in robots.txt, listing 66 URLs.

URLs collected
66
Documents checked
1
Discovery via robots.txt
Declared

Sitemap sample

  • https://invoiceize.com/sitemap.xml · 66 URLs
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "urlCount": 66,
  "documents": [
    {
      "url": "https://invoiceize.com/sitemap.xml",
      "kind": "urlset",
      "urls": 66,
      "error": null,
      "valid": true,
      "children": 0,
      "compressed": false
    }
  ],
  "declaredInRobots": true
}

Related checks

See sites that pass Sitemap →
Methodology →

Readable base · invoiceize.com

schema.org JSON-LD

Describes itself to machines with schema.org JSON-LD

Passes8.3 of 8.3 points

What we found

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

Pages read

Each page is checked on its own; the median page decides. Types and counts below cover every page read.

  • Passes: Homepage

    The homepage describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.

  • Passes: /blog/how-to-make-an-invoice/

    The page at /blog/how-to-make-an-invoice/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.

  • Passes: /blog/

    The page at /blog/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.

  • Passes: /about/

    The page at /about/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.

Entities
68
Valid JSON-LD blocks
14
Pages examined
4

JSON-LD types

  • Organization
  • ImageObject
  • ContactPoint
  • WebSite
  • SoftwareApplication
  • Person

+12 more recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "nodes": 68,
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "ok",
      "status": "pass",
      "summary": "The homepage describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "ok",
      "status": "pass",
      "summary": "The page at /blog/how-to-make-an-invoice/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/blog/",
      "reason": "ok",
      "status": "pass",
      "summary": "The page at /blog/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/about/",
      "reason": "ok",
      "status": "pass",
      "summary": "The page at /about/ describes itself to machines as Organization, ImageObject, ContactPoint in valid schema.org JSON-LD.",
      "homepage": false
    }
  ],
  "types": [
    "Organization",
    "ImageObject",
    "ContactPoint",
    "WebSite",
    "SoftwareApplication",
    "Person",
    "AggregateOffer",
    "Offer",
    "FAQPage",
    "Question",
    "Answer",
    "HowTo",
    "… 6 more items"
  ],
  "blocks": 14,
  "reason": "ok",
  "contexts": [
    "https://schema.org"
  ],
  "rdfaTypes": [],
  "truncated": false,
  "validBlocks": 14,
  "brokenBlocks": [],
  "unknownTypes": [],
  "pagesExamined": 4,
  "skippedBlocks": 0,
  "topLevelNodes": 14,
  "microdataTypes": [],
  "missingProperties": [],
  "unnamedTopLevelTypes": [
    "FAQPage",
    "BreadcrumbList"
  ]
}

Related checks

See sites that pass schema.org JSON-LD →
Methodology →

Readable base · invoiceize.com

Semantic HTML

Content is marked up so a reader can find it

Half passes5 of 10 points

What we found

None of the 4 pages read pass fully; 4 partly. The homepage is partly structured: No <main> element and nothing carrying role="main".

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Half passes: Homepage

    The homepage is partly structured: No <main> element and nothing carrying role="main".

  • Half passes: /blog/how-to-make-an-invoice/

    The page at /blog/how-to-make-an-invoice/ is partly structured: No <main> element and nothing carrying role="main".

  • Half passes: /blog/

    The page at /blog/ is partly structured: No <main> element and nothing carrying role="main".

  • Half passes: /about/

    The page at /about/ is partly structured: No <main> element and nothing carrying role="main".

Extracted words
1,741
Headings
44
H1 headings
1

Content and navigation

Share of extracted homepage words by marked region. Navigation inside a header, footer or main region is counted once, under navigation.

Extracted words and their share by page region
RegionWordsShare
Main region00%
Navigation140.8%
Page header211.21%
Page footer382.18%
Other text1,66895.81%

No main region was identified; other text may include the page’s main content.

Diagnostic only; it does not affect the score. Recognised hidden text and script payloads are excluded. Stylesheet visibility and repetition across pages are unknown. A large menu is not necessarily a problem.

Heading outline · first 4

  • H1Free Invoice Generator
  • H2Your business
  • H2Bill to
  • H2What are you charging for?

40 more headings recorded

Page landmarks

  • banner
  • contentinfo
  • navigation
  • region

Structure findings

  • No <main> element and nothing carrying role="main".

How to fix

+5score from 93 to 98
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "gaps": [
    "No <main> element and nothing carrying role=\"main\"."
  ],
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The homepage is partly structured: No <main> element and nothing carrying role=\"main\".",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /blog/how-to-make-an-invoice/ is partly structured: No <main> element and nothing carrying role=\"main\".",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/blog/",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /blog/ is partly structured: No <main> element and nothing carrying role=\"main\".",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/about/",
      "reason": "partly-structured",
      "status": "warn",
      "summary": "The page at /about/ is partly structured: No <main> element and nothing carrying role=\"main\".",
      "homepage": false
    }
  ],
  "roots": [],
  "reason": "partly-structured",
  "h1Count": 1,
  "headings": [
    {
      "text": "Free Invoice Generator",
      "empty": false,
      "level": 1
    },
    {
      "text": "Your business",
      "empty": false,
      "level": 2
    },
    {
      "text": "Bill to",
      "empty": false,
      "level": 2
    },
    {
      "text": "What are you charging for?",
      "empty": false,
      "level": 2
    },
    {
      "text": "Details",
      "empty": false,
      "level": 2
    },
    {
      "text": "Show on invoice",
      "empty": false,
      "level": 3
    },
    {
      "text": "Customize wording",
      "empty": false,
      "level": 2
    },
    {
      "text": "How to make an invoice in 3 steps",
      "empty": false,
      "level": 2
    },
    {
      "text": "Fill in who and what",
      "empty": false,
      "level": 3
    },
    {
      "text": "Pick a look",
      "empty": false,
      "level": 3
    },
    {
      "text": "Download and send",
      "empty": false,
      "level": 3
    },
    {
      "text": "What goes on an invoice",
      "empty": false,
      "level": 2
    },
    "… 32 more items"
  ],
  "bodyWords": 1781,
  "landmarks": [
    {
      "role": "banner",
      "named": false,
      "source": "native",
      "element": "header"
    },
    {
      "role": "navigation",
      "named": true,
      "source": "native",
      "element": "nav"
    },
    {
      "role": "region",
      "named": true,
      "source": "native",
      "element": "section"
    },
    {
      "role": "region",
      "named": true,
      "source": "role",
      "element": "div"
    },
    {
      "role": "contentinfo",
      "named": false,
      "source": "native",
      "element": "footer"
    }
  ],
  "textRatio": 0.0328,
  "truncated": false,
  "articleCount": 1,
  "contentWords": 1708,
  "headingCount": 44,
  "headingSkips": [],
  "requirements": {
    "landmarks": true,
    "contentRoot": false,
    "headingOutline": true
  },
  "landmarkRoles": [
    "banner",
    "contentinfo",
    "navigation",
    "region"
  ],
  "hiddenMainCount": 0,
  "textComposition": {
    "words": {
      "main": 0,
      "other": 1668,
      "footer": 38,
      "header": 21,
      "navigation": 14
    },
    "shares": {
      "main": 0,
      "other": 0.95807007466973,
      "footer": 0.021826536473291212,
      "header": 0.012062033314187249,
      "navigation": 0.0080413555427915
    },
    "version": 1,
    "truncated": false,
    "totalWords": 1741,
    "analysisLimited": false,
    "mainRegionCount": 0,
    "wordsBeforeMain": null
  },
  "emptyHeadingCount": 0,
  "misnestedMainCount": 0
}

Related checks

See sites that pass Semantic HTML →
Methodology →

Readable base · invoiceize.com

Crawlable navigation

Navigation links expose usable destinations

Passes8.3 of 8.3 points

What we found

6 of 6 assessed homepage navigation links expose usable destinations.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 6,
  "page": "homepage",
  "total": 6,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "skippedContactLinks": 0,
  "brokenLabelReferences": 0
}

Related checks

See sites that pass Crawlable navigation →
Methodology →

Readable base · invoiceize.com

Named links and buttons

Links and buttons have accessible names

Passes4.2 of 4.2 points

What we found

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

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 437,
  "page": "homepage",
  "total": 437,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "skippedContactLinks": 0,
  "brokenLabelReferences": 0
}

Related checks

See sites that pass Named links and buttons →
Methodology →

Readable base · invoiceize.com

Named form fields

Form fields have names and recognizable semantics

Passes2.5 of 2.5 points

What we found

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

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 43,
  "page": "homepage",
  "total": 43,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [],
  "truncated": false,
  "nativeForms": 0,
  "submitControls": 0,
  "inputTypeFallbacks": 0,
  "formsWithoutSubmitControl": 0
}

Related checks

See sites that pass Named form fields →
Methodology →

Readable base · invoiceize.com

Control roles and states

Controls expose roles, states and relationships

Half passes1.3 of 2.5 points

What we found

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

How to fix

The prompt is in Pro →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "good": 481,
  "page": "homepage",
  "total": 482,
  "reason": "observed-gaps",
  "limited": false,
  "examples": [
    {
      "id": "",
      "href": null,
      "issue": "broken-aria-controls",
      "element": "button"
    }
  ],
  "truncated": false
}

Related checks

See sites that pass Control roles and states →
Methodology →

Readable base · invoiceize.com

Canonical URL

Each page declares one usable canonical URL

Passes1.7 of 1.7 points

What we found

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

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage declares itself as its canonical URL.

  • Passes: /blog/how-to-make-an-invoice/

    The page at /blog/how-to-make-an-invoice/ declares itself as its canonical URL.

  • Passes: /blog/

    The page at /blog/ declares itself as its canonical URL.

  • Passes: /about/

    The page at /about/ declares itself as its canonical URL.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "declared",
      "status": "pass",
      "summary": "The homepage declares itself as its canonical URL.",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "declared",
      "status": "pass",
      "summary": "The page at /blog/how-to-make-an-invoice/ declares itself as its canonical URL.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/blog/",
      "reason": "declared",
      "status": "pass",
      "summary": "The page at /blog/ declares itself as its canonical URL.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/about/",
      "reason": "declared",
      "status": "pass",
      "summary": "The page at /about/ declares itself as its canonical URL.",
      "homepage": false
    }
  ],
  "reason": "declared",
  "target": "https://invoiceize.com/",
  "readings": [
    {
      "url": "https://invoiceize.com/",
      "target": "https://invoiceize.com/",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://invoiceize.com/",
          "href": "https://invoiceize.com/",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "target": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
          "href": "https://invoiceize.com/blog/how-to-make-an-invoice/",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    },
    {
      "url": "https://invoiceize.com/blog/",
      "target": "https://invoiceize.com/blog/",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://invoiceize.com/blog/",
          "href": "https://invoiceize.com/blog/",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    },
    {
      "url": "https://invoiceize.com/about/",
      "target": "https://invoiceize.com/about/",
      "relative": false,
      "crossHost": false,
      "truncated": false,
      "duplicates": 0,
      "declarations": [
        {
          "url": "https://invoiceize.com/about/",
          "href": "https://invoiceize.com/about/",
          "source": "head"
        }
      ],
      "selfReference": true,
      "invalidDeclarations": 0
    }
  ],
  "relative": false,
  "crossHost": false,
  "truncated": false,
  "duplicates": 0,
  "declarations": [
    {
      "url": "https://invoiceize.com/",
      "href": "https://invoiceize.com/",
      "source": "head"
    }
  ],
  "selfReference": true,
  "invalidDeclarations": 0
}

Related checks

See sites that pass Canonical URL →
Methodology →

Readable base · invoiceize.com

Working section links

Section links reach an element on the page

Passes0.8 of 0.8 points

What we found

Both pages read pass. The homepage has 2 section links, and every one reaches an element on the page.

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Passes: Homepage

    The homepage has 2 section links, and every one reaches an element on the page.

  • Passes: /blog/how-to-make-an-invoice/

    The page at /blog/how-to-make-an-invoice/ has 56 section links, and every one reaches an element on the page.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "working",
      "status": "pass",
      "summary": "The homepage has 2 section links, and every one reaches an element on the page.",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "working",
      "status": "pass",
      "summary": "The page at /blog/how-to-make-an-invoice/ has 56 section links, and every one reaches an element on the page.",
      "homepage": false
    }
  ],
  "reason": "working",
  "readings": [
    {
      "top": 0,
      "url": "https://invoiceize.com/",
      "working": 2,
      "assessed": 2,
      "examples": [],
      "truncated": false,
      "baseElsewhere": 0,
      "missingTarget": 0,
      "textDirectives": 0,
      "scriptAddresses": 0
    },
    {
      "top": 0,
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "working": 56,
      "assessed": 56,
      "examples": [],
      "truncated": false,
      "baseElsewhere": 0,
      "missingTarget": 0,
      "textDirectives": 0,
      "scriptAddresses": 0
    }
  ]
}

Related checks

See sites that pass Working section links →
Methodology →

Agent layer · invoiceize.com

llms.txt

llms.txt is present and well formed

Passes11.3 of 11.3 points

What we found

/llms.txt is well formed: 12 links across 4 sections.

Links
12
Sections
5
Characters
5,919
Document title
Invoiceize
Opening summary
Present

Parser findings

No parser errors recorded

File contents are not shown here.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "links": 12,
  "title": "Invoiceize",
  "errors": [],
  "sections": 5,
  "charLength": 5919,
  "hasSummary": true,
  "sectionsWithLinks": 4
}

Related checks

See sites that pass llms.txt →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · invoiceize.com

Descriptive llms.txt

llms.txt is descriptive, not a bare link list

Passes7.5 of 7.5 points

What we found

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

Links
12
Characters
5,919
Links with descriptions
9
Opening summary
Present
Additional context
Not found

File contents are not shown here.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "links": 12,
  "charLength": 5919,
  "hasDetails": false,
  "hasSummary": true,
  "describedLinks": 9,
  "descriptionRatio": 0.75,
  "unconventionalSeparators": 0
}

Related checks

See sites that pass Descriptive llms.txt →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · invoiceize.com

llms-full.txt or .md pages

Serves markdown at its own URL

Fails0 of 12.5 points

What we found

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

Bytes received
0
Markdown links in llms.txt
0

Response receivedHTTP 404

Full-text file
Not usable

How to fix

+12.5score from 70 to 83
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "none",
  "llmsFullTxt": {
    "status": 404,
    "usable": false,
    "rejected": null,
    "truncated": false,
    "byteLength": 0
  },
  "markdownLinksInLlmsTxt": 0,
  "servesMarkdownOnRequest": false
}

Related checks

See sites that pass llms-full.txt or .md pages →Check again: llms.txt checker →Guide: How to write a useful llms.txt →
Methodology →

Agent layer · invoiceize.com

Markdown negotiation

Serves markdown when asked for it

Fails0 of 10 points

What we found

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

Pages read

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Fails: Homepage

    Asking the homepage for markdown still returns text/html.

  • Fails: /blog/how-to-make-an-invoice/

    Asking the page at /blog/how-to-make-an-invoice/ for markdown still returns text/html.

  • Fails: /blog/

    Asking the page at /blog/ for markdown still returns text/html.

  • Fails: /about/

    Asking the page at /about/ for markdown still returns text/html.

Response characters
310,342

Response received

Content-Type: text/html; charset=utf-8

Vary: Accept
Not found

How to fix

+10score from 83 to 93
Copy the prompt in the owner view →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "vary": "accept-encoding",
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "not-markdown",
      "status": "fail",
      "summary": "Asking the homepage for markdown still returns text/html.",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "not-markdown",
      "status": "fail",
      "summary": "Asking the page at /blog/how-to-make-an-invoice/ for markdown still returns text/html.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/blog/",
      "reason": "not-markdown",
      "status": "fail",
      "summary": "Asking the page at /blog/ for markdown still returns text/html.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/about/",
      "reason": "not-markdown",
      "status": "fail",
      "summary": "Asking the page at /about/ for markdown still returns text/html.",
      "homepage": false
    }
  ],
  "reason": "not-markdown",
  "charset": "utf-8",
  "variant": null,
  "bodyLength": 310342,
  "contentType": "text/html; charset=utf-8",
  "variesOnAccept": false
}

Related checks

See sites that pass Markdown negotiation →Check again: Markdown negotiation checker →Guide: How to serve Markdown to AI agents with content negotiation →
Methodology →

Agent layer · invoiceize.com

AI crawler rules

States a position on AI crawlers

Passes5 of 5 points

What we found

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

Named AI crawlers
12
Wildcard rule at /
Does not block crawling

Allowed at /

  • oai-searchbot
  • chatgpt-user
  • claude-searchbot
  • claude-user
  • perplexitybot
  • amazonbot

+6 more recorded

Blocked at /

None recorded

Declared purposes

  • search
  • user-fetch
  • training
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "allowed": [
    "oai-searchbot",
    "chatgpt-user",
    "claude-searchbot",
    "claude-user",
    "perplexitybot",
    "amazonbot",
    "gptbot",
    "claudebot",
    "google-extended",
    "applebot-extended",
    "ccbot",
    "meta-externalagent"
  ],
  "blocked": [],
  "purposes": [
    "search",
    "user-fetch",
    "training"
  ],
  "crawlersNamed": 12,
  "wildcardBlocksEverything": false
}

Related checks

See sites that pass AI crawler rules →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Agent layer · invoiceize.com

Content Signals

Declares AI usage preferences

Passes2.5 of 2.5 points

What we found

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

Preference vocabularies

  • Content-Signal

Content-Signal declarations

  • search=yes,ai-input=yes,ai-train=yes

Content-Usage declarations

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "carriers": [
    "robots.txt"
  ],
  "contentUsage": [],
  "vocabularies": [
    "Content-Signal"
  ],
  "contentSignal": [
    "search=yes,ai-input=yes,ai-train=yes"
  ],
  "contentUsageHeader": null,
  "recognisedUsageCategories": [],
  "recognisedSignalCategories": [
    "ai-train",
    "ai-input",
    "search"
  ]
}

Related checks

See sites that pass Content Signals →Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Agent layer · invoiceize.com

Typed links

Advertises machine-readable resources with typed links

Fails0 of 1.3 points

What we found

None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.

Each page is checked on its own; the median page decides. The measurements below describe the homepage.

  • Fails: Homepage

    The homepage's links are all ordinary page furniture; none point an agent anywhere.

  • Fails: /blog/how-to-make-an-invoice/

    The page at /blog/how-to-make-an-invoice/'s links are all ordinary page furniture; none point an agent anywhere.

  • Fails: /blog/

    The page at /blog/'s links are all ordinary page furniture; none point an agent anywhere.

  • Fails: /about/

    The page at /about/'s links are all ordinary page furniture; none point an agent anywhere.

Links inspected
13

Discovery relations

None recorded

Other relations

  • preconnect
  • canonical
  • stylesheet
  • icon
  • apple-touch-icon

How to fix

The prompt is in Pro →
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "url": "https://invoiceize.com/",
      "reason": "ambient-only",
      "status": "fail",
      "summary": "The homepage's links are all ordinary page furniture; none point an agent anywhere.",
      "homepage": true
    },
    {
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "reason": "ambient-only",
      "status": "fail",
      "summary": "The page at /blog/how-to-make-an-invoice/'s links are all ordinary page furniture; none point an agent anywhere.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/blog/",
      "reason": "ambient-only",
      "status": "fail",
      "summary": "The page at /blog/'s links are all ordinary page furniture; none point an agent anywhere.",
      "homepage": false
    },
    {
      "url": "https://invoiceize.com/about/",
      "reason": "ambient-only",
      "status": "fail",
      "summary": "The page at /about/'s links are all ordinary page furniture; none point an agent anywhere.",
      "homepage": false
    }
  ],
  "reason": "ambient-only",
  "sources": [],
  "totalLinks": 13,
  "ambientOnly": [
    "preconnect",
    "canonical",
    "stylesheet",
    "icon",
    "apple-touch-icon"
  ],
  "markdownAlternates": [],
  "meaningfulRelations": []
}

Related checks

See sites that pass Typed links →Guide: How to serve Markdown to AI agents with content negotiation →
Methodology →

Penalties · invoiceize.com

No bot challenge

Serves our crawler without a challenge

PassesPenalty: 0 of 15 points

What we found

Our crawler reaches the page without being challenged.

Response receivedHTTP 200

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "status": 200
}

Related checks

Methodology →

Penalties · invoiceize.com

No noindex

The homepage does not block indexing or snippets

PassesPenalty: 0 of 20 points

What we found

Nothing on the homepage tells a crawler to skip it or to withhold its snippet.

Indexing restrictions

None recorded

Snippet restrictions

None recorded

Training opt-outs

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "blocking": [],
  "finalUrl": "https://invoiceize.com/",
  "redirects": 0,
  "directives": [],
  "ignoredScopes": [],
  "trainingOptOut": [],
  "snippetBlocking": []
}

Related checks

Methodology →

Penalties · invoiceize.com

No JavaScript wall

Serves its content without JavaScript

PassesPenalty: 0 of 25 points

What we found

The captured homepage HTML contains 1708 content words; completeness is not assessed.

Words in raw HTML
1,708
Script elements
15
Markup characters
310,342

Measured from the response HTML, before JavaScript runs.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "text-observed",
  "bodyWords": 1781,
  "truncated": false,
  "scriptCount": 15,
  "contentWords": 1708,
  "markupLength": 310342,
  "passWordThreshold": 120,
  "hasNoscriptFallback": false,
  "nontextElementCount": 916
}

Related checks

Guide: How to serve content AI crawlers can read without JavaScript →
Methodology →

Penalties · invoiceize.com

AI search bots let in

Allows search and user-fetch crawlers

PassesPenalty: 0 of 25 points

What we found

robots.txt allows every known search and user-fetch crawler to reach the homepage.

Blocked crawlers
0
Path checked
/

Blocked crawlers

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "path": "/",
  "capped": false,
  "blocked": [],
  "blockedCount": 0,
  "penaltyPoints": 0
}

Related checks

Check again: robots.txt checker →Guide: How to write robots.txt rules for AI crawlers →
Methodology →

Penalties · invoiceize.com

HTTPS and HTTP 200

Serves the homepage over HTTPS with HTTP 200

PassesPenalty: 0 of 10 points

What we found

The homepage is served over HTTPS and returns HTTP 200.

Response receivedHTTP 200

https://invoiceize.com

Final URL: https://invoiceize.com/

Final connection
HTTPS
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "error": null,
  "secure": true,
  "status": 200,
  "finalUrl": "https://invoiceize.com/",
  "requestedUrl": "https://invoiceize.com"
}

Related checks

Methodology →

Penalties · invoiceize.com

Title and description

Provides a title and meta description

PassesPenalty: 0 of 3 points

What we found

The homepage provides both a non-empty title and meta description.

Title elements
1
Meta descriptions
1

Page metadata

Free Invoice Generator — Create PDF Invoices | Invoiceize

Free invoice generator with live preview: add your logo, tax and discounts, then download a PDF invoice. No signup, no watermark, saved in your browser.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "title": "Free Invoice Generator — Create PDF Invoices | Invoiceize",
  "titleCount": 1,
  "description": "Free invoice generator with live preview: add your logo, tax and discounts, then download a PDF invoice. No signup, no watermark, saved in your browser.",
  "descriptionCount": 1
}

Related checks

Methodology →

Penalties · invoiceize.com

Two redirects at most

Reaches the homepage within two redirects

PassesPenalty: 0 of 3 points

What we found

The homepage is reached in 0 redirects.

Redirects
0

Response received

https://invoiceize.com

Final URL: https://invoiceize.com/

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "finalUrl": "https://invoiceize.com/",
  "redirects": 0,
  "threshold": 2,
  "requestedUrl": "https://invoiceize.com"
}

Related checks

Methodology →

Penalties · invoiceize.com

Answers within 3 s

Returns the homepage within three seconds

PassesPenalty: 0 of 3 points

What we found

The homepage reached a plain crawler in 198 ms.

Response time
198 ms
Direct attempts
1
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "durationMs": 198,
  "thresholdMs": 3000,
  "directAttempts": 1
}

Related checks

Methodology →

Agent capabilities · invoiceize.com

API catalog

Publishes an API catalog

Not applicableAdds +1 to the badge when found

What we found

No API catalog published.

Response receivedHTTP 404

Discovery result
absent

Advertised via

None recorded

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "wellKnown": {
    "status": 404,
    "problem": "absent",
    "profile": null,
    "contentType": null
  },
  "advertisedVia": []
}

Related checks

See sites that pass API catalog →
Methodology →

Agent capabilities · invoiceize.com

auth.md

Publishes an auth.md for agents

Not applicableAdds +1 to the badge when found

What we found

No /auth.md published.

Response receivedHTTP 404

Content-Type: text/html

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "error": null,
  "reason": "absent",
  "status": 404,
  "contentType": "text/html"
}

Related checks

See sites that pass auth.md →
Methodology →

Agent capabilities · invoiceize.com

MCP server card

Lists an MCP server card in its AI Catalog

Not applicableAdds +1 to the badge when found

What we found

No AI Catalog published, so no MCP server card can be discovered.

Catalog entries
0

Response receivedHTTP 404

Discovery result
absent
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "catalog": {
    "status": 404,
    "entries": 0,
    "problem": "absent",
    "contentType": null,
    "specVersion": null,
    "malformedEntries": 0
  }
}

Related checks

See sites that pass MCP server card →
Methodology →

Agent capabilities · invoiceize.com

A2A agent card

Publishes an A2A Agent Card

Not applicableAdds +1 to the badge when found

What we found

No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.

Catalog entries
0

Response receivedHTTP 404

Content-Type: text/html; charset=utf-8

Discovery result
absent
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "cards": [
    {
      "via": "well-known",
      "name": null,
      "error": null,
      "notes": [],
      "shape": null,
      "skills": 0,
      "source": "https://invoiceize.com/.well-known/agent-card.json",
      "status": 404,
      "usable": false,
      "problem": "absent",
      "version": null,
      "bindings": [],
      "identifier": null,
      "interfaces": []
    }
  ],
  "reason": "absent",
  "catalog": {
    "status": 404,
    "entries": 0,
    "problem": "absent"
  },
  "wellKnown": {
    "status": 404,
    "problem": "absent",
    "contentType": "text/html; charset=utf-8"
  }
}

Related checks

See sites that pass A2A agent card →
Methodology →

Agent capabilities · invoiceize.com

Agent Skills index

Publishes an Agent Skills index

Not applicableAdds +1 to the badge when found

What we found

No usable Agent Skills index was found at either well-known path or in the AI Catalog.

Artifact verification
not-performed
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "catalog": {
    "status": 404,
    "problem": "absent",
    "individualSkills": 0
  },
  "indexes": [
    {
      "via": "well-known",
      "error": null,
      "notes": [],
      "total": 0,
      "format": null,
      "issues": [],
      "schema": null,
      "source": "https://invoiceize.com/.well-known/agent-skills/index.json",
      "status": 404,
      "usable": 0,
      "entries": [],
      "problem": "absent",
      "rejected": 0,
      "identifier": null
    },
    {
      "via": "well-known",
      "error": null,
      "notes": [],
      "total": 0,
      "format": null,
      "issues": [],
      "schema": null,
      "source": "https://invoiceize.com/.well-known/skills/index.json",
      "status": 404,
      "usable": 0,
      "entries": [],
      "problem": "absent",
      "rejected": 0,
      "identifier": null
    }
  ],
  "artifactVerification": "not-performed"
}

Related checks

See sites that pass Agent Skills index →
Methodology →

Agent capabilities · invoiceize.com

WebMCP

Declares WebMCP tools for browser agents

Not applicableAdds +1 to the badge when found

What we found

No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.

Pages checked
4
Declarations
0
Usable declarations
0
Detection method
static
Runtime verification
not-performed
Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "pages": [
    {
      "key": "homepage",
      "url": "https://invoiceize.com/",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    },
    {
      "key": "page:https://invoiceize.com/blog/how-to-make-an-invoice/",
      "url": "https://invoiceize.com/blog/how-to-make-an-invoice/",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    },
    {
      "key": "page:https://invoiceize.com/blog/",
      "url": "https://invoiceize.com/blog/",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    },
    {
      "key": "page:https://invoiceize.com/about/",
      "url": "https://invoiceize.com/about/",
      "secure": true,
      "usable": 0,
      "truncated": false,
      "references": 0,
      "parseErrors": 0,
      "declarations": 0
    }
  ],
  "reason": "absent",
  "detection": "static",
  "pageCount": 4,
  "references": [],
  "parseErrors": 0,
  "usableCount": 0,
  "declarations": [],
  "referenceCount": 0,
  "declarationCount": 0,
  "runtimeVerification": "not-performed"
}

Related checks

See sites that pass WebMCP →
Methodology →

Agent capabilities · invoiceize.com

Web Bot Auth

Publishes a Web Bot Auth key directory

Not applicableAdds +1 to the badge when found

What we found

No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "keys": {
    "total": 0,
    "sample": [],
    "usable": 0,
    "testKeys": 0,
    "evaluated": 0,
    "privateMaterial": 0
  },
  "notes": [
    "media-type",
    "unsigned"
  ],
  "shape": null,
  "reason": "absent",
  "signature": {
    "total": 0,
    "status": "absent",
    "ignored": 0,
    "coverage": null,
    "malformed": false,
    "signatures": []
  },
  "wellKnown": {
    "status": 404,
    "problem": "absent",
    "finalUrl": "https://invoiceize.com/.well-known/http-message-signatures-directory",
    "redirects": 0,
    "contentType": null
  },
  "extraMembers": [],
  "signatureAgent": "https://invoiceize.com"
}

Related checks

See sites that pass Web Bot Auth →
Methodology →

Agent capabilities · invoiceize.com

x402 / MPP payments

Accepts agent payments with x402 or MPP

Not applicableAdds +1 to the badge when found

What we found

No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "manifest": {
    "kind": null,
    "notes": [],
    "shape": null,
    "status": 404,
    "problem": "absent",
    "finalUrl": "https://invoiceize.com/.well-known/x402",
    "resources": {
      "total": 0,
      "sample": [],
      "skipped": {},
      "eligible": 0,
      "examined": 0
    },
    "contentType": null
  },
  "protocols": [],
  "responses": [],
  "verification": null,
  "paymentVerification": "not-performed"
}

Related checks

See sites that pass x402 / MPP payments →
Methodology →

Agent capabilities · invoiceize.com

ACP commerce

Publishes ACP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No ACP discovery declaration established at /.well-known/acp.json.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "api": false,
  "key": "well-known-acp",
  "issues": [],
  "marked": false,
  "reason": "absent",
  "status": 404,
  "usable": false,
  "problem": "absent",
  "version": null,
  "commerce": false,
  "services": [],
  "transports": [],
  "capabilities": [],
  "transactionVerification": "not-performed"
}

Related checks

See sites that pass ACP commerce →
Methodology →

Agent capabilities · invoiceize.com

UCP commerce

Publishes UCP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No UCP discovery declaration established at /.well-known/ucp.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "api": false,
  "key": "well-known-ucp",
  "issues": [],
  "marked": false,
  "reason": "absent",
  "status": 404,
  "usable": false,
  "problem": "absent",
  "version": null,
  "commerce": false,
  "services": [],
  "transports": [],
  "capabilities": [],
  "transactionVerification": "not-performed"
}

Related checks

See sites that pass UCP commerce →
Methodology →

Agent capabilities · invoiceize.com

AMP discovery

Publishes AMP discovery metadata

Not applicableAdds +1 to the badge when found

What we found

No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.

Response receivedHTTP 404

https://invoiceize.com/.well-known/agent.json

Content-Type: text/html; charset=utf-8

Discovery source
native
Declaration location
https://invoiceize.com/.well-known/agent.json

Declared agent addresses

No usable addresses recorded

Declaration issues

No issues recorded

Discovery documents

  • https://invoiceize.com/.well-known/agent.json · absent

Discovery only. Messaging, health, identity ownership and extension activation were not tested. This does not establish Level 0 conformance.

Technical scan data JSON

Archived measurements. Long values and lists are shortened for display.

{
  "reason": "absent",
  "selected": {
    "via": "native",
    "issues": [],
    "marked": false,
    "source": "https://invoiceize.com/.well-known/agent.json",
    "status": 404,
    "usable": false,
    "problem": "absent",
    "version": null,
    "endpoint": null,
    "finalUrl": "https://invoiceize.com/.well-known/agent.json",
    "contentType": "text/html; charset=utf-8",
    "identifiers": [],
    "requestedUrl": "https://invoiceize.com/.well-known/agent.json",
    "lifecycleStatus": null
  },
  "declarations": [
    {
      "via": "native",
      "issues": [],
      "marked": false,
      "source": "https://invoiceize.com/.well-known/agent.json",
      "status": 404,
      "usable": false,
      "problem": "absent",
      "version": null,
      "endpoint": null,
      "finalUrl": "https://invoiceize.com/.well-known/agent.json",
      "contentType": "text/html; charset=utf-8",
      "identifiers": [],
      "requestedUrl": "https://invoiceize.com/.well-known/agent.json",
      "lifecycleStatus": null
    }
  ],
  "runtimeVerification": "not-performed"
}

Related checks

See sites that pass AMP discovery →Check again: Agent Mesh Protocol checker →Guide: How to publish Agent Mesh Protocol discovery →
Methodology →

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

14th of 58 in SaaS & Web Apps

Full ranking →Whole category →
  1. 1Appnaryappnary.com
  2. 2BulkSharebulkshare.cloud
  3. 14Invoiceize · this reportinvoiceize.com

The prompts in the owner view would take Invoiceize to 98, 2nd in its category.

To the prompts →

Category average 57. 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
29 Oct 2026
Rubric
0.9.0
Requests
23
Fetched
1.7 MB
Took
14.8 s
Homepage
198 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/how-to-make-an-invoice/article · linked from the homepage · from the sitemap · read
  • /blog/collection · linked from the homepage · from the sitemap · read
  • /about/about · linked from the homepage · from the sitemap · read

Similar reports

The whole directory →

More like Invoiceize:SaaS & Web AppsFinance & AccountingProductivityB2B

Good for Bots

goodforbots.com

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

Same category

Relanco

relanco.ca

Automated bilingual SMS and email payment reminders for Canadian contractors

Same category

סלייט

slate.co.il

Free invoicing and bookkeeping software for Israeli freelancers and small businesses

Same category

Baiivo

baiivo.com

Client work and payment software for freelancers and small studios

Same category

NextFeed

nx-feed.com

Product feed management software that finds errors before channels reject them

Same category

EmailFig

emailfig.com

Email marketing platform with campaigns, automations, and scalable pricing

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