It only takes one line of code on your website for InLinks to save you hundreds of hours on tasks that few web owners ever have time to carry out. Adding the code is the single most important step in the on-boarding process. This page talks about how to add the code and sets out to our strict policies on what we can and cannot do with the code.

The short version

On registering, you will be given one line of code, which we recommend is placed in the footer section of your website, so that the line of code runs on any page that loads on your site. The script will look something like this:

(Sample code for InLinks integration)

Reasons to add the code

The code helps InLinks to manage internal links on your site and add Schema to your web pages.

  • It does NOT collect any personal data (not even the IP numbers) of any users. You should not need to update any GDPR or privacy policies.
  • It will not create links OUT of your website. If (in the future) this is a requested feature, every out-link would be entered by the user.
  • It will NOT slow down your site. The latency on the code is extremely low.
  • It only requires the same 1 line of JS code on every page.
  • No server-side slow down as js is rendered by the browser. your site might get FASTER.
  • Very little latency
  • Links are integrated in text paragraphs. Your navigation bars will not be affected.
  • Internal Links are created without further code, the anchors use exact match, synonyms & sentence fragments.
  • Internal linking & Schema is fully interpreted by Google

At any time, you will be able to see the code that is executed.

Installing inLinks on WordPress

If you are not a coder (or even if you are!), then you may be using WordPress. to run your website. If you do, then there are many ways to add the code. For example, install the “Insert Headers and Footers” plugin or the “Header and Footer Scripts” plugin and add the code in the footer section there. You do this by:

  • Logging into your blog via the /wp-admin
  • Select “Plugins” then “Add New”
  • in the search bar, search for “Header and Footer” and select based on the reviews and installs
  • Follow the instructions on the screen to make the plugin active and to add the script.

Installing Inlinks using Google Tag Manager

If you are an agency, it is likely that you will not have access to the site itself, but may have access to Google Tag Manager. You can use this to insert the code. a good explanation on how to do that is written here (opens in a new tab).

Security Considerations

You do not NEED to call the .js file on a third party server if you do not wish to do so, but you will need a developer or system administrator to amend the implementation process. You can see the actual code executed by simply entering the .js link into a browser. The code for all sites beyond the first 600 or so, is this:

// JavaScript Document 
// Substitute pid = xxx for the pid variable in your project
var pid = XXX ;
var jsonPath = "https://jscloud.net/x/" + pid + "/" + window.location.href.replace(/\/|\.|\-|\:|\=|\?/gi, "") + ".json";
 
 jQuery.getJSON(jsonPath, function (data) {
     jQuery.each(data, function(i, element) {
         var t =element['t']; var a = element['a'] ; var n = element['n'] ; 
         if (t === 'p' || t === 'li')
         {
          var o = new RegExp(element['o'],"g"); 
          jQuery( document ).ready( function( $ ){ $(t + ':contains("' + a + '")').html(function(index, html) { return html.replace(o, n); }); });
          
      }
      else if (t === 'h2')
      {
      jQuery( document ).ready( function( $ ){ $(t + ':contains("' + a + '")').after('RELATED CONTENT: ' + n); }) ;
      } 
      else if (t === 's') /* Schema */
      {
      var o = element['o']; 
      var scriptTag = document.createElement("script");
 scriptTag.setAttribute("type", "application/ld+json"); 
 scriptTag.appendChild(document.createTextNode(o)); 
 document.getElementsByTagName("head")[0].appendChild(scriptTag);       
      } 
      
     });
 });

Your web developer may choose to add this code directly or put the .js file on your own server, to avoid a third party server being able to execute a .js file. In doing so, then only .json (text) files are called from third party servers and these are not executable. In this kind of installation, even if a bad actor were to compromise inLinks’ servers, they would not be able to run malicious code on your website by amending the .js file.

What is NOT possible to mitigate is a bad actor being allowed access to your inLinks login. From there, they would be able to add links out of context or delete schema. Do not, therefore, provide login details to untrusted third parties. Removing the javascript would, however, remove all changes made by inLinks.net.

Modifying the installation

Your developer has the option to only use the code that generates the schema OR only use the code that generates the internal links. If you require further information on how to do this, please ask via the website.

A great post from inLinks.net

An Internet Marketer SEO Speaker and online strategist, specializing in SEO and SAAS technologies. First Degree in Maths and Management Studies. MBA with Strategy from Aston.

Notable Awards:
Search Personality of the Year
Lifetime Achievement Award
Outstanding Technology Individual of the Year

Comments (1)

  1. Pingback: Onboarding – Setting Topics – InLinks

Leave a comment

Your email address will not be published. Required fields are marked *