No supported contact signal found in the selected privacy-policy page
The selected static privacy-policy page did not contain a supported contact signal.
Why it matters
Contact information can make a published policy easier for readers to follow up on. This finding is a prompt to review the static policy content and the contact information the organisation intends to publish.
The check is deliberately narrow: it reports only the absence of its supported static signals in one selected policy page, rather than deciding whether a contact route is usable or legally sufficient.
How ShipReady detects it
What it inspects
ShipReady selects the first crawled page whose path contains privacy or datenschutz when it has a successful HTTP 200 response, is not truncated, contains HTML, and has at least 500 characters of extracted visible text.
On that selected static page, ShipReady inspects the captured HTML and extracted visible text for supported contact signals.
What triggers a finding
The rule triggers only when the selected policy has no mailto link, no visible email-shaped address, none of the recognised phrases contact us, get in touch, write to us, reach us, or contact our, and no link whose href or anchor text contains contact, support, help, or kontakt.
What the evidence shows
The evidence proves that the selected captured policy page did not contain a contact signal recognised by this rule.
Limits of this check
ShipReady is silent when it did not crawl an eligible policy page, when the candidate is truncated or too short, or when a supported signal is present. It evaluates one selected crawled policy page, not every possible policy location.
ShipReady inspects static fetched content only. It does not render client-side content, verify mailbox delivery, test a linked route, establish that readers have no other way to contact the organisation, or make a jurisdictional or legal-compliance assessment.
How to fix it
Review the published policy
Open the policy page that the site publishes and decide which contact method readers should be able to find there.
Publish the intended contact information
If appropriate for the organisation, add a maintained email address, mailto link, or clearly labelled link to a support or contact route in the policy's server-rendered content.
How to verify the change
Verify the static policy response
Fetch the deployed policy page without relying on client-side rendering and confirm that the intended contact signal appears in the response content.
Expected: The selected policy page contains the contact information or route the organisation intends to publish.