thedaviddias/Front-End-Checklist / skills/tel-mailto
tel-mailto
VerifiedUse when applies to contact pages, business listing pages, headers/footers, and any page displaying a phone number or email address. Use when auditing contact UX or schema-marked LocalBusiness pages.
Tel & Mailto Links
On mobile devices, tel: and mailto: links trigger the native phone dialer and email client with one tap; plain-text contact info forces copy-paste and measurably reduces contact conversion rates.
Quick Reference
- Wrap phone numbers in
<a href="tel:+15551234567">for click-to-call on mobile devices - Wrap email addresses in
<a href="mailto:contact@example.com">for one-click email compose - Use E.164 format for
tel:links:+followed by country code and number, no spaces or dashes - Plain text phone numbers and emails require users to copy-paste — a UX and conversion friction point
Check
Scan the HTML for phone numbers (patterns like \+?[0-9\s\-().]{7,}) and email addresses ([\w.-]+@[\w.-]+\.[a-z]{2,}). Verify that phone numbers are wrapped in <a href="tel:..."> and emails in <a href="mailto:...">. Flag any that appear as plain text.
Fix
Wrap each phone number in an anchor tag: <a href="tel:+15551234567">+1 (555) 123-4567</a>. Wrap each email in: <a href="mailto:contact@example.com">contact@example.com</a>. Format tel: values using E.164 (+[country][number]) without spaces.
Explain
Explain how tel: and mailto: URI schemes work in HTML, why E.164 format is required for international compatibility, and how these links improve mobile UX and contact conversion rates.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Tel & Mailto Links. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/tel-mailto
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |