User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Content-Signal: search=yes, ai-input=yes, ai-train=no
Disallow: /*?*add_to_wishlist=
Disallow: /*?*remove_from_wishlist=
Disallow: /*add-to-cart=
Disallow: /*?*attribute_pa_material
Disallow: /?s=*
Disallow: /*?*style_tags=
Disallow: /*?*room_tags=
Disallow: /*?*colour_tags=
Disallow: /*?*pa_material=
Disallow: /*?*

# Specific Bot Blocks
User-agent: Yandex
Disallow: /

# Bytespider ignores robots.txt in practice and spoofs its user agent, so this is a
# courtesy declaration, not a control. The rule that stops it is at the Cloudflare edge.
# No Content-Signal here: it would be incoherent alongside a blanket disallow.
User-agent: Bytespider
Disallow: /

# Specific Bot Permissions
User-agent: facebookexternalhit
Allow: /schedule

Sitemap: https://www.feathr.com/sitemap.xml
Sitemap: https://www.feathr.com/uk/sitemap.xml
Sitemap: https://www.feathr.com/eu/sitemap.xml
Sitemap: https://www.feathr.com/au/sitemap.xml
Sitemap: https://www.feathr.com/global/sitemap.xml