Auto Links for SEO

English

Français

English

Français

Appearance

Auto Links for SEOFrom focus keywords to internal links

A dense WordPress SEO site for two plugins that work better together than alone.

Download the plugins
See pricing
Understand the pipeline
Auto Links for SEO pipeline

Two plugins, one coherent story

Auto Focus Keyword creates the keyword layer. Automatic Internal Links turns that layer into site-wide internal linking opportunities.

Honest free vs Pro boundaries

The site explains what is manual in free, what is continuous in Pro, and where product or custom post type support begins.

Better than a directory listing

WordPress.org remains a distribution point. This site becomes the canonical place for strategy, compatibility, troubleshooting, and conversion.

Why this site exists ​

These two plugins already behave like a pipeline. Auto Focus Keyword for SEO fills missing focus keyword fields from page titles. Automatic Internal Links for SEO can then use those focus keywords as anchor signals to create internal links across the site.

That relationship is too important to leave trapped inside two separate plugin directory pages. This site gives the pair a canonical product surface, a documentation system, a pricing surface, and a machine-readable layer.

The pipeline in two steps ​

Step 1 — Assign focus keywords at scale ​

Auto Focus Keyword scans your site, finds pages without focus keywords, and populates them from page titles. Works with Yoast SEO, Rank Math, and All in One SEO.

Auto Focus Keyword interface

Automatic Internal Links scans your content, detects focus keywords, and creates internal links automatically — using those keywords as anchor text.

Automatic Internal Links sync in progress

Product truths we keep explicit ​

  • Auto Focus Keyword is useful because it is fast, but page title does not equal ideal keyword in every editorial case.
  • Automatic Internal Links is strongest when described honestly: manual SYNC in free, continuous AUTO LINKS in Pro.
  • The site treats compatibility per plugin, not as one flattened promise.

Start in the right order ​

{ message }

{ primaryLabel }{ secondaryLabel }