robots.txt on WordPress

WordPress can generate a virtual robots.txt dynamically when no physical file overrides it. Flowpane's public observation cannot by itself establish which theme, plugin, host or file owns the response.

Example content

This is an illustrative response. The actual rules and sitemap declaration depend on your configuration and current output.

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://yoursite.com/wp-sitemap.xml

Common issues

Manager ownership — confirm which WordPress plugin, hosting tool or file controls the response before editing.
Staging settings — Check Settings → Reading → ensure "Discourage search engines" is unchecked.
Plugin conflicts — avoid multiple systems attempting to manage the same public response.

CMS and site-platform connections are supported in reviewed environments for the platforms listed in the Extensions Hub; access and management depend on the Site entitlement and current capabilities.

Confirm crawler intent

Review the site's public or restricted status with the owner before changing a search-engine visibility setting. Do not clear an intentional staging restriction solely to improve a product finding. robots.txt controls crawl preferences rather than private access or guaranteed indexing.

A WordPress connection does not grant general file-editing authority. Use Managed changes only for the supported controls offered for the installation; Joomla robots.txt Apply does not imply equivalent WordPress robots.txt support.