Internal Links

If you want to remove a keyword for a post or page, simply go to the asset’s editor and remove it from the Internal Link Juicer keyword editor list. After removal, the link associated with that keyword is also removed.

If you want to keep the keyword but only limit the number of inbound links, you can do so using the options in the Internal Link Juicer settings for all assets (the Pro version also lets you limit inbound links for individual assets such as posts or pages).

If you want to delete keywords in bulk, simply export the entire existing keyword configuration in our “Tools” section, modify (remove or add keywords) the file using a spreadsheet program of your choice (e.g. MS Excel), and then re-import it.

Can you tell me a bit more details about your site:
– for how many posts/pages do you try to build links?
– how many keywords do you already have configured?

Thanks for getting in touch.

Seems like this has to do with the deactivation of the Internal Link Juicer. As long as the deactivation mechanism is working, you can ignore that error for now.

We will have a look at it and try to fix it.

That is possible. You can exclude any page you want from giving internal links by adding it to the post blacklist.

You find the setting in the Internal Link Juicer’s options. You can also find further help about that feature here in our docs.

In principle, this is possible.

The Internal Link Juicer uses keywords for matching in the order of the posts where they were configured.

This means, that if the post with the keyword “Green Apples” configured has a lower ID than the one with “Apples”, it will get matched first.

Yes – the free version supports custom post types. For (custom) taxonomies you would need to have the Pro version running.

Let me reproduce that example.

You have 2 posts:
– Post A, has the keyword “Mario” configured
– Post B, has the keyword “Super Mario Bros” configured

When the content of Post C gets published, which has “Super Mario Bros” in it, the Internal Link Juicer matches “Mario” first, so there is no chance for “Super Mario Bros” to get linked.

Is that the concern of your thread?

This only happens, when you have the “greedy” linking mode (“link everything that is possible”) active.

The Internal Link Juicer uses everything chronologically on its matching algorithm. This means that the older post (with the smaller ID; Post A) gets matched with its keywords first. All the others after that get ignored.

Then the solution would be, to recreate the older posts (with the keyword “Mario”), so that has a higher ID in your database.

I’m sorry, but currently, we can’t provide compatibility mode for Translatepress. However, I will put this suggestion on our backlog to take it up when the time comes.

At the moment we offer assured compatibility for the two translation plugins “WPML” and “Polylang”.

Thanks for providing your example.

With our recent release of version 1.3.9 we made it possible to use nearly all special characters (beside comma, curly braces, and +/- as these are reserved for internal usage).

May I ask you to update to the latest version? Afterward a linking of character sheet (HTML) should be possible.

Do you mean that you want to add a keyword that will link to your category?

If so you need to add a keyword in your category and the plugin will search all the contents for that keyword and link it to your category, also don’t forget to add the category(taxonomy) to the whitelist.

Please bear in mind, that the feature for linking taxonomies is a Pro feature. We can only point to you that this is possible – if you need specific support for that, you would need to use the support channels for our Pro users.

• This reply was modified 2 years, 6 months ago by Internal Links.

If nothing is imported, this may be due to various reasons.

One reason can be that there are no keywords that can be imported. For example, because they already exist and are already configured.

The most common reason, however, is an incorrect CSV format. It is important that the import file has the same format as the CSV file from our export.

The best way to check is to directly export a complete dump using our import/export tools and start editing from there.

Some tools, such as MS Excel, change the CSV format when saving directly, which means that the import can no longer be processed correctly. Please open your file in a conventional text editor and check first whether it has the same structure as the file from our export.

If necessary, you have to adjust the export settings of your spreadsheet program accordingly.

If it still does not work despite the check, please send me the file that causes the problems with the import. Then I will be pleased to look at it for you.

Is the post type of “https://www.gmengine.com/article/wp-activity-log-for-bbpress/” also whitelisted for giving links?

Can you share some screenshots of your Internal Link Juicer settings, as well as from the keyword editor, where you configured the keyword “bbpress”?

The Internal Link Juicer is explicitely working case insensitive. This means the configured keyword “fruit lover” should lead to linking “Fruit Lover”, “Fruit lover”,… and so on as well.

If it is still not working it may be that you have something in your setting that permits the linking.

Can you please check that and if the problem still exists send us some screenshots of your plugin settings as well as the content you try to set links and the keywords you have configured for?

Can you please give us a concrete example, that we can replicate on our end?

In general:

• Post the keywords you have configured (the ones with the special characters
• Post a small excerpt of content where you expect the linking happening

With your examples, we can have a look at what might go wrong on the plugin side or whether it is dependent on your configuration.

Thanks!

Can you please give us a concrete example, that we can replicate on our end?

In general:

• Post the keywords you have configured (the ones with the special characters
• Post a small excerpt of content where you expect the linking happening

There are indeed some “protected” characters, that we use to internally separate keywords or which we use for our keyword-related features (like the gap feature).

With your examples, we can have a look at which characters you want to use and tell you exactly whether what will work or may not (and what we can maybe enable by our next releases).

Thanks!