phoenixedu.com.bd
success
Claude Code
intent
What does phoenixedu.com.bd do and who is it for? Explain it back to me.
13steps
64.0sduration
$0.7097cost
157,938tokens
21 steps8 reasoning steps4 searches
home
docs
docs
/features
search
/about-us
/courses-list
search
home
search
search
/courses/nsu-bracu-onl…
/faq
56%
on-site discovery
44%
reliability
11%
link following
path origin
- previous resource11%
- web search44%
- prior knowledge44%
insight
The agent assembled a serviceable overview of Phoenix Education's business by combining fragments from the homepage, search results, and one accessible course page, but was severely hampered by a non-functional website architecture. Most key pages (About Us, Courses List, Pricing, FAQ) returned 404 errors despite being indexed; the agent had to rely on search snippets and prior knowledge to construct answers about pricing tiers, target audience, and differentiation. The site is poorly navigable for automated discovery.
- ›Step [1] (homepage) and [4] (about page) returned HTML but lacked readable text content—only metadata and Next.js scaffolding were visible in the fetches, indicating heavy client-side rendering that blocks server-side content discovery.
- ›Steps [8], [13], [16], [19] (web searches) were the primary source of actionable information: search result titles and snippets revealed course names, pricing examples, and competitor names that the website itself did not surface in machine-readable form.
- ›Step [18] (course detail page for NSU/BRACU combo) successfully returned a page, but the fetch response shown is again truncated/scaffold-only, suggesting the actual course details (syllabus, instructor bios, enrollment mechanics) are loaded client-side and invisible to the agent.
- ›Pricing data in the final answer came from search result snippets ([8], [13], [16]), not from a dedicated pricing page—the agent inferred price structure from course listing titles rather than accessing a pricing table or comparison matrix.
- ›Steps [3], [5], [7], [10], [11] all returned 404s for standard pages, indicating either URL structure mismatch, broken navigation, or that the site uses client-side routing incompatible with direct URL guessing.
- ›Step [15] (phoenixadmissioncare.com) was fetched but contributed no visible content to the final answer, despite being mentioned as related. The relationship between the two domains remains unexplained because the fetches did not surface that information.
- ›The agent explicitly flagged in its response that full page content was inaccessible ('Many pages I tried to access returned 404 errors, and the full text content wasn't accessible through standard page fetches'), indicating clear awareness of the site's poor machine readability.
Help the next agent finish on phoenixedu.com.bd
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 →