Docs

Getting Started

From sign-up to your first deployed fix in 7 steps. No technical knowledge required.


Step 1: Create Your Account

Go to velrageo.com/sign-up and create your account with Google, GitHub, or email. Every new account starts with a 7-day free trial — no credit card required. You get full access to all features on your chosen plan from day one.

Available plans:

  • Starter ($79/mo) — 500 pages/scan, basic fixes, GEO Score
  • Growth ($239/mo) — 2,000 pages/scan, full Fix Engine + Monitoring
  • Agency ($499/mo) — 5,000 pages/scan, white-label, multi-client
  • Enterprise (From $1,500/mo) — Unlimited, API/MCP, dedicated support

Save 20% with annual billing. You can upgrade, downgrade, or cancel anytime.

Step 2: Create a Project

After signing in, you land on the Dashboard. Click "New Project" and enter your domain (e.g., lanisilk.com). One project = one domain. Agency plan supports multiple projects for different clients.

You can optionally add your brand name, industry vertical, and target keywords at this stage. These help VELRA GEO personalize your scan results and benchmark comparisons.

Step 3: Run Your First Scan

Click "Start GEO Scan". The scanner does three things simultaneously:

  1. Crawls your website— up to your plan's page limit (500 / 2,000 / 5,000 pages). Extracts content, headers, metadata, schema markup, internal links, and more.
  2. Queries AI engines — sends your target keywords to ChatGPT, Perplexity, Google AI Overviews, Gemini, and Claude. Records whether your brand is mentioned, cited, or recommended.
  3. Analyzes technical health — checks robots.txt, sitemaps, page speed, SSL, canonicals, redirect chains, and schema markup.

This takes 5-15 minutesdepending on site size. You'll see a real-time progress bar. You can leave the page — the scan runs in the background and you'll be notified when it completes.

Step 4: Review Your GEO Score

Once the scan completes, you see your GEO Score — a composite 0-100 score weighted across 5 categories:

  • Technical SEO (40%) — Can AI bots access your site? robots.txt, SSL, sitemaps, redirects, page speed, canonicals.
  • Content Quality (25%) — Is your content comprehensive and well-structured? Word count, headers, FAQs, internal links, image alt text.
  • AI Readiness (20%) — Does your site speak AI? llms.txt, schema markup, entity density, answer blocks.
  • Trust & Authority (10%) — Are you credible? Author attribution, E-E-A-T signals, citations, brand consistency.
  • User Experience (5%) — Baseline quality: mobile responsiveness, Core Web Vitals, navigation.

Each category breaks down into specific metrics. Click any category to drill into page-level details. See GEO Score documentation for the full breakdown.

Step 5: Review Priority Fix List

Navigate to Fix Engine → Priority List. Every issue found during the scan is ranked using an Impact x Effort matrix:

  • P1 — Critical: High impact, low effort. Fix these first. (e.g., robots.txt blocking AI bots, missing llms.txt)
  • P2 — High: High impact, moderate effort. (e.g., missing FAQ schema, no answer blocks)
  • P3 — Medium: Moderate impact. (e.g., missing author schema, entity gaps)
  • P4 — Low: Nice-to-have improvements. (e.g., breadcrumb schema, HowTo markup)

Each fix item shows the module that detected it, the affected pages, and a "Generate Fix" button.

Step 6: Generate and Deploy Your First Fix

Click "Generate" on your top priority issue. VELRA GEO creates the actual deployable code — not just a suggestion. Common first fixes:

  • robots.txt patch (A1) — Download the patched file. Upload it to your server root directory, replacing the existing robots.txt. Allows 14 AI bots (GPTBot, ClaudeBot, PerplexityBot, etc.) to crawl your content.
  • llms.txt file (A2) — Download both llms.txt and llms-full.txt. Upload to your domain root: yourdomain.com/llms.txt. No competitor generates this file.
  • FAQ Schema (S1) — Copy the generated JSON-LD <script> tag. Paste into your page's <head> section. For Shopify: paste into theme.liquid. For WordPress: use a header/footer plugin.

Every generated file is saved in your dashboard under Fix Engine → Generated Files and can be re-downloaded anytime.

Step 7: Re-scan to Verify

After deploying your fixes, run another scan. Go to Reports → Before/After to see the comparison:

  • GEO Score change (e.g., 35 → 52)
  • Per-category improvement breakdown
  • Number of issues resolved vs remaining
  • AI visibility changes (if monitoring is active)

Most technical fixes (robots.txt, schema, llms.txt) show impact within 1-7 days. Content fixes take 2-4 weeks to reflect in AI engine responses.


What's Next?

  • Set up AI Visibility Monitoring (M2) to track when AI engines mention your brand
  • Add competitors for Competitive Benchmarking (CA2)
  • Connect Slack for citation alerts, Jira/Asana for fix ticket export, GA4 for revenue attribution
  • Explore the full Fix Engine — 28 modules generating deployable code
  • Read the 5-Step Pipeline to understand how all 42 modules work together