We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On a multilanguage website, localized TYPO3 content elements contain an anchor with its localized UID (e.g. <a id="c198"></a>).
<a id="c198"></a>
These anchor links (missing the href attribute) are considered as internal links in the Yoast SEO analysis.
href
<!-- TYPO3SEARCH_begin --> <div id="c197" class="frame frame-default frame-type-textmedia frame-layout-0"> <a id="c198"></a> <header><h1 class="">Localized content element</h1></header> <div class="ce-textpic ce-center ce-above"> <div class="ce-bodytext"> <p>Some content</p> </div> </div> </div> <!-- TYPO3SEARCH_end -->
Analysis result: "Internal links: You have enough internal links. Good job!"
This result can be confusing for editors which try to optimize a web page.
The analysis should take into account, if an anchor actually contains the href attribute.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Please give us a description of what happened.
On a multilanguage website, localized TYPO3 content elements contain an anchor with its localized UID (e.g.
<a id="c198"></a>
).These anchor links (missing the
href
attribute) are considered as internal links in the Yoast SEO analysis.Analysis result: "Internal links: You have enough internal links. Good job!"
Please describe what you expected to happen and why.
This result can be confusing for editors which try to optimize a web page.
The analysis should take into account, if an anchor actually contains the
href
attribute.How can we reproduce this behavior?
Technical info
The text was updated successfully, but these errors were encountered: