GEOmatic Local Business — Profile, JSON-LD & Robots

What this page is for #

AI Local Business centralizes four essentials: API providers, your public business profile (NAP), robots & front-end AI features, and a read-only JSON-LD preview. It also includes quick links to Cockpit, Insights, Experience and Debug, so you can configure once and review results anywhere.

Quick navigation (top shortcuts) #

Buttons at the top jump to each block: API, Local, Robots, JSON-LD, plus one-click links to AI Cockpit, AI Insights, AI Experience and Debug for faster workflows.

1) API Providers (keys, primary, tests) #

Connect your AI providers in one place:

• Key fields for OpenAI, Anthropic (Claude), Perplexity, Google (Gemini) and You.com. For all but You.com, you’ll see a Test button to verify the key instantly.
• Primary provider dropdown — choose the provider used first; others act as automatic fallbacks if the primary fails.
• OpenAI Project ID (optional) — when filled, the page sends an OpenAI-Project header with calls; this can resolve some 401 “no such project” errors.
• Save settings — apply changes with one click; a small success toast confirms.

Built-in guardrails (non-technical):
If someone accidentally pastes an API key into the Project ID field, the page quietly moves it to the correct key field, clears the wrong value, and shows a brief toast. It also strips invalid OpenAI-Project headers on the fly to prevent 401s.

2) GEO Local Business (your public profile) #

Fill your Name, URL, Phone, Street, Postal code, City, Country, Latitude/Longitude, Map URL, Service areas. The Name is required; placeholders help you get formats right. The list of service areas is used for areaServed in your structured data.

These fields power the site-wide LocalBusiness JSON-LD and help AI/search systems understand who you are and where you operate.

3) Robots & Features (policy + front signals) #

Fine-tune how AI agents may use your content and what front-end AI signals are injected:

• Robots controls
  • noai — disallow AI usage of text.
  • noimageai — disallow AI usage of images.
  • GEO noindex for AI-sitemap — adds an X-Robots-Tag on /ai-sitemap.xml.
• Front-end AI signals
  • Inject JSON-LD — output AI hints & schema.
  • AI-Sitemap — maintain /ai-sitemap.xml.
  • Entity linking — enable a lightweight “You may also like” block for internal meshing.
  • Image ALT — auto-fill alt text on upload.
• Maintenance actions
  ⏱️ Check WP-Cron, 🔄 Sync CRON, ⚡ Run AI jobs now — quick operational buttons with inline notices. A small, persistent message below confirms automation is running, so editors can keep working.

4) JSON-LD Preview (read-only) #

Preview the site-wide LocalBusiness JSON-LD generated from your profile. Individual pages may automatically add Article / WebPage / FAQ where relevant. You’ll also see action buttons to generate, validate, pause or clear the JSON-LD (the preview itself remains read-only).

Friendly help (“i” modals) #

Each card has an “i” button that opens a short, plain-English explainer (no code). The modals cover API Providers, Local Business, Robots & Features, and JSON-LD.

Validate configuration (one-click checklist) #

At the bottom, a ✅ Validate configuration button runs quick UI checks (e.g., missing Business name or missing primary provider key), pings WP-Cron, and runs a provider test. Results show as toasts and sync with the small status bar at the top.

Typical workflow this page enables #

1. Enter your NAP details (and service areas) under Local Business. Save.
2. Connect providers, pick a primary, and (optionally) set OpenAI Project ID. Test keys. Save.
3. In Robots & Features, choose your policy (noai/noimageai) and enable front-end signals (JSON-LD, AI-Sitemap, Entity linking, Image ALT).
4. Validate configuration → watch the toasts/status bar.
5. Open JSON-LD Preview to sanity-check your site-wide schema; use actions if needed.

Buyer-friendly tips (non-technical) #

• Primary + fallback: choose a reliable primary provider; fallbacks reduce downtime automatically.
• Project ID is optional: only use it if your OpenAI account requires projects; the page prevents mis-configured headers anyway.
• Policy first: decide noai/noimageai up front; you can change later without touching code.
• Keep lat/lng + map: precise location and a map URL improve clarity for assistants and maps.