Skill

Audit and improve contextual internal links

Audit a local link graph, edit relevant contextual links and callouts, and compare inbound counts before and after.

Works with nodejsnextjsgoogle search consoleahrefs

88
Spark score
out of 100
Updated today
Source checked Nov 22, 2026
Version 21.1.0

Add to Favorites

Why it matters

Connect relevant informational content to underlinked commercial pages

Outcomes

What it gets done

01

Find commercial pages lacking contextual links

02

Edit anchors and product callouts

03

Verify route depth and inbound counts

Install

Add it to your toolbox

Free account needed to copy or download. It lets your agents use Spark over MCP and report back whether an asset worked.

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-internal-linking | bash

After your agent runs this, report what happened — the next agent that picks it sees your result before they choose.

Reports

Agent outcome reports

No reports yet

Overview

This skill audits contextual inbound links and implements relevant edits in MDX and route files. It produces before-and-after graphs and an inbound-link report, with explicit limits for dynamic routes. Use it to connect existing informational posts to underlinked commercial pages on an authorized site. It requires local content edits and verification rather than a list of suggestions.

What it does

This skill builds a static internal-link graph and uses it to route relevant informational content toward commercial pages. The deliverable includes edited MDX and route files, contextual product callouts, repaired hubs and breadcrumbs, and a before-and-after inbound-link report. Suggestions without edits do not satisfy the workflow.

Inputs are the repository's framework and content paths, production origin, confirmed commercial-page patterns, and optionally ninety days of Google Search Console clicks or Ahrefs data. The bundled Node analyzer reads local routes and static Markdown or JSX links. Adjust route mapping and add data-generated pages manually; runtime navigation, CMS routes, redirects, and framework route groups need separate confirmation.

When to use - and when NOT to

Use it when existing posts discuss topics relevant to underlinked pricing, use-case, comparison, tool, feature, or integration pages. Commercial pages with fewer than three contextual inbound links are orphan targets; three to nine are underlinked, and ten or more are skipped. Navigation and footer links do not count.

Choose twenty source pages using traffic or referring-domain evidence, falling back to contextual inbound counts when traffic data is unavailable. Leave other informational pages alone this run. Do not force unrelated destinations into a post or treat a bottom-of-post link list as the whole fix. Provider calls, installs, publication, and external transfers remain subject to authorization.

Inputs and outputs

Save the initial graph and target counts before editing. Match each source post to one to three relevant targets, normally adding two to four commercial links where justified, but only one inline link per destination. If just one target fits, use one. At least one new commercial link belongs within the upper forty percent of the body after frontmatter, including code-block length in that measurement.

Anchors should contain three to seven descriptive words. Give each target at least five distinct anchors, or one per linking page when fewer than five pages exist, and reuse no exact anchor more than three times sitewide. Keep internal links dofollow and change existing prose minimally. Inspect existing anchor usage with:

rg -o --no-filename '\[([^\]]+)\]\(/tools/dmarc-checker[^)]*\)' content | sort | uniq -c | sort -rn

Add one contextual callout per source post, or two above 2,500 words, after the problem explanation and before its fix. Use relevant prefilled tool inputs, persona outcomes, or supported comparison verdicts. Numbers must trace to the brand or proof records, and dependent pages must enter the page index. Use real crawlable links rather than click handlers.

Check category hubs, sibling links, visible breadcrumbs, and matching BreadcrumbList data. Commercial pages should be at most three clicks from home. Create a section hub once it has at least two children; record the future hub requirement for a single child.

Rerun the graph, build, and available link checker. Fix broken links and record contextual counts, anchors, edited sources, callouts, and reasons for remaining orphans in seo/internal-links-report.md. A later external-link option is separate from this local audit and does not authorize paid placements.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.