Business export README

This sample is fictional. Do not publish it unchanged. A real packet must name the business, maintenance owner and last verified date. Unknown facts stay unknown; do not infer prices, hours, licenses or insurance.

1. Have the owner approve the name, contact details, service area, services, prices and hours against current records. Remove unsupported licensing or insurance assertions. Record who approved each fact and when.
2. Synchronize the visible website and relevant listings first. The optional export must agree with what a customer can read. Assign a maintenance owner and review whenever facts change.
3. Ask the web editor to publish the approved export at the site root as /agent.json, served over HTTPS with application/json content type. This format is an informational export, not a universal assistant standard.
4. Open that exact URL while signed out. Confirm HTTP 200, parse valid JSON, check the response content type, and verify that the host has not returned a login page or HTML error. Compare all values with the approved visible pages.
5. If adding LocalBusiness structured data, generate standards-based JSON-LD separately using the appropriate business subtype. Keep it consistent with visible content, then validate with the relevant structured-data tools. Do not use this custom export as schema.org markup.
6. Keep the approved file, source facts, owner/date and these instructions together as the implementation packet. Record the published URL and verification date. List consuming systems only if their use has actually been verified.

Hosting this file does not guarantee indexing, assistant use or recommendations. Google Search guidance on special AI files.