Maximum allowed internal link per post (not per link appearance) and method?

  • Resolved devdev3919

    (@devdev3919)


    2 months ago

    Hello,

    Thank you for providing a free and simple plugin. I have 2 questions:

    1-) If i have 10,000 posts and each post has 2-3 (trail words, not single, usually 2 words only) words associated to them, any post with similar words will be completely populated with the internal links. There must be a limit for it.

    2-) If i have many blog posts (10,000), how would the plugin work? Does the plugin checks the database for the words on the page, and randomly select multiple words for the posts?

    3-) Is there a prerender option? Such as updating the post’s links internally before they are fetched so there is no database query when the users are loading the page? If there is 100 concurrent users, picking a random post with with 2000 words, and 10,000 posts with multi internal link words, this would be a devastating query to the database.

    For large blogs, what is your suggestion? Thank you.

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

    (@webraketen)

    Thank you for your message!

    Unfortunately, I’m not quite sure if I understand your first question correctly. Do you have a concrete example that you can show us? Or can you explain in more detail what the limit should look like?

    We will get back to you about your other 2 points. We have forwarded the question internally.

    Plugin Author webraketen

    (@webraketen)

    Hey @devdev3919,

    we’ve got some feedback regarding your other 2 questions!

    Re 2: Whenever a page is viewed, all the words to be linked are loaded from the database and a check is made für each individual word to see whether it occurs in the text. If so, the word is linked according to the settings you’ve defined within the plugin.

    Re 3: The list of links is actually loaded on every page and replaced in the text. This is only one additional database query, but the replacement of words with links is comparatively computationally intensive, so that long texts and many links can certainly put quite some load on the system.
    For this reason, we will be offering a caching function in our upcoming Pro version that will support various cache providers (Redis, Memcached, APCu, database and file cache). When the cache is activated, the result of the link replacement is stored temporarily and loaded directly from the cache the next time it is called, so that neither additional database queries nor the actual replacement are carried out again. There is currently no pre-render option, but we will consider to also implement this in addition to caching.

    The recommendation for large blogs would be to use a cache plugin until then, but at the moment we cannot guarantee which plugin will take all adjustments into account.

    Hope this helps!

    Thread Starter devdev3919

    (@devdev3919)

    Thanks for the answers. I will wait patiently.

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