Quick Reference
Inline Link
[Link text](URL "Title")Reference Link
[Link text][ref]
[ref]: URLInline Link Syntax
Inline links put the URL directly after the link text, making them easy to write and understand at a glance.
Basic Inline Links
Markdown:
[Visit Google](https://www.google.com) [View on GitHub](https://github.com/user/repo) [Send Email](mailto:hello@example.com)Links with Titles (Tooltips)
Markdown:
[Google](https://google.com "World's most popular search engine") [GitHub](https://github.com "Code hosting platform") [Stack Overflow](https://stackoverflow.com "Q&A for developers")Output:
Reference Link Syntax
Reference links separate the link definition from the text, making documents more readable and easier to maintain.
Numbered References
Markdown:
Check out [Google][1], [GitHub][2], and [Stack Overflow][3] for web development resources. [1]: https://www.google.com [2]: https://github.com [3]: https://stackoverflow.comOutput:
Check out Google, GitHub, and Stack Overflow for web development resources.
Named References
Markdown:
The best [search engine][google] and [code repository][github] sites. [google]: https://www.google.com "Google Search" [github]: https://github.com "GitHub - Code Repository"Output:
The best search engine and code repository sites.
Advanced Hyperlink Techniques
Links in Different Contexts
Markdown:
### Links in Headers: [GitHub](https://github.com)> Blockquote with [link](https://example.com) - List item with [link](https://example.com/) - Another [link](mailto:user@example.com) **Bold text with [link](https://example.com) inside** *Italic text with [link](https://example.com) inside*Internal Document Links
Markdown:
[Jump to Section](#section-name) [Go to Top](##top) [See Footer](#footer-section) ## Section Name Content here... ## Footer Section {#footer-section} More content...Output:
Links with Complex URLs
Markdown:
[Search for "markdown"](https://www.google.com/search?q=markdown) [Wikipedia Article](https://en.wikipedia.org/wiki/Markdown) [API Endpoint](https://api.example.com/v1/users?limit=10&offset=0)Best Practices
✅ Best Practices
- Use descriptive link text: "Download the user manual" instead of "click here"
- Add meaningful titles: Provide context with title attributes
- Use reference links for readability: In documents with many repeated links
- Test all links: Verify URLs work before publishing
- Use HTTPS: Always prefer secure links when available
- Consider accessibility: Screen readers benefit from descriptive link text
❌ Common Mistakes
- Generic link text: "Click here", "Read more", "Link"
- Broken or outdated URLs: Always verify links work
- Missing protocols: Some parsers need "https://"
- Unescaped special characters: URL-encode spaces and special characters
- No title attributes: Missing helpful tooltip text
Common Issues and Solutions
❌ Problem: Spaces in Link Text
Wrong:
[ Link with spaces ](https://example.com)Correct:
[Link with spaces](https://example.com)Don't add spaces between brackets and parentheses.
❌ Problem: Parentheses in URLs
Problematic:
[Wiki](https://example.com/page_(disambiguation))Solutions:
[Wiki](https://example.com/page_%28disambiguation%29) [Wiki][wiki-link] [wiki-link]: https://example.com/page_(disambiguation)URL-encode parentheses or use reference links.
❌ Problem: Missing Reference Definitions
Wrong:
[Link text][missing-ref]Correct:
[Link text][ref] [ref]: https://example.comAlways include reference definitions at the bottom of your document.
Try Hyperlinks Yourself!
Practice hyperlink syntax with our free online converter.