52 practical lenses for crawlability, identity, structured data, trust, and content signals.
Referral traffic shows visits, not AI influence. Use four answer-level metrics to measure whether AI mentions, recommends and cites your company.
Read lensA page can rank well in search and still be absent from AI answers because AI citation selection and classic search ranking are different visibility signals.
Read lensIf no one owns AI-visible company evidence, website updates, profiles, schema and old content can drift without accountability.
Read lensIf old press releases, event pages or news posts explain the company better than core pages, AI may use old context as evidence.
Read lensIf old PDFs and legacy pages remain crawlable, AI may cite outdated documents as stable evidence.
Read lensIf services are named differently across pages, AI may alternate categories and describe the offer inconsistently.
Read lensIf city, country and service-area claims differ across pages, AI crawlers may hesitate about where the company operates.
Read lensIf phone numbers and emails vary without clear purpose, AI crawlers may treat company contact identity as less certain.
Read lensIf legal, brand and profile names vary without explanation, crawlers treat the company identity as uncertain.
Read lensIf sameAs links are wrong, outdated or noisy, AI systems can connect your website to the wrong entity graph.
Read lensIf logos differ across your website, schema, social profiles or directories, AI systems may have weaker confidence that they refer to the same company.
Read lensIf key company pages are not reachable through working internal links, AI crawlers may not use them as evidence when describing your business.
Read lensIf key pages about who you are, what you do and why you are credible are too hard to reach, AI may treat them as secondary evidence.
Read lensIf critical website files are blocked to crawlers, AI systems may see an incomplete page and describe the company from partial evidence.
Read lensCookie or consent banners can prevent AI crawlers from seeing service, product or reference content that human visitors can access after one click.
Read lensIf security rules block AI crawlers, important pages may be missed and AI systems may describe your company from incomplete information.
Read lensIf staging robots, WAF rules, headers or bot blocks remain active on the live site, AI crawlers may see blocked or incomplete content.
Read lensIf sitemap lastmod dates are stale, fake or updated by every deployment, AI crawlers may lose confidence in page freshness signals.
Read lensLanguage switchers are crawlable internal links. If they send bots to different main pages, AI may see split site structures across language variants.
Read lensHreflang tells crawlers which language version belongs to which audience. If mapping is missing or inconsistent, AI may mix language versions.
Read lensIf UTM, filter or tracking URLs are indexable, AI crawlers may treat them as separate pages and split evidence across multiple URL variants.
Read lensIf both / and /index.html are crawlable, AI crawlers may treat them as separate homepage variants and weaken the primary identity signal.
Read lensIf both /page and /page/ are treated as valid, AI crawlers may treat them as different pages and split authority across two URLs.
Read lensIf your website works on both http and https (or redirects are inconsistent), AI tools may not agree which version is the official source.
Read lensIf both versions of your website (with and without www) are treated as valid, AI tools may not agree on which one is the official source.
Read lensIf reaching your real page requires several redirects, AI crawlers may not always land on the same final page. They can remember different links as "official".
Read lensAI crawlers use <title> and meta description as high-weight summary signals. If they’re vague or inconsistent, identity extraction becomes generic and unstable.
Read lensAI crawlers infer reliability from HTTP behavior. If reference pages intermittently return 403/404/500 (or soft 404), identity evidence becomes unstable and summaries drift.
Read lensAI crawlers increase confidence when identity claims are corroborated by concrete proof points — not just assertions.
Read lensAI crawlers use timestamps to judge freshness and stability. If key identity pages lack dates, machines assume stale content.
Read lensIf multiple URLs publish near-identical content, AI crawlers can split authority signals and reduce citation confidence.
Read lensAI crawlers can't rely on JavaScript execution. If your identity content is rendered by JS, it may be invisible to machines.
Read lensAI crawlers extract meaning from structure. Clear H1/H2 headings and consistent hierarchy improve extraction accuracy.
Read lensAI crawlers use sitemap.xml to discover what you consider important and crawl-worthy. A poor sitemap is a missed opportunity.
Read lensIf AI hedges about where you operate or how to contact you, your contact and location signals are likely too weak to verify.
Read lensIf AI is vague about what you do or who you serve, your About page is usually too thin or too generic to anchor identity.
Read lensIf AI lists services you don't sell, assume naming ambiguity is allowing category drift. How to fix it with signal specificity.
Read lensAI crawlers connect entities via identifiers and corroboration. Without clear identifier chains, identity stays ambiguous.
Read lensAI crawlers don't just read content — they follow resolution paths. Inconsistent redirects fragment authority.
Read lensSoft-404 pages weaken search and AI crawler trust because the URL returns 200 OK while the body looks missing, empty, or error-like.
Read lensIf key identity pages are not clearly discoverable via internal links, machines may never resolve your full entity surface.
Read lensThe homepage is often the default entity surface used to infer category, scope, and credibility by AI systems.
Read lensMachines prefer repeatable, stable signals over one-off explanations. If your identity works once, make it work every time.
Read lensDeclaring credibility is not the same as being machine-verifiable. Why hedging and vague claims reduce AI citation confidence.
Read lensMultilingual sites can create accidental identity forks. Why EN and local variants must share a consistent entity surface.
Read lensIf AI treats you like two different companies, assume competing entity anchors. How to establish a single authority surface.
Read lensAI systems reward consistency more than cleverness. Why varying identity claims across pages create resolution drift.
Read lensWhen first-party signals are weak, machines lean on third-party anchors. Why stable external references matter.
Read lensAI cannot interpret what it cannot reliably fetch. Why uneven crawl access causes identity drift.
Read lensSchema.org Organization is a machine-readable identity contract. What it means, why it matters, and what to verify.
Read lensCanonical consistency is an identity control when AI is the consumer. What it means, why it happens, and what to verify.
Read lensWhen AI tools disagree, assume signal inconsistency first. What it means, why it happens, and what to verify (evidence-only).
Read lensA diagnostic framework mapping observable AI output symptoms directly to verifiable web signal categories.
The primary authoritative surface, such as a canonical homepage or JSON-LD contract, a machine uses to resolve entity reality.
The deterioration of AI confidence caused by fragmented, contradictory, or outdated references overriding primary signals.
Run a free AI Readiness baseline, then use the relevant lens to classify what needs fixing.