Introduction

Before you click Start in Scalenut Interlinking, decide which domain owns the article. In the supplied help documentation, the domain connection is permanent for that particular report, and the documented remedy for a wrong connection is to open a different report. This article is documentation-based research, not a live API test. This article may contain affiliate links. For related background, see /scalenut-review/.

The practical question is not how to operate the interface. It is how to prevent an editorial mistake from becoming a report rebuild. Our recommendation is to hold the report and confirm the owning client domain before connecting anything. Because the binding cannot be changed for that report, confirming the owner first costs less than rebuilding. The official help page documents the binding rule and the disconnect path, but it does not say how to choose a domain before Start; this process turns that gap into a pre-connection check. The vendor marketing claims about factual accuracy, rankings, AI citations or visibility are not measured evidence, Google ranking factors or indexing guarantees.

Documented Workflow

The official help documentation describes a sequence for using Interlinking inside the editor. The page explains that Interlinking is for linking pages within the same domain and that the feature is available in the editor after opening a report or completing Cruise Mode steps (https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature). It describes opening the Interlinking option, clicking Add Domain if no domain was connected prior, selecting the Gmail account associated with the domain, and continuing. Once the domain appears, the documented action is to click Start. The page also states that once you have connected the domain for the article, you cannot change it for that particular report, and that you have to open a different report to connect a different domain for interlinking. It documents a disconnect path through My Account, the Domains section, and a delete confirmation (https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature).

The same help page lists interlinking availability for certain plan levels (https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature). This guide does not restate numeric plan details because the decision here is about domain ownership, not plan selection. The second supplied source is a broader platform overview that describes GEO positioning, AI visibility, content strategy, auditing apps, and authority building (https://www.scalenut.com/helpdoc/what-can-you-achieve-with-scalenut). Those are vendor descriptions of the platform, not independent measurements. Our workflow below is original editorial advice for deciding which domain to bind before Start.

Editorial Decision Checklist

The following checklist is our suggested process, not a description of the vendor API contract. It is designed to be reused for each report where Interlinking will be used.

Write a Domain Binding Note before opening Interlinking. Include the report name, the owning client domain, and the confirmation source. The confirmation source can be a client email, a signed brief, a project management record, or another authoritative owner statement.
Confirm the report belongs to the client domain named in the note. If the report was opened for a shared keyword or a generic test, pause until the owner is confirmed.
Check whether the report is a throwaway draft whose only purpose is to preview suggestions. If yes, connect any domain and accept that the report is disposable. This is a choice-changing exception, not the default.
If the report is not disposable, hold the report and confirm the owning client domain before connecting anything. Do not connect a domain merely because it is the most recently used or the first one offered.
When the owning domain is confirmed, connect it and click Start. Record the connection in the Domain Binding Note.
If the wrong domain was already connected, do not assume an in-report swap exists. The documented remedy is to open a different report and connect the correct domain there. Treat the original report as lost for that client unless the owning client is actually the one already connected.
If the domain must be removed from the account entirely, use the documented disconnect path through My Account and the Domains section. Do not confuse account-level removal with changing the domain on an existing report.
Before rebuilding a report, check whether the original report can be repurposed for the client whose domain is already connected. If the content is generic enough, reassigning the article may be cheaper than rebuilding.
After the interlinking pass, review suggestions and either add or dismiss them. The help page notes that when a single keyword appears in multiple places, you can use the arrow to select where to insert the link (https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature).
Exit Interlinking Mode only after the suggestions are fixed. Then update the Domain Binding Note to show the report is complete.

Hypothetically, an agency runs several client domains and one editor opens a Cruise Mode report for a shared keyword. The editor connects Client A’s domain, then learns the brief belongs to Client B. The page offers no swap, so the editor must open a fresh report for Client B and redo the interlinking pass. The Domain Binding Note would have prevented this by requiring the owning client domain before Start. This example is hypothetical and illustrates the cost of skipping the pre-connection check.

Limits

This guide is documentation-based research, not a live API test. It does not verify the behavior of the Scalenut interface beyond what the supplied help documentation states. It does not test whether any undocumented change, account setting, or future update alters the binding rule. It does not measure the quality, accuracy, or ranking effect of interlinking suggestions. It does not claim that connecting a domain guarantees indexing, citations, visibility, or conversions. It does not provide prices, numeric quotas, invented request schemas, or executable code. It does not imply undocumented automatic publishing, paid backlinks, account access, or integrations.

The absence of a detection signal is not proof of human authorship, and the presence of a vendor feature is not proof of measured performance. The vendor overview describes GEO positioning and AI visibility features (https://www.scalenut.com/helpdoc/what-can-you-achieve-with-scalenut), but those descriptions are marketing claims, not independent evidence. Our checklist is an editorial control, not a vendor guarantee. If the official documentation changes, the binding rule and disconnect path should be rechecked against the current help page (https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature).

Final Verdict

Hold the report and confirm the owning client domain before connecting anything. The documented binding rule makes a wrong connection permanent for that report, and the documented remedy is a different report. A one-line Domain Binding Note, written before Start, is cheaper than rebuilding an interlinking pass. If the report is a throwaway draft for previewing suggestions, connect any domain and accept that the report is disposable. Otherwise, treat domain confirmation as a gate, not a step. This article is documentation-based research, not a live API test, and it does not replace the official help documentation.

Official Sources

Scalenut help documentation, How to use the Interlinking feature: https://www.scalenut.com/helpdoc/how-to-use-the-interlinking-feature
Scalenut help documentation, What can you achieve with Scalenut: https://www.scalenut.com/helpdoc/what-can-you-achieve-with-scalenut
Related background: /scalenut-review/