Inputs
Two public URLs and the evidence returned by the crawler: page count, issue volume, critical errors, server response, metadata, image accessibility, analytics signals and sitewide controls.
APIS LAB / Tool
Website comparison
Run two real crawler audits and compare technical signals, indexability, content structure and the scale of issues in a single view.
How to read the result
Workspace
Enter the inputs and the model will show both the result and its reliability
The result will appear here.
Check the units, periods and definitions before running the calculation. Weak input data produces weak conclusions.
Method
A tool is useful only when you can see what the conclusion rests on
The interface is only the front layer. The real value is the ability to inspect the inputs, understand how the output is calculated, recognise what the model cannot know and translate the result into a management action.
Calculation method
The model compares the fields available from both crawls and highlights the largest observable gaps. It does not compress them into one artificial “site score”.
Limitations
The scan cannot prove commercial conversion, Core Web Vitals under real user conditions, lead quality or revenue impact. Network restrictions can also affect the crawler.
Management output
A short list of technically verifiable differences that deserve manual confirmation and can be prioritised against business importance.
APIS LAB principle
A result is complete not when a chart appears, but when it becomes clear which decision follows, which assumptions remain disputed and what next evidence could change the conclusion.
Method