A customer's AI agent vetted us before he bought. Here is what it fetched, what 404'd, and what we changed.

Description and use

A small software vendor fixed missing routes and added machine‑readable signals so an AI assistant no longer reported 404 pages, increasing buyer trust and speeding up the sale.

Problem

Small software vendors lack machine‑readable signals, causing AI agents to report missing contact or pricing pages and potentially deterring buyers.

Outcome

Adding standard routes and machine‑readable signals corrected agent reports, improved buyer confidence, and prevented future 404‑related detractions.

Workflow

• 1. Buyer’s AI agent crawled legal, support, security.txt, product, home pages.
• 2. Agent requested /suites, /contact, /p/field-service-suite, /jobora and received 404s.
• 3. Agent reported missing pages to buyer.
• 4. Buyer returned after 15h and purchased.
• 5. Ownware added missing routes and redirects the same morning.
• 6. Updated tests to cover new routes and enforce download file presence.
• 7. Deployed changes via standard pipeline.

Evidence

The agent fetched /legal, /support, /.well-known/security.txt, product page, home page, then requested /suites, /contact, /p/field-service-suite, /jobora and received 404s.

Source

By the time this was written, the four missing addresses existed and had been verified from outside the network.

Source