Questions answered.
Claims kept honest.

It is a signed-in question-level register that joins uniquely allocated search demand, the strongest crawled owner, fixed provider observations, configured-brand mentions, recommendations and citations, exact landing-page AI referrals, conversions and revenue. It labels the earliest actionable evidence gap and preserves every denominator.

No. Search impressions, fixed provider responses and GA4 sessions are different evidence populations. IndexHalo places them in a parallel chain for diagnosis but never multiplies them, converts search impressions into AI prompt volume or reports a universal stage-to-stage conversion rate.

Each imported search query-and-page row is allocated to one best-matching buyer question in portfolio totals. Similar questions can retain visible supporting matches, but they cannot each claim the same impressions and clicks.

It is the earliest missing observable stage for a buyer question: credible owner, monitoring, mention, recommendation, citation, connected outcome evidence, identifiable referral or conversion. The state determines the recommended owner, production change and repeat test.

It separates awareness, consideration, decision and activation questions, then reports how many questions in each stage have a credible public owner and how much uniquely allocated search demand is represented. A missing stage becomes a research requirement before content is commissioned.

It means no current monitored or research question maps that URL as its best owner. The page is unclassified, not automatically irrelevant, low quality or removable. A strategist should connect it to a validated question, retain it for another purpose, consolidate it, or intentionally exclude it.

The free report includes the overall readiness score, six measured signal scores, top evidence findings, four disclosed evidence-readiness lenses, and the highest-priority actionable recommendation. It does not spend paid live-model calls, and no card is required.

The signed-in workspace adds whole-site crawling, page-level inventory, buyer-question demand research, retained customer-supplied or authorized answer observations, AI Share of Voice and Recommendation Intelligence, passage retrieval testing, an evidence knowledge graph, measured AI-referral revenue attribution, longitudinal citation and brand-narrative observatories, evidence-backed implementation briefs, a commercial impact portfolio, controlled experiments with frozen baselines, scheduled monitoring, historical comparisons, server-log crawler evidence, full recommendations, OCR, Intelligence Hub history, CSV and JSON exports, and printable reports.

For each monitored buyer question, IndexHalo recommends whether to create, consolidate, strengthen, or protect an owning page. The brief includes the measured baseline, exact page purpose and outline, evidence specification, entity and internal-link plan, truthful metadata checklist, current page findings, definition of done, and repeat-measurement tests. Imported demand, competitor benchmarks, provider observations, crawler logs, and workflow state are included only when connected.

No customer AI connection is required. The brief engine deterministically combines the latest measured crawl with the fixed buyer-question portfolio and any connected measured evidence. Forecasts are explicitly labelled as modelled planning estimates, not promised traffic or citations.

Signed-in reports can be downloaded as JSON and printed or saved as PDF. AI Share of Voice, citation intelligence, brand narrative evidence, buyer-question research, answer-passage evidence, the evidence knowledge graph, AI-referral revenue attribution, operational alerts, the controlled experiment register, and the commercial impact portfolio can also be downloaded as CSV. Website monitoring preserves dated snapshots for comparison.

Yes. Signed-in reports can import CSV exports from Google Search Console, Bing Webmaster Tools, and Google Analytics 4. IndexHalo maps measured impressions, clicks, CTR, position, users, conversions, and revenue to crawled pages and buyer questions, then ranks concrete opportunities. Customers do not provide API keys.

It is a signed-in report that classifies only GA4 rows whose supplied session source, source / medium, referrer or campaign explicitly identifies an AI answer product. It reports measured sessions, engagement, conversions and revenue by provider and landing page, then joins landing pages to crawl, passage and claim evidence.

No. Direct, unattributed, organic, unknown and not-set rows are never redistributed across AI providers. The report intentionally understates influence when the source is unavailable rather than inventing a larger attribution number.

No. A referral is measured analytics evidence; a citation is a separate timestamped provider observation. IndexHalo can display them beside each other as an observable funnel, but it does not claim that one caused the other.

Include landing page, session source or session source / medium, sessions, engaged sessions, key events or conversions, and revenue. Full referrer, channel group and campaign are useful supporting dimensions. Add a dated window and use the same dimensions for later comparisons.

