How Flowpane works with Joomla

Joomla separates its output across a physical robots.txt file, extensions that build XML sitemaps, and layered robots settings on menu items, categories and articles. Its router also decides the exact address of every page. Flowpane examines the robots.txt, sitemaps and page directives a Joomla Site actually delivers, including where extensions shape that output, and brings in Joomla's own view of its configuration through the connector. This page explains how each output is produced, how to confirm what the public Site serves, and what the Flowpane connector adds.

For the general model, read How Flowpane works with your CMS.

Joomla's extension model

Joomla is extended with components, modules, plugins and templates, often installed together as a package. For machine-readable output the distinction matters:

• Components own pages and addresses. Sitemap extensions such as OSMap and JSitemap are components with their own XML views.
• System plugins run on every request and can change the page head, including robots directives and canonical links. SEO extensions such as EFSEO work this way, and sh404SEF also rewrites page addresses.
• Templates render the head and can print their own tags.

A single Site can have more than one extension shaping the same output. Knowing which one is active is the first step in explaining a public result.

robots.txt is a file

Joomla does not generate robots.txt on request. The public response is a file at the Site root, unless the web server or hosting layer answers first:

Request for /robots.txt
 |
 +-- Web server or hosting rule answers?  -> that response is served
 +-- robots.txt file at the Site root?    -> the file is served
 +-- neither                              -> not found
 |
 +-- A CDN or cache in front of the Site can serve an older copy.

Because it is a file, robots.txt on Joomla changes only when someone edits it: through the host's file manager, a deployment, an extension that writes the file, or a managed change. A site restore can also put back an older copy. Joomla's own robots.txt does not declare a sitemap, so a Sitemap: line has to be added deliberately.

curl -s https://example.com/robots.txt

XML sitemaps come from extensions

Joomla core has no XML sitemap generator. Sitemaps come from extensions or from files uploaded to the Site. Their addresses depend on the extension and on Joomla's search-engine-friendly URL settings. For OSMap, for example, the same XML view can appear in two forms (illustrative, example.com):

Without SEF URLs:  https://example.com/index.php?option=com_osmap&view=xml&id=1
With SEF URLs:     https://example.com/component/osmap/?view=xml&id=1

Sitemap extensions typically build their URL lists from Joomla's menus and content, so publishing, hiding or excluding a menu item changes which addresses the sitemap lists. Some SEO suites, such as RSSeo, can also generate sitemap files on disk. An extension's XML view can answer with a redirect to a variant of its address, for example one that adds a format parameter, before serving the XML. Flowpane follows that redirect within the Site, as crawlers do.

When the connector reports a sitemap address from an extension, Flowpane confirms that it belongs to the Site's verified address, including the www or bare-domain form the Site uses, then reads it from the public web and parses the XML independently. Sitemaps reported by the CMS appear as source evidence beside the sitemaps crawlers discover publicly, and the Site's score reflects what the public Site declares and serves.

Addresses and the Itemid parameter

Joomla's router ties each page to a menu item. Without SEF URLs, or for content that is reachable outside the menu, addresses carry parameters such as option, view, id and Itemid:

https://example.com/index.php?option=com_content&view=article&id=12&Itemid=101

These parameters are part of Joomla's routing, not tracking. Flowpane's sitemap assessment treats recognised tracking parameters as a URL hygiene concern and leaves Joomla routing parameters alone. Page builder content, such as SP Page Builder pages, is reported at the menu address visitors actually use.

Page indexing directives are layered

Joomla builds a page's <meta name="robots"> from several layers. A more specific explicit setting normally replaces the site-wide default, and later layers can change the result again:

• Global Configuration → Site → Metadata → Robots, the site-wide default.
• The menu item's robots setting for the page it opens.
• The category and article robots settings in their publishing options.
• System plugins and templates that change the head after Joomla has built it.
• The host or CDN, which can add an X-Robots-Tag header.

The public page is the final answer, so confirm it there:

curl -s https://example.com/about-us | grep -i 'name="robots"'
curl -sI https://example.com/about-us | grep -i 'x-robots-tag'

Caching and delivery

Joomla's own page cache, a host cache or a CDN can store page HTML and sitemap XML. Redirects between www and the bare domain decide which copy crawlers reach. Flowpane records the response crawlers receive, including the redirect path, so a cached or redirected answer is visible as such.

What Flowpane observes on every Joomla Site

Without a connection, Flowpane checks the public robots.txt, the sitemaps it can discover, the governance files and sampled pages, and records Results, Changes and Findings from what the public web serves. This is identical for every CMS.

What the connector adds

The connector sends counts, addresses and settings; article content stays on your Site. See Source activity, health and change summaries.

Reported and verified on Joomla

Flowpane shows the connector's report and the public observation separately, each with its own date:

• Reported: counts such as one robots.txt source change, two indexing setting changes or one unpublished article. This is what Joomla says happened.
• Verified: the public check that followed, showing what crawlers receive now. This is what records a Change or a Finding.

When the two disagree, the gap is the useful part. A reported robots.txt change that the public file does not show usually means a cache or a hosting rule is answering. A menu item set to index whose public page carries noindex usually means a system plugin or the template is adding it.

What managed changes permit on Joomla

A connection provides observation and reporting. Where Managed changes is enabled for the Site, a person with the right role can approve:

• robots.txt: publish a saved, validated and reviewed robots.txt revision. Joomla writes it to the file at the Site root, and Flowpane then checks the public file.
• Page directives: set a specific page's indexing or link-following policy. Directives are tied to the connection and end when the Site is disconnected.
• The Flowpane-managed sitemap: Flowpane's own sitemap, served at /flowpane-sitemap.xml when SEF URLs with URL rewriting are on, or at a query address otherwise. It runs alongside sitemaps from OSMap, JSitemap or any other extension.

Each action is approved in Flowpane, applied by the connector and checked on the public Site. Drafts are saved and reviewed in Flowpane; publication happens at the Apply step. See What Flowpane can manage on Joomla.

Worked examples

A sitemap on the other host form. A representative case: a Site's address is the bare domain, while its sitemap extension declares a sitemap on www. Flowpane confirms that both forms belong to the same verified Site before reading the reported sitemap, follows the extension's redirect to the XML and parses it. The reported sitemap appears as source evidence, and the score stays based on the sitemaps the public Site declares.

Routing parameters in a sitemap. A sitemap lists addresses with Itemid parameters because SEF URLs are off. Flowpane recognises them as Joomla routing, so they do not count as tracking parameters in the sitemap assessment.

A restored robots.txt. A Site restore puts back an older robots.txt. The connector reports the file change and sends a priority event, and the public check records the Change with before and after content, so the team can see exactly which rules returned.

Environments

Supported Joomla, PHP and database versions are listed in Joomla compatibility.

Flowpane for Joomla · robots.txt on Joomla · Managed changes