In one paragraph
Contact information missing on website means the scan did not recognise a link matching its contact vocabulary. Details can already exist as plain text, while an unrelated matching destination can pass. Check the actual operator's applicable disclosure duties and provide accurate, accessible identity and contact information. One contact link does not prove completeness, and a heuristic warning does not establish that all required information is absent.
Why it matters
Article 5 of the EU e-Commerce Directive requires covered providers to make specified information easily, directly, and permanently accessible, including identity, establishment address, and contact details such as email. Registers and other particulars apply where relevant.
Consumer, professional, and national requirements can add detail. The obligations depend on the service and legal setting, not merely a .com address or a visitor count. Do not treat one universal contact template as a substitute for scope-specific review.
A useful route should also work in practice. An unmonitored mailbox, broken form, or provider profile that never reaches the operator can leave users without effective communication even when its wording passes the detector.
How WebAuditOS evaluates this finding
The supplied site-wide rule searches link addresses and visible text for recognised contact or imprint terms in selected languages. It uses the documented rendered-link fallback. A match passes; no match on readable pages warns at low severity; unavailable coverage can remain ungraded.
Plain-text addresses and some mail links can be missed, while a third-party matching link can pass. It does not validate the target content, operator identity, legal particulars, response handling, or the actual communication route.
How to fix it
- Establish who operates the service and which disclosure rules apply. Keep business identity, trading name, relevant registration, address, and contact responsibilities aligned with the real arrangement.
- Review existing footer, legal, imprint, and privacy resources before adding duplicates. A separate contact page is useful in many cases but is not the only possible information architecture.
- Publish the required information accurately in a clearly accessible location. Do not expose a private personal address indiscriminately without understanding the actual obligation and available lawful arrangements.
- Provide a clear route. For example:
<a href="/contact">Contact the operator</a>Use a real maintained resource. This sample does not itself supply the required identity or establish a legally sufficient set of communication methods.
- Test mail delivery, forms, required fields, error feedback, and relevant access restrictions. Avoid collecting unnecessary personal information just to ask a basic question.
- Distinguish support, sales, complaints, and data-rights routes where necessary without obscuring the responsible organisation. A general contact route may be useful but should not falsely imply a formally appointed DPO.
- Verify localised versions and mobile navigation. The detector's languages are not a rule requiring English labels; choose wording the audience understands.
- Rescan recognition and separately review disclosure completeness and practical contactability. A matching imprint link cannot certify legal compliance.
What the fix can break
Copied templates can identify the wrong company or an outdated address. Review operator changes and provider arrangements rather than assuming the footer stays true indefinitely.
A contact form can fail silently or route messages to an abandoned team. Assign operational ownership and test it.
Do not add irrelevant matching links merely to remove a low-severity warning. Preserve accurate discoverable information that actually reaches the responsible service.
Questions
Does the warning prove no contact information exists?
No. The rule reads matching links, not every visible disclosure.
Does one contact page satisfy every national obligation?
Not necessarily. Verify applicable information and access requirements for the actual service.
Can a provider's profile replace the operator's identity?
Not automatically. Users need the relevant responsible-party details and an effective route.
Which related checks help?
Review privacy information, terms links, and the website audit checklist.