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: turn an appearance into a citation
When a page already shows up in AI answers but isn't cited, the command center suggests an "Improve this page" action. AI knows about it but doesn't find it relevant enough to link to. Pinpoint-improving such a page is the fastest way to lift brand visibility and direct traffic: you turn an appearance into a citation exactly where the AI engines already show interest.
- The "Optimize" button on the card launches an AI agent. The source page is picked from the brand's sitemap or entered manually by URL — the domain must match the brand's site
- The "Target queries" block shows the prompts where AI engines found the page as an answer candidate but didn't cite it. The optimization targets exactly those queries, not abstract "improve SEO"
- The agent runs 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 pack) → save to history. Every run is kept in the "Generation history"
- The result opens with an "Optimization strategy" — a short summary and the number of edits by priority: Critical, High, Medium. You see what the rewrite targets and how many changes are coming
- The key part: beyond general recommendations, the result gives answer capsules for the uncited queries — a ready paragraph that directly answers the prompt's intent and positions the brand as a relevant choice
- Each edit shows WHERE to insert it, what it is NOW, and what it SHOULD BECOME, plus markup (FAQPage and others), and copies with one button — you just move the ready block onto the page
- Once you mark it "Done", the recommendation for that page leaves the queue and returns to the command center only if the page turns up uncited again for a different prompt. That's how the platform raises domain visibility systematically, prompt by prompt
Don't rewrite the page "in general". Answer capsules target a specific uncited query — move the ready paragraph and markup over, and the page starts answering exactly the intent AI was skipping it for. Closing query after query, you build up the domain's citation rate 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
Close the technical barriers first, then optimize content. If an AI bot is blocked in robots.txt or a page has no markup, even perfect text won't make it into answers. Schema, llms.txt, and open bot access are the foundation that answer capsules and publications run on.