Audit links between pages on a website to find important pages with few incoming links. Suggest relevant connections from related content and clearer link text that describes the destination page.
Use when auditing a site's internal link structure, identifying pages that need more incoming links, generating contextual linking opportunities between related content, or reviewing a CMS template's internal linking patterns.
This skill examines how pages on a website connect and finds important pages with too few incoming links. Using site crawl data, it maps link relationships and checks how many distinct pages link to each page. It identifies orphan pages with no incoming links and pages with few links in body content, then suggests natural places to add links from related articles. It also reviews whether link text describes the destination.
Use it to review paths to key product pages or articles and find linking opportunities between related content. It also helps you inspect link placement in CMS templates and check whether central guide pages and supporting articles link to one another.
Link analysis uses site crawl data. When reviewing pages listed in the sitemap, it accounts for search exclusions through robots or noindex. The review checks for relevant links in body content as well as navigation and footers.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Internal links are how PageRank flows through your site. A key page with few internal links receives less PageRank signal, ranking lower than its content quality would otherwise allow. Googlebot also discovers pages through internal links — a page with zero incoming links is likely an orphan page.
Using a site crawl, build a map of internal links. For each important page (key landing pages, top blog posts, product pages): (1) Count the number of unique internal pages linking to it. (2) Check if the anchor text of those links includes relevant keywords for the target page. (3) Identify pages with 0–2 incoming internal links (likely orphans or under-linked). (4) Verify links are in body content, not only in global navigation or footer.
PageRank, Google's foundational ranking algorithm, flows from page to page through internal links. A page with many high-quality internal links pointing to it receives more PageRank signal and ranks more competitively. Anchor text of internal links also provides keyword context signals to Google about the target page's topic.
Build an internal link graph from crawl data. Compute in-degree (number of pages linking in) for each page. Flag pages with in-degree < 2 that are in the sitemap and not excluded by robots/noindex. Check anchor text of internal links for generic text ('here', 'click', 'read more') that could be replaced with descriptive keyword-rich text.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/internal-links
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.