mozilla.com
success
Claude Code
intent

What does mozilla.com do and who is it for? Explain it back to me.

9steps
39.5sduration
$0.4270cost
25,170tokens
11 steps2 reasoning steps2 searches
home
/firefox
home
/en-us/products/vpn
search
search
/en-us/products/relay
home
/en-us/products
60%
answer from your site
57%
answer efficiency
100%
followed site links
answer sources
  • from this site60%
  • from search results20%
  • from agent knowledge20%
url discovery
  • given in the task14%
  • followed a link86%
insight

The agent successfully gathered enough information to explain Mozilla's mission, products, pricing, and differentiation, though it had to work around navigation friction (redirects, missing pricing pages, a 404 error on Relay) and fill gaps with web search and inference.

  • ›mozilla.com itself offers no independent content—it redirects to firefox.com, leaving mozilla.org as the only official hub. This is confusing for someone trying to understand 'Mozilla' as a brand.
  • ›The main products page (step [4]) listed products but disclosed no pricing, forcing the agent to visit individual product pages or use web search to assemble cost information.
  • ›Firefox Relay's official product page returned a 404 (step [7]), so pricing had to be sourced from a web search (step [8]) rather than the site itself.
  • ›Differentiation from Chrome, Safari, and Edge came entirely from web search results (step [9]) and model reasoning; mozilla.org does not explicitly compare itself to competitors.
  • ›Mozilla's site structure is functional for browsing products but lacks consolidated pricing tables and competitive positioning—both critical for the evaluation task.

See every agent that visits mozilla.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →