Web & SEO Autolinker – AI Internal Linking
AI-powered internal linking. OpenAI embeddings find the targets, GPT picks natural anchors, and the links are written into your posts.
Solid choice
Web & SEO Autolinker is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 days ago, and scores 64/100 on our health check.
- Actively developed — last update 4 days ago
- Tested with the latest WordPress (7.1)
- Small user base (<10 active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Web & SEO Autolinker stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| AI | >100 |
| internal linking | >100 |
| links | >100 |
| openai | >100 |
| seo | >100 |
About Web & SEO Autolinker
From the official readme · v0.3.3Description
Autolinker builds internal links between the posts you already have. It reads
each post, finds the most semantically related pages on your site, and asks a
language model to choose an anchor phrase that already exists, word for word, in
the source text. The link is then written into the post content and kept in a
registry so it can be tracked, repaired, or removed later.
There is no keyword list to maintain. Relevance comes from meaning, not from
matching strings.
How it works
- Embedding. Each post is converted to a vector with an OpenAI embeddings
model, stored locally, and refreshed only when the content changes. - Candidate search. Cosine similarity ranks every possible target above a
configurable threshold. - Filtering. A first model pass drops candidates that are topically close but
editorially wrong. - Anchor selection. A second model pass proposes an anchor phrase. The plugin
verifies the phrase appears verbatim in the source; if it does not, the link is
rejected rather than forced. - Writing. The link is inserted with a marker attribute so the plugin can find
its own links again without guessing.
Every rejection is written to a journal with a reason, so an empty result is never
indistinguishable from a broken plugin.
IMPORTANT: this plugin relies on a third-party service
Autolinker does not work without an OpenAI API key that you supply. The plugin
sends data to the OpenAI API (api.openai.com), a third-party service that is not
affiliated with this plugin or with WordPress.org.
What is sent: the text content of the posts you choose to process, the titles
and excerpts of candidate link targets, and the prompts the plugin builds around
them. Your API key is stored encrypted in your WordPress database and is sent to
OpenAI to authenticate each request.
When it is sent: only when a post is processed: automatically when you publish
it, or when you trigger a scan. Processing on publish is on by default; you can
switch it off in Settings (“Full auto on publish”), and then nothing is sent until
you start a scan yourself. Your post content is never
sent to OpenAI at any other time.
What is not sent: no data is sent to the plugin author, and no post content
leaves your site other than to OpenAI, as described above.
One clarification about link health. The plugin also checks whether the links in
your content still resolve. That check runs on a schedule and makes ordinary HTTP
requests to the URLs already present in your posts, and to their robots.txt, which it
honors. It sends none of your content and involves no third-party service: it only
visits the addresses you already link to. Those requests identify themselves with a
user agent naming the plugin and your site URL, so the hosts you link to can see that
the request came from your site.
Using this plugin means your content is processed under OpenAI’s terms. Please read
them before installing:
- OpenAI Terms of Use: https://openai.com/policies/terms-of-use
- OpenAI Privacy Policy: https://openai.com/policies/privacy-policy
- OpenAI API data usage policies: https://openai.com/policies/api-data-usage-policies
You pay OpenAI directly for the tokens the plugin consumes. See the FAQ for cost
control.
Features
- Semantic candidate search with a configurable similarity threshold
- Verbatim anchor validation, so anchors are never invented
- A per-post link budget and anchor length bounds (default 2 to 6 words)
- Silo mode, to keep links inside the same category
- Per-post exclusions: exclude entirely, as a source only, or as a target only
- Link health: periodic checking, broken link detection with a failure threshold,
and an orphaned state when a link disappears from the content - Slug refresh: when a target’s permalink changes, the links pointing at it are
rewritten - Elementor support, including posts stored in Elementor’s own data structure
- A decision journal covering every link placed and every candidate rejected
Multilingual
Sites running WPML or Polylang are detected automatically and links are kept inside
a single language. A French post never links to its English translation.
Detection requires at least two active languages, with WPML as with Polylang: a
site with a single language is treated as monolingual. Translation layers that render
on the fly without duplicating posts (TranslatePress, Weglot, GTranslate) are treated
as monolingual, because only the original content exists in the database.
On a multilingual site the plugin switches to a larger embedding model for better
cross-language separation. When the site changes mode (a second language added, or
removed), every post is queued once to be embedded again with the new model, which
means a one-off token cost for the whole catalogue.
Installation
- Install and activate the plugin.
- Go to Autolinker > Settings and paste your OpenAI API key. You can create one
at https://platform.openai.com/. Review the OpenAI terms linked in the description
before you do. - Set your similarity threshold and per-post link budget, or keep the defaults.
- Either enable automatic processing on publish, or run a scan by hand from the
plugin screen.
Processing runs through WP-Cron. On a site with little traffic, consider a real
system cron calling wp-cron.php so scans do not stall.
Frequently asked questions
Do I need an OpenAI API key?
Yes. The plugin has no bundled key and no free tier of its own. You create a key on your own OpenAI account and pay OpenAI for what you use.
How much does it cost to run?
It depends on how many posts you process and how long they are. Two levers reduce it: the per-post link budget caps how many placements are attempted, and embeddings are cached, so a post that has not changed is never re-embedded.
Does it modify my post content?
Yes. Links are written into the post content, with a marker attribute so the plugin can identify its own links later. This is deliberate: the links are real HTML, they survive in exports, in feeds, and for search engines, and they do not depend on a filter running at display time.
What happens if I deactivate the plugin?
The links stay in your content, because they are ordinary HTML. Link tracking, health checks and repair stop until you reactivate.
Can I stop it from touching a specific post?
Yes. Each post has controls to exclude it entirely, to stop it being used as a link source, or to stop it receiving links.
Does it work with page builders?
Elementor is supported, including content stored in Elementor’s own data structure. Within an Elementor page, text editor widgets are linked; other widgets are left alone. Builders that store their layout as shortcodes in the post content, such as Divi, are linked inside their text, and their shortcodes are left untouched. Text that a builder keeps in a shortcode attribute rather than in the body, such as a module title, is never linked: writing there would break the module and the link would be invisible. The journal records those as an anchor found only in a shortcode. Builders that keep…
Does it conflict with Yoast SEO, Rank Math, All in One SEO or SEOPress?
No, and the reason is structural rather than a list of integrations: the plugin adds nothing to the front end. No meta tag, no canonical, no sitemap, no filter on the content at display time. The links are written into your content as ordinary HTML, so an SEO plugin counts them exactly like a link you typed yourself. The plugin does read the noindex setting of those four: a page you have marked noindex is never chosen as a link target. Nothing to configure. Two limits are worth knowing. It reads the setting you put on the page itself, not a site-wide rule that makes a whole post type noindex…
Does it work with caching plugins?
Yes. Nothing is computed at display time, so a cached page can never serve a version without the links: they are already part of the stored content. Writing to the post content goes through the normal WordPress update path, which is the signal WP Rocket, W3 Total Cache, LiteSpeed Cache, WP Super Cache, WP Fastest Cache and SG Optimizer already watch in order to clear a page by themselves. On an Elementor page, and in ACF fields, the plugin writes to post meta instead of the post content, which does not fire the post update hooks. Since 0.2.1 it signals the change itself on those paths: it…
Why did it place no links on a post?
Open the journal. Every candidate that was considered and dropped is recorded with a reason: below the similarity threshold, rejected by the filtering pass, or an anchor that did not appear verbatim in the source. The last one is the most common, and it is working as intended: the plugin will not invent an anchor that is not in your text.
Does it send my content anywhere other than OpenAI?
No. The only external service is the OpenAI API, and only for the posts you process.
Changelog
WPML sites with a single language now use the standard embedding model, as Polylang sites already did; their posts are embedded again once. No settings or data changes.
0.3.3
- WPML now follows the same rule as Polylang: the multilingual mode starts at two active languages. A WPML site with a single language was treated as multilingual and used the larger embedding model for no benefit. It now uses the standard model, and each post is embedded again once with it, a one-off cost.
- When the site changes mode (a second language added or removed), every post is now queued once to be embedded again with the new model. Before, posts switched one by one at their next scan, and in the meantime a newly processed post could find no candidates at all.
- The readme now says plainly that processing on publish is on by default, and how to switch it off.
- For developers: AIAL_Link_Registry::targets_without_inbound() and AIAL_Link_Registry::first_inbound_between() now count the links you wrote yourself in your content, as recorded by the link inventory. A page that only receives manual links is no longer reported as receiving none.
- No settings or database changes.
0.3.2
- Silo mode now does what the setting says. Until this version the choice was saved but never applied, so a site set to Strict could still receive links between categories.
- Strict: a post only links to posts that share at least one category with it. Each post where the silo set candidates aside gets one line in the journal, with how many were set aside.
- Soft: posts from the same category are offered first and placed first, so they use the link budget before the others. Posts from other categories can still get a link.
- The “Force silo” box on a post applies Strict to that post, whatever the site setting.
- A post with no category is not affected by either mode. Only standard post categories are read; tags and custom taxonomies are not.
- No settings or database changes.
0.3.1
- The anchor-choice step now calls GPT-6 Sol instead of GPT-5.6 Terra. Sol is priced lower per token than Terra ($2 and $10 per million input and output tokens, against $2.50 and $15). The filtering step (GPT-5.6 Luna), the nano fallback and the embeddings are unchanged.
- For developers: AIAL_Linker::build_terra_input(), AIAL_Linker::terra_schema() and the TERRA constants still work and now point to Sol. They are deprecated; use the sol names.
- No settings or database changes.
0.3.0
- A page you have marked noindex is no longer chosen as a link target. Sending internal links to a page you have deliberately kept out of the index is the opposite of what you asked for, and nothing on screen told you it was happening. Works with Yoast SEO, Rank Math, All in One SEO and SEOPress, and there is nothing to configure.
- Links already written to such a page are left where they are. Removing them by itself would rewrite your content without being asked; the Links screen lets you revoke any of them.
- This reads the setting you put on the page itself, not a site-wide rule that makes a whole post type noindex. That limit is written in the FAQ.
- New filter for developers, aial_target_is_noindex: force a target out, keep one in, or restore the previous behaviour entirely.
- No settings or database changes.
0.2.1
- The working language now follows your site language instead of always starting at French. A fresh install on an English site was sending French instructions to the model, at the same cost and with no guarantee on anchor quality. Sites that had already saved their settings keep the language they chose.
- Links written into Elementor pages and ACF fields now clear the page cache. They were only showing up once the cache expired: the link was in the stored content, but it read like a broken plugin. Measured against WP Super Cache, W3 Total Cache, Cache Enabler and LiteSpeed Cache.
- New action for anyone whose cache is not one of those four: aial_post_content_changed, fired with the post id whenever the plugin writes to post meta.
- No settings or database changes.
0.2.0
- The admin interface is now in English. It was written in French, which read oddly next to an English listing and left the plugin untranslatable for everyone else.
- French is not gone. It ships with the plugin as a translation, so a site running in French keeps the interface it already had. Nothing to install, nothing to configure.
- The plugin can now be translated into any language, either on translate.wordpress.org or with your own .po file.
- The reason codes in the journal are in English too: anchor_inside_link rather than ancre_dans_un_lien. Entries written before this update keep their old code until they age out of the journal.
- No settings or database changes.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Web & SEO Autolinker alternatives
All AI plugins →
FAQ
Web & SEO Autolinker: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Oct 12, 2026
Is Web & SEO Autolinker free?
Yes. Web & SEO Autolinker is free to download and use from the official WordPress.org plugin directory.
Is Web & SEO Autolinker safe to use in 2026?
Web & SEO Autolinker is a solid plugin choice in 2026, with a few things worth checking first. Was last updated 4 days ago, and scores 64/100 on our health check.
How many websites use Web & SEO Autolinker?
Web & SEO Autolinker is active on <10 WordPress websites and has been downloaded 431 times since it launched in September 2026. It was downloaded 259 times in the last 30 days.
Does Web & SEO Autolinker work with WordPress 7.1?
Yes. The developer has tested Web & SEO Autolinker up to WordPress 7.1.3, the latest release. It requires WordPress 6.2 or newer.
What PHP version does Web & SEO Autolinker need?
Web & SEO Autolinker requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Web & SEO Autolinker last updated?
The latest version, 0.3.3, was released on October 9, 2026 (4 days ago).
Who makes Web & SEO Autolinker?
Web & SEO Autolinker is developed and maintained by Web & SEO.
What are the best alternatives to Web & SEO Autolinker?
The most popular alternatives to Web & SEO Autolinker are Elementor Website Builder (10M+ installs), All in One SEO (2M+ installs) and AI Agent by SiteGround (1M+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
