Interpreting Your Report
Why a check turns green only when an assistant answer changes
A deployment is not the finish line. A check turns green when the assistant can now use the corrected evidence.
This is the core difference between a technical checklist and an EAC audit. You can publish schema, update a profile, add a service page, or fix a booking link, but the business has not improved in the answer layer until assistants reflect the new evidence.
Why deployment is not enough
Several things can delay or prevent a green check:
- Crawlers have not fetched the changed page yet.
- A listing provider still has old data.
- The page update is visible to humans but absent from raw HTML.
- Schema validates but contradicts visible content.
- A stronger third-party source still says something stale.
- The assistant chooses a competitor because authority or action path is still stronger.
What green means
A green check means the observed assistant answer now satisfies the audit condition. Examples:
| Fix | Green condition |
|---|---|
| Add schema | The assistant identifies the business facts more clearly. |
| Publish service facts | The assistant answers the buyer question without guessing. |
| Fix crawler access | The page can be fetched and cited. |
| Update hours | The assistant returns current hours from current evidence. |
| Add booking path | The assistant surfaces or follows a valid next step. |
How to work the loop
- Apply the fix.
- Validate the page, profile, or source.
- Wait for realistic propagation where needed.
- Re-run the same prompt set.
- Compare the before and after answer.
Useful discipline
Keep before and after evidence. Screenshots, citations, timestamps, and changed URLs make it easier to tell propagation delay from an incomplete fix.
Verify the answer layer
Re-run after each meaningful change so the report reflects assistant behavior, not just deployment activity.
Run scan