Only when a previous GA4 import exists and both imports contain dated windows of equivalent length within one day. Otherwise it shows the current measured values and withholds the comparison.

No. It shows revenue recorded on sessions explicitly identified with an AI answer-product source in the supplied export. It is not universal multi-touch attribution and does not prove that GEO work, a citation, or any single content change caused the conversion.

For each measurement source, the newest import is the current reporting window and the prior import is used for change comparison. The report labels these values as imported measurements and keeps them distinct from observed citations and modelled readiness scores.

It ranks evidence-backed GEO work by strategic gap, uniquely allocated search demand, confidence, implementation effort, and commercial value. Each row contains the buyer question, target page, measured baseline, conservative, base and upside scenarios, cost, formula, confidence factors, decision, and workflow state.

IndexHalo models additional visits from measured monthly impressions and a visible fraction of the gap between measured CTR and the saved target CTR. It values those visits using measured GA4 revenue per session when available, otherwise explicit conversion assumptions. Contribution uses the saved margin and implementation cost uses saved effort and hourly-cost inputs. Every input and formula is shown.

No. Visit lift, monetary value, ROI, and payback are clearly labelled planning scenarios. They are conditional on measured baselines and visible assumptions. IndexHalo does not convert readiness scores into revenue or present a forecast as an observed outcome.

IndexHalo can still model additional visits where measured search demand exists, but it withholds revenue, ROI, and payback. Import GA4 revenue or save explicit conversion-rate and value assumptions to add a monetary business case.

Every normalized search query and landing-page row is allocated to the best matching monitored buyer question once. Overlapping briefs cannot each claim the same demand. The original allocated rows remain visible and exportable for audit.

The report orders work by evidence priority, commercial case, and confidence, then allocates estimated effort against the saved monthly capacity. Work that fits the first capacity window is marked now, the second window is next, and the remainder is later.

Signed-in reports can be downloaded as JSON or Markdown, exported as a CSV of the page inventory, and printed or saved as PDF. Accounts with branding configured add the white-label client export. Website monitoring also preserves dated snapshots for comparison.

Start with access failures and high-value pages, assign the recommended owner, implement the target condition, then recrawl and verify the stated test. Repeatable evidence matters more than the headline score alone.

The saved task keeps the exact question, affected URL and thresholds. A later crawl and unchanged provider run must confirm the owner, mention, recommendation and citation targets; when analytics is connected, the next equivalent outcome evidence must also meet the saved conversion threshold. Each evidence source remains separate.

Yes. A topic action preserves its exact questions, affected pages and completion thresholds. After a later crawl, IndexHalo evaluates operational ownership, average page readiness, source-ready coverage and internal support. Controlled experiments require the same topic identifier and question fingerprint before classifying score movement.

The later run must use the same question set, provider set and configured brand universe. A saved task can require the target to rank first, receive a minimum number of recommendation labels and lead the next brand by at least ten measured index points. Failed responses remain unavailable rather than becoming negative evidence.

No. It proves only that the exact public link present in the prior crawl is absent from the current page. A human reviews the claim, current primary evidence and reason for the change before restoring, replacing or removing anything.

A fresh crawl must find a safely parseable explicit date within the saved content policy, the required number of source links for claim-bearing content, and no saved DATE_MISSING or SOURCE_GAP finding. Updating a date alone cannot pass when the evidence remains weak.

It compares matched URLs across repeated bounded public crawls and records pages added or removed plus measured changes in score, words, claims, sources, headings, links, authorship, dates and schema. It reports the change without inferring competitor intent or commercial impact.

IndexHalo reruns the unchanged buyer-question set against the configured public domains. The saved acceptance test can require the target to rank first, retain one canonical owner, reach a minimum relevance lead and satisfy exact evidence conditions. Changed denominators remain a new benchmark rather than a rewritten win.

The task stores the original cohort dimension and key, issue code, maximum acceptable prevalence and minimum average score. A later whole-site crawl rebuilds the cohort and verifies the complete saved threshold. Passing one example page cannot automatically close the estate task.

