WORDPRESS ROBOTS.TXT VERIFICATION
Web Aloha | 28 October 2026
Guide: https://webaloha.co/wordpress-robots-txt/
These accompanying before/after text files are examples, not a universal production policy.

Public scheme, hostname and exact /robots.txt URL:
Redirect destination, if any:
Authority: physical file / WordPress virtual / plugin / host / CDN:
Where the authoritative configuration is maintained:
Current body and headers saved privately at:
One intended change and rollback method:
Verified live sitemap URL:

For each important origin:
[ ] Confirm the request returns intended plain text and an appropriate status.
[ ] Compare the public body with the edited source after any cache refresh.
[ ] Verify a public page intended for crawling is allowed.
[ ] Verify a stylesheet/script required for rendering is allowed.
[ ] Verify the intended restricted path is disallowed.
[ ] Check the real admin and admin-ajax paths, including subdirectory installs.
[ ] Check any specific crawler group as well as the wildcard group.
[ ] Check Reading screen search visibility, page robots meta and HTTP headers separately.
[ ] Keep authentication for private content; robots.txt is not an access control.
[ ] Re-fetch and repeat path tests after publishing, then record the final body/time.

Example diagnostic matrix, repeated for Googlebot and Bingbot on 28 October 2026:
Path                                           Before      After
/                                              Disallowed  Allowed
/services/                                     Disallowed  Allowed
/wp-admin/                                     Disallowed  Disallowed
/wp-admin/admin-ajax.php?action=example         Allowed     Allowed
/wp-content/themes/example/style.css           Disallowed  Allowed

These results came from Web Aloha's local rules diagnostic, not live crawler observations.
They do not establish indexation, ranking, cache-refresh time or origin/CDN behavior.