Cross-Site SEO, AI & GEO Optimization Strategy

Master plan for SEO, Generative Engine Optimization (GEO), and AI agent discoverability across all urWave Company websites.

Created: 2026-02-19 Scope: urWhats.com, urWave.com, urLead.net, urHackathon.com Parent Company: urWave Company (LLC), CR: 7052775355, Riyadh, Saudi Arabia Hosting: Cloudflare Pages (static hosting, no Workers) Framework: All sites use Astro v5 (static output)

Table of Contents

1. Current State Audit
2. Critical Issues
3. AI Agent Optimization Standards
4. Generative Engine Optimization (GEO)
5. Execution Plan
6. Per-Site Details
7. Contact Info Standard
8. Cloudflare Configuration Notes

Current State Audit

Site Overview

AI/SEO Readiness Matrix

Critical Issues

SEVERITY: CRITICAL (Fix Immediately)

1. Fake AggregateRating Data -- Google Penalty Risk

Affected: urWhats, urWave, urLead Issue: Fabricated review scores in JSON-LD structured data

• urWhats: 4.8/5 from 150 reviews (SEO.astro, schema.json, ai-plugin.json, llms.txt, llms-full.txt)
• urWave: 4.9/5 from 127 reviews (SEO.astro) + 4.8/5 from 45 reviews (product schema)
• urLead: 4.8/5 from 150 reviews (SEO.astro) Risk: Google manual action (penalty), loss of rich snippets Fix: Remove ALL aggregateRating from structured data until real reviews exist. Use Google-verified review platforms when ready.

2. No Google Search Console

Affected: ALL sites Issue: Cannot monitor indexing, crawl errors, or search performance Fix: Set up GSC for all 4 domains. Add verification meta tag to each site.

3. Broken OG Images

Affected: urWhats (file missing), urWave (SVG, not renderable), urLead (likely wrong) Fix: Create 1200x630 PNG images for each brand. Social sharing is fundamentally broken without this.

4. Malformed Sitemaps

Affected: urWhats (invalid XML), urLead (wrong URLs)

• urWhats: static sitemap.xml has closing </urlset> in the middle, orphaned entries after
• urLead: generates English URLs as /en/tools instead of /tools -- all 301 redirect Fix: urWhats: delete static sitemap, install @astrojs/sitemap. urLead: fix URL generation.

SEVERITY: HIGH

5. Contact Info Inconsistencies

All sites show different phone numbers and emails. Standard should be:

• Phone: +966 508 777 669
• Sales email: sales@urwave.com
• Info email: info@urwave.com (for general inquiries)

6. Route Casing Mismatch

/Privacy and /Terms (PascalCase) on urWhats, urWave, urLead. Sitemaps reference lowercase. Creates 404 crawl errors.

7. False Claims in llms.txt Files

• urWhats: Claims Salesforce/HubSpot/Zoho/Shopify/WooCommerce integrations (unverified)
• urWhats: References "UAE PDPL" (should be Saudi PDPL)
• urWhats: Claims "10,000+ businesses" (unverified)
• urWave: References "50-100 employees" (unlikely for company founded Dec 2025)

8. urLead Site Quality Issues

• Footer says "urWhats" copyright instead of "urLead"
• RTL CSS not loaded (Arabic pages render LTR)
• No Arabic font loaded
• api.config.ts is a stub (Plans.astro may fail)
• Content JSON has urIdea contamination

SEVERITY: MEDIUM

9. Duplicate Meta Tags

• urWhats: Duplicate <meta name="robots"> tag
• urHackathon: Duplicate og:type, og:locale, theme-color, apple-touch-icon, manifest

10. SearchAction Schema Points to Non-existent Pages

All sites have SearchAction in WebSite schema pointing to /search?q= or /contact?q= -- no search functionality exists.

11. Missing .well-known/ Directory

Only urWhats has .well-known/. urWave, urLead, urHackathon need it for AI agent discovery.

AI Agent Optimization Standards

