I built a free alternative to a $9.99 SEO/AEO/GEO auditor

I am a school teacher from Pakistan, not a software engineer. I build free tools with AI assistance. This week's one is AuditBeacon: paste any URL and it audits the page for SEO, AEO and GEO — 52 checks across 13 categories, with pillar scores, a letter grade, and fix guidance for every failed check.

Try it: https://auditbeacon.pages.dev/
Code: https://github.com/zhbhaider-coder/auditbeacon

It exists because the Chrome extension it is modelled on, SAGE, gives you 10 free scans and then charges $9.99. Ten scans is a teaser, not a tool. So I built the unlimited version.

What it checks

The 13 categories: meta tags and discoverability, semantic HTML, internal linking, machine readability, structured data and schema, AI-crawler access (it parses your robots.txt per agent — GPTBot, ClaudeBot, PerplexityBot and the rest), entity and authority signals, citability (stats, quotes, sources — the things AI engines actually cite), answer targeting for featured snippets, FAQ and HowTo structure, concise formatting, and voice/conversational readiness including a Flesch-Kincaid reading grade.

You get 0–100 scores per pillar (SEO, AEO, GEO), a combined score, an A–F grade, a "fix these first" list, and the report exports as Markdown, HTML, CSV or plain text.

I ran my own book-summary site through it: 89/100, grade B. The fixes it flagged — Speakable schema, sameAs identity links — were correct and took ten minutes.

Why it is free

The analysis runs on Cloudflare's edge as a serverless function: it fetches your page, robots.txt and llms.txt, runs the checks, returns JSON. No account, no scan counter, no paywall. The frontend is a static page.

What it honestly cannot do

It reads raw HTML — it does not render JavaScript. Heavy client-rendered apps will score lower than a real crawler with rendering would give them. It audits one page at a time, not whole sites. And it is unofficial and not affiliated with SAGE.

How it is built

A Cloudflare Pages Function (no dependencies, plain regex parsing — unfashionable but fast), a static frontend, SVG score rings, client-side report export. No database, no tracking.

What is next

Multi-page crawls and score history are the obvious next steps. But first: paste your URL in and tell me your score — and tell me where the grader is wrong. Graders that cannot be argued with do not get better.