About
What we can prove, and what we cannot.
Indexation coverage, crawler behaviour verified from your logs, and Search Console figures on a frozen query set are provable. Movement in AI answers is a sample with error bars. Most of the work is knowing which of those two you are looking at, and saying so before anyone asks.
How we work
- Measure before advising. No recommendation without data behind it.
- Separate provable from inferred. Indexation coverage, verified crawler behaviour from your logs, and Search Console figures on a frozen query set are provable. AI-answer movement is a sample, and is reported with a confidence interval.
- Every figure sourced, dated, and labelled with the instrument that produced it.
- Report flat months as flat. Most months nothing measurable changed, and a retainer that only ever reports gains cannot be checked.
- Cite official documentation. Google's own guidance tells buyers to check whether a consultant's recommendations cite it.
- Be measured on the work. The audit fee is refundable in full if it produces no finding at or above a severity agreed in writing beforehand.
What would make us tell you not to hire us
- If your site is small and clean and your problem is that nobody has written anything, you need editorial help, not us.
- If your buyers do not search, because you sell entirely through outbound or channel, the ceiling on this work is low, and we will say so.
- If nobody on your side can ship a fix within a reasonable cycle, a technical retainer will produce reports and no change.
The name
An auspex was a Roman augur: an official who read the flight of birds to advise on decisions before they were made. The work was interpretation under uncertainty, reading the available signals even when they were unclear.
That is a fair description of measuring AI answers today. The systems are opaque and non-deterministic. Nobody outside those companies knows exactly how sources get chosen, and the answer changes from month to month.
Jason Klein
Three years with AltheaSuite, working with its clients on their websites and webstore fronts. That included travelling around the US to meet businesses in person and work on optimisation with them, from family-run shops to enterprises turning over hundreds of millions a year.
A mom-and-pop storefront and a nine-figure operation fail in recognisably similar ways at the engineering layer. A template renders differently than it was built to, pages exist and never get indexed, a change ships and breaks something downstream. What differs is how long it takes anyone to notice, and how much it costs while nobody does.
That experience comes from the client side of the table. The five gates are a way of organising failures that had to be found and fixed on live sites, on deadlines, with the people affected in the room.
The specialism is the engineering layer: rendering, indexation, crawl access, and the gap between what a site serves and what a machine keeps. It is the layer most agencies are weakest on, and it is what this practice is built around.
Alex Galvez
Delivery partner. A computer science background and prior work in cyber security, which lands on the parts of this practice that touch client systems: how server logs are handled, how access is scoped and revoked, and the discipline of not asking for more than the work requires.
An engagement here asks for Search Console, Analytics and raw server logs, and turns down DNS credentials, hosting root and shared passwords. Those lines were drawn with Alex's background in mind.
Alex also works on the measurement tooling: the crawler-access checks and the prompt-panel runs that produce the figures in a report.
jason@auspexseo.com · alex@auspexseo.com
Email is the only contact method listed. Neither of us keeps a profile page current, and a stale one is worse than none.