On a multisite network, Delete data on uninstall now cleans up every site where the box is ticked, not only the main site. No settings or data changes.<\/p>","0.4.1":"
Anchors are no longer linked in the middle of a word, and the readme now lists every case in which content is sent to OpenAI. No settings or data changes.<\/p>","0.3.3":"
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.<\/p>","0.3.2":"
Silo mode is now applied: Strict keeps links inside shared categories, Soft places same-category links first. No settings or data changes.<\/p>","0.3.1":"
Anchors are now chosen by GPT-6 Sol, priced lower per token than GPT-5.6 Terra. No settings or data changes.<\/p>","0.3.0":"
Pages you marked noindex are no longer used as link targets. Links already written to them are left alone. No settings or data changes.<\/p>","0.2.1":"
Two fixes. The working language follows your site language instead of defaulting to French, and links written into Elementor or ACF pages now clear the page cache. No settings or data changes.<\/p>","0.2.0":"
The admin interface moves from French to English. Sites running in French keep French: the translation ships with the plugin. No settings or data changes.<\/p>","0.1.3":"
Cosmetic and documentation. The admin screens now carry the plugin's name, and the journal shows why a candidate was dropped.<\/p>","0.1.2":"
Fixes content damage on page builders that store their layout as shortcodes, such as Divi. Recommended for those sites.<\/p>","0.1.1":"
Performance only. No settings or data changes.<\/p>","0.1.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3677147,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3677147,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3677147,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3677147,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.1.1","0.1.2","0.1.3","0.2.0","0.2.1","0.3.0","0.3.1","0.3.2","0.3.3","0.4.0","0.4.1","0.4.2"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3679761,"resolution":"1","location":"assets","locale":"","width":1400,"height":820},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3679761,"resolution":"2","location":"assets","locale":"","width":1400,"height":1500},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3679761,"resolution":"3","location":"assets","locale":"","width":1400,"height":950},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3679761,"resolution":"4","location":"assets","locale":"","width":1400,"height":820},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3679761,"resolution":"5","location":"assets","locale":"","width":1400,"height":560},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3679761,"resolution":"6","location":"assets","locale":"","width":1400,"height":900}},"screenshots":{"1":"Every link the plugin has placed, with its source, its target, the anchor it used and the similarity that justified it. One click revokes a link and removes it from the content.","2":"The whole configuration on a single screen: similarity threshold, link budget per post, anchor length, which post types are sources and which are targets.","3":"Link health. Broken internal and external links, duplicate destinations, anchor cannibalisation, and registry entries whose target no longer exists.","4":"The journal. Every candidate that was considered and dropped, with the reason next to it.","5":"One button scans the whole catalogue. Progress is shown as it goes.","6":"The result in the published article: ordinary HTML links in the text, which survive in exports and feeds and do not depend on the plugin still running."}},"plugin_section":[],"plugin_tags":[2353,19933,175,194533,186],"plugin_category":[55],"plugin_contributors":[274230],"plugin_business_model":[],"class_list":["post-358763","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-internal-linking","plugin_tags-links","plugin_tags-openai","plugin_tags-seo","plugin_category-seo-and-marketing","plugin_contributors-webandseofr","plugin_committers-webandseofr"],"banners":{"banner":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/banner-772x250.png?rev=3677147","banner_2x":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/banner-1544x500.png?rev=3677147","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/icon-128x128.png?rev=3677147","icon_2x":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/icon-256x256.png?rev=3677147","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-1.png?rev=3679761","caption":"Every link the plugin has placed, with its source, its target, the anchor it used and the similarity that justified it. One click revokes a link and removes it from the content."},{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-2.png?rev=3679761","caption":"The whole configuration on a single screen: similarity threshold, link budget per post, anchor length, which post types are sources and which are targets."},{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-3.png?rev=3679761","caption":"Link health. Broken internal and external links, duplicate destinations, anchor cannibalisation, and registry entries whose target no longer exists."},{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-4.png?rev=3679761","caption":"The journal. Every candidate that was considered and dropped, with the reason next to it."},{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-5.png?rev=3679761","caption":"One button scans the whole catalogue. Progress is shown as it goes."},{"src":"https:\/\/ps.w.org\/web-seo-autolinker\/assets\/screenshot-6.png?rev=3679761","caption":"The result in the published article: ordinary HTML links in the text, which survive in exports and feeds and do not depend on the plugin still running."}],"raw_content":"\n
Autolinker builds internal links between the posts you already have. It reads\neach post, finds the most semantically related pages on your site, and asks a\nlanguage model to choose an anchor phrase that already exists, word for word, in\nthe source text (capitalisation aside). The link is then written into the post\ncontent and kept in a registry so it can be tracked, repaired, or removed later.<\/p>\n\n
There is no keyword list to maintain. Relevance comes from meaning, not from\nmatching strings.<\/p>\n\n
Every rejection is written to a journal with a reason, so an empty result is never\nindistinguishable from a broken plugin.<\/p>\n\n
Autolinker does not work without an OpenAI API key that you supply. The plugin\nsends data to the OpenAI API (api.openai.com), a third-party service that is not\naffiliated with this plugin or with WordPress.org.<\/p>\n\n
What is sent:<\/strong> the text content of the posts you choose to process, the text of\nyour link targets (up to 8,000 characters each, to compute the embeddings\nthat match them), the titles and excerpts of candidate link targets, and the\nprompts the plugin builds around them. Your API key is stored encrypted in your\nWordPress database and is sent to OpenAI to authenticate each request.<\/p>\n\n When it is sent:<\/strong> in these four cases, and no others:<\/p>\n\n The last two cases run in the background through WP-Cron, even with \"Full auto on\npublish\" switched off. They only send content that has no embedding yet, or whose\ntext or embedding model has changed since its embedding was computed.<\/p>\n\n What is not sent:<\/strong> no data is sent to the plugin author, and no post content\nleaves your site other than to OpenAI, as described above.<\/p>\n\n One clarification about link health.<\/strong> The plugin also checks whether the links in\nyour content still resolve. That check runs on a schedule and makes ordinary HTTP\nrequests to the URLs already present in your posts, and to their robots.txt, which it\nhonors. It sends none of your content and involves no third-party service: it only\nvisits the addresses you already link to. Those requests identify themselves with a\nuser agent naming the plugin and your site URL, so the hosts you link to can see that\nthe request came from your site.<\/p>\n\n Using this plugin means your content is processed under OpenAI's terms. Please read\nthem before installing:<\/p>\n\n You pay OpenAI directly for the tokens the plugin consumes. See the FAQ for cost\ncontrol.<\/p>\n\n Sites running WPML or Polylang are detected automatically and links are kept inside\na single language. A French post never links to its English translation.<\/p>\n\n Detection requires at least two active languages, with WPML as with Polylang: a\nsite with a single language is treated as monolingual. Translation layers that render\non the fly without duplicating posts (TranslatePress, Weglot, GTranslate) are treated\nas monolingual, because only the original content exists in the database.<\/p>\n\n On a multilingual site the plugin switches to a larger embedding model for better\ncross-language separation. When the site changes mode (a second language added, or\nremoved), every post is queued once to be embedded again with the new model, which\nmeans a one-off token cost for the whole catalogue.<\/p>\n\n\n Processing runs through WP-Cron. On a site with little traffic, consider a real\nsystem cron calling wp-cron.php so scans do not stall.<\/p>\n\n\n Yes. The plugin has no bundled key and no free tier of its own. You create a key on\nyour own OpenAI account and pay OpenAI for what you use.<\/p><\/dd>\n It depends on how many posts you process and how long they are. Two levers reduce\nit: the per-post link budget caps how many placements are attempted, and embeddings\nare cached, so a post that has not changed is never re-embedded.<\/p><\/dd>\n Yes. Links are written into the post content, with a marker attribute so the plugin\ncan identify its own links later. This is deliberate: the links are real HTML, they\nsurvive in exports, in feeds, and for search engines, and they do not depend on a\nfilter running at display time.<\/p><\/dd>\n The links stay in your content, because they are ordinary HTML. Link tracking,\nhealth checks and repair stop until you reactivate.<\/p><\/dd>\n By default, everything is kept. Tick \"Delete data on uninstall\" in Settings and\nuninstalling removes everything the plugin created, except the links already written\ninto your posts and their revisions. To take links out, revoke them before you\nuninstall: once its data is deleted, the plugin can no longer find them. On a\nmultisite network, each site where the box is ticked is cleaned up, and sites where\nit is not ticked keep their data. With a persistent object cache (Redis, Memcached),\nthe robots.txt rules cached by the link checker are not deleted: they expire on their\nown within 24 hours.<\/p><\/dd>\n Yes. Each post has controls to exclude it entirely, to stop it being used as a link\nsource, or to stop it receiving links.<\/p><\/dd>\n Elementor is supported, including content stored in Elementor's own data structure.\nWithin an Elementor page, text editor widgets are linked; other widgets are left\nalone.<\/p>\n\n Builders that store their layout as shortcodes in the post content, such as Divi,\nare linked inside their text, and their shortcodes are left untouched. Text that a\nbuilder keeps in a shortcode attribute rather than in the body, such as a module\ntitle, is never linked: writing there would break the module and the link would be\ninvisible. The journal records those as an anchor found only in a shortcode.<\/p>\n\n SeedProd is supported on landing pages and on pages edited with SeedProd. Text\nblocks are linked in both places SeedProd keeps them, so the link shows at once and\nsurvives the next save in the SeedProd builder. Other blocks, such as headlines and\nbuttons, are left alone. Tested with SeedProd Lite. Pages built with the SeedProd Pro\ntheme builder use the same storage but were not tested.<\/p><\/dd>\n No, and the reason is structural rather than a list of integrations: the plugin adds\nnothing to the front end. No meta tag, no canonical, no sitemap, no filter on the\ncontent at display time. The links are written into your content as ordinary HTML,\nso an SEO plugin counts them exactly like a link you typed yourself.<\/p>\n\n The plugin does read the noindex setting of those four: a page you have marked\nnoindex is never chosen as a link target. Nothing to configure.<\/p>\n\n Two limits are worth knowing. It reads the setting you put on the page itself, not\na site-wide rule that makes a whole post type noindex. And it reads the four\nplugins above; another SEO plugin is not recognised. In both cases the page can\nstill be chosen as a target, and the per-post controls in the sidebar exclude it.\nDevelopers can also filter aial_target_is_noindex.<\/p><\/dd>\n Yes. Nothing is computed at display time, so a cached page can never serve a version\nwithout the links: they are already part of the stored content. Writing to the post\ncontent goes through the normal WordPress update path, which is the signal WP Rocket,\nW3 Total Cache, LiteSpeed Cache, WP Super Cache, WP Fastest Cache and SG Optimizer\nalready watch in order to clear a page by themselves.<\/p>\n\n On an Elementor page, and in ACF fields, the plugin writes to post meta instead of the\npost content, which does not fire the post update hooks. Since 0.2.1 it signals the\nchange itself on those paths: it calls clean_post_cache(), which WP Super Cache and\nW3 Total Cache listen to, and it clears Cache Enabler and LiteSpeed Cache through\ntheir own per-post API. Measured against those four.<\/p>\n\n Two are not covered. WP Fastest Cache exposes no per-post purge that another plugin\ncan reach. WP Rocket could not be tested here, so nothing is claimed about it. If a\nnew link on an Elementor or ACF page does not appear on either of those, purge that\npage in your caching plugin, or hook the aial_post_content_changed action to call your\ncache's own purge.<\/p><\/dd>\n Open the journal. Every candidate that was considered and dropped is recorded with a\nreason: below the similarity threshold, rejected by the filtering pass, or an anchor\nthat did not appear verbatim in the source. The last one is the most common, and it\nis working as intended: the plugin will not invent an anchor that is not in your text.<\/p><\/dd>\n No. The only external service is the OpenAI API, and only for the posts you process.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\n
Features<\/h4>\n\n
\n
Multilingual<\/h4>\n\n
\n
\n
Do I need an OpenAI API key?<\/h3><\/dt>\n
How much does it cost to run?<\/h3><\/dt>\n
Does it modify my post content?<\/h3><\/dt>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\n
What happens if I uninstall the plugin?<\/h3><\/dt>\n
Can I stop it from touching a specific post?<\/h3><\/dt>\n
Does it work with page builders?<\/h3><\/dt>\n
Does it conflict with Yoast SEO, Rank Math, All in One SEO or SEOPress?<\/h3><\/dt>\n
Does it work with caching plugins?<\/h3><\/dt>\n
Why did it place no links on a post?<\/h3><\/dt>\n
Does it send my content anywhere other than OpenAI?<\/h3><\/dt>\n
0.4.2<\/h4>\n\n
\n
0.4.1<\/h4>\n\n
\n
0.4.0<\/h4>\n\n
\n
0.3.3<\/h4>\n\n
\n
0.3.2<\/h4>\n\n
\n
0.3.1<\/h4>\n\n
\n
0.3.0<\/h4>\n\n
\n
0.2.1<\/h4>\n\n
\n
0.2.0<\/h4>\n\n
\n
0.1.3<\/h4>\n\n
\n
0.1.2<\/h4>\n\n
\n
0.1.1<\/h4>\n\n
\n
0.1.0<\/h4>\n\n
\n