This allows editors to decide directly while editing an article whether search engines should index that specific page or not. Typical options include index, follow or noindex, follow.

The value is stored directly in the Joomla core metadata field. No custom database tables are created, and no core hacks are required.

This makes it easy to exclude individual pieces of content from search engines without changing the global SEO settings of the entire website.

Key Features

• list text hereRobots setting directly in the frontend editor Authors and editors do not need to switch to the Joomla backend. The Robots selector is available directly while editing an article in the frontend.
• Clean storage in the Joomla core The Robots value is stored in Joomla's existing article metadata field. The plugin intentionally uses Joomla's built-in structure.
• No custom tables, no core modifications The extension stays lean and update-friendly. No Joomla core files are modified.
• Visible only to approved user groups You can define exactly which user groups are allowed to see and edit the Robots field in the frontend editor.
• Additional server-side protection Even if someone tries to submit a manipulated request manually, only an allowed Robots value will be accepted.

Typical Use Cases

• Set individual landing pages to noindex If certain campaign, test, or promotional pages should not appear in search engines, the Robots value can be adjusted individually per article.
• Give editors more SEO control Teams can make SEO-related decisions directly during the editorial process without needing an administrator every time.
• Keep global Joomla settings unchanged The site's standard Joomla configuration remains unchanged. Only selected articles receive a different Robots rule when needed.

How it works

The plugin adds an extra Robots field to the Joomla frontend article editing form. The selected value is then stored in that article's metadata.

In the default Joomla frontend editor, this field currently appears as its own tab because the core template does not render all metadata fields dynamically.