Our Story • Free & Open Source WordPress Plugin

Why We Built LinkCortex

Selvakumar Duraipandian and Mayakrishnan (Maya) worked together at Kissflow for around eight years. Maya was Selva’s manager, and one of the people who taught Selva the most about WordPress.

Years later, on a casual catch-up phone call, we realized internal linking was a problem both of us had seen many times—and that it should be solved properly as a WordPress plugin. The next morning, we started building it together.

Mayakrishnan and Selvakumar Duraipandian, co-creators of LinkCortex, catching up on the Chennai Metro
Maya (left) and Selva (right)—from eight years building at Kissflow to launching LinkCortex. Chennai Metro
The Shared Pain

The Problem We Kept Seeing

Whether you run an in-house content team, manage SEO for agency clients, or write for a large personal blog archive, internal linking in WordPress usually breaks down into the same three headaches:

  • The Spreadsheet Trap & Orphan Pages: As sites grow past 50 or 100 articles, tracking link equity in memory or sheets becomes impossible. Newly published guides quickly become isolated orphan pages with zero inbound internal links . Content teams spend hours every month manually cross-referencing URLs in Google Sheets just to build structured topic clusters in WordPress .
  • Per-Site Subscriptions for Basic Plumbing: Many commercial linking plugins charge recurring annual subscriptions for every single domain ( see our LinkCortex vs. Link Whisper comparison ). For freelancers and agencies managing client portfolios, license fees multiply quickly for what should be fundamental publishing tooling.
  • Plugins That Corrupt Gutenberg Blocks: Legacy link plugins frequently rely on crude regular expressions that cut straight through WordPress block comments (<!-- wp:paragraph -->). A single bad string replacement can break post markup, corrupt layouts, and make content uneditable in the block editor.
  • The Exact Friction We Faced: [CONFIRM: One specific real-world internal-linking pain Selva and Maya both encountered, e.g. a specific site audit where dozens of cornerstone posts were orphaned or a plugin broke layout formatting]
The Build & WordPress.org Review

So We Started Building the Next Day

The morning after that phone call, we began coding LinkCortex. We wanted an internal-linking assistant that worked right where you write: suggesting contextual 2-to-5 word anchors, keeping drafts secure, and letting you inspect and approve every change before it goes live.

Before LinkCortex went live in the official WordPress.org plugin directory, it went through three detailed review rounds with the WordPress.org plugin review team. That review was not an endorsement or certification from WordPress—WordPress.org does not certify plugins. But those three rounds were invaluable: they made the plugin fundamentally safer for live production websites by tightening [CONFIRM: One specific thing the three review rounds improved, e.g. strict nonce verification and output escaping / secure API credential handling / WP_HTML_Tag_Processor edge-case parsing].

[CONFIRM: One real result or number, e.g. "Today, LinkCortex helps site owners map internal links in under 60 seconds without leaving WordPress." — or leave blank to omit]

Our Commitments

What We Believe

Three simple principles behind every line of code in LinkCortex.

public

1. Free (No Per-Site Subscriptions)

Essential SEO infrastructure should not be gated behind recurring paywalls or artificial domain limits. LinkCortex is 100% free and open-source under GPLv2+. Use it on your personal blog or fifty client sites without paying for additional licenses.

shield_check

2. Safe (Never Breaks Your Posts)

We never use brittle regex to alter post content. LinkCortex uses WordPress Core's official WP_HTML_Tag_Processor to insert links around text nodes without touching Gutenberg block markup. Every change is tracked with one-click JSON rollback.

key

3. Yours (You Own Your Keys & Data)

Your Gemini, OpenAI, or Anthropic API keys stay strictly on your server or in wp-config.php. Candidate drafts are matched locally in your database first—zero central intermediary servers snooping on your unpublished content.

The Co-Creators

Who We Are

Two developers and publishers who built the plugin they needed for their own sites.

person

Selvakumar Duraipandian

Co-creator & Developer

Worked alongside Maya at Kissflow for around eight years. A WordPress theme and plugin developer focused on clean WordPress Core APIs, editor performance, and building open tools that give site owners full data ownership.

person

Mayakrishnan (Maya)

Co-creator & Product Strategist

Selva’s former manager and mentor during their eight years together at Kissflow, where he taught Selva much of what he knows about WordPress. Co-creator of LinkCortex focused on content architecture, publishing workflows, and product strategy.

For Developers & Technical SEOs

How It Works Under the Hood

A quick plain-language summary of our core architectural decisions.

1. Local BM25 Shortlisting

Term-frequency matching runs directly in your MySQL database. Potential linking candidates are shortlisted locally before any AI call, keeping API token costs near zero and unpublished drafts confidential.

2. WP_HTML_Tag_Processor

Introduced in WordPress 6.2, this official streaming parser tokenizes post HTML safely. It inserts anchor tags into text nodes without corrupting Gutenberg block comments or triggering regex memory leaks.

3. One-Click JSON Rollback

Every inserted link writes a localized rollback snapshot into post meta. If you ever change your mind or want to undo a suggestion, revert the post in one click without touching revision history.

100% Free & Open Source (GPLv2+)

Inspect the code on GitHub or install the reviewed version from the WordPress plugin repository.

Ready to Build Topic Clusters Without the Headache?

No subscription tiers. No per-site licensing. 100% free and open-source under GPLv2+.