Audit Your Published Page
Ask your connected AI assistant:
Check the published homepage at https://example.com/ against my Consent Pro settings. Show me evidence, failures and anything you cannot verify.
The assistant prepares a summary of the exact page URL, its connected project when available, the expected banner and regional behavior, and any publication uncertainty. Confirm this summary before it visits the site. Confirmation is required even for a project you already have connected.
The audit checks one page at a time, using the homepage by default. To check a different page, explicitly ask for its exact URL, for example:
Audit only https://example.com/pricing/ instead of the homepage.
Changing the selected page requires a new confirmation. It does not crawl the website, follow internal links or inspect other project domains. You can also confirm a page that is not connected to your workspace; private project expectations will then be unavailable.
What the assistant checks
Using its browser, the assistant observes the configuration actually delivered and exercises applicable consent controls: a first visit, rejection or opt-out, partial and full acceptance, returning visits and withdrawal. It also checks applicable privacy signals and regional behavior where it can observe them.
An incognito session is preferred. The debugger panel is not required. If a browser observation is unavailable, the assistant continues with the remaining checks and records that limitation. Clicking consent controls may create normal test consent records and analytics activity.
Saved settings can contain unpublished changes. The report keeps those settings separate from what the selected published page actually delivers. A simulated region does not prove what a visitor in that region receives.
Read the report
The assistant presents a readable report in the conversation, preferably as an HTML preview or artifact. A text report is available when previews are unsupported.
| Result | Meaning |
|---|---|
| Passed | The recorded evidence supports this check for the selected page and scenario. |
| Failed | An observed result contradicts the expected behavior. |
| Unverified | Evidence, access, coverage or an applicable test was missing or inconclusive. |
| Not applicable | The delivered configuration establishes why this particular check does not apply. |
Each finding explains the expected behavior, what the browser observed, supporting evidence and a proposed fix. Unverified checks remain visible. An empty request log, a saved tracker category or a banner labelled “blocked” does not independently prove consent enforcement.
Other pages, server-side processing, business-event conversions that could not safely be exercised, and legal applicability remain outside the verified coverage. Technical checks do not certify legal compliance or readiness for every country or US state.
Review fixes separately
An audit proposes fixes without changing settings, installing code, importing scan findings, updating checklist acknowledgements or publishing. Request any desired changes separately, review their effects, and publish only when ready.
Reports are delivered in your AI conversation. Consent Pro does not add a saved audit history or retain browser evidence for this feature. Your AI client’s own conversation and artifact retention settings still apply.