It is a signed-in before-and-after evidence register for every changed public URL. It preserves exact crawl fields, findings, claims and sources; exact-page citation movement when question and provider sets match; bracketed equivalent-period search and analytics outcomes; linked workflow history; and a keep, revise, investigate or selective-rollback decision with an acceptance test.

No. It reports an observed association between public page states and later evidence. Seasonality, demand, campaigns, competitors, provider changes, tracking and concurrent releases may also affect citations or business outcomes.

A normal crawl proves only that a public change occurred between two snapshot timestamps. A CMS or deployment trigger can provide useful workflow context, but the report keeps the observed crawl window visible and does not invent an exact author or publish time.

Only when dated imported periods sit on opposite sides of the observed release window and are equivalent in length within one day. Non-bracketing or unequal periods remain visible as unavailable or not comparable rather than being used to claim impact.

A material readiness decline, a new high-severity finding, a comparable exact-page citation loss, or a material decline in a bracketed outcome can trigger investigation. IndexHalo recommends a selective evidence-backed rollback and human review; it does not automatically change the website.

No. It identifies the exact changed fields, source, claim, access condition or metadata that needs review, assigns an owner and defines the next recrawl test. A human release owner decides and performs any production change.

Yes. Signed-in website reports convert ranked findings into a persistent action queue inside the Intelligence Hub. Teams can add an assignee, due date, implementation evidence, and workflow status while preserving the original measured finding, definition of done, affected pages, and verification rule.

It is a signed-in Intelligence Hub view for turning a prioritised workstream into a controlled before-and-after measurement. IndexHalo freezes the target page, question portfolio, crawl snapshot, evidence source sets and primary threshold, then automatically evaluates later comparable evidence.

No. A user can choose the workstream, hypothesis, primary metric, threshold, owner, review date and notes before measurement. The frozen baseline and calculated outcome cannot be manually edited. The experiment can be paused or cancelled without deleting its history.

The applicable guardrails require the same buyer-question portfolio, target page, search source set, provider set and competitor set, plus search periods of comparable length. IndexHalo shows every guardrail and refuses to classify changed evidence as a win.

No. A positive outcome means the comparable primary metric met the threshold saved at baseline. It supports an association between the bounded intervention and later movement, but it does not prove the intervention was the only cause or guarantee future results.

IndexHalo labels the evaluation not comparable and identifies the failed guardrail. The defensible next step is to begin a new experiment from the changed state rather than rewrite the original baseline.

For CTR and citation proportions, IndexHalo reports a two-proportion z diagnostic and a 95% difference interval. It also requires a minimum sample before labelling movement statistically reliable, so a threshold result can remain explicitly directional.

Yes. Signed-in website reports maintain a persistent incident centre across crawl health, timestamped citation observations, public competitor benchmarks, declared-crawler server evidence, imported performance, content ownership, and workflow verification. Secure crawler events can update the underlying evidence immediately; scheduled crawls and new imports update their respective alert layers.

Every alert records severity, priority, category, evidence class, supporting evidence, affected URLs, exact response, automatic resolution test, recommended owner, assignee, response target, first and last detection time, recurrence count, investigation note, and event history.

No. A user can acknowledge, assign, annotate, or return an alert to open investigation. Resolution occurs automatically only when the latest connected evidence no longer meets the disclosed rule. If the condition returns later, IndexHalo reopens the same durable alert and preserves its history.

Yes. Signed-in users can download the complete active and resolved operational alert register as CSV. The full website JSON and printable report also include the Intelligence Hub alert history.

When a task is marked ready to verify, IndexHalo requests the next matching evidence source: a fresh website crawl, competitor benchmark, or later crawler-log event. It evaluates the recorded completion rule, records whether the task passed, failed, or later regressed, and preserves the supporting evidence. A user cannot manually label an action as automatically verified.

The platform can compare scores, discovered and failed pages, status and canonical changes, extracted evidence, source links, and live citation observations. The interface surfaces material changes rather than a meaningless raw HTML diff.

Weekly is a useful default for active publishers. Daily suits fast-changing news, product, or launch environments; monthly may suit stable reference material. Run an extra crawl after migrations or major template changes.

