Files
company_site/company_site/docs/agentic-browsing.md
T
westfarn 846f1b8a37
Deploy Company Site / test (push) Successful in 10s
Deploy Company Site / deploy (push) Successful in 5s
Improve Lighthouse Agentic Browsing readiness (#8)
## Summary

- Add `robots.txt`, `sitemap.xml`, and `llms.txt` endpoints so crawlers and AI agents can discover public pages
- Fix accessibility tree issues: contact form labels, semantic nav/profile dropdown buttons, cookie consent dialog ARIA, and dead `href="#"` links
- Reduce layout shift on homepage/contact via hero min-heights, trusted-by marquee sizing, and fixed cookie banner
- Add regression tests and `docs/agentic-browsing.md` for Lighthouse agentic-browsing audits

Closes #5. Also addresses overlap with #3 (sitemap + robots.txt).

## Test plan

- [x] `python manage.py test public.tests` (14 tests pass)
- [ ] Verify `GET /robots.txt`, `/sitemap.xml`, `/llms.txt` return 200 in staging/prod
- [ ] Confirm contact form labels visible and submittable on `/contact`
- [ ] Run Lighthouse `--only-categories=agentic-browsing` on homepage and contact page
- [ ] Smoke test mobile nav dropdown and cookie consent banner

Reviewed-on: #8
2026-07-02 11:36:54 +00:00

1.7 KiB

Agentic Browsing Readiness

This site targets Google's experimental Agentic Browsing Lighthouse category (v13.3+), which checks whether AI agents can read, navigate, and act on public pages.

PageSpeed Insights does not yet expose this category. Run audits locally:

npx lighthouse@latest https://aimloperations.com \
  --only-categories=agentic-browsing \
  --chrome-flags="--enable-experimental-web-platform-features" \
  --output=html --output-path=agentic-browsing-report.html

Test at minimum:

  • / (homepage)
  • /contact (primary conversion page)

What we ship

Check Implementation
llms.txt GET /llms.txt — machine-readable site summary
robots.txt GET /robots.txt — crawl rules + sitemap reference
sitemap.xml GET /sitemap.xml — public marketing URLs
Accessibility tree Form labels, semantic nav controls, ARIA on dialogs
Layout stability Fixed cookie banner, reserved hero/marquee space, font fallbacks

WebMCP is intentionally deferred until browser and agent support stabilizes.

Regression checklist

Before merging public-facing template or CSS changes:

  1. Contact form fields have associated <label> elements (not placeholder-only).
  2. Nav dropdowns use <button> triggers with aria-expanded / aria-haspopup.
  3. Cookie consent banner stays position: fixed (no document flow shift).
  4. GET /robots.txt, /sitemap.xml, /llms.txt return 200.
  5. Re-run Lighthouse agentic-browsing on homepage and contact page.

References