Preview, Publish, Duplicate, and Unpublish explained
| Term | What it means |
|---|---|
| Draft and preview | The working agent you build and test in your workspace before releasing it to visitors. |
| Publish | Release the agent at its own URL using the access settings you confirm. |
| Publish again | Apply a new version or changed publishing settings to the same published agent. |
| Duplicate | Create a separate draft from an existing agent so you can customize the copy independently. |
| Unpublish | Take the published agent offline and remove its published resources. The working draft remains in your workspace. |
Prepare the experience for real visitors
- Complete a representative customer task in the preview.
- Check the business knowledge, visible results, and next steps.
- Verify which connections and actions are available to the published agent.
- Choose Public, Restricted, or Private. For Public, choose whether visitors must sign in and whether others may duplicate the agent.
- Complete the publishing flow and test the resulting link as the intended audience.
Is a slow response caused by the model or the server?
Loading the application, waiting for the AI model, and running connected tools are different stages. A long response can come from the model processing a complex request or waiting for an external service. Response time alone does not establish that the hosting machine is slow.
The published agent uses a prepared build. It does not wait for the rebuilds that follow edits in the working preview. Model and connected-service latency still apply, and publication does not guarantee that every timeout disappears.
For a consistently slow task, compare models on the same request and check which stage is taking time. When asking for support, include the agent URL, approximate time, and the task that was slow.
Can my agent serve customers at night?
Yes. Your published agent can serve customers 24/7 without an operator being online. Configure the knowledge, actions, and handoff rules it needs for after-hours requests. Actions involving your team or another service still depend on their availability.
If your organization needs a contractual availability commitment, contact us to discuss service levels in an Enterprise agreement.
Can I hand an agent to a client or host it myself?
You can build an agent for a client and share its published URL or connected custom domain. Agentplace runs the hosted service. Access to generated project code through GitHub is separate from transferring the hosted platform or receiving a standalone desktop application.
For a client handoff, agree on who will manage access, connected accounts, billing, and future updates. Contact us about export and custom delivery requirements before committing to a particular handoff format.
Can search engines index my agent?
Publishing gives your agent a live URL; search visibility depends on what a crawler can access there. Public business information can be prepared for search. Personalized answers that appear only after a conversation should not be treated as indexed pages. Google Search does not interact with a page to reveal its content.
Server-side rendering (SSR) sends page content in the initial HTML response. Pre-rendering prepares that HTML ahead of time. Either can make public information easier for crawlers to read, but neither automatically exposes later conversations or guarantees indexing. Check the published result rather than assuming Publish enables SSR or generates searchable pages.
How do I prepare public information for search?
Start with the facts people should discover: your services, service area, expertise, and answers to common business questions. The agent continues to deliver the personal service. These public materials help people find and understand it.
- Choose information that is safe to publish. Keep customer conversations, uploaded files, and personal results behind their appropriate access controls.
- Give useful public information stable URLs that open without sign-in or a conversation. You can also use relevant pages on your existing business website and link to the agent.
- Provide readable page content, a descriptive title and description, and links between relevant pages. If the content requires SSR or pre-rendering, review that implementation with the Builder or your website developer.
- Include the public URLs in a sitemap and submit it through Google Search Console. A sitemap helps discovery; it does not guarantee indexing.
- Use Search Console’s URL Inspection to check the rendered HTML and indexing status. Confirm that the intended text is visible and the public pages are not blocked from crawling or marked noindex.
A home-services agent
Publish the business’s services, coverage area, and general booking information. Link that information to the agent, where a homeowner can describe a problem, share photos, and request an appointment. Keep the homeowner’s address, photos, and personal estimate private.
Do I need llms.txt or llms-full.txt?
These optional text files can collect approved public facts and links for AI tools that use them. They do not replace accessible web content or a sitemap. Google says these files are not required and do not improve visibility in Google Search, including its generative AI features.
If you maintain an AI reference, keep it consistent with your public pages and exclude private customer data. Treat it as a reference for supported tools, without promising rankings, citations, or automatic use by every AI service.
Agent URL, Remix URL, and other ways to use the agent
Share the Agent URL with customers who should use your agent. Share the Remix URL with people who should build their own version. Copy the actual links from the publishing result.
| Link or option | What the recipient can do |
|---|---|
| Agent URL or Web | Open and use the published agent under its access settings. |
| Remix URL | Start a separate copy in an Agentplace workspace when Allow duplication is enabled. The recipient signs in to create and customize the copy. |
| Custom domain | Reach the same agent through a domain you connect. Domain setup is separate from the access settings. |
| Claude Code, Codex, or MCP | Use the connection instructions shown after publishing to access the agent from a compatible AI tool. Available options and authentication depend on the destination. |
Review updates before customers use them
Continue refining the agent in the workspace as your business changes. Follow the update and publishing flow shown there, and test the live experience after publishing changes.
Review the publishing summary for changes to integrations, scheduled work, and other connected features. A preview edit becomes live when you publish that update.
Duplicate an agent to create another version
Use Duplicate from the agent menu in your workspace to create a new draft from the current working version. This is useful when adapting the same agent for another business, audience, or experiment. The original remains unchanged.
The copy is a separate project. Changes do not automatically synchronize between the two agents, and the copy must be published separately to receive its own live address. Review copied instructions and files, reconnect the required app accounts, and test the new version.
Allow duplication is a different setting. It lets other people copy your published agent through its Remix URL. You do not need to enable public duplication to duplicate your own agent in the workspace.
Take an agent offline with Unpublish
Use Unpublish when you want to remove the live experience while keeping the working draft. The published URL stops serving the agent, and its published resources are removed. You can continue editing the draft and publish it again later.
Unpublish is different from Private. A Private agent remains published for the owner to use after signing in. Review the unpublish confirmation before taking an agent offline.