It is a signed-in operating map that groups the monitored and evidence-backed buyer-question universe into strategic subjects, then joins each topic to public page owners, allocated search demand, answer-ready passages, claim-to-source support, hub-and-spoke links, freshness, observed citations and configured-brand AI market presence when those layers are available.

The disclosed score weights question ownership at 20%, mapped-page readiness at 15%, answer-ready passages at 15%, evidence support at 15%, hub-and-spoke internal authority at 10%, explicit freshness at 5%, observed citations at 10%, and measured configured-brand AI market presence at 10%. Unavailable optional layers are removed and the remaining weights are normalized.

No. It is an IndexHalo planning score for the exact monitored question and page map. It is not a search-engine or LLM ranking factor, backlink metric, universal authority score, prompt-volume estimate, proof of training inclusion, or guarantee of citation.

Yes. Strategic topics and buyer questions preserve Unicode and can be entered in major commercially relevant languages. The deterministic map uses language-aware terms, while page evidence, authorities, regulation, currency, terminology and buyer criteria remain local to each market.

It is a signed-in multi-brand measurement layer built from timestamped verified response text, exact configured brand aliases and returned citation domains. It reports mention, recommendation, citation and first-choice share by portfolio, provider and buyer question, then creates actions with repeatable acceptance tests.

Without the exact brands, questions, providers, timestamps and successful-response count, a percentage cannot be reproduced or compared. IndexHalo preserves that universe and excludes changed runs from movement rather than presenting them as progress.

A mention names the configured brand in response text. A recommendation is a disclosed multilingual lexical label where a brand appears in recommendation language. A citation is an exact configured domain in returned sources. First choice is the earliest recommended configured brand in that response. None automatically proves endorsement or causation.

The disclosed index weights mention share at 35%, recommendation share at 35%, citation share at 20% and first-choice share at 10%. A signal with no observations anywhere in the configured market is removed and the remaining weights are normalized; all component shares and counts stay visible.

No. It describes only the configured brands, fixed questions, successfully verified responses and provider set. It is not prompt volume, total audience reach, revenue share, training inclusion, private model preference or general market share.

Competitors come from domains deliberately configured for the monitored website. IndexHalo uses exact domain matches in citations and conservative aliases derived from the configured domain or measured public title. Ambiguous aliases are rejected and the final brand universe remains visible.

Yes. IndexHalo preserves original Unicode questions and responses and applies disclosed multilingual recommendation and stance rules across the platform's supported languages. Local brand spelling, evidence, regulation, pricing, units and review still require the appropriate market owner.

It is a signed-in renewal layer that evaluates explicit public review dates, content-specific review policies, claim support, exact source-link movement, page findings, imported outcomes and exact-URL citation evidence. It creates a prioritised calendar and verifiable renewal actions.

No. IndexHalo calculates review age only from safely parseable structured or meta publication and modification dates. Years found in body text remain content signals and are never promoted into review-date evidence.

No. Missing explicit date evidence is labelled freshness unverified. The action is to complete a genuine review and expose a matching visible and structured date, not to manufacture a date merely to improve a score.

The disclosed operational defaults are 120 days for volatile decision content, 365 days for research and claim-dense evidence, and 730 days for standard evergreen content. These are planning controls; legal, medical, financial or editorial teams may require stricter policies.

Yes. Exact original-language claims, titles, URLs and source evidence are preserved across the platform's sixteen supported languages. Multilingual rules help assign content policy, while regional evidence, terminology, law, currency and review remain human responsibilities.

It is a signed-in public-site comparison layer that ranks every configured domain for the same fixed buyer questions, calculates monitored ownership share, compares the exact mapped pages, recommends create, strengthen, consolidate, defend or protect, and stores an acceptance test for the next identical benchmark.

No. It is the percentage of the saved buyer-question set won by a domain inside the successfully crawled comparison set. It is not general market share, search share, traffic, revenue, provider share of answer or a private model ranking.

Create is recommended only when the target lacks a credible owning page. If a relevant target page exists, IndexHalo strengthens it. Multiple close target pages trigger consolidation; a material target lead triggers protection; a narrow lead triggers defence.

No. It compares observable public-page fields such as claims, sources, headings, internal links, authorship, dates and structured data. These differences guide production work but do not reveal a provider's private retrieval or ranking system.

