Introduction

This guide answers a practical editorial question: after connecting a domain in Scalenut Link Manager, how do you decide whether the link-status data is current enough to approve and push internal links? The official help documentation states that pages are never refreshed automatically; a manual click on the refresh button is required to update status. It also says that seeing Opportunity or Action Required is the cue to click the recommended action and begin reviewing suggestions. Those two documented mechanics are separate, and the documentation does not explicitly tie them together into an approval-time data-currency rule. This article is documentation-based research, not a live API test. The affiliate and research disclosure applies once here: This article may contain affiliate links. For broader background on the platform, see /scalenut-review/.

The decision matters because approving and pushing links writes changes to the live site. If the status column is stale, an editor may approve suggestions against link health that no longer reflects the site. The official page does not promise any automatic refresh, and it does not guarantee that status indicators remain current between manual refreshes. Our suggested process adds a refresh precondition before approval, while keeping the vendor’s documented steps intact. Vendor marketing claims about factual accuracy, rankings, AI citations or visibility are not measured evidence, Google ranking factors or indexing guarantees.

Documented Workflow

According to the Link Manager overview (https://www.scalenut.com/helpdoc/link-manager-an-overview), the documented flow is: connect a domain through Google Search Console, select pages, wait for analysis, connect the domain by adding a script, verify the connection, then work from the dashboard. To push changes, the page says to select a page URL based on link status; if you see Opportunity or Action Required, click the recommended action. The tool then identifies internal linking opportunities, categorized as Outbound or Inbound, each with Target URL, Anchor Text Content and Suggestions. After reviewing context and anchor text, you click Approve. You can see the number of approved suggestions, click Review changes, and on the final review screen edit or delete suggestions. Then you click Push Changes Live. The same page includes a note that you must manually click the refresh button to trigger a refresh and that pages are not automatically refreshed.

The second official source, What Can You Achieve with Scalenut (https://www.scalenut.com/helpdoc/what-can-you-achieve-with-scalenut), describes Link Manager as a tool that automates internal linking structure and helps spread link equity so search bots and AI models can understand content hierarchy. It also lists AI Visibility, Action Center, Content Optimizer, Traffic Analyzer, Content Audit, OnPage Pro, Social UpReach, Backlinks Marketplace, and Detect and Humanize as platform capabilities. Those descriptions are vendor claims about what the platform is intended to do, not measured evidence of ranking, citation or visibility outcomes. The page also mentions purchasing backlinks; this guide does not recommend or imply paid backlink tactics, and it does not claim any account access or integration beyond what the documentation describes.

Our original workflow separates the vendor’s contract from our editorial decision. The vendor contract, as documented, is: manual refresh only, and Opportunity or Action Required is the status cue for starting the approve-and-push flow. Our editorial decision is: treat a manual refresh as a precondition of approval unless the report was refreshed earlier in the same working session and no site changes occurred since. This is our suggested process, not an undocumented API behavior and not a guarantee about how the tool behaves beyond the documentation.

Editorial Decision Checklist

Use this numbered checklist before approving and pushing internal links. It is our original operational aid, not a vendor-provided procedure.

Confirm the report name and the page URL you intend to work on, so the approval is tied to a specific review context.
Record the last refresh date and time shown or known for that report. If you cannot determine when it was last refreshed, do not treat the status column as current.
If the report was refreshed earlier in the same working session and no site changes occurred since, you may proceed to review the status column without refreshing again. This is our choice-changing exception.
If the report was last refreshed in a prior session, or if any site changes occurred since the last refresh, click the manual refresh button before reviewing status.
After refreshing, re-read the status column. Look for Opportunity or Action Required as the documented cue that a recommended action is available.
If the status no longer shows Opportunity or Action Required, do not approve suggestions from the prior status. Re-evaluate the page or close the report.
If the status still shows Opportunity or Action Required, open the recommended action and review each suggestion’s Target URL, Anchor Text Content and Suggestions.
Approve only suggestions whose context and anchor text align with the page’s purpose and user journey. The documentation says Approve adds the internal link to your content structure.
Use Review changes to verify the approved set. On the final review screen, edit or delete suggestions that do not align.
Before clicking Push Changes Live, confirm the refresh was done in this session or that the exception in item 3 applies. If neither is true, return to item 4.
After pushing, record the refresh-before-approve note: report name, last refresh date, and whether refresh was clicked before approving.

Hypothetical worked example: an editor opens a Link Manager report that was last refreshed two weeks ago. The status column still shows Opportunity on a page whose links were since fixed elsewhere. The editor follows item 4, clicks refresh, and re-reads the status column. The status now reflects the changed link health, and the editor avoids approving against outdated data. This example is hypothetical and is used only to illustrate the decision; it is not a live API test and does not describe a measured outcome.

The reusable deliverable is a one-line Refresh-Before-Approve Note: report name, last refresh date, and whether refresh was clicked before approving. This note makes the approval decision auditable without implying any automatic publishing or integration.

Limits

This guide is documentation-based research, not a live API test. It does not measure refresh latency, status accuracy, or approval outcomes. The official page does not state how long status remains valid, how often pages change, or whether refresh updates every status field. It also does not link the manual refresh note to the Opportunity cue, so the question of whether existing status data is trustworthy at approval time is unresolved by the documentation. Our checklist resolves it editorially by making refresh a precondition, but that is our process, not a vendor guarantee.

The sources also contain vendor marketing language about AI visibility, rankings, citations and content discoverability. Those claims are not measured evidence, Google ranking factors or indexing guarantees. The documentation mentions connecting a domain through Google Search Console and adding a script; this guide does not claim any other account access, integration or automatic publishing. It does not provide prices, quotas, trial details, or invented request schemas. It does not claim that absence of a detection signal proves human authorship. The Backlinks Marketplace is described in the official source, but this guide does not recommend paid backlinks or imply that buying backlinks is a required or effective tactic.

Final Verdict

Click refresh first, then re-review the status column before approving any suggestion, unless the report was refreshed earlier in the same working session and no site changes occurred since. The documented manual-refresh note means a stale status column can misrepresent current link health; refreshing first costs one click and prevents approving against outdated data. This recommendation is our editorial decision, not a documented vendor requirement and not a guarantee about tool behavior.

The practical value is the checklist and the Refresh-Before-Approve Note. They turn a vague question about data currency into a repeatable approval gate. If you want a broader platform overview before applying this workflow, see /scalenut-review/. Keep the vendor contract and your editorial policy separate: the vendor documents manual refresh and the Opportunity cue; you decide when those are sufficient for approval.

Official Sources

https://www.scalenut.com/helpdoc/link-manager-an-overview
https://www.scalenut.com/helpdoc/what-can-you-achieve-with-scalenut