Real-site evidence example

What an OpenForBots report looks like on InvoiceCraftly

A recognizable site makes the report easier to trust. This example uses InvoiceCraftly’s current deployable public-source files to show the kind of evidence OpenForBots surfaces and how that evidence turns into a next action.

Run your website audit How the audit works

OpenForBots evidence example

invoicecraftly.com

4 signals reviewed

Decision first

Strong discovery foundations; crawler policy is the clearest next decision

InvoiceCraftly already exposes strong initial HTML, connected structured identity, and a substantial llms.txt file. The most useful remaining policy decision is whether its intentionally broad User-agent: * access should stay universal or become explicit by crawler purpose.

FindDecideFixVerify

01Observed

Crawler policy is broadly open

InvoiceCraftly’s deployed robots.txt source uses User-agent: * with Allow: / and publishes sitemap and feed locations. The source does not currently distinguish search crawlers from training-oriented or other automated agents.

Source: robots.txt

02Observed

The homepage exposes strong initial HTML signals

The deployable homepage source includes a descriptive title, meta description, canonical URL, language declaration, a single product-focused H1, and meaningful product copy before relying on application interaction.

Source: Homepage HTML

03Observed

Structured identity is unusually complete

The homepage source publishes Organization, WebSite, WebApplication, WebPage, ImageObject, and FAQPage JSON-LD, with stable @id relationships connecting the site, software, organisation, founder, and primary image.

Source: Homepage JSON-LD

04Observed

llms.txt is present and substantive

InvoiceCraftly publishes an llms.txt file describing the product, guides, engineering notes, use cases, templates, document types, trust pages, and explicit product boundaries with same-site links.

Source: llms.txt

Highest-value follow-up

Decide whether crawler-specific policy is actually needed

There is no automatic requirement to split crawler access. If InvoiceCraftly wants different rules for search, training, or other automated agents, explicit groups make that policy observable and testable. If broad access is intentional, the existing simple rule is itself a valid policy choice.

Define intentChoose which crawler purposes should be allowed or restricted.
Express the policyAdd crawler-specific groups only where they reflect a real business decision.
Verify the deployed fileRe-run the crawler checker or full audit after deployment.

Inspect the same signals directly

Use a focused tool when you already know the question

AI crawler robots.txt checkerInspect crawler-specific access rules.robots.txt generatorDraft a clearer crawler policy.llms.txt checkerInspect the optional discovery file.JSON-LD generatorCreate cleaner machine-readable identity data.

Now check your own site

Replace the example with your public evidence

No account or email is required. Completed anonymous audit snapshots are retained for up to 30 days and then automatically deleted under the published privacy policy.

Run website audit