No. Competitor analysis uses bounded public-page crawls and respects authentication, paywalls, robots policies and private-network protections. Failed or inaccessible crawls remain unavailable instead of becoming invented scores.

It is a signed-in portfolio-analysis layer that facets every measured page by first URL directory, analysed language, declared or conservatively inferred content type, and recurring structural pattern. It calculates cohort readiness, risk prevalence, source coverage, outcomes, exact-URL citation evidence, movement and system-level actions while retaining every affected URL.

No. A structural cohort groups pages with the same observable combination of authorship, dates, schema, source count, claim density, length and heading depth. It is a diagnostic similarity group, not proof of shared code, CMS components, ownership or release history.

Directory, language, content-type and structural views are overlapping facets. One URL can appear once in each dimension. IndexHalo keeps the unique site page total separate and never adds facet counts together as additional pages or opportunity.

The disclosed priority uses measured readiness, high-risk rate, leading-issue prevalence, cohort size and connected imported demand or value. A repeated finding must clear a multi-page prevalence threshold before it becomes a system-level action.

Yes. Language is one measured facet, and exact original-language pages, claims and evidence remain visible. IndexHalo does not require identical wording and does not infer that an absent language is a market opportunity. Regional evidence, law, currency, terminology and review remain local responsibilities.

The score summarises six disclosed signal groups: retrievability, authority, specificity, structure, freshness, and transparency. It is a prioritisation aid, not a private model ranking or a guarantee of citations.

Direct findings can include response status, readable text, headings, authorship, dates, canonical metadata, structured data, quantitative claims, source links, crawler rules, redirects, and document extraction results.

A modelled estimate is a clearly labelled planning projection calculated from measured content, demand, cost, or conversion inputs. It is kept separate from archived answer observations and is never presented as a provider response, private ranking factor, or guaranteed outcome.

It is a timestamped provider response for a stored query, including the returned citation URLs, target-domain position, and competing domains. It proves what that response returned at that time and nothing more.

No independent GEO tool can reliably prove inclusion in undisclosed private training data. IndexHalo does not make that claim. It can document public crawl conditions and citations that appear in observable provider responses.

No. Search and answer systems change, personalise results, and evaluate many competing sources. IndexHalo identifies controllable gaps and verifies implementation, but it does not promise a future vendor decision.

Using the same declared question across compared sources improves comparability. Differences in answers, mentions, citations, and rank are interpreted only inside that retained question, source, locale, and time scope.

It is a signed-in longitudinal Intelligence Hub view built from timestamped verified provider responses. It tracks citation coverage, returned-source share, target position, query and provider movement, source gains and losses, volatility, convergence, concentration, and exact recovery or protection actions.

It is a signed-in source-network Intelligence Hub view built from timestamped verified provider responses. It maps returned domains to questions and providers, scores bounded source authority using disclosed factors, identifies configured competitors and source types, and turns question-level source gaps into exact actions and repeat tests.

No. It uses appearances, provider reach, question reach, run persistence and movement only inside the monitored response set. It does not measure backlinks, traffic, trust, expertise, reputation or general web influence.

No. Answer Source Intelligence preserves and analyses the exact returned URLs and domains. Public target and configured competitor sites are crawled through separate bounded workflows. A returned source must be reviewed before a team relies on it.

A domain is labelled a configured competitor only when the customer included it in the separate public-site benchmark and the same domain appears in verified provider evidence. Other commercial domains remain external sources rather than assumed competitors.

It means producing genuinely useful, independently verifiable evidence—such as an original dataset, transparent method or named expert context—and making it available for legitimate editorial review. IndexHalo does not recommend buying, fabricating or implying endorsements or citations.

No. Repeated appearance is an observable pattern in a fixed test set, not proof of accuracy, trust, endorsement, traffic, backlinks or causal influence. Review the source, exact URL, claim, date, method and limitations before acting.

It is a signed-in Intelligence Hub view that segments stored verified answer text into exact statements, compares semantically related claims across providers, extracts values, maps statements to measured owned-page claims, and identifies shared claims, numeric disagreement candidates, provider-specific statements and bounded omissions.

