litigator-website

OPTIVIS // LITIGATOR — landing page for the Texas PI litigation intelligence platform.

Production URL: https://litigator.automate-law.com

---

Files

• index.html — the landing page (single file, no build step)
• vercel.json — security headers + caching rules
• robots.txt — allows indexing
• sitemap.xml — single-URL sitemap

---

Deploy steps (one-time, ~15 minutes)

1. GitHub

1. Create a new repo: xdullah/litigator-website (Public is fine — no secrets in this code)
2. Drop all four files at the repo root: index.html, vercel.json, robots.txt, sitemap.xml
3. Commit + push

2. Vercel

1. Vercel → Add New → Project → import xdullah/litigator-website
2. Framework Preset: Other
3. Build Command: (leave empty)
4. Output Directory: (leave empty)
5. Root Directory: (leave empty)
6. Click Deploy
7. Test at the auto-generated litigator-website.vercel.app URL — confirm the page loads correctly

3. Domain

1. Vercel project → Settings → Domains → Add Domain → enter litigator.automate-law.com
2. Vercel will show the CNAME target (usually cname.vercel-dns.com)
3. GoDaddy → DNS for automate-law.com → Add Record
   • Type: CNAME
   • Name: litigator
   • Value: cname.vercel-dns.com (whatever Vercel showed you)
   • TTL: 600
4. Wait ~5–10 min for propagation
5. Test https://litigator.automate-law.com in incognito

---

Form wiring (required before going public)

The form currently logs submissions to the browser console. To capture real leads:

Zapier path (recommended — fastest)

1. Zapier → Create Zap → trigger: Webhooks by Zapier → Catch Hook
2. Copy the webhook URL (format: https://hooks.zapier.com/hooks/catch/XXXXXXX/YYYYYYY/)
3. Open index.html → find the line const FORM_ENDPOINT = '';
4. Paste the webhook URL between the quotes:

   const FORM_ENDPOINT = 'https://hooks.zapier.com/hooks/catch/...';

5. Commit + push — Vercel auto-redeploys
6. Back in Zapier:
   • Action 1: HubSpot → Create or Update Contact
     • Map: email → email, name → name, firm → company, phone → phone
     • Add to a list: OPTIVIS LITIGATOR — Applications
   • Action 2: Slack → Send DM to yourself
     • Message: 🎯 New LITIGATOR application — {{firm}} ({{attorneys}} attys) — {{name}} ({{role}}) — {{email}} — Notes: {{notes}}
7. Test by submitting a fake application

Email fallback

If Zapier ever fails, the form will display an error message with mailto:applications@automate-law.com. Set up that inbox or a forwarding rule in Google Workspace before going live.

---

Redirect cluster (point dead AI/LLM domains here)

After the site is live, set up these GoDaddy domain forwards to capture stray search traffic:

Source domain	Forwarding type	Target
aiforlawyers.dev	301 Permanent, Forward only	https://litigator.automate-law.com
aiforlawyers.xyz	301 Permanent, Forward only	https://litigator.automate-law.com
getlawllm.com	301 Permanent, Forward only	https://litigator.automate-law.com
llmforlawfirms.com	301 Permanent, Forward only	https://litigator.automate-law.com
llmlawfirms.com	301 Permanent, Forward only	https://litigator.automate-law.com
lawfirmai.dev	301 Permanent, Forward only	https://litigator.automate-law.com
lawllmsolutions.com	301 Permanent, Forward only	https://litigator.automate-law.com

Skip: aiforlawyers.blog — keep separate as a future content/SEO site.

GoDaddy steps for each: Domain Settings → Forwarding → Add Forwarding → Forward to URL (paste target) → Forward Type: Permanent (301) → Settings: Forward only (NOT Masking) → Save.

---

Post-launch checklist

• Form endpoint wired and tested
• HubSpot list "OPTIVIS LITIGATOR — Applications" created
• Slack DM working from a test submission
• applications@automate-law.com inbox set up (or forwarding to your inbox)
• Google Search Console: verify litigator.automate-law.com and submit sitemap.xml
• All 7 redirect domains forwarding correctly (test each by typing URL in incognito)

---

Editing copy later

Everything renders from index.html. Numbers, builder names, deployment criteria, copy — all editable directly. After a commit + push, Vercel redeploys in ~30 seconds.

Common edit points:

• Hero headline: search <h1 class="reveal">
• Spec numbers: search <div class="num">
• Document inventory: search <!-- ============ INTEL BRIEF
• Form questions: search <form id="applicationForm"