InLinks

# InLinks review

InLinks approaches internal linking through entities and topics rather than matching keywords alone. It crawls pages, builds a knowledge graph, lets an editor associate important topics with target pages, then proposes or injects internal links and structured data. The same entity layer supports keyword research, content briefs and content planning.

This makes InLinks broader than a WordPress-only link suggestion tool. It also means the buyer is delegating semantic interpretation and potentially rendered markup to an external system. The purchase case depends on precision, review controls and safe rollback—not the number of links it can create.

Distinctive strength

InLinks connects four jobs around one entity model: topical analysis, content briefs, internal linking and About/Mentions-style schema. A well-maintained topic-to-page map can reduce arbitrary exact-match anchors and reveal when several pages compete for the same concept.

The product documents human control: editors associate target topics, can review generated links and can modify anchor text. That is materially better than an opaque “auto-link everything” switch.

Where it stops being an advantage

Entity extraction can be confidently wrong. A product name may be interpreted as a generic topic, a multi-intent page may be assigned to the wrong concept, or a generated anchor may read unnaturally. At scale, small precision errors become a sitewide graph problem.

Deployment also matters. Historic official material describes JavaScript injection for links and schema. A buyer should confirm whether links are present in server-rendered HTML, visible to target crawlers, stable under caching and removable without leaving broken markup.

How much does InLinks cost?

Current product pages say plans start at $49/month and describe access to the suite. A public October 2023 pricing document maps $49 to 100 pages or 20 audits and scales capacity in $49 increments. Because that document is old, it is evidence of the meter—not proof of current checkout limits.

The useful denominator is pages under management, not the number of suggestions. Capture current included pages, audits, projects, users, overage behaviour and annual terms before purchase. A 5,000-page site should not extrapolate from a 100-page historical tier.

Are entity-based links better than keyword links?

They can be better when the entity map is correct. Topics provide context that raw keyword matching lacks and can encourage varied, meaningful anchors. But no taxonomy automatically knows the commercial role of every page.

Test precision. Take 20 representative pages: products, comparisons, guides, categories and ambiguous names. Have an editor create a gold-standard topic and destination map before importing it. Then measure accepted suggestions, wrong destination, awkward anchor, duplicate intent and missed opportunity separately.

Should InLinks generate schema automatically?

Only when the schema accurately represents visible page content and the page is eligible for that type. About/Mentions relationships can express entity context, but they should not become a decorative graph detached from the text. FAQ schema should not be generated merely because headings contain questions; current search-engine eligibility and content rules are stricter than many historic examples.

Validate the final JSON-LD with both syntax and factual review. Omit ambiguous relationships rather than forcing them.

Does it replace Link Whisper?

Not exactly. InLinks is suited to cross-CMS entity strategy, schema and content planning. Link Whisper is a more direct WordPress/Shopify-oriented internal-link maintenance product with orphan reports, broken-link tooling and optional click tracking. The right choice depends on whether the buyer needs a semantic content graph or operational link maintenance.

The orphan-recall rate decides the purchase

Measure suggestion precision before scale:

`accepted-link precision = useful accepted suggestions ÷ all reviewed suggestions`

If an editor reviews 100 suggestions and accepts 72, then 28% of the queue created correction or rejection work. Break those 28 down into wrong destination, awkward anchor, duplicated intent and link that adds no reader value. This is more informative than the number of links generated.

Also measure orphan recall against an independent crawl. A system can have high suggestion precision while missing important pages entirely. Compare the set of pages with zero relevant incoming links, not merely pages with zero links of any kind.

What should happen before sitewide automation?

Require a staging proof with explicit acceptance thresholds. Generated markup should survive server rendering, client hydration and caching; the same canonical URL should remain visible to users and crawlers. Disable or remove InLinks and prove that the original HTML, schema and navigation return without orphan scripts or stale relationships.

For a multilingual site, test entity extraction separately per supported language. Eight advertised languages do not establish equal topic precision across all niches. A regulated or technical vocabulary deserves its own gold-standard set.

Audit the graph, not just the suggestions

1. Select 20 pages across five page types.
2. Build a human topic-to-destination gold standard.
3. Import the pages and compare extracted entities.
4. Score every suggested destination and anchor.
5. Reject links that do not help a reader continue research.
6. Inspect server HTML, hydrated HTML and crawler-visible output.
7. Validate generated schema against visible content.
8. Test removal and rollback on a staging site.
9. Record page/audit consumption and current checkout limits.
10. Expand only after precision meets the editorial threshold.

The 20-page proof before automation

Use the free/small allowance as a precision test, not as a race to create links. The conversion-worthy outcome is a cleaner research path with fewer orphan pages and no misleading anchors. If the editor rejects a large share of suggestions, the entity layer is adding review cost rather than value.

Continue through the AI SEO directory, compare InLinks vs Link Whisper, and use an independent Screaming Frog crawl to verify orphan recall before automating a sitewide graph.

Our InLinks verdict

InLinks merits a place in the catalog because it represents entity SEO and graph-level internal linking, not another generic content score. Its strongest purchase case is a team prepared to curate topics and review markup. Its weakest is a buyer seeking one-click links at scale without a gold standard, rendering test or rollback plan.

Official sources

• InLinks entity keyword research and suite pricing ↗
• InLinks product demo ↗
• InLinks internal-link automation method ↗
• InLinks October 2023 pricing schedule ↗
• InLinks support ↗

Sources checked 2026-08-28. Verify current checkout capacity and rendering behaviour before procurement.