No. Agreement shows that multiple verified responses expressed a similar statement in the fixed test. Providers may repeat the same stale or incomplete information. Teams must verify the statement against current primary evidence before relying on it.

No. Different values create a verification candidate. The values may use different years, markets, populations, units, scenarios or methods. IndexHalo preserves every exact statement and source URL so a research owner can resolve the scope.

A provider omission means a shared statement cluster did not appear in one comparable response. An owned-evidence omission means a measured claim on the mapped owner was not reflected in the verified answer set. Neither state proves suppression, provider failure or deliberate exclusion.

Only when the provider returns durable inline attribution. Otherwise IndexHalo labels the URLs as response-level citations and does not claim that one source supports every answer sentence.

Yes. It uses Unicode sentence segmentation, language-aware tokenization and the platform’s sixteen supported language profiles. Exact original-language wording remains visible, and fluent human review is required for high-risk interpretation.

It is a signed-in Intelligence Hub view that separates exact brand naming from citations, recommendation context, lexical stance, observed attributes, provider differences, narrative movement, and statements that require factual review. Every label points to a stored response excerpt, query, provider, and timestamp.

No. IndexHalo reports named-and-cited, named-without-citation, cited-without-name, and neither as separate states. Recommendation language is measured independently because a mention alone is not an endorsement.

No. Numeric, dated, absolute, comparative, or configured risk statements become verification candidates. A human compares the exact excerpt with current canonical evidence before deciding whether any correction or clarification is needed.

Yes. Exact configured aliases work across Unicode text, while disclosed recommendation, stance, and attribute lexicons cover the platform’s major supported economic languages. The original provider excerpt remains visible so a fluent reviewer can validate every rule-based label.

Movement requires the same versioned buyer-question portfolio and provider set. Runs with changed denominators or no verified response text remain stored but are excluded from the trend with an explicit reason.

It is a signed-in Intelligence Hub view that combines the fixed monitoring portfolio, imported Search Console or Bing demand phrases, question-form headings from the measured website, and explicitly labelled deterministic evidence-question suggestions. It maps each candidate to intent, journey, demand, page ownership, provider evidence, public competition, action, and verification.

No. Imported impressions measure exposure in the supplied search-platform period. IndexHalo never relabels them as model queries or total AI demand. Provider observations remain a separate evidence layer with their own exact denominators.

Question-level fuzzy matches remain visible, but every imported query and landing-page row is allocated to one best candidate for portfolio, intent, and market summaries. The CSV export retains the evidence needed to audit that allocation.

A signed-in user can promote a recommended question into the fixed portfolio. IndexHalo versions the question set and requests a fresh crawl and provider baseline. Earlier runs remain stored but are excluded from comparisons that require the old denominator.

Yes. It can use the existing monitored portfolio, question-form language found on crawled pages, page evidence, and explicitly labelled deterministic suggestions. Demand and trend remain unavailable until Search Console or Bing evidence is imported, so confidence stays lower.

It is a signed-in passage-level audit that tests the exact bounded public text available for each buyer question. It preserves the excerpt, page, section, language, evidence links and component scores, then classifies the result as answer-ready, unsupported, fragmented, missing or internally competing.

No. A high score means IndexHalo could isolate a useful answer unit from the measured public page using its disclosed formula. Only a stored timestamped provider response can show that a provider returned a citation in that particular observation, and neither result proves training use.

The disclosed formula weights question relevance at 30%, answer completeness at 20%, visible provenance at 20%, factual specificity at 15%, self-containment at 10%, and dated freshness at 5%. The report exports every component and the exact passage.

It retains the runner-up for every buyer question. When similarly relevant passages on different pages sit within the disclosed threshold, the report flags an internal conflict and prescribes one canonical owner, consolidation or deliberate differentiation.

Yes. Passage fingerprints are compared across crawl snapshots. If a previous answer-ready unit changes, moves, loses support or no longer meets the thresholds, the Professional incident centre can create a retrievable-answer-loss alert with the former and current evidence.

It is a signed-in site-wide map of measured relationships between public pages, material claims, adjacent or page-level source links, authors and parsed JSON-LD entities. It exposes unsupported claims, source concentration, identity inconsistencies, potential numeric conflicts and evidence changes between crawls.

