Homepage messaging review

Review proposed homepage and landing page revisions against approved audience definitions, core messaging pillars, and verified product capabilities before staging handoff. One run handles a single proposed page update from submission through claim verification, copy adjustment, owner approval, and verified staging handoff. Public website publication is a separate human decision and production deployment outside the boundary of this playbook. When access to a draft document or CMS staging environment is unavailable, work from an exported draft file or manual copy excerpt and note the access fallback on the case record.

• Extract the proposed page copy, section headers, value propositions, and numerical claims from the designated draft in Google Docs or Notion, or from staged page elements in Webflow. Record the target URL, submission date, and submitting team member. If the submitted draft is incomplete or missing key section copy, notify the submitter and pause processing until the full text is provided.
• Compare each extracted headline, capability claim, and performance metric against approved company positioning guides, feature registries, and customer reference records. Check that cited metrics match documented case study cohorts and methodologies, referenced product features are generally available rather than unreleased beta roadmaps, and target audience language matches approved buyer personas. Tag each claim as confirmed by source records, unverified due to missing evidence, or conflicting with documented capabilities.
• Information request. When a proposed claim or numerical proof point lacks documented support in approved records, request the specific source data, case study link, or product manager confirmation from the submitter. Upon receipt of submitted evidence or statements, evaluate the source against approved benchmark cohorts, measurement definitions, and customer reference terms rather than treating submission as automatic verification. If the substantiation withstands evaluation, update the claim audit to confirmed status; if the evidence is insufficient, contradictory, or unprovided within the turnaround window, retain the unverified flag and draft an alternative claim grounded strictly in verified company records.
• Draft concise, context-aware copy recommendations for any unverified or conflicting statements, preserving the original tone and section length while removing unsubstantiated superlatives or unreleased feature commitments. For confirmed claims, record the verified source reference in the audit notes. Assemble the comparative claim audit showing the original text, verification status, supporting documentation references, and proposed copy adjustments.
• Approval. Present the comparative claim audit and proposed copy adjustments to the product marketing lead. The owner decides whether to approve the recommended copy adjustments, specify custom wording edits, or reject the proposed page revision. If the owner approves or provides specific edits, proceed to staging preparation; if the owner declines the update or requests further source validation, return the audit with feedback to the submitter and update the case board to declined or unresolved.
• Apply approved copy revisions to the staging draft in Google Docs, Notion, or Webflow staging. Re-read the updated page copy to verify that only the approved wording changes were applied, section layouts remain intact, and no unapproved edits were introduced. Confirm verified staging handoff by recording the staging preview link, timestamp, and approving owner on the case record without authorizing or triggering production publication.
• Exception. If an approved copy update fails during staging due to CMS connection errors, layout permission restrictions, or unverified discrepancies between the approved draft and staged preview, record the exact error details on the case timeline. Notify the website operations manager and product marketing lead with the failed change details, pause automatic staging, and await manual confirmation of staging before closing the case.
• Conclude the case by archiving the verified claim audit, approval record, and verified staging handoff link. If the submitter declines required adjustments, or if necessary claim evidence remains unavailable after escalation, close the case under declined or unresolved with the specific outstanding blockers documented for future review.
• In a representative fictional example, a product marketing team prepares a new hero section stating that the platform cuts customer onboarding time by 80%. The agent cross-references the claim against approved customer case studies in Notion and technical documentation in Google Docs, discovering that verified onboarding reductions average 45% specifically among mid-market fintech cohort accounts, whereas the 80% figure applies only to a pilot workflow in an upcoming enterprise tier. The agent flags the discrepancy, prepares an annotated comparison, and proposes revised copy: 'In the evaluated mid-market fintech cohort, average onboarding time fell 45% with verified identity workflows.' The product marketing lead reviews the audit, approves the descriptive cohort phrasing for the staging draft, and defers the 80% claim until the enterprise tier reaches general availability. The agent stages the approved copy in Webflow, reads back the updated preview to verify accuracy, logs the handoff confirmation link, and hands off the staged page to the web operations owner for future deployment.