Skip to main content
URLs are the core unit of a zued audit. Each URL you add is crawled, split into content chunks, scored for technical health, and tested against AI engine responses.

​
Adding URLs

Add URLs from your project’s URL management view.
URLs are re-crawled fresh with every weekly snapshot. You don’t need to re-add them manually when your content changes.

​
Which URLs should you add?

zued is designed to audit the pages that AI systems directly cite when answering user queries. Prioritize pages that contain your core product, service, or expertise content — these are the pages that enter the retrieval pipeline, pass re-ranking, and get attached as citations. These formats perform best in AI retrieval and citation:
  • Product and service pages — especially with clear purpose lines, selection criteria, and testable claims
  • How-to guides with numbered steps and direct answers
  • Comparison and “vs.” pages — AI systems frequently cite these for purchase decisions
  • FAQ pages where each question is a heading with a direct answer in the first paragraph
  • Case studies with before/after metrics and specific results
  • Data-driven content with original research or statistics
Pages like impressum, about us, contact, privacy policy, terms of service, and career pages are not recommended for zued audits. These pages still hold value — they contribute to your overall domain trust, entity clarity, and E-E-A-T signals that AI models factor into their reasoning. However, they influence AI visibility indirectly. AI systems rarely retrieve or cite them directly in their answers to user queries. zued measures and optimizes direct visibility: whether your page is retrieved, cited, and surfaced in AI-generated responses. Since legal, contact, and corporate pages almost never appear in that citation pipeline, auditing them won’t produce actionable insights or move your visibility metrics.
Focus your URL slots on pages you want AI systems to cite directly. The indirect trust signals from legal and corporate pages still work in the background — they just don’t need to be tracked in zued.

​
What zued does with each URL

  1. Crawls the page using a real browser — the same way AI crawlers access your site
  2. Chunks the content into meaningful segments that preserve the page structure
  3. Scores the page for Technical Health: bot accessibility, JS rendering, Core Web Vitals, structured data, and meta tags
  4. Maps audit prompts to the most relevant content on your page — including prompts that span multiple URLs in your project
  5. Analyzes alignment between AI engine responses and your content
  6. Cross-URL analysis — for prompts targeting multiple URLs, shows how your pages work together and where the internal linking gaps are
  7. Fact-checks verifiable claims (prices, specs, features) against AI engine responses — showing which facts AI reproduces accurately and which it gets wrong

​
AI crawler access

Some checks are about your site, not any single page. zued runs these once per audit and shows the result on every URL, labelled site-wide.

​
Does your server treat AI crawlers differently?

Allowing a crawler in robots.txt and actually serving it a page are two different things. Bot protection, WAF rules and CDN defaults sit in front of many sites and can turn an AI crawler away long before your own rules apply. zued checks this by comparing, over one connection, how your site answers a normal browser against how it answers requests identifying as AI crawlers. A difference between the two is the only part a site owner controls, so it is the only part worth reporting.
A difference on its own is not proof that an engine is blocked. Bot protection routinely filters requests that claim to be a crawler but cannot prove it, while letting the verified crawler through. Tools that stop here report false alarms — including, memorably, on the websites of the CDN vendors themselves.
zued goes one step further, because it has something a scanner does not: your actual engine results. If the affected engines are still citing your pages, the verified crawler is clearly getting through, so zued reports the finding for your records and applies no penalty at all. The same applies when the difference only touches crawlers behind no engine your audit queries: worth knowing, but it cannot move a number. Evidence only ever works in that direction. A citation proves an engine reached you; an engine staying quiet proves nothing, because that is also what ordinary low visibility looks like. So a difference we cannot rule out stays a finding, not a verdict: it costs a few points in the technical score and is never treated as a proven block.

​
Content Signals

Some sites publish preferences in robots.txt about how their content may be used by AI systems. These are not all equal: If you did not intend to opt out of AI answers, this is usually the fastest fix in the whole audit — and it is invisible in every content-focused tool.

​
AI content endpoints

zued also checks for llms.txt, llms-full.txt, .well-known/ai.txt and whether your site serves Markdown to clients that ask for it.
These are shown but not scored. No AI engine has confirmed reading them. Scoring a signal that cannot be tied to measured visibility would make the Technical Score less predictive of the visibility zued actually observes, so zued reports what is there and leaves it at that.

​
Agent readiness

Separately, zued looks for the emerging conventions that let autonomous agents act on a site rather than just quote it — service and API descriptions, agent capability files, and, for sites that sell things, agent commerce protocols. None of this affects your score, and for most sites everything here will read “not found” for some time yet. It is shown so the question is on your radar before it becomes urgent. The commerce checks only appear when your site actually publishes product markup, so a services business never sees a checkout checklist it has no use for.