-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
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
h1 duplicate error, but nothing in source code #530
Comments
We updated to yoast_seo_premium 5.3.0 on a dev server, the bug is still the same |
Any update to this problem? We face it in all our typo3 systems as well. |
for me, this false positive is solved with the yoast_seo v9.0.0 |
Updated to yoast_seo 9.0.1 and the problem still exists on all typo3 systems |
We also have this issue. It happens when there is content before the first h1. I moved the marker after the headline, and the breadcrumb navigation below the content and moved it up via CSS. I'd love to provide a fix for this, but I have no clue how to compile JS sources in this project. |
same issue for us on latest state/version |
thanks a lot for the hint. I am xclassing the previewservice and move everything before the h1 to the end. this might not fit for you but maybe gives you an idea <?php
declare(strict_types=1);
namespace StudioMitte\Theme\XClass\YoastSeo;
use YoastSeoForTypo3\YoastSeo\Service\PreviewService;
class XclassedPreviewService extends PreviewService {
protected function prepareBody(string $body): string
{
$body = parent::prepareBody($body);
$pos = strpos($body, '<h1');
if ($pos !== false) {
$firstPart = substr($body, 0, $pos);
$body = substr($body, $pos) . $firstPart;
}
return trim($body);
}
} |
Please give us a description of what happened.
In Backend I click on "SEO needs improvement" and I get the H1 duplicate warning. But on the page, there is just one H1 as it should be:
https://www.leuphana.de/studium.html
Please describe what you expected to happen and why.
The H1 warning shall only be displayed, if more than one H1 in source code
How can we reproduce this behavior?
Screenshots
Additional context
Is there maybe some kind of caching involved, so the result is not updated?
Technical info
The text was updated successfully, but these errors were encountered: