"nthlink" is an informal name for the technique of targeting the nth hyperlink on a webpage. Whether you’re writing CSS to style a specific link, scripting an interaction in JavaScript, or scraping content with a bot, selecting a link by its ordinal position is a common need. This article explains how to find the nth link, when to use this approach, and how to avoid common pitfalls. How to select the nth link - CSS: Use :nth-child or :nth-of-type. Example: a:nth-of-type(3) targets the third element among its siblings of the same type within a parent. Note that :nth-child(3) selects the third child irrespective of tag type — so structure matters. - JavaScript: Query all links then index. Example: const links = document.querySelectorAll('a'); const thirdLink = links[2]; // zero-based index - XPath: Use positional predicates. Example: (//a)[3] returns the third in document order. - Server-side scraping: In Python/BeautifulSoup: links = soup.find_all('a'); third = links[2]; in Selenium: driver.find_elements(By.TAG_NAME, 'a')[2]. Use cases - Automation and testing: Validate or click a specific link in a list-based UI. - Web scraping: Extracting a particular link among a predictable list (e.g., the third resource in a feed). - Conditional styling: Temporarily highlight a specific link based on position in navigation. - Pagination and indexing: Working with ordered lists where position conveys meaning. Pitfalls and limitations Selecting by index is brittle. DOM changes, ad insertion, internationalization, or dynamic loading can shift positions and break logic. Positional selectors can also be ambiguous across different viewport sizes if the layout rearranges content. CSS positional selectors depend on parent structure, so nested elements can produce unexpected targets. Accessibility and semantics Relying on position ignores content meaning. For users of assistive technologies, semantics, ARIA labels, and descriptive link text matter more than ordinal placement. If the link’s function is important, use stable, meaningful attributes (IDs, classes, aria-labels) instead of position-based targeting. Best practices - Prefer stable selectors: data-* attributes, unique IDs, or consistent class names. - Use position only when the structure is controlled and stable (e.g., generated lists you own). - Combine checks: when selecting the nth link, verify its text, href pattern, or surrounding attributes to avoid false positives. - Wait for DOM readiness in scripts and handle dynamically inserted elements with mutation observers or retry logic. - In scraping, design fallbacks: if the nth link isn’t present, search by link text or attribute patterns. Conclusion "nthlink" techniques are useful quick tools but should be used with caution. For maintainable and accessible code, prefer semantic and stable selectors; reserve positional selection for controlled contexts and add safeguards to handle changes in the DOM.