Documentation
Improving visibility on your own domain
How the GEO Scout command center turns monitoring signals into concrete actions on your site: schema markup, content, and pillar pages with ready-to-use artifacts
Contents
1.Page optimization: turning appearances into citations
When a page already shows up in AI answers but isn't cited, the command center raises a "Improve this page" action. AI knows about the page but doesn't consider it relevant enough to link to. Fixing exactly that page is the fastest way to lift brand visibility and direct traffic: you convert an appearance into a citation where the engines are already interested.
- The command center is split across three tabs — "Site changes", "External publications", and "Publication plan" — with a type filter and a "Pending / Completed" switch. Actions are grouped ("Content", for example), and each card shows the providers where the page surfaced and an effort estimate
- The "Improve this page" action appears when a page has already landed in AI answers without being cited: the card states how many times that happened and which engines saw it
- Inside the card sits the "Prompts where the page wasn't cited" list with a closed-count. Those are exactly the queries the page needs to be reworked for — not an abstract "improve SEO"
- The "Optimize" button opens the content studio with the source page already filled in — from the brand's sitemap or entered manually by URL (the domain must match the brand's site) — plus the "Target queries" block. "Generation history" next to it keeps every previous run
- The agent works in real time and shows its steps: load brand → scrape page → AI rewrite (the LLM rewrites the page and generates an FAQ and a schema bundle) → save to history
- The result opens with the "Optimization strategy": a short summary of what changes and why, plus the number of edits by priority — Critical, High, Medium
- Every edit is its own card with a type (citability, FAQ, and so on) and a priority: WHERE to insert it (section and snippet), what's there NOW, what it SHOULD BECOME or what to INSERT, and a note on which query it works for. The "Copy" button hands over the ready block — paste it onto the page and mark the action as done
Don't rewrite the page "in general". The edits target specific uncited queries — paste in the ready paragraph that answers the prompt's intent directly, and the page starts answering the exact query AI was skipping it on. Closing query after query is how domain citability grows systematically.
2.Technical groundwork: Schema, llms.txt, and AI-bot access
For the AI engines to confidently read and cite your site, GEO Scout watches the technical groundwork of AI visibility: structured JSON-LD markup, an llms.txt file, and AI-bot access in robots.txt. These actions are gathered in the command center under the "Schema markup" and "Technical" groups.
- Schema markup: GEO Scout finds pages missing the right JSON-LD types (e.g. TechArticle on /docs/payment-solution or ContactPage on /contacts) and explains why it matters — JSON-LD raises the odds of landing in AI Overviews, rich results, and AI-answer citations
- The "Generate Schema" button (1 credit) creates the missing markup for a specific page. The result is a ready JSON-LD block with real brand data (name, description, contacts, opening hours); just paste it onto the page and mark it "Done"
- llms.txt: if the site root has no /llms.txt, GEO Scout offers to generate it. It's an emerging standard for AI assistants — a short Markdown map of your site's important pages that helps ChatGPT, Claude, and Perplexity understand your content
- The ready llms.txt can be copied or downloaded and uploaded to the site root as /llms.txt. Inside is a list of key pages with descriptions (payment solutions, API, guides, etc.), built from your site
- robots.txt: GEO Scout checks whether AI bots are blocked (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, YandexBot, and others). If a bot is blocked, you get a notification: the engine simply can't read your site and cite you, no matter how well the content is written
- Technical actions are tagged "Quick fix" / "Fast": low effort, but they remove the barriers without which the rest of the visibility work has no effect
Clear the technical barriers first, then work on content. If an AI bot is blocked in robots.txt, the engine simply can't read the page — and even perfect copy won't reach the answers. Bot access and llms.txt are the foundation that page improvements and publications rest on.