Documentation
Who can do what, and multilingual sites
Who can do what
Open OnlyAI SEO, Settings, Who can do what. Each role (editor, author and so on) can be given any of five rights. Out of the box, Authors get none (they see the basic title, description and keyword fields and the score, and no AI buttons), Editors get AI help, the Agent Inbox and the advanced fields, and administrators have everything:
| Manage everything | Settings, import, cloud and Google, agents on or off. Includes all the rest. |
| Redirects and 404s | Add, edit and delete redirects; read the 404 monitor. |
| Agent Inbox | Run the agents and accept or dismiss their proposals. Each action still needs the right to edit the post it touches. |
| Advanced SEO fields | Noindex, nofollow, canonical, rich results and custom JSON-LD on a post, and noindex on a category or tag. |
| AI help | Use AI in the editor (titles, descriptions, keywords, 1-click SEO wording) and on Content ideas. Every press uses one of the site's cloud AI requests. |
- Administrators always have all five, and so does anyone granted "manage everything", so nobody can be locked out.
- Only an administrator can change who has what. Someone allowed to manage OnlyAI SEO cannot hand out rights.
- Each person sees only the sections they may open: an editor given just the redirects right sees a single "Redirects" page under the OnlyAI SEO menu. In the editor, the advanced fields are shown but locked for people without that right, and the server refuses changes to them from other routes as well (the REST API, Quick Edit and Bulk Edit).
- AI help is checked on the server as well as in the buttons, so a role without it cannot spend the site's cloud requests by any route. A site that already handed out rights before 2.22 keeps them, and those roles keep AI help.
- On uninstall, the rights are removed from every role.
Multilingual sites (Polylang and WPML)
OnlyAI SEO detects Polylang or WPML by itself and then:
- Translates your templates. Every title, description and share-text template in Titles & social is handed to the language plugin as a string (group "OnlyAI SEO"). Translate them in Polylang's Languages, Translations screen or WPML's String Translation; visitors get the one for the language they are reading. The settings screen always shows the original text.
- Says which language a page is in. Open Graph carries the page's own locale plus
og:locale:alternatefor its other languages, and the page and article structured data use the page's language forinLanguage. - Keeps internal links in one language. The Link Builder only suggests links between pages in the same language, and the Auditor does not call the same title in two languages a duplicate.
- Lists the right pages in the HTML sitemap.
[onlyai_sitemap]shows the language being viewed; addlang="all"orlang="fr"to choose. - Asks the AI for the right language. AI text is requested in the language of the content it is given.
- Redirects use the real address. Rules are matched on the site's stored address, so a
/fr/prefix or a language domain added by the language plugin never causes a mismatch or a doubled/fr/fr/. Include the language prefix in the address you redirect from.
OnlyAI SEO does not print hreflang tags: Polylang and WPML already do, and printing them twice would confuse search engines. The XML sitemap lists the pages of every language in one file.