Connect your site to Labrika
With all of our Labrika subscriptions you are able to create exportable white-label reports that you can also host on your site for your clients to download. Reports can be customized with your own logo and menu structure to align with your company’s branding. All of our reports are broken down into different categories so you can choose to share specific reports such as keyword rankings only.
Different ways of sharing Labrika reports
Share Labrika report link:
You can share a link to the report which will enable the recipient to access the report providing they use this specific link (no login required).
This requires you using the “link’ option (selected by default) after clicking the ‘get a link to the report” icon in the sidebar in the top right hand corner (share icon including three dots and two lines).
All you have to do is then copy the link shown below ‘report link’.
Self-hosted report on your website:
You can also download a copy of the report and host it directly on your website for your clients to access. This is the preferred option for those that want a truly white label report for clients and co-workers.
How to create and use a self-hosted Labrika report on your website:
Click the “file’ option after clicking the ‘get a link to the report” icon in the sidebar in the top right hand corner (share icon including three dots and two lines).
You should now be viewing a page with the title ‘Connect your site to Labrika’.
You page should look like this:
Under ‘report name’ please type the name that you wish the report to have and then click ‘apply’.
If you typed ‘wikipedia-ranking’ and clicked ‘apply’ then your page should look like this:
Click ‘Download this HTML file’ and upload it to your websites public_html (you can pick a different directory but you will have to reflect this in the link given to the user) folder via FTP or cPanel/Plesk file manager.
Provide the link/s for your clients to access their report on via your self-hosted Labrika report.
If you had uploaded the downloaded file in the screenshot (in step 3.) to your public_html directory then the download link for your self-hosted report would be:
Please note: You should create an individual report name for each report you upload to your site, otherwise you would have to use separate files or directories for every report as they would have the same filename.
‘share.html’ is the file name in the link:
You would want to change the name of this to something like
The second report you were uploading to your site could then be named
‘report2.html’ and would allow you to use the same directory for all of your reports.
Create your own custom menu for multiple reports per client:
You can create your own menu for clients so that the client can easily switch between reports without having to leave/open new tabs every time.
Simply paste your code with multiple links to different reports in the ‘paste’ sections below for multiple reports to show per page.
<template id="app-header"> <!-- Paste header code here --> </template> <template id="app-header"> <!-- Paste footer code here --></template>
How to rename and/or move the self-hosted report files after uploading them for more personalised link URL’s
The link after downloading the report from Labrika, and then uploading to public_html on your site, without changing any of the names or file locations, would be:
share.html is the file name and
wikipedia.com is your parameter name.
To change the file name or to change the link URL you would want to change the folder you uploaded the file to and/or the name of the
If you moved the
‘share.html’ file from the ‘public_html’ folder to the ‘private’ folder and also renamed it to
‘position.html’ then the new URL for clients to access would be this:
Restricting outside access to the report
There are several ways to restrict access to the report:
Control access using HTTP Basic authentication.
Adding additional characters to the report name so that outsiders cannot guess the link.
Examples of this would be:
Changing parameter name to:
Using a generated code without names:
Or making a completely separate file name for each client: