GEO
GEO Docs

Troubleshooting

How to diagnose an unchanged head, unmatched rules, wrong hreflang, failed JSON-LD validation and other common issues.

The head does not change

  1. Open Sites → SDK setup in the console and confirm the last heartbeat is within 5 minutes; no heartbeat means the script did not load or the key is wrong
  2. Check GET /sdk/config in the browser devtools: NOT_FOUND means a wrong key, 403 means the current origin is not allowlisted
  3. In fill mode existing fields are not overwritten; switch to replace if you need that

Rule not matched

  • Use SEO head rules → Preview with the real path to verify matching
  • Path patterns are case-sensitive; on sites with a language prefix do not include the prefix in the pattern (the SDK strips it first)
  • When several rules match, the highest priority wins, so check the numbers

hreflang points at a 404

The language has no page yet or the translation is unfinished. Enable auto translate for that language, or disable it temporarily in site languages.

JSON-LD validation fails

  • Use the validation panel next to the editor to find missing properties
  • Fields whose variable such as {cover} is empty are omitted; provide the variable if the field is required
  • datePublished must be ISO 8601; use {publishedAt | date:ISO}

Title not updated after SPA navigation

Make sure data-spa is not off. If your framework manages document.title itself, switch the SDK to replace mode or call geo.page() after navigation completes.

Events are not counted

Events use sendBeacon and fail silently when blocked by browser extensions; the head update is unaffected. Counts are aggregated, not real time.

Getting help

Send the site public key, SDK version and recent errors from SDK setup → Debug info to the support team.