Diagnostic
Review search and answer-engine coverage.
Free
Review search coverage, answer-engine citations, tracking, and prioritized gaps.
01 — Review scope
Questions, sources, and conversion gaps are documented, with priorities tied to the reviewed pages, accounts, and measurement definitions.
Review buying question
Comparison question selected. The comparison needs concrete operating evidence.
Representative answer-visibility review — buying questions, sources, and citation gaps are compared.
Illustrative example — not a customer transcript or reported outcome.
02 — Request the diagnostic
Send the site. Keep the request exact.
The request stays bounded to the website and contact information supplied here.
The success message states whether a delivery provider accepted the request or whether it was accepted only in local development. Neither state confirms inbox delivery, reading, or assignment. See the privacy page.
03 — Go deeper
AI opportunity audit
Map the funnel, inbox, and back office into a prioritized brief with assumptions, boundaries, and acceptance tests.
Scoped engagement
- Funnel
- Map the reviewed path from entry point to handoff.
- Inbox
- Document repeated inputs, decisions, and escalation points.
- Back office
- Identify records and handoffs involved in the selected workflow.
- Build brief
- State assumptions, boundaries, dependencies, and acceptance tests.
The output is a scoped brief with explicit assumptions, boundaries, and acceptance tests. Ownership and handoff terms are documented in the engagement scope before work starts.
04 — Common questions
What the diagnostic does—and does not—commit to.
What is in the SEO and AI-visibility diagnostic?
Review search coverage, answer-engine citations, tracking, and prioritized gaps.
What input does the diagnostic require?
The request form requires a website URL and email address and accepts an optional company name.
What is the AI opportunity audit?
Map the funnel, inbox, and back office into a prioritized brief with assumptions, boundaries, and acceptance tests.
Does a diagnostic commit us to a build?
No. Any follow-on implementation is scoped separately with its own boundary and acceptance tests.
What does an engagement document?
The scope records the workflow, source boundaries, assumptions, acceptance tests, exclusions, and handoff requirements.
Who owns the output?
Ownership and handoff terms are documented in the engagement scope before work starts.