1. llms.txt (llmstxt.org) -- IMPLEMENTED, NEEDS CLEANUP

What it is: A /llms.txt file in the site root providing LLM-friendly content in Markdown format. Helps AI tools (ChatGPT, Claude, Perplexity, etc.) understand your site at inference time.

Spec format:

# Site Name

> Brief description (blockquote)

Detailed info paragraphs

## Section Name
- [Link title](url): Description

## Optional
- [Link title](url): Can be skipped for shorter context

Current status: All 4 sites have llms.txt but need cleanup:

• Remove fake statistics
• Fix incorrect legal references (UAE -> Saudi Arabia)
• Remove unverified integration claims
• Restructure to follow the spec format strictly
• Add proper cross-links between product sites

2. llms-full.txt -- PARTIALLY IMPLEMENTED

What it is: Expanded version of llms.txt with full content from linked pages. Gives AI tools complete context without needing to fetch multiple URLs.

Current status: Only urWhats has it. Needs adding to urWave, urLead, urHackathon.

3. .well-known/ Directory Files

ai-plugin.json

What it is: Originally an OpenAI standard for ChatGPT plugins. Now used broadly for AI agent discovery. Status: Only urWhats has it. Template:

{
  "schema_version": "v1",
  "name_for_human": "urWhats",
  "name_for_model": "urwhats_whatsapp_api",
  "description_for_human": "...",
  "description_for_model": "...",
  "auth": { "type": "none" },
  "api": { "type": "openapi", "url": "..." },
  "logo_url": "...",
  "contact_email": "...",
  "legal_info_url": "..."
}

schema.json

What it is: Machine-readable Organization/Product schema for AI tools that look for structured data. Status: Only urWhats has it.

security.txt (RFC 9116)

What it is: Security contact information. Builds trust with both AI tools and security researchers. Status: Only urWhats has it (but references non-existent pgp-key.txt).

4. Markdown Page Versions (.md endpoints)

What it is: The llmstxt.org spec recommends serving Markdown versions of pages at {url}.md or {url}.html.md. AI tools can then fetch clean, parsed content instead of parsing HTML.

Implementation: Create Astro API routes that serve Markdown versions of key pages. Priority: MEDIUM -- Useful for developer-focused sites, less critical for SaaS landing pages. Recommendation: Implement for urWave (corporate/products) first, then evaluate impact.

5. AI Meta Tags

What they are: Custom meta tags that help AI tools categorize and understand pages:

<meta name="ai:description" content="...">
<meta name="ai:category" content="...">
<meta name="ai:features" content="...">
<meta name="ai:use_cases" content="...">
<meta name="ai:audience" content="...">

Status: urWhats has extensive AI meta tags. Other sites have minimal or none.

6. Link to llms.txt from HTML Head

<link rel="author" href="/llms.txt">

Status: urWhats and urLead have it. urWave and urHackathon need it.

7. Directory Registration

Register all sites on:

• llmstxt.site -- Main llms.txt directory
• directory.llmstxt.cloud -- Secondary directory

Generative Engine Optimization (GEO)

GEO optimizes content for AI-powered search (Google AI Overviews, Perplexity, ChatGPT with search, Bing Copilot, etc.).

Key GEO Principles

1. Cite Statistics & Data Points

   • BAD: "We help many businesses"
   • GOOD: "urWhats processes over 50 million WhatsApp messages monthly across 150+ enterprise clients in Saudi Arabia"
   • AI models weight specific, cited numbers higher than vague claims

2. Use Authoritative Language

   • BAD: "We're a good WhatsApp solution"
   • GOOD: "As an Official Meta Technical Provider, urWhats delivers enterprise-grade WhatsApp Business API solutions"

3. Entity-Rich Descriptions

   • Include: company name, product names, locations, partner names (Meta), certifications
   • AI tools extract entities for knowledge graph matching

4. Structured FAQ on Every Page

   • Not just the FAQ page -- add 3-5 relevant Q&As at the bottom of EVERY page
   • Use FAQPage schema markup

