# Unsupported Anchor Hreflangs
All anchor links which include hreflang elements.
**Priority**: Low
**Impact**: Negative
## What issues it may cause
Hreflang attributes inside normal anchor tags are [not supported by search engines](https://www.searchenginejournal.com/google-says-hreflang-attributes-should-not-be-used-in-anchor-tags/347706/#close) so they will be ignored. They need to be inside <link> tags in the HTML head, response headers or in Sitemap links.
## How do you fix it
The hreflang attribute to specify a language or/and locale versions of your pages should be implemented as [link tags in the HTML, HTTP Headers or in Sitemaps](https://developers.google.com/search/docs/specialty/international/localized-versions).
## What is the positive impact
Adding valid hreflang attributes on pages with a language alternative can help for the following reasons:
- It increases the discoverability of the alternative language or/and locale versions of your pages.
- It removes potential duplication of the alternative versions.
-
It ensures that the correct pages are ranking for the right users e.g. pages with the appropriate language and
currency.
## How to fetch the data for this report template
You will need to run a crawl for report template to generate report. When report has been generated and you have
crawl id you can fetch data for the report using the following query:
```graphql
query GetReportStatForCrawl(
$crawlId: ObjectID!
$reportTemplateCode: String!
$after: String
) {
getReportStat(
input: {crawlId: $crawlId, reportTemplateCode: $reportTemplateCode}
) {
crawlUniqueLinks(after: $after, reportType: Basic) {
nodes {
anchorText
urlTo
urlToTitle
primaryUrlFrom
primaryUrlFromTitle
instanceCount
primaryUrlFromDeeprank
urlToDeeprank
hreflang
linkType
nofollow
isRedirect
}
totalCount
pageInfo {
endCursor
hasNextPage
}
}
}
}
```
**Variables:**
```json
{"crawlId":"TjAwNUNyYXdsNDAwMA","reportTemplateCode":"unsupported_hreflang_links"}
```