[Programcode]

Task 3 from the 3 Nov SEO list. Google shows "Is there an AI for debate?" as a People also ask question for "what is DebateOwl". This adds an answer-first FAQ item for it on /, /es, /hu and /ai-debate. On each page it is the first visible FAQ item and is in the FAQPage JSON-LD. The existing "Which AI is best for debate?" item stays as it was, and the new answer reuses none of its wording.

What changed

• src/locales/{en,es,hu}.json: faq.q11 / faq.a11. The price and trial length come from {{proMonthly}} / {{trialDays}}.
• src/components/landing/FAQ.tsx: shows the item first. "/ai-debate mini round" links to the route.
• src/prerender/entry.tsx: adds the same pair to the landing FAQPage JSON-LD, without the link tag.
• src/pages/AiDebatePage.tsx: the item goes first in the page FAQ and its JSON-LD. Here it points at the mini round above the FAQ instead of linking the page to itself. MODIFIED is now 2026-11-03.
• scripts/generate_seo_content.py → public/llms.txt: a new key fact for the no-account mini round. Until now the key facts listed only /tools as free.

Rendered answer lengths: EN home 58 words, ES 60, HU 52, /ai-debate 60.

Claims, checked against code

• No free plan; 3-day trial, then $5/month plus tax: site.json pricing, existing faq.a1/a9 and FREE_PLAN.
• Free mini round with no account: supabase/functions/demo-rebuttal (Turnstile only, 3 sessions per IP per day, 2 turns). It is on in production: the live /ai-debate bundle includes the demo chunk with a Turnstile site key.
• Case with "If they say… we answer…" replies: CASE_FORMAT. AI rebuttals, cross-examination and timed rounds: Case attacker, Crossfire and Sparring.
• No phone number or postal address added.

Verification

• npm run verify at this head: all 9 steps passed (docs, jargon, typecheck, guards, lint, edge, smoke, build, sw-offline).
• JSON-LD: I parsed the built dist/index.html, dist/es/index.html, dist/hu/index.html and dist/ai-debate/index.html. Each has one JSON-LD block that parses, with one FAQPage, and the new question is in it and visible on the page. check-site.mjs also checks both of those during the build.
• dist/sitemap.xml lastmod is 2026-11-03 for /, /es, /hu and /ai-debate. The home pages get theirs from the commit date of the landing sources.
• Titles are unchanged.
• Not run: the schema.org validator, the browser recipes (verify-debatelab), and agentic tests. Nothing in e2e/ or agentic/ refers to the landing FAQ order.

Draft: this touches only copy, but it waits for Adam to merge. After deploy, ping IndexNow for the four URLs.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 59 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Programcode/DebateOwl
• Branch: seo/is-there-an-ai-for-debate
• File: .coderabbit.yaml
• Commit: 101f901
• Layers: Repository YAML (base), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 7596a9ee-ed2a-4cd2-b9ba-3938cd0a6639

Commits

Reviewing files that changed from the base of the PR and between a7ced49 and 101f901.

Files selected for processing: 8

• public/llms.txt
• scripts/generate_seo_content.py
• src/components/landing/FAQ.tsx
• src/locales/en.json
• src/locales/es.json
• src/locales/hu.json
• src/pages/AiDebatePage.tsx
• src/prerender/entry.tsx

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

CodeRabbit Verify

• Run CodeRabbit Verify to test the changes in this pull request.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.