No. Related claims on different pages with different extracted values become verification candidates. The report preserves both exact claims, pages, values, similarity and support evidence so a qualified reviewer can determine whether one is obsolete or whether differences in period, geography, sample, method or unit explain both.

Adjacent evidence is an external source link published inside the passage that most closely contains the material claim. Page-level evidence exists elsewhere on the same page, so the relationship to that exact claim is weaker. Unsupported means neither relationship was found.

It compares visible authorship with structured authors, checks whether accountable content names a publisher, and groups JSON-LD entities by normalized name to find conflicting @id values, incompatible types or repeated entities without a stable identity reference.

Yes. Comparable crawl snapshots preserve claim and support fingerprints. If the same public claim moves from adjacent support to page-level or unsupported, IndexHalo can create a durable evidence-loss alert with the affected page and an automatic recrawl condition.

No. Citation coverage and returned-source share describe the fixed questions, providers and timestamps in the monitored sample. IndexHalo publishes the denominator and does not present those observations as universal AI market share.

The disclosed index combines 50% observed citation coverage, 30% position-weighted presence, and 20% target share of returned citation appearances. The report keeps all component metrics visible, because the index is a summary rather than an external ranking.

A provider error is unavailable evidence, not a negative citation result. IndexHalo reports attempted and verified checks separately and does not turn an incomplete response into 'not cited'.

Longitudinal movement requires the same versioned buyer-question portfolio and provider set. Runs with a different denominator or no verified evidence remain in history but are excluded from movement calculations with a stated reason.

Source convergence is the overlap between domains returned by different observed providers for the monitored questions. It helps identify evidence patterns shared across providers, but does not imply a private vendor relationship or prove why a source was selected.

Recommendations combine the observed gap, number and value of affected pages, expected signal impact, implementation effort, and confidence. Workspace actions include an owner, current state, target state, and verification test.

Yes. Signed-in users can add up to five competitor domains. IndexHalo crawls their public pages with the same bounded measurement engine, compares evidence signals and buyer-question ownership, identifies the strongest public competitor pages, and creates a displacement plan without requesting a customer API key.

No. It is a transparent content-relevance comparison across the public pages IndexHalo crawled for the fixed question set. The report identifies the domains, URLs, relevance values, crawl limits, and date; it does not mislabel that evidence as a private external ranking.

It is a signed-in report that groups the crawled inventory by language, measures readiness and commercial evidence per language, audits declared hreflang relationships, compares explicit locale sets for evidence parity, and creates market-specific actions with recrawl tests.

No. A supported language with no measured page is labelled not observed. Market entry requires business demand, legal, operational and commercial analysis beyond a website crawl.

It tests missing self-references, inaccessible or uncrawled alternate targets, declared-language mismatches, missing reciprocal return links, unsupported codes and missing x-default in an existing multilingual alternate graph.

No. It means comparable decision usefulness, answer completeness and evidence quality. Claims, law, currency, dates, terminology, methodology and sources must remain locally appropriate.

Yes. Imported search demand and explicitly identifiable AI-referral outcomes are joined to the language of their landing page. The figures remain separate measured evidence layers and are never redistributed across markets.

IndexHalo is GEO intelligence software that analyses public websites, individual pages, pasted text, uploaded documents, and supported images. It measures observable citation-readiness signals and can join customer-supplied or authorized answer observations to evidence-linked recommendations.

It is designed for marketing, communications, SEO, research, journalism, economics, publishing, product, and business teams that need to understand how clearly their material can be discovered, retrieved, verified, and cited.

No server-side model key is required. Customers can supply answer evidence they already hold or authorize a supported browser session; any provider subscription or usage cost belongs to that customer, not IndexHalo. Each accepted answer retains its source, question, timestamp, and citations.

Yes. Paste a draft or upload a supported document to receive an estimated citation-readiness assessment and recommendations before publication.

Yes. Professional accounts can crawl same-domain pages across a site, using sitemaps and discoverable links, then produce a page inventory, site-wide metrics, failures, and prioritised actions.

