Preparing your website for a live AI host
Organize public information, visitor choices and consent boundaries before placing a live host on your website.
Keep the page useful before the host speaks
A talking website still needs clear written information. Visitors arrive with different devices, abilities and preferences, and they may read before they listen. Start by checking the page title, service explanation and next step. A live host should help people understand the page rather than compensate for missing facts. Prepare an approved answer to the main question a visitor is likely to ask. Then identify the page or form that answers the next question. This preparation is useful whether the visitor speaks with the AI or simply reads the site. The host and the written content should describe the same service.
NetShow's agentic site factory combines a business record with website content and machine-readable discovery files. Using the same business facts for those outputs helps keep the public description consistent. A host that explains a service, a guide about that service and an LLM summary should not give incompatible answers. Before a website discussion, gather your current pages and identify any contradictions, old offers or incomplete descriptions. Keep speculative features out of the factual list. The AI's public answers should come from information you approve, and anything that is still being built should be described with that status.
Plan the first moment for different devices
The host introduces itself as an AI and greets first. It should be visibly present when the page loads. Browsers may block sound before an interaction, so the visible greeting and the voice start are separate parts of the experience. The NetShow direction is to speak at the first interaction anywhere on the page when immediate sound is blocked. Do not make visitors discover a required talk button before they understand that a host is present. Ask to see the proposed first moment on a phone and a desktop, including the experience with sound unavailable.
A character's position matters because people still need to read and choose. NetShow's stage supports the host moving around the page and returning to its container. The free host uses one small menu revealed through hover or touch rather than surrounding itself with a second row of controls. For your site, discuss where the host begins and which sections it should help explain. Check that it does not obscure an important action or the answer someone is trying to read. This is a review of the intended visitor experience, not a promise that every page has already been tested on your devices.
Make consent part of the job description
Navigation, pointing and explaining content are different from sending a form or making a commitment. List the actions the host may perform for a visitor and mark which ones require consent or owner review. A sensible first discussion names the information a form collects and why it is needed. The visitor should know whether the AI is preparing information, helping fill a field or actually submitting something. Do not infer successful completion from a spoken sentence. Ask how the interface reports a held action, a completed action and an action that could not be completed.
Camera access can help when a visitor needs to show a device, screen or visual problem. It also requires consent and a reason tied to the task. Do not request unrelated private material simply because an eyes option exists in the agent surface. Prepare an explanation of what the agent would need to see and what the visitor should keep out of view. A camera is an optional source of context, not a requirement to read a service page. For questions requiring professional judgment, the website should preserve the appropriate human handoff instead of presenting visual understanding as authority to decide.
Keep human and machine discovery aligned
People share pages through social links, while search engines and answer engines need their own readable descriptions. The factory supplies llms files, a sitemap, robots instructions and structured page data. A useful sitemap lists public pages that exist; it should not advertise private editing screens or disabled services. Article and FAQ data should describe the words actually visible on the page. When checking the proposed site, open a guide directly rather than relying only on the home page. Confirm that the page has its own title, description and next step, and that its share preview describes that page.
Your next step is to explore NetShow's talking websites page and prepare a short site brief. Include the public pages to explain, the visitor's main question, the approved sources and the permitted digital next step. Keep language needs, phone layout and the human handoff in that brief. Ask which parts work today and which need setup for your site. The factory and agent kit are reusable pieces, so the discussion should focus on your information and boundaries rather than inventing a separate host system. A good talking website gives a stranger a clear answer and a clear choice while retaining useful written content. Keep the approved page copy and visitor questions together so the team can check the spoken explanation against the written information.
Questions about this guide
Which voice does the NetShow host use?
The host uses the NetShow proxy voice path. Mrs. NetShow uses marin and Mr. NetShow uses cedar. Browser sound restrictions can delay speech until the first interaction.
Does the host need camera access?
Only when seeing would help and the visitor consents. Keep unrelated private information out of view; reading the site does not require camera access.
Where can an agent read about NetShow?
The llms.txt summary, llms-full.txt guide, public Harness discovery files and the public article, FAQ and service pages describe the platform. Discovery does not grant private tool permissions.