5. Comparison Content

   • "urWhats vs Twilio", "urWhats vs Respond.io", "urLead vs HubSpot"
   • AI tools are often asked comparison questions -- be the source of truth

6. Technical Depth

   • Include API documentation references
   • Show integration capabilities
   • Provide implementation details

7. Local Authority

   • "Headquartered in Riyadh, Saudi Arabia"
   • "Compliant with Saudi Personal Data Protection Law (PDPL)"
   • "Serving businesses across the GCC region"

Content Structure for GEO

Every key page should follow this structure:

1. Clear H1 with primary keyword and entity
2. Introductory paragraph with key facts (who, what, where, why)
3. Feature sections with specific capabilities
4. Use cases with industry/role context
5. Social proof (real testimonials, partner badges -- NOT fabricated)
6. FAQ section with FAQPage schema
7. CTA with clear next step

Execution Plan

Phase 0: Emergency Fixes (ALL SITES) -- Priority: CRITICAL

Phase A: AI Agent Optimization (ALL SITES) -- Priority: HIGH

Phase B: SEO Foundation (ALL SITES) -- Priority: HIGH

Phase C: Content & GEO Enhancement -- Priority: MEDIUM-HIGH

Phase D: Technical Optimization -- Priority: MEDIUM

Per-Site Details

urWhats.com

• Repo: D:\Work\Website-urWhats.com
• Branch: feature/seo-enhancements
• Existing plan: .specs/IMPROVEMENT-PLAN.md (49 tasks, 5 phases)
• Status: Phase 1 mostly done (7/8), uncommitted
• Key issues: Fake ratings, malformed sitemap, missing OG image, false llms.txt claims

urWave.com

• Repo: D:\Work\Website-urWave.com
• Branch: main (1 unpushed commit)
• CLAUDE.md: .claude/CLAUDE.md (211 lines)
• Key issues: SVG OG image, fake ratings, route casing, hardcoded hero, phone inconsistency

urLead.net

• Repo: D:\Work\Website-urLead.net
• Branch: (check)
• CLAUDE.md: MISSING
• Key issues: Wrong sitemap URLs, urWhats copyright in footer, RTL CSS broken, no Arabic font, urIdea content contamination, fake ratings, stub API config

urHackathon.com

• Repo: D:\Work\Website-urHackathon.com
• Branch: (check)
• CLAUDE.md: MISSING
• Key issues: Hardcoded values everywhere, no centralized config, duplicate meta tags, 2 pages only, missing analytics

Contact Info Standard

All urWave Company websites MUST use these contact details:

Old numbers to remove globally:

• +966547778955
• +966544757057
• +971509056326

Cloudflare Configuration Notes

All Sites Use:

• Cloudflare Pages (static hosting)
• No Workers (yet)
• _headers file for security headers (CSP, HSTS, XSS protection)
• _redirects file for URL redirects
• Asset caching: 1 year for immutable assets, 0 for HTML

Recommended Cloudflare Additions:

1. Cloudflare Web Analytics -- Free, privacy-friendly, no JS overhead. Complements GA4.
2. Cloudflare Turnstile -- Already used on contact forms (good).
3. DNS records -- Ensure all domains have proper CNAME/A records pointing to Cloudflare Pages.
4. Email routing -- sales@urwave.com and info@urwave.com should be set up via Cloudflare Email Routing if not already.

Headers Recommendations:

Add to all sites' _headers:

# AI/LLM files
/llms.txt
  Content-Type: text/plain; charset=utf-8
  Cache-Control: public, max-age=86400
  X-Robots-Tag: noindex

/llms-full.txt
  Content-Type: text/plain; charset=utf-8
  Cache-Control: public, max-age=86400
  X-Robots-Tag: noindex

/.well-known/*
  Content-Type: application/json
  Cache-Control: public, max-age=86400
  Access-Control-Allow-Origin: *

Version History