Diagnose an answer that uses old documentation

Preserve the stale response

Record the exact question, answer, cited URL and time. Identify the outdated claim and the current authoritative passage that contradicts it. Do not merely label the response old; it may have combined current and retired material. Keeping the specific evidence allows you to distinguish a source-refresh issue from a citation mismatch, a version ambiguity or an answer generated without adequate support.

Trace the update path

Confirm that the public source was actually changed, that the intended collection includes it and that the import or refresh completed. Inspect any visible source timestamp or content where supported. A successful article edit does not prove the assistant’s separate copy has changed. Avoid repeatedly requesting refreshes without first understanding which part of the path still contains the obsolete information.

Retest the old and new wording

Ask the current task question and a version that uses the old terminology. Check whether both routes now produce the correct current answer or an appropriate version clarification. Use a fixed configuration and preserve the results. This fictional diagnostic procedure does not establish a refresh-time guarantee for SiteGPT or any competitor; actual product behavior must be observed in the reader’s authorized environment.

Narrow the public scope if needed

If the update path cannot meet the importance or frequency of your changes, remove the affected topic from the assistant or direct readers to the live source. Do not promise real-time freshness solely because an automatic refresh feature exists. Choose a review cadence based on what changes and what an incorrect answer would mean, then retain a manual way to stop or correct misleading guidance.

• Keep the old claim, corrected source passage, refresh observation and final answer together so the update path can be inspected later.