Vlink is Verbolia’s internal linking engine—a powerful, cloud-based solution designed to enhance internal linking across your website. It works by intelligently injecting a linking block into your pages, improving navigation and SEO performance.
F.A.Q
Vlink Settings – API usage this month: If we reach the limit, what happens? Can we quickly increase it to avoid issues?
If your usage exceeds the limit set on your contract, your monthly usage indicator will turn red, and a warning will be displayed within the app.
Furthermore, the API will automatically be blocked. This results in a “quota exceeded” error message and error code 403 appearing on your pages, indicating that no further API calls can be made.
If you exceed your quota, please contact support@verbolia.com. Our team can assist you in upgrading to a higher quota limit to quickly resolve the issue and help prevent future service disruptions.
Vlink Settings – API usage this month: When does Verbolia reset the quota usage?
Quota usage is reset on the first day of each month.
Vlink Settings – API usage this month: Can we query an endpoint to verify quota usage?
No, quota usage is only visible in the Verbolia back office. There is currently no API endpoint for checking quota usage.
Vlink Settings – API Usage this month: Are requests that result in timeouts or errors counted toward the usage limit?
No. Only requests that return a 200 status code are counted toward your monthly quota.
Vlink Settings – Automatic file retrieval: Is the connection with the feed live, or is it refreshed on a schedule like with Vpage?
The connection is asynchronous. In the Vlink settings, users must enter and validate the feed URL, define the refresh interval, and save the changes. After that, they need to manually trigger the refresh by clicking the Refresh button under Vlink Destination URLs.
Vlink Settings – Automatic file retrieval: If there’s a connection issue or the feed has the wrong format, is there an alert or notification?
Yes, users are alerted during the feed validation process if any errors are detected. It’s important to validate the feed after entering the URL to ensure it is correctly formatted and accessible.
If an error occurs after the feed has already been configured—during one of the scheduled refreshes—we will retain the last valid version and notify you of the issue.
Vlink Settings – Automatic file retrieval: For the feed, are there any formatting details that could cause errors and which I should avoid?
We support both “Destination URL” and “To:Page URL” column headers, so no errors should occur if you use either of them. However, issues may arise in the following cases:
- Incorrect column names (e.g., “Destination U” instead of “Destination URL”)
- Missing or empty URL fields
- Invalid values in the priority column (must be a number between 1 and 100)
- Malformed URLs or typographical errors
Vlink API– Operational guidelines: What is the response format?
All responses are returned in JSON format.
Vlink API– Operational guidelines: What are the possible error codes?
- 403 – Triggered by issues such as “unknown origin”, “invalid API key”, or “Max number of calls reached”.
- 500 – Internal server error.
Vlink API– Operational guidelines: Are both query parameters (metatitle and H1) mandatory?
No, only one of the two parameters is required to match a rule.
Vlink API– Operational guidelines: Does Verbolia provide a health check endpoint?
No, Verbolia does not currently offer a dedicated health check endpoint.
Vlink API – Are `StatusCode`, `Linkings`, `RuleName`, and `Errors` always present in the response?
HTTP Status code 200: you will always receive are StatusCode, RuleName, Errors, Linkings.
HTTP Status code 403: You will always receive message (e.g., origin missing, API missing, maximum calls reached etc.).
