Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.haloxlabs.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Share progress with Weekly Reports

Weekly Report turns GEO operations into a regular reporting cadence. It summarizes AVI, SEO, GEO changes, site issues, content execution, and next actions.
HaloX Weekly Report

​
What the report is for

In meetings, the Weekly Report is closer to an operating agreement than a scorecard. It shows what changed, why it changed, and which feature/team/content task should move next.

Status

Summarize AVI, SEO, GEO, citation rate, and Web Health changes.

Cause

Separate search foundation issues, AI citation issues, and site-structure issues.

Action

Move next steps into Strategy Map, Site Audit, and Content Factory.

Cadence

Track the same strategic question sets every week so trends are visible.
ItemWhat to readNext action
AVI/SEO/GEO changeDid search and AI visibility improve or decline?Identify the weakest axis
Citation rateAre your own assets cited in AI answers?Inspect competitor/source patterns
Prompt coverageAre the important strategic questions monitored?Add or refine prompt sets
Site issuesWhat technical or structural issues matter this week?Split developer action items
Content executionWhich clusters moved into content production?Update Content Factory and Strategy Map
Next actionsWhat should be fixed, created, or checked next week?Assign owner and deadline

​
Audience-specific reporting

AudienceEmphasizeAvoid
ExecutivesAVI Overall Score, risks, competitor gaps, next actionsLong keyword lists without decision points
CustomersWork completed, issues found, content opportunities“The score went up” without explanation
MarketingStrategy Map clusters, Content Factory tasks, prompt changesChoosing work by volume only
DevelopersSite Audit critical issues, performance, accessibility, schemaTreating all content performance as a dev issue
PR/BrandHow media, owned pages, and external sources appear in AI answersTreating AI answers as simple reputation monitoring

​
Reading workflow

1

1. Write the one-line weekly conclusion first

Example: “Citation improved, but competitors are taking more source positions for non-brand questions.”
2

2. Explain only the metrics that moved

Do not narrate every number. Focus on the changes that affect the decision.
3

3. Attach evidence by screen

Use Dashboard for score movement, Citation Tracking/Site Audit for causes, and Strategy Map/Content Factory for action.
4

4. Limit next actions to three

Split technical fixes, content work, and prompt-set changes by owner.

​
Reporting examples

This week, brand visibility in AI answers remained stable, but cited source share moved toward competitors for several non-brand questions.
The risk is not immediate traffic loss; it is losing evidence positions inside AI comparison and recommendation answers.
Next week, we will strengthen three non-brand clusters and assign structured-data fixes from Site Audit.