Choose the future section's address first
If /answers/ can be configured on the main website, content will be available within the familiar domain. When separate infrastructure is more convenient, a subdomain such as knowledge.example.com is suitable. This is an address example, not a required name. The agent prepares the connection and obtains instructions for the specific mode. The owner or authorized specialist installs the required adapter or DNS setting. Do not copy a random CNAME from someone else's example: use parameters returned for your particular project. DNS changes require separate access and are not granted by merely connecting MCP to AURA.
Verification applies to a specific placement
A project may have separate checks for the root domain and publication section. Success for one does not automatically enable the other. After installation, check the expected files at the public address, then publication status and the content's accessibility. If a draft exists in the workspace but the URL returns an error, start with routing and section enablement. If a subdomain opens a page with another hostname or an unexpected canonical, that also requires correction. Check the address visitors will actually see and assistants will use in links.
Install a separate tracker on the main website
AURA returns an installation snippet, which the external agent adds to an authorized public-page template. Deployment follows, then verification that an actual event arrives. The managed section has its own observation collection; this cannot automatically be extended to the entire original website. In analytics, distinguish views, recognized AI referrals, browser goals and confirmed server events. Server-side bot requests need another adapter. A visit with a User-Agent resembling a known bot does not alone prove that the request belongs to the corresponding provider.
Interpreting the first figures
One visit to an article is not a unique person and does not prove an AI recommendation. The source may be identified by a transmitted referrer or tag; some apps hide it. Some events then remain without precise AI classification. Check which pages the installation covers and which period has actually been collected. Begin with a small verifiable test: the public article is accessible, the tracker fired on the intended page, and the event appeared in the correct project. That is more reliable than looking at a zero table before installation or inventing approximate referrals.
Conditions and limitations
- DNS is not changed without separate access
- Some apps do not send referrers
- Visits are not unique people
Explore the details
Content is accessible at the intended address and events arrive in the corresponding project
Check installation and analytics