AI visibility has two layers. A site must first be technically discoverable and understandable; providers must then actually mention or cite it for relevant questions. This public audit measures the first layer. Connected-brand observations belong to the second.
The auditor couldn't complete a clean fetch. Common causes: site blocks non-browser user agents, HTTP/2 negotiation failed, or the path returned a non-2xx.
target: https://highsignal.app · code: http_522
Check the URL and run the audit again →Enter any public URL to inspect its SEO and GEO primitives. The audit grades canonical metadata, Open Graph and Twitter metadata, Schema.org JSON-LD, robots and sitemap discovery, RSS where present, and agent-readable surfaces such as llms.txt. It separates the search axis from the agent-readiness axis so a technically strong Google surface is not mistaken for complete AI visibility.
A strong technical grade means crawlers and assistants have clearer paths to canonical, structured, citable material. It does not prove that Google has indexed every page, that a page ranks for a target query, or that ChatGPT, Claude, Perplexity, or Gemini currently cite the brand. Those outcomes require observation over time. Technical readiness is a prerequisite, not the awareness result.
Fix missing or conflicting canonicals first. Ensure public pages are allowed by robots policy and present in one canonical sitemap. Add structured data that matches visible content. Publish concise product facts, methodology, evidence, and change history in human-readable pages. Expose stable Markdown or API surfaces for agent retrieval where they genuinely represent the product. Then rerun the audit and measure search and provider observations separately.
For a connected brand, High Signal can store provider observations and mention evidence through its AI-visibility engine. Useful measurement asks specific, repeatable questions: whether the brand is mentioned, whether it is cited, which competitors appear, which source URLs are used, and how those results change after the site's content or technical surfaces change. A zero should mean an observed absence, not a missing run.
The page defaults to highsignal.app so its own readiness remains visible. High Signal publishes a canonical sitemap, robots policy, structured data, llms.txt, a full agent brief, Markdown alternates, an agent catalog, source-backed signals, methodology, and a changelog. The same public audit can be rerun after each release.