Support » Plugin: The SEO Framework » The description generates the plugin automatically – but wrong?

  • Resolved SamuelFernandez

    (@samuelfernandez)


    If I have not inserted an individual description, the META description is created automatically. So the plugin draws a certain number of characters from the content and sets a “…” behind it. Is this correct?

    Strangely enough, this is not the case with me: http://prntscr.com/ofrktg

    The description generates the plugin automatically and nevertheless it indicates that too many characters are used (see left – the area is not green, but yellow). I mean: I could edit any description now, but if the plugin does that automatically, then it’s correct. Or? 🙂

    Or have I set something wrong.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Sybre Waaijer

    (@cybr)

    Hi Samuel!

    First, thank you so much for your review. I truly appreciate it!

    Yes, that’s correct, but not always. The description generator is a bit more intricate than that. It is so complicated, I decided to write a KB entry on it today: Explaining the description generator.

    I wrote it with v3.3 of TSF in mind. But, v3.2.4 almost works the same, yet only a few hundred times slower, and without Unicode-punctuation support.

    In your case, the last word stopped precisely at the 160-character limit we impose. We added an ellipsis (…) because there’s no other punctuation found. This symbol makes for 161 characters in total.

    Please keep in mind that the character counter is a rough guideline, whereas the pixel counter asserts the true length. To learn what this means, see our KB entry on pixel counters.

    You used a few capital W letters, which makes up for a longer description. Maybe I should adjust the guidelines slightly for German because in that language we tend to capitalize nouns?

    In any case, in the final paragraph of the description-generator KB entry, I explained why it’s not perfect. For example, it can’t calculate the pixels. I also wrote that if you really want it to be accurate, you must write a description yourself. The goal I have for TSF is to take that work away from you so that you can focus on other things.

    I hope this explains everything and more! If you have more questions, feel free to reach out again. Cheers!

    SamuelFernandez

    (@samuelfernandez)

    Hi @cybr and thanks for the eplanation.

    Then I’m curious about version 3.3 :-).

    I read your article very enthusiastically and it proves one thing to me again: the world needs such developers. Please continue with your devotion. I would like to support that with a premium purchase!

    Please continue with it!

    Plugin Author Sybre Waaijer

    (@cybr)

    Thank you so much for your support, Samuel! I’m glad you liked the article!

    There are over 800 changes logged for v3.3 (please don’t waste your time reading that, it’s for reference only), and the update is almost ready for beta! I’m going to write a “what to expect” article soon after it reaches that stage. To stay up-to-date, I recommend following our main Twitter account: https://tsf.fyi/twitter

    Cheers! 🙂

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘The description generates the plugin automatically – but wrong?’ is closed to new replies.