Tagged: , ,

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #861640

    Dear Kriesi,
    i hope you have the knowledge, that YOU use H1-Tag for your predefined stuff. h1-tag is every time user defined and not by theme.
    I hope, you will inform your user about that behavior. Normaly, you should give the user this option, where the user can use the h1 tag.
    It seems, that you can’t differentitate for “title” and h1. There is no reason to put a breadcrumb into h1.
    You haven’t understand this, what is the role in 2017 of user created content and machine learning and other new algorithms and quality guidlines.
    You don’t see, what googles say. John mueller has answered to this and closed this scene with “this has no big impact, but if i were the developer, i would make it clean” What does it mean “no big impact”? Since 200 signals exist, no big impact means: it has an impact.

    You have the knowledge, that every user, which use own H1-Tag in Content and your enfold theme is in a worst case of Keywordstuffing and doubleusage of h1.
    You can find in every good SEO ressource, that the h1-tag should not used two or more times. Google can render the page and can see: that the first h1 has a smaller size as other h1-tags. i can’t understand, why is it fixed. other users have mentioned this again and again,.
    Every SEO tool tell you the same: Double H1-Usage


    As i have modified the “functions-enfold.php” to
    ‘heading’ => ‘p’,

    my semrush-score for page health is rising from 72% to 84%.

    But you ignore such topics. With the p-tag: The design is the same and push my my score more than 10%. Same on other professional seo-tools.

    But, hear, what yoast tell to you in 2010 – 7 years ago :-)

    • This reply was modified 6 years, 9 months ago by Hokuspokus.

    Hi Hokuspokus,

    Thank you for bringing this up, I relayed your concern to Kriesi.

    If you need further assistance please let us know.
    Best regards,

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.