Actual served destination
For each priority URL, do status, redirects, indexability and canonical match the intended destination? Retain an intentionally excluded URL as a control.
Review checks before a decision
Choose the protocol that fits your question. For each check, record what was observed and within which scope. A positive response is a documented observation, not certification of a site or source.
Entries stay in this browser, without submission or automatic storage. Download the record before closing the page. Do not enter secrets.
Crawling and indexing audit
Variants and changes
After correction, do language variants and incoming links reach the right content? Repeat the check after changes to routes or rendering.
Evidence and source register
Recoverable evidence chain
Can a reviewer recover the document, version and used passage from the claim? Are repetitions of the same document marked as dependent?
Retained qualifications
Does the conclusion retain contradictions, covered period and missing evidence? Reopen the record when a source is corrected or replaced.
AI citation observatory
Reproducible comparison
Do before and after records use the same question panel, language, context and collection protocol? Separate site changes from engine variation.
Relevant citation
Is each cited URL accessible and does it support the attributed passage? Retain wrong citations and uncited answers, not only favourable results.
Control AI crawler access
Rule and scope
Does the published rule target the right agent and paths? Distinguish a crawling declaration, access control and actual observations in available logs.
Opposite controls
Have an allowed and an excluded path been compared without changing access? Revisit rules when an operator changes its agents or documentation.
Build a verifiable entity profile
Identity and period
Do stable identifier, jurisdiction and period distinguish a namesake, establishment and organisation? Retain rejected matches and reasons.
Conflicting attributes
Do incompatible values stay linked to their sources and dates? Do not merge past and current roles, or a registered address and an observed presence.
Audit a multilingual website
Complete journey
Does a real task retain the selected language through errors, confirmations, documents and related links? Also check numbers, dates and right-to-left passages.
Reciprocal alternatives
Does each language alternative point to its equivalent, with consistent visible language and canonical? Repeat the check when a page is merged or retired.
Map AI system dependencies
Whole dependency chain
Does the record cover model, retrieval, tools, hosting, logs and known subcontractors? For each output, specify what actually leaves the boundary.
Tested exit
Have a useful export and recovery outside the provider been tested with test data? A downloaded archive without restoration or reading does not demonstrate reversibility.
Audit structured data
Visible facts
Does every marked-up date, price, role, review or availability have a justified visible equivalent? Remove inferred or outdated properties rather than filling fields artificially.
Syntax and scope
Do type, properties and relationships pass the appropriate validator? Separate markup validity, search-feature rules and actually observed display.
Evaluate an AI agent before release
Forbidden action actually blocked
Is an out-of-scope request denied by the tool without an external effect? Use an authorised test environment and retain arguments, decision and observable result.
Failure and recovery
After timeout or ambiguous result, does the agent stop or recover under a bounded rule? Check that a retry does not duplicate an already completed action.
Maintain a reliable editorial corpus
Correction propagation
Does the correction reach affected related pages, translations, snippets, tables and structured data? A fresh date without substantive change does not resolve outdated information.
Understandable retirement
When a page is merged or retired, does its destination preserve useful intent and are links corrected? Review old references before redirecting to a general page.
Audit accessibility across a web journey
Keyboard task
Can the task be completed by keyboard without a trap, with visible focus and no control obscured by a fixed region? Retain the tested path and browser.
Understandable errors
Do fields have explicit names and do errors explain recovery? Complement automated checks with zoom and screen-reader testing on the selected journeys.
Measure the performance people experience
Comparable measurement
Do before and after measurements specify matching device, network, cache, page and conditions? Retain several observations and distinguish laboratory tests from real usage.
Journey without regression
Does faster loading preserve search, interactions, forms and useful images? Test a late interaction and an error state, not only initial arrival.
Audit a form from start to finish
Error then recovery
In a test environment, does invalid input explain the problem without losing other useful fields? Also check keyboard, language and recovery after server failure.
No duplicate submission
Can double activation or a late response produce two operations? Distinguish displayed success, confirmed receipt and final processing without using real personal data.
Audit a site’s editorial images
Origin and purpose
Are origin, known rights and modifications documented? Do caption and alternative distinguish documentary photo, logo, diagram and atmosphere illustration?
Actually displayed file
On a small screen, does the chosen file retain dimensions, clarity and meaningful framing? Also check lazy loading and missing resources without artificially enlarging a poor original.
Qualify an open source before using it
Document scope
Are operator, jurisdiction, period, version and exclusions identified? An empty search must retain its query and filters before interpretation.
Examined independence
Do confirmations rely on distinct documents or the same repeated report? Retain their common origin and narrow the conclusion when corroboration is missing.
Reconstruct a timeline of public signals
Distinct dates
Does each row separate event, publication, capture and observation, with known precision and time zone? A page update must not become a new event date.
Justified interval
Is the first recovered trace presented as an observation rather than a certain origin? Retain gaps and check the date of each destination when navigating an archive.
Map actors using public sources
Documented relationship
Does each edge specify relationship type, direction, period, source and status? Graph proximity or a shared address must not replace a relationship document.
Identity before merging
Were nodes matched using compatible identifiers and attributes? Keep namesakes separate and unknown relationships explicit rather than treating them as certain absence.
Verify the context of a public image
Version and context
Was the used version compared with earlier traces, framing and the recovered original caption? Reverse search provides a lead; it does not alone establish date, place or authenticity.
Corroborated clues
Were location and period clues compared with independent sources? Retain contradictions and distinguish present metadata, verified metadata and a visual hypothesis.
Read and cite a public decision
Decision and stage
Do court, number, date and procedural stage identify the exact document? Distinguish request, quoted argument, reasoning and operative decision before summarising.
Retained scope
Does the wording retain parties, addressed issue, period and document qualifications? Revisit the record if a later decision or correction changes what can be stated.
Assess a public dataset before reuse
Like-for-like comparison
Do compared values use compatible definition, unit, population, area and period? Retain filters, missing values and series breaks rather than inventing continuity.
Recoverable extraction
Do the exact distribution, version, licence and transformations permit recalculation? Recheck a series revision before reusing an old chart.
No plan matches this search.
Using a review
Does a completed review prove compliance?
No. It retains observations within a defined scope. Two questions are neither a full audit nor legal, technical or accessibility certification.
How should a non-applicable check be handled?
Choose outside scope and explain why: absent resource, unused feature or excluded scope. Export requires this justification.
Can unchecked controls be exported?
Yes. Their state stays explicitly unchecked. The tool never treats a missing answer as a pass.
When should the review be repeated?
After a change to source, version, route, provider or usage that could affect the result. Retain the previous record to compare scopes.