Website visit
A visit to your website.
/running-shoes
Website Traffic in the AI Era
Understand human visits, AI referrals and crawler activity.
See how people reach your website from AI services and which pages AI crawlers access. Connect activity, traffic sources and page context to understand what is changing.
Crawler request
Automated access to a page.
/guides/shoe-fit
ACTIVITY AND SOURCE
See the visit and its AI source together.
A person can reach your website through an AI service. Keep the visit classification and referral source connected so the team can understand both the activity and the channel.
Website visit
- Classification
- Human
- Source category
- AI referral
- Landing page
- /running-shoes
One visit, two useful pieces of context.
A CONNECTED WEBSITE VIEW
Put activity, source and page context in the same view.
Bring together what happened, where the visit came from and which page was involved. Use that context to move beyond an isolated traffic total.
Built for marketers and agencies interpreting website activity alongside AI visibility.
Activity details
- Observation
- Crawler request
- Activity classification
- AI crawler
- Requested page
- /guides/shoe-fit
- Page role
- Product advice
- Review focus
- Access to the shoe-fit guide
Keep the observation connected to the page it concerns.
WHAT TO EXPLORE
Find the activity behind the change in traffic.
Explore AI-referred visits, crawler requests and quality signals around the pages that matter to your business.
AI referral
- Source category
- AI referral
- Landing page
- /running-shoes
AI-referred visits
See which landing pages receive visits attributed to AI services and compare them within the same reporting period.
Crawler request
- Request
- Page access
- Requested page
- /guides/shoe-fit
Crawler requests
Review recorded AI crawler activity and the pages being requested. Keep automated access separate from visitor traffic.
Pattern to review
Repeated requests
- Page
- /guides/shoe-fit
- Context
- Similar request pattern
Quality signals
Inspect repeated or unusual patterns alongside page and source context to choose where a closer review is useful.
TURN CONTEXT INTO QUESTIONS
Ask a more useful question about each signal.
Use the type of observation to choose what to explore next. Referral sources, crawler requests and quality patterns lead to different questions.
| Observation | Useful context | What to explore |
|---|---|---|
| AI-referred visit | Landing page and source category | Which pages receive visits from AI services? |
| AI crawler request | Requested page and crawler classification | Which pages are being accessed by AI crawlers? |
| Repeated request pattern | Page and request context | Which pattern deserves a closer review? |
KEEP THE CONTEXT
Keep useful details visible when activity is unclassified.
An unclassified observation can still show the page and available source context. Keep those details together so the team knows where to look next.
Website visit
- Classification
- Unknown
- Source category
- AI referral
- Landing page
- /running-shoes
Next step
Review the activity and source details.
Unknown describes the activity classification, not a threat verdict.
USE THE TRAFFIC CONTEXT
Choose the next step for the page that matters.
Use source, activity and page context to decide what to examine next, whether you are reviewing acquisition, content access or an unusual traffic pattern.
- Action
- Review /running-shoes
- Question
- Does the page help first-time runners compare the range?
- Why now
- AI-referred visits point to this destination.
Review a landing page
Focus on the destination receiving AI-referred visits and check whether it serves the questions your audience brings.
- Action
- Inspect /guides/shoe-fit
- Question
- Is the guide current and easy to use?
- Why now
- Recorded crawler requests include this page.
Inspect a content page
Use crawler access as context for reviewing a content page and its role on the website.
- Action
- Review repeated requests to /guides/shoe-fit
- Question
- What explains the repeated access?
- Why now
- A recurring request pattern deserves a closer look.
Investigate a request pattern
Review the details of repeated activity before choosing a further response.
NEXT STEP
See what is happening around your website.
Explore AI referrals, crawler activity and page context with Travatar.