As we improve the features, fix bugs and generally develop inLinks, we’ll record launches here.

FAQ Schema Generator

InLinks has a built in FAQ Schema Generator. Inlinks to scans your content looking for questions in your text that you answer succinctly and will then automate the generation of FAQ Schema and show an “accepted answer” using JSON-LD automatically. This means that FAQ schema can appear anywhere on your site, not simply on a dedicated support page. What does adding FAQ Schema do? By adding FAQ Schema to your content, you tell a search

New way to measure how Google understands content in a verticle

Inlinks has today started a series of ongoing reports for the Online Marketing Industry. Each report selects an industry sector with a keyword triggered market focus. The reports then compare the entities identified on the most relevant content for that market with the entities detected using Google’s Natural Language Processing API. The results show at this stage that Google can still only positively identify (on average) less than 20% of all entities or topics discussed,

New Stuff: Improved Javascript code and more

It has been a busy week. The most notable launch was Monday’s announcement that you can now start assigning content briefs to writers, as reported in our “Content Management system for SEOs” post. There are also a few things that were fixed along the way that I never got around to documenting. Adding “Defer” to the default Javascript code A few people were suggesting that the .JS code was creating a small, but real, page

Inlinks screenshot: Project assigning

Content Management for SEO Content Writers

InLinks has launched the ability to assign content briefs to SEO Content writers, whilst retaining overall control of the content. This turns the Inlinks optimization module into an SEO Content management system. It gives the ability for SEOs who need to delegate content writing to freelancers or in-house teams. Enterprise Collaboration Tool InLinks builds content briefs around topics, rather than keywords. In order to scale the optimization of content for search engines, it is necessary

Change your Competitor List

When trying to write better content than anyone else, our content optimization tool uses the top search results to build a content brief. At times, though, you know better than the search engines as to what is the BEST content out there, so we have given you the chance to change the competitor cohort list for any given keyphrase: Knowledge Graphs and Training Sets When inLinks creates a content brief for your writers, it first

Change Competitors on Content Analysis Tool

When you create content briefs to write the perfect content for search, inLinks analyses the top 10 URLs that rank for that phrase in your market. Now we have given paid accounts the ability to change URLs in that competitor set. This might be useful if: The competitor page is uncrawlable There is a better competitor that Google has not recognized The key phrase is new and not yet an established search term.

Manually Manage Internal Linking

Managing Internal Links is a real challenge for SEOs and although inLinks has automated much of this process, sometimes you need to be a little more precise and perhaps would like to create your own. The inLinks system now supports the ability to curate and create internal links directly from your inlinks.net dashboard, so now you will never again need to go back to your web team to ask them to add or change links

API Upgrade and More

Today we have upgraded the API for our NLP analysis algorithm so that it works significantly faster and picks up more topics. The API is the part of our system that integrates the web interface with our Knowledge Base. When you update your associations or topics, this creates a ripple in the space-time continuum (OK… not really… but it does change your link graph, which we need to recalculate). The most noticeable effect will be

Addressed a minor .js issue

One of our users noticed that when a page loaded which had our code on, but that page itself was not analyzed against our knowledge graph, the .js file called a non-existant JSON file, which created a 404 error in testing. In truth, the “cost” was small, but we are SEOs and details matter, so we have now fixed this in .htaccess. Javascript response times looking good We appreciate that the load times of javascript