Observed evidence

Citation Path's public AI visibility self-audit.

This review uses only public pages and checks that any visitor can repeat. It does not disclose private analytics, search-performance, lead, customer, or operational data.

By Jesús MendozaUpdated July 23, 2026

Request a snapshot Compare approaches

Citation Path Self-Audit resource visual

Guide

Buyer criteria

Compare

Weak vs useful

Buyer questions

The decision to make first.

Start with the buyer decision, then inspect the evidence, caveats, and next useful page.

Question

What does Citation Path's current visibility evidence show?

As of July 23, 2026, Citation Path exposes the public crawl, canonical, sitemap, structured-data, and authorship signals expected from an AI-search-focused agency website. Those signals improve machine readability and make the technical surfaces repeatable for reviewers, but they do not prove rankings, AI citations, traffic, leads, or customer outcomes from the public site alone.

This review uses public response headers, rendered pages, machine-readable files, structured data, sitemap coverage, and repeatable lab checks.

What changes in practice

Visitors can inspect the same public surfaces directly without access to Citation Path's private analytics or operational systems.

AI Visibility Audit GEO service Monitoring and attribution AI SEO pricing

Request a visibility snapshot

Question map

Questions worth answering.

Each question has a page role, proof requirement, answer format, and next step.

Public review

What can visitors verify without private access?

Answer format: A dated checklist of public pages, response headers, crawl directives, canonical URLs, structured data, and sitemap entries.
Proof needed: A live URL or repeatable public test for every observation.

Open the cited public surface and repeat the check.

Technical review

What does technical readiness prove?

Answer format: A concise explanation of what crawlability, structured data, and lab checks establish—and what they do not.
Proof needed: Rendered page output, machine-readable files, and repeatable test results.

Compare the structured data with the visible page.

Limitations

What does this public review leave unclaimed?

Answer format: A clear boundary around private analytics, rankings, AI citations, leads, conversions, customer outcomes, and operating plans.
Proof needed: No unsupported performance or outcome claims on the page.

Treat public technical readiness separately from authority or performance.

Proof notes

What to verify.

The public sitemap listed 20 canonical URLs on July 23, 2026.
Production validation passed 60 public AI-readiness checks.
A Lighthouse lab check of this page scored 100 for accessibility and 100 for SEO.
The founder page identifies Jesús Mendoza and links to his public personal site, GitHub, and LinkedIn profiles.

Caveats

Keep the claim bounded.

Technical readiness does not guarantee rankings or AI citations.
Lab checks are not field performance measurements.
No private analytics, lead, conversion, customer, or operational data is disclosed.
This is a Citation Path self-audit, not independent third-party validation.

Source assets

Evidence buyers can inspect.

Live assets are linked. Planned assets stay clearly labeled until they are published.

Citation Path self-audit
Live
A dated review using only public pages and repeatable checks.
Inspect this asset
Public machine-readable surfaces
Live
The sitemap, robots file, llms.txt, and pricing summary are available directly from the production domain.
Inspect this asset

Key takeaways

What should change after reading this.

These points are meant to change a decision, not restate the category definition.

The public site exposes the core crawl, canonical, sitemap, and machine-readable surfaces.

Structured data connects the organization, founder, services, resources, and visible page content.

Owned-site clarity is useful, but it is not evidence of rankings, AI citations, or customer outcomes.

Guide sections

Where the decision usually breaks.

Each section focuses on the place teams tend to confuse strategy, implementation, and measurement.

Public crawl surfaces are available

The production site exposes canonical URLs, a public XML sitemap, robots.txt, llms.txt, and a machine-readable pricing page. The sitemap listed 20 public URLs when this review was updated on July 23, 2026.

Structured data matches visible pages

Rendered pages identify Citation Path, its founder, services, resources, breadcrumbs, and visible FAQs with JSON-LD. The founder entity links to the same public biography and profiles shown on the About page.

Public technical checks pass

The July 23 production review passed 60 checks covering response status, canonical URLs, rendered JSON-LD, robots directives, AI crawler access, machine-readable files, and sitemap coverage. A Lighthouse check of this page scored 100 for accessibility and 100 for SEO.

Authority requires evidence beyond this website

Clear owned pages do not prove rankings, AI citations, customer outcomes, or independent authority. This review makes no claims about private search performance, traffic, leads, conversions, customer results, or third-party coverage.

Comparison

The pattern to avoid.

The weak version sounds plausible in a meeting. The useful version leaves behind an artifact someone can inspect.

Criteria	Weak approach	Useful approach
Crawl access	Assume a polished page is automatically available to every relevant crawler.	Check response status, robots rules, canonical URLs, and the public sitemap directly.
Structured data	Treat JSON-LD as a substitute for clear, visible page content.	Confirm that every marked-up entity and answer matches what visitors can read.
Authority	Treat owned-site clarity as proof of rankings, citations, or market authority.	Require independently verifiable sources before making performance or outcome claims.

Decision guide

When this deserves budget.

Use this section to decide whether the issue is urgent, foundational, or not ready for investment yet.

What visitors can verify

Public pages, crawl directives, canonical URLs, sitemap coverage, rendered structured data, and named authorship.

What this page does not disclose

Private analytics, search-performance reports, prompt monitoring, leads, conversions, customer results, or operating plans.

FAQ

Questions buyers ask before choosing.

Is this a customer case study?

No. It is a review of Citation Path's public website. It does not represent a customer outcome.

What evidence was used?

The review used public response headers, canonical URLs, rendered JSON-LD, robots rules, AI crawler access, machine-readable files, sitemap coverage, and Lighthouse lab measurements.

What does this review not show?

It does not disclose or claim private analytics, search performance, prompt-monitoring results, leads, conversions, customer outcomes, or operational plans.