plugins/aem/edge-delivery-services-content-ops/skills/internal-linking/SKILL.md
Analyze and improve the internal link structure of an AEM Edge Delivery Services site. Builds a link graph from the query index and page content, identifies orphan pages, hub pages, and content silos, and generates specific linking recommendations with suggested anchor text and placement. Use when improving site navigation, fixing orphan pages, strengthening topical authority, or auditing link equity distribution.
npx skillsauth add adobe/skills internal-linkingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Crawl an EDS site's query index and .plain.html page content to build a complete internal link graph. Analyze the graph to find orphan pages, weak connections, content silos, and linking opportunities, then produce specific recommendations with exact anchor text and placement.
This skill fetches external web pages for analysis. When fetching:
.plain.html variants).Do not use for external/backlink auditing, broken link checking, non-EDS sites, or unscoped sites with 500+ pages.
For recommendation format templates, troubleshooting, link classification details, and table schemas, see references/internal-linking-reference.md.
Before starting, create a checklist to track progress:
.plain.html for each page and extract all internal linksFetch https://<domain>/query-index.json. If paginated (has total and offset), fetch all pages using ?limit=500&offset=0. Build a map of all paths to their titles and descriptions — this is the universe of pages to analyze.
If the user specifies a path prefix (e.g., /blog/), filter to that prefix. If there are 200+ pages, recommend scoping and confirm before proceeding.
// Fetch and paginate the query index
async function fetchQueryIndex(domain) {
const pages = [];
let offset = 0;
const limit = 500;
let total = Infinity;
while (offset < total) {
const res = await fetch(`https://${domain}/query-index.json?limit=${limit}&offset=${offset}`);
const json = await res.json();
total = json.total ?? json.data.length;
pages.push(...json.data);
offset += limit;
if (!json.total) break; // not paginated
}
return pages; // each entry has: path, title, description, lastModified
}
For each page in the inventory, fetch <path>.plain.html and extract all <a> elements. Record the source page, target path (normalized — strip domain, query params, fragments), anchor text, and surrounding context.
Classify links as body contextual, block, or CTA (see reference file for definitions). Also fetch /nav.plain.html and /footer.plain.html once to tag structural links.
// Extract internal links from a page's .plain.html
async function extractLinks(domain, path) {
const res = await fetch(`https://${domain}${path}.plain.html`);
const html = await res.text();
const linkPattern = /<a\s+[^>]*href="([^"]*)"[^>]*>(.*?)<\/a>/gi;
const links = [];
let match;
while ((match = linkPattern.exec(html)) !== null) {
const href = new URL(match[1], `https://${domain}`);
if (href.hostname === domain) {
links.push({
source: path,
target: href.pathname.replace(/\/$/, ''),
anchorText: match[2].replace(/<[^>]*>/g, '').trim(),
});
}
}
return links;
}
Batch fetches in groups of 10-20 for large sites. Report progress as you go.
Construct a directed graph: nodes = pages from the query index, edges = body links between them.
For each page, compute inbound and outbound body link counts (exclude nav/footer from primary counts). Present the top 10 most-linked and bottom 10 least-linked pages in a table (see reference file for table format).
List all pages with zero inbound body links. For each, note whether it appears in nav or footer, its outbound link count, and its title/description. Pages with zero inbound links of any kind are critical priority.
Hub pages have outbound body links exceeding 2x the site average. List them with their role (pillar / index / landing).
Content silos are clusters that link heavily internally but rarely cross-link to other clusters. For each silo, report pages, internal link count, cross-silo link count, and the silo ratio (internal / total). A ratio above 0.8 suggests isolation. Recommend specific cross-silo links with anchor text.
Compute overall link health metrics:
Group pages by path prefix or topical similarity. For each cluster, check whether pages link to each other, whether a pillar page exists, and whether obvious connections are missing.
For each orphan and under-linked page, provide a specific recommendation: which page should link to it, where in that page's content the link should go, the exact suggested sentence with anchor text, and a rationale. Follow the recommendation format in the reference file.
Provide at least one recommendation per orphan, and at least one per under-linked page (1-2 inbound links). Include cross-silo bridge links where topics naturally overlap. Always use descriptive anchor text — never "click here" or "read more."
Compile findings into a structured report:
Summary — Total pages, total internal body links, average inbound per page, orphan count and percentage, silos detected.
Sections — Orphan pages, hub pages, content silos, link distribution health (rated Healthy / Needs Improvement / Poor), and all recommendations prioritized as:
tools
Use the run-workflow MCP to discover, compose, execute, publish, and save Adobe Firefly workflows. TRIGGER when: user asks what actions are available, what the MCP can do, how to process images/video/3D via workflow, wants to build/run/save/publish a workflow, OR pastes any workflow/batch/execution ID. BARE ID (UUID/workflowId/batchId) = INSPECT ONLY — call inspect_run, NEVER run_workflow_submit. ALWAYS call list_actions first for capability/discovery questions. DO NOT TRIGGER for direct Firefly API calls without MCP (use firefly-api-specs).
tools
Run predefined featured workflows via run-workflow MCP. TRIGGER when user names a featured workflow (retargeting, banners at scale, localization, packaging, banner advertising, etc.) or asks to run a known marketing/production workflow. Requires run-workflow MCP. ALWAYS call get_featured_workflow before compose_workflow. DO NOT TRIGGER for custom one-off workflows with no named template — use run-workflow skill.
tools
Migrate an Adobe Commerce App Builder project from the Integration Starter Kit or Checkout Starter Kit to the new App Management approach. Run from the root of the App Builder project to be migrated. Pass --auto to skip confirmation prompts (suitable for CI or batch use) — auto mode prints a summary of all Q&A questions answered with their defaults. Pass --doc-scan-only to scan README.md and env.dist for outdated content without modifying any files. Use when the user wants to migrate an App Builder project from the Integration Starter Kit or Checkout Starter Kit to the App Management approach, or mentions upgrading their Adobe Commerce extension architecture.
development
Add or modify webhook interceptors in an Adobe Commerce app. Use when the user wants to intercept Commerce operations to validate input, append data, or modify behavior — before or after execution. Requires a base app initialized with commerce-app-init.