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 the sign-up page and create your account with Google, GitHub, or email. You get full access to all features on your chosen plan.

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 pages and prompts

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 Kenvada GEO personalize your scan results and benchmark comparisons.

Step 3: Run Your First Scan

Click "Start GEO Scan". The scanner does two things:

  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. Analyzes technical health — checks robots.txt, sitemaps, page speed, SSL, canonicals, redirect chains, and schema markup.

AI search observation is a separate step under Monitoring: it looks up your target prompts in Google Search results (AI Overview + organic, US) and records whether your brand is mentioned or cited. No other engine is queried, and a scan does not run it for you.

This takes 5-15 minutes depending on site size. You'll see a progress bar that updates while the scan runs. 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 carries a severity set by the module that found it:

  • Critical — e.g., robots.txt blocking an AI crawler, a noindex directive on a key page.
  • High — e.g., missing FAQ schema where visible Q&A exists, no answer block.
  • Medium — e.g., missing author schema, entity gaps.
  • Low — e.g., breadcrumb schema, generated sitemap.

The dashboard groups issues by what you can do about them — one-click deployable fixes first, then copy-and-paste fixes, then content hand-offs, then review-only guidance — and within each group orders them by severity, then by how many pages they affect. The Resolution Workbook (.xlsx) export carries the same resolutions with their severity and affected pages. Effort is not estimated.

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. Kenvada 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. This is an optional standard for the LLM ecosystem, not a Google requirement.
  • 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)

Technical fixes (robots.txt, schema, llms.txt) are live as soon as you deploy them, and the re-scan verifies that. When or whether any AI engine reflects a change is outside our control and is not something we predict.

What's Next?

  • Set up AI Search Observation (M2) to track when Google Search results mention your brand
  • Add competitors for Competitive Benchmarking (CA2)
  • Download the Resolution Workbook (.xlsx) from a scan's Fixes tab to hand fixes to your team
  • Explore the full Fix Engine — 28 modules generating deployable code
  • Read the 5-Step Pipeline to understand how the modules work together
Previous
Overview
Next
The 5-Step Pipeline