Yes. Professional monitoring supports daily, weekly, or monthly recrawls, dated snapshots, and change comparison. Answer observations run only through a supported customer-authorized source; unavailable sources remain explicit.

Yes. Whole-site crawling reads public crawler guidance, stays on the submitted domain, rejects private-network targets, limits page and response size, and records blocked or failed pages instead of hiding them.

It can read declared XML sitemaps and follow same-domain links from reachable pages. The report distinguishes discovered, analysed, redirected, blocked, duplicate, non-content, and failed URLs.

The current evidence crawler focuses on safely retrievable server responses and document structure. Heavily client-rendered content may expose less evidence than a server-rendered or progressively enhanced page, and the report records that limitation.

IndexHalo is designed for public material and deliberately rejects private-network destinations. It does not bypass authentication, paywalls, or access controls.

Yes. Signed-in reports accept common Apache or nginx logs, CSV, JSON, and NDJSON exports and can receive sanitized real-time crawler events through a rotating per-site secret. Recognized requests are mapped to the crawled page inventory, response errors, coverage gaps, and verifiable actions.

No. The crawler-evidence pipeline discards IP addresses and the raw log body before saving the normalized evidence. It retains only the request time, method, same-site URL or path, HTTP status, response-byte count, declared user agent, and crawler classification.

Not by itself. User-agent strings can be imitated. IndexHalo labels this as a request declaring the named crawler and does not present it as independently verified network identity, model training, citation, or downstream use.

The website accepts PDF, DOCX, TXT, Markdown, CSV, JSON, HTML, PNG, JPG, WEBP, and TIFF files up to the displayed upload limit.

Yes. When a PDF contains little or no extractable text, OCR processes its rendered pages and records the extraction path so the result is not confused with native document text.

No. OCR quality depends on resolution, contrast, language, layout, and scan quality. Important findings should be checked against the original document, especially when numbers or tables are involved.

IndexHalo detects and analyses English, Chinese, Spanish, Hindi, Arabic, Portuguese, French, German, Japanese, Korean, Italian, Russian, Indonesian, Turkish, Dutch, and Polish. For scanned PDFs and images, select the document language so the matching bundled OCR model is used.

Original uploads are processed for the requested analysis and are not retained as a customer document library. Generated report data may be stored for signed-in report history according to the privacy policy.

No. A free single-content report can be run without payment. An account is needed to preserve report history, hold observation credits, and use whole-site monitoring.

Yes. Accounts support password reset links when transactional email is configured and a private recovery-code route that does not depend on an external identity provider.

IndexHalo sells prepaid observation credits: 100 credits for $5 or 1,000 credits for $10. A completed Google Organic scan uses one credit and Google AI Mode uses two. Stripe Checkout shows the final one-time amount before purchase.

No. Credit top-ups use one-time Stripe payments with no recurring charge or automatic renewal. Credits remain in the account until used.

Monitoring is paused before paid infrastructure starts, the account is alerted, and execution remains stopped until the balance is topped up.

Stored account and historical report data are handled separately under the privacy and deletion policies. A verified refund may adjust unused credits but does not silently rewrite completed historical evidence.

No. IndexHalo does not sell submitted content. The privacy policy explains the operational data used to provide reports, accounts, security, analytics, and payments.

Google Analytics is configured with Consent Mode and advertising storage remains disabled. Region-appropriate analytics defaults apply, and every visitor can accept or reject optional analytics from the website privacy banner.

The labels stop direct findings, live observations, and estimates from being blended into a misleading claim. Professionals can see exactly what supports each conclusion.

The answer-experience catalogue is versioned, and every archived answer records the declared target and returned model identifier when available. Target changes affect new observations only; historical answers keep their original identity so comparisons remain interpretable.

Yes. Answer engine optimisation (AEO) and generative engine optimisation (GEO) describe the same underlying work — making content easy for AI systems to retrieve, verify and cite — with slightly different emphasis. Every IndexHalo check applies to both, and the same is true if your team calls the practice LLMO, AI SEO or generative search optimisation.

No. GEO builds on technical SEO, information architecture, quality content, authority, and user experience. It adds passage-level evidence analysis, citation observations, and stronger provenance and measurement requirements.