GenGrowth

GEO tools

GEO Knowledge Base

Keep your complete Profile copy, brand identities, audience roles, sourced facts and questions together. Review the complete candidate in Website Profile before freezing the exact version your GEO tools will use.

Edit the complete GEO knowledge base at the bottom of your Website Profile in Settings. This public address provides information and a shortcut, not another editor or a second knowledge base. All websites

What this does not do

  • Product fields are inherited from an exact confirmed Website Profile. Changes require review before the next freeze; previously frozen versions never change.
  • It does not fill in facts for you. An empty value with a reason is the honest state, and the brief generator relies on it.
  • GSC evidence requires the same signed-in Google account and a granted property. Without GSC, reviewed Profile or manual roles can still support problem and evaluation questions when their pain points or criteria are present. Unsupported layers are disclosed, not invented.
  • Question generation currently supports English. New semantic questions are uncalibrated demand questions; only separately identified, unchanged measured retrieval probes contribute to calibrated citation metrics.

Questions about the knowledge base

Why does freezing matter?
A visibility run points at a frozen version. If the knowledge base could change underneath it, two runs would not be comparable, and the report could not say which names it was matching on. Freezing is what makes "the same question set, asked again" a true sentence.
How are generated questions different from calibrated retrieval probes?
Semantic questions use your reviewed roles, pain points, criteria and source evidence, and you inspect them before freezing. They are uncalibrated and do not enter calibrated citation metrics. Measured retrieval probes remain a separate, clearly identified cohort. Freezing saves the exact reviewed question set rather than generating it again.
Why must a competitor's name be confirmed separately from its domain?
A model writes "Linear", not "linear.app". Counting a mention needs the name; knowing where a citation points needs the domain. An unconfirmed competitor stays in the list and out of the share figures, and the report names it as excluded.