Product evidence and controls
A bounded technical site audit
Start with a small, transparent crawl instead of a mysterious health score. GrekSignal reports what it fetched, what it could not fetch and the evidence behind each finding.
01
Collect public evidence
The free entry scan samples up to three public pages. Project audits use finite page, depth, request, response-size and time ceilings. Robots directives, safe public addresses and redirect boundaries constrain the crawl; authenticated pages and private networks are excluded.
02
Inspect a finding in context
Review title and description problems, indexability directives, internal links, supported schema and AI crawler signals. Findings identify sampled URLs, observation time and why the issue matters. A suggested fix is a recommendation, not an automatic website edit.
03
Understand the coverage
A completed or limited run is a snapshot of the sampled crawl. It is not a comprehensive web index, a browser performance benchmark or a guarantee of search engine indexing. Compare runs only after checking their scope and limits.
Practical questions
Does the scan modify my website?
No. It reads public pages and stores observations; implementation remains under your control.
Does it provide a fabricated SEO score?
No. It exposes actual findings, sample sizes, sources and unavailable measurements.
Start with observable evidence
Run the bounded public scan on the homepage, then save a project when you are ready. Connected measurements need real authorization and available quota.