If your blog has hundreds of posts, internal linking is probably the cheapest SEO fix you’re not making. Codex can audit every article, find the orphan pages nobody links to, write a linking plan, implement it across the codebase, and then re-audit to confirm it worked. In this guide I’ll walk through the exact workflow I used on my own SaaS blog, plus the research I fed it and how much weight that research deserves.
Prefer to watch? See the full walkthrough on YouTube. I run the audit and apply the linking plan on screen.
Want the written version? Read the free AI Automation Station guide: Internal Link Audit with Codex: A Reviewed SEO Workflow.
Why internal linking deserves your attention
Internal links do three jobs. They help search engines find and crawl your pages, they tell search engines which pages matter and how they relate, and they keep readers moving to the next useful article instead of leaving. Google’s own link best practices say that every page you care about should be linked from at least one other page on your site, and that anchor text should describe the page it points to.
The trouble is scale. Linking a 20-post blog by hand is easy. A blog with several hundred AI-assisted posts is where links get skipped, new posts never get linked from older ones, and orphan pages pile up. Mine had exactly that problem, and I’d been fighting pages that Google crawled but never indexed.
The research I fed Codex, and how to treat it
The trigger for this workflow was a long forum post on Black Hat World from a content-site owner who described years of internal linking tests across their portfolio. Their main takeaways, in their own words, were roughly:
- Aim for 10 or more contextual internal links per article. They saw no ranking drop at 20 or more.
- About five internal links looked like the minimum to avoid indexing problems.
- Links placed higher on the page seemed to carry more weight than links near the bottom.
- Links that people actually click seemed to matter, and the poster tracked clicks per link.
Treat this as one practitioner’s anecdotal experience, not proof. Codex flagged the same thing when it read the post: the core rule is useful but anecdotal. Google’s documentation doesn’t name a magic number of links. What the findings give you is a sensible, testable house rule: link generously, link early, and link to pages people will actually want to click.
Step 1: Install an internal linking skill
Codex works better when it has a skill that already knows the job. I used the Internal Linking Optimizer skill from the open-source SEO and GEO skills collection, which is listed on skills.sh. You can install it with one command:
npx skills add aaron-he-zhu/seo-geo-claude-skills --skill internal-linking-optimizer
The same skill works in Claude Code. There are other internal linking skills on skills.sh as well; this is simply the one I prefer.
Step 2: Have Codex audit your current links
I gave Codex the forum post and asked it to create an internal linking plan based on the research in it. It picked up the skill, mapped the principles onto my blog’s structure, and then ran an audit over every article to count the links that were already there.
Ask it to report on:
- Average contextual body links per article, counted separately from navigation and footer links.
- How many articles meet your target, say 10 or more body links.
- Orphan articles with zero inbound links from other posts.
- Weakly linked articles with only one or two inbound links.
My results were humbling. I thought I’d already done a good job on internal linking, but most articles were far below the target and hundreds had no inbound blog links at all. That’s the value of an audit: it replaces your gut feeling with counts.
Step 3: Turn the audit into a linking plan
The plan Codex produced is a good template for any content site:
- Mix your link targets. Each article gets at least six links to closely related posts, at least two to relevant guides, tools, features or comparison pages, and at least two to product or action pages.
- Put the first contextual link early, before the first major section where it reads naturally, without forcing links into the introduction.
- Repair inbound authority first. Link from your strongest existing articles to your highest-priority orphans, aiming for three to five distinct inbound links each.
- Build hub-and-spoke clusters. Each hub links out to 8 to 12 relevant articles and gets links back from them.
- Measure clicks, not just counts. A link nobody clicks is doing less work than you think.
It also said to pick targets by topic similarity, not by category alone. That matters: two posts in the same category aren’t always relevant to each other, while a post in another category can be the perfect next read.
Step 4: Write an implementation plan, then run it
A report isn’t a fix. I asked Codex to turn the report into a phased implementation plan saved in the repo’s docs folder. It came back with four phases: repair high-value authority, bring articles up to the body-link minimum, complete orphan and cluster coverage, and handle navigation clicks and maintenance.
Then I asked it to implement the plan. Pick a model that matches the job: bulk link edits across a few hundred files don’t need your most expensive model, and I was low on credits, so I used a mid-tier one. The full run took about 21 minutes on my blog.

Review before you deploy
Before pushing, spot-check a handful of articles. Read the new links in context. Are the anchors descriptive? Do the links point to the right pages? Does the paragraph still read naturally? Then deploy as usual. My site is on Vercel, so that meant pushing the updated codebase.
Step 5: Re-audit to confirm it worked
Once it was live, I had Codex run the same audit again with the same skill. It took about a minute and a half. The re-audit reported every public English article with 10 to 15 unique internal body links, valid targets and no orphans, plus a short list of under-linked pages that I told it to fix next.
Make this a habit. Every batch of new posts creates new orphans, so put the audit on a monthly checklist, or run it whenever you publish a batch.
Common mistakes to avoid
- Counting navigation links. Menus and footers repeat on every page. Count contextual body links separately.
- Forcing links into intros. An early link is good. A clumsy link in your first sentence is not.
- Linking by category only. Pick targets by topic similarity.
- Using vague anchors. “Click here” tells readers and search engines nothing. Describe the page you’re linking to.
- Treating forum findings as rules. Use them as a starting hypothesis, then watch your own Search Console data.
- Skipping the re-audit. Confirm the plan was implemented, then fix what’s left.
Want help building this for your own business?
The video shows what’s possible. Inside AI Income Lab, the paid community from AI Automation Station, you get step-by-step courses, reusable templates, and a place to ask questions while you build. The courses walk you through builds like this one step by step. Over 2,900 members are already building with it, from $29 a month, and you can cancel anytime.
FAQ
How many internal links should a blog post have?
Google doesn’t publish a number. The forum research I used suggested 10 or more contextual links per article, and that worked as a practical target on my blog. Relevance matters more than hitting an exact count.
Can Claude Code do this instead of Codex?
Yes. The Internal Linking Optimizer skill works in Claude Code too, and the audit, plan, implement and re-audit steps are the same.
Will internal links fix pages that aren’t being indexed?
They can help, because orphan pages are harder for search engines to discover and judge. But indexing depends on many things, including content quality and duplication, so treat internal linking as one fix, not a guaranteed cure.
Does this work on WordPress, or only on a code-based site?
The steps are the same. On a code-based site like mine, Codex edits the content files directly. On WordPress, you’d export the content or work through the WordPress API, and review the changes before you update the posts.
Conclusion
Internal linking at scale used to mean weeks of manual work. With Codex and a good skill, you can audit every post, plan the links, implement them and confirm the result in an afternoon. Start by running the audit on your own blog, because the numbers will tell you how much work there is, then follow the plan in phases. Watch the video above to see the whole workflow on screen.
If you’d rather not figure this out alone, AI Automation Station has a paid community for it: AI Income Lab. It’s where the courses, templates and help that go with these builds live, with 2,900+ members, from $29 a month, cancel anytime.
Leave a Reply