# axe-core identical-links-same-purpose error: same text different destinations - how to fix it

## TL;DR

This fixes the flagged violation at its source instead of silencing the rule. Two or more links share identical text but go to different destinations, so the purpose is ambiguous. Follow the steps, re-run the scan, and gate the rule in CI so it stays fixed.

## The error, verbatim

```text
axe-core identical-links-same-purpose error: same text different destinations
```

## Fix it step by step

### Step 1

Rewrite the link text so each destination is distinguishable, or extend the text with visually-hidden context.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 2

Alternatively, give each link an aria-label that states the differing purpose.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 3

Screen-reader-test a list of the links: each announcement should make the destination clear.

Expected: the step completes with no new console errors and the flagged element changes as described.

### Step 4

Re-run axe to confirm.

Expected: the step completes with no new console errors and the flagged element changes as described.

## When to use this skill

- Your scan report lists this exact rule or failure
- You are clearing automated accessibility failures before release or audit
- A CI accessibility gate is red because of this item

## When NOT to use this skill

- Links that go to the same destination with the same text are fine; this rule is about differing purposes.
- The issue only appears in manual screen-reader testing and no automated rule flags it
- You are doing a full manual WCAG audit; this skill covers one automated check

## Compatibility

axe-core 4.8+ (rule identical-links-same-purpose, WCAG 2.4.9).

## Variant phrasings

### axe identical-links-same-purpose: same text different destinations

Same underlying issue and the same fix. Searchers phrase it different ways; the remediation does not change.

## Why it happens

Two or more links share identical text but go to different destinations, so the purpose is ambiguous. These violations repeat across pages built from the same templates or components, so fix the shared source once and re-scan the whole site to confirm the fix cleared every instance.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_axbXCrrrbsxO1P2osri7nA