Product evidence and controls
Inspect known-source backlinks
Work with links you can trace to a source. GrekSignal’s bounded public verification is useful for inspecting known pages, while comprehensive discovery remains provider-dependent.
01
Verify a known source
Supply an allowed public source page and inspect observed links to the project domain. The parser records supported URL, anchor and relationship attributes. Public fetch budgets, caching and robots rules apply rather than unlimited crawling.
02
Keep interpretations explicit
A previously observed link that is absent from a later sample is not automatically proof of a permanently lost backlink. Check fetch status, changed markup and sample coverage. Referring domains and anchors come from saved observations rather than an invented authority metric.
03
Organize outreach internally
Save project outreach references and review relevant evidence before contacting a publisher. The workspace does not send outreach messages automatically. Global backlink coverage, competitor discovery and historical estimates require an appropriate configured data provider.
Practical questions
Is this a complete backlink database?
No. Known-source public observations are bounded; a comprehensive index requires a provider.
Does it email website owners?
No. Outreach records are internal planning material.
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.