HomeDocumentationFix and verify
Fix and verify
We do not call a fix successful just because it was published. The path is draft, approved, live, crawled, mentioned, cited, then resolved.
Last updated 7 October 2026
What you'll do
- Review drafts in To do.
- Apply a supported technical fix or a reviewed passage.
- Wait for a later measurement before calling the opportunity resolved.
To do
To do lists drafts waiting for approval and fixes waiting to be applied. Approving a draft does not deploy it. Deploying it does not resolve the opportunity.
Fix Studio
Fix Studio prepares technical outputs such as llms.txt, robots guidance, structured data, metadata or an FAQ. You review the draft. It can be applied manually or, where connected, through an Edge deployment.
Supported technical remediation can be automated when Autopilot is enabled. That automation is narrower than public Knowledge Hub publishing, and it still does not mean the issue is resolved.
PASSAGE
A lost question can produce a recommended answer or short passage aimed at a missing or inaccurate answer, with a target URL. You review it.
If the content belongs on your website, the supported remediation workflow can place it there after review. If it belongs on a third-party website, Basiro cannot silently edit that site. The opportunity stays open until the proof condition is met.
Proof
Basiro tracks approved, live, crawled, mentioned, cited, exact target citation and resolved as separate states. Published is not resolved. Deployed is not resolved. A brand mention is not resolved.
For a remediation with a target URL, success means that URL is present in a later answer's cited URLs.
What the result means
You can see how far a change has gone. Only the required later evidence closes it.
Important distinctions
- Basiro does not guarantee that a published fix will be cited.
Continue