Skip to main content

Links : Empty Link, Broken Link, Navigation Link, Non-navigation Link

 

🔘 1. Empty Link

  • Definition: An <a> tag with no href or no visible content.
  • Example: <a></a> or <a href="#"></a>
  • Usage: Often unintentional or used as placeholders during development.
  • Problem: Bad for accessibility and SEO—screen readers can’t interpret them, and users get confused.

❌ 2. Broken Link

  • Definition: A link that points to a non-existent or unreachable resource.
  • Example: <a href="https://example.com/deleted-page">Click</a>
  • Usage: Usually accidental—caused by deleted pages, typos, or outdated URLs.
  • Problem: Leads to 404 errors, hurts user experience and SEO.

🧭 3. Navigation Link

  • Definition: A link used to move between sections or pages of a website.
  • Example: Menu items like <a href="/about">About Us</a>
  • Usage: Essential for site structure and user flow.
  • Benefit: Helps users explore your site and improves crawlability for search engines.

🚫 4. Non-Navigation Link

  • Definition: A link that doesn’t lead to a new page or section.
  • Example: <a href="#" onclick="toggleMenu()">Menu</a>
  • Usage: Often used to trigger JavaScript actions like opening modals or dropdowns.
  • Note: These should be used carefully—if there's no href, consider using a <button> instead for accessibility.

🧠 Summary Table

Link Type Has href Navigates? Common Use Case
Empty Link ❌ or empty ❌ Placeholder or coding mistake
Broken Link ✅ ❌ (fails) Outdated or incorrect destination
Navigation Link ✅ ✅ Menus, footers, internal links
Non-Navigation Link ✅ or ❌ ❌ JavaScript triggers, UI toggles

If you're building or testing a site, it's smart to audit for these regularly. Want a Selenium script to detect empty or broken links automatically? I can help you build one! 🛠️🌐

Follow on LinkedIn
Labels:

Comments

Post a Comment

Popular posts from this blog

What is an SDET? – Roles, Responsibilities, and Career Path

Introduction The field of software testing has evolved significantly, and with the rise of automation, the Software Development Engineer in Test (SDET) role has become crucial. SDETs are technical testers with strong programming skills who ensure software quality through test automation and continuous integration. But what does an SDET really do? Let’s dive in.   Key Responsibilities of an SDET An SDET wears multiple hats—part developer, part tester, and part automation engineer. Their primary responsibilities include: Developing test automation frameworks for functional and regression testing. Writing automated test scripts to validate application functionality. Collaborating with developers to ensure testability of code. Implementing CI/CD pipelines with automated testing for continuous deployment. Conducting performance, security, and API testing to enhance software robustness. Required Skills for an SDET To excel as an SDET, you need a mix of technical and so...
2 comments
Read more

Keys.RETURN vs Keys.ENTER in Selenium: Are They Really the Same?

When you're automating keyboard interactions with Selenium WebDriver, you're bound to encounter both Keys.RETURN and Keys.ENTER . At a glance, they might seem identical—and in many cases, they behave that way too. But under the hood, there’s a subtle, nerdy distinction that can make all the difference when fine-tuning your test scripts. In this post, we’ll break down these two key constants, when to use which, and why understanding the difference (even if minor) might give you an edge in crafting more accurate and resilient automation. 🎹 The Subtle Difference On a standard physical keyboard, there are typically two keys that look like Enter: Enter key on the numeric keypad. Return key on the main keyboard (near the letters). Historically: Keys.RETURN refers to the Return key . Keys.ENTER refers to the Enter key . That’s right—the distinction comes from old-school typewriters and legacy keyboard design. Return meant returning the carriage to the beginning ...
Post a Comment
Read more

Regression Testing vs. Sanity Testing: Detailed Explanation with Example

  Regression testing and sanity testing are both essential software testing techniques, but they serve different purposes in ensuring software stability after modifications. Regression Testing Definition: Regression testing is a comprehensive testing approach that ensures recent code changes do not negatively impact the existing functionality of an application. It involves re-running previously executed test cases to verify that the software still works as expected after modifications such as bug fixes, feature additions, or updates. Key Characteristics: Scope: Covers the entire application. Purpose: Ensures that new changes do not break existing functionality. Execution Time: Time-consuming due to extensive testing. Test Cases: Uses a large set of test cases. Automation: Often automated for efficiency. Depth: In-depth testing of all functionalities. When Used: After major updates, bug fixes, or new features. ...
Post a Comment
Read more