Generate the slug and create a 301 redirect

What it is

AISA can generate the URL slug alongside the title, meta and keyphrase, keeping the focus keyphrase in the URL the way SEO plugins reward. The suggestion is optional and off by default: your addresses never change on their own. When it is on and you change the slug of an already-published page, AISA creates the 301 redirect from the old address to the new one by itself, so no link breaks and no traffic is lost. The post_name is only ever touched when you edit the slug field yourself; a save that leaves that field alone never changes the URL.

Where to find it

The site-wide switch is Settings → Analysis → Suggest URL slugs, off by default. Every editor also has its own tickbox under the generate button, Also suggest a URL slug, next to Also generate AI Search Context: in the floating panel, in the Standalone SEO block and in the AISA SEO panel inside the Elementor editor. Each one starts from the site-wide setting and then remembers your choice. Ticking it is an explicit decision, so the slug the AI writes is applied when you save; leave it unticked and the slug field simply shows the real address of the content and nothing ever writes into it. The automatic 301 on slug change also happens through the Auto SEO Fix box (optional slug correction) and in the bulk "Fix all + URL" group action.

Requirements & tier

An AI provider for generation (Cloud credits or your own key).
The 301 redirect is created when the slug of an existing post changes; AISA's redirects layer handles it.
Slug fix with automatic 301 in Auto SEO Fix is part of the AI-correction flow (Premium for the AI fix).

How to use

Turn the suggestion on: the tickbox in the panel, or Settings → Analysis → Suggest URL slugs for the whole site. With it off, no slug is asked for and none is proposed.
Generate the focus keyphrase and SEO first so the slug can include the keyphrase.
Edit the Slug URL field, or let Generate SEO / Auto SEO Fix propose one.
Save the post. AISA updates the post_name only if you edited the slug field yourself — saving without touching it leaves the URL exactly as it is.
On an already published page, AISA creates the 301 redirect from the old URL to the new one automatically. On a draft there is nothing to redirect, so none is created.
For mass changes, use the "Fix all + URL" group action in the lists / Bulk — slugs change with automatic 301s in the background.

Questions people ask

Will changing the slug break my links? No — AISA adds a 301 redirect from the old address, so visitors and search engines land on the new URL.
Does it change the slug every time I edit the title? No. Nothing touches the post_name unless you edit the slug field yourself; otherwise WordPress derives it from the title as usual.
I do not want AISA proposing slugs at all. That is the default. Leave Settings → Analysis → Suggest URL slugs off and the panel tickbox unticked: the AI is not even asked for a slug, no slug row appears, and your URLs stay untouched.
Where does the keyphrase fit? The focus keyphrase is placed in the slug, matching title and meta, which is what the SEO plugins check.
Can I do this in bulk? Yes — the "Fix all + URL" group action and Bulk apply slug fixes with automatic 301 redirects.
Where are the redirects managed? Settings → Redirect & 404 manages 301/302 rules; AISA's redirects also apply only when a page would truly 404, avoiding conflicts.

Troubleshooting

Slug didn't update. It only changes when the field differs from the original value; edit the slug explicitly.
Old URL still 404s. Confirm the redirect was created (Settings → Redirect & 404); the automatic 301 is added on slug change for existing posts.
Redirect conflicts with another plugin. AISA's redirects fire only when the page would otherwise 404, minimising conflicts.

Generate the focus keyphrase
The Standalone SEO block (when no SEO plugin is active)
The floating SEO panel (generate title, meta, keyphrase, slug)