Maintain the website as a useful source of current facts. Assign someone to review important pages and integrations after product changes and at an interval appropriate to the site's activity. A published page can become misleading without a technical failure.
Keep an inventory and owner#
Record the workspace, site slug, public hostname, editable Astro source location, repository/branch when used, and the intended release workflow. Keep source archives free of credentials and private launch responses. Preserve the same source and site identity across agent sessions.
For important pages, record the responsible editor and the changes that should trigger review: pricing, eligibility, supported integrations, product behavior, policy, or contact details. Consolidate duplicated explanations so the same fact does not drift across multiple pages.
Review the user journeys#
| Area | Practical check |
|---|---|
| Public content | Important pages return successfully and contain current answers in HTML. |
| Navigation/assets | Links, images, downloads, and social previews still point to intended resources. |
| CMS | Drafts and archived entries are deliberate; templates and indexes render correctly. |
| Chat | A few factual questions produce correct answers and useful references. |
| Forms | Capture, continuation, and notification delivery work when an authorized test is appropriate. |
| Search | Relevant queries return the intended pages under the site's entitlement. |
| Analytics | Date coverage, collection method, and reporting freshness are understood. |
| Domains/releases | HTTPS, routing, staging/production pointers, and repository linkage are correct. |
Coordinate tests that create conversations or queue email. Use non-sensitive content and distinguish saved capture from delivered notification. Do not generate repeated production traffic merely to populate a report.
Review access and dependencies#
Inspect connected agents and personal tokens in MCP settings. Remove access that is no longer needed. Check supported plugin installation instructions and repository release information before updating an integration. Discover current MCP schemas rather than assuming an old argument list still applies.
For website dependencies, review release notes relevant to your installed versions, build locally, and run the project's meaningful checks. Preserve the current design and content contracts while applying updates. A documentation update does not itself require a platform or dependency upgrade.
There is no universal product changelog URL documented here. Use the current Answer Cloud documentation and official plugin repository information for the integration concerned, and ask support about a specific platform change or compatibility requirement. Avoid treating old screenshots or a cached guide as a current release notice.
Publish and verify a bounded change#
Preview the change, confirm the intended site/destination, and publish through the established workflow. Afterward, check the actual public result and relevant warnings. Record the deployed sequence or CMS entry IDs with the reviewed date so future operators can identify what changed.
Use content readiness for editorial checks, account security for access review, and deployment troubleshooting when the live result differs from the reviewed build.