AI Content Optimization

AI Content Optimization (the “content audit”) scans your site and scores how likely each page is to be quoted when an AI platform synthesizes an answer. It then ranks the fixes that would lift your citation potential the most. It is the content-side companion to Readiness: Readiness checks whether your site is machine-reachable; Content Optimization checks whether your content is worth citing. It lives at /dashboard/content-audit.

​

What you see

• An overall citation-potential score out of 100 for every audited page.
• Each page scored across six dimensions (four computed, two judged by AI).
• A worklist of fixes — the cross-page problems ranked by impact, with an estimated score lift and an effort tag.
• Cross-page recommendations — places where a strong page can donate copy to a weak one.
• Per-page AI rewrite drafts you can copy, and a PDF export of the whole report.

​

Running an audit

Start a run from the Content Optimization surface. Pick a scope:

• Whole site — discovers pages from your sitemap plus a crawl, up to your per-run cap.
• Single page — scores just one URL you paste in. A single-page run is fast and uses one page from your allowance.

Results stream in as the run executes. The dashboard polls live progress so you see scored vs. planned pages while it runs. Each run is saved to run history when it finishes, and any prior run reopens in full detail. Under the hood, each page is scraped with Firecrawl. Every page is scored on the four computed dimensions instantly and at zero cost; the two AI-judged dimensions and the per-page problem breakdown run on top.

​

The six dimensions

Each dimension is scored 0–100. The overall score is a weighted blend that favors the dimensions that matter most for getting cited.

1. Headline answer (AI-judged) — does the page open with one bold sentence that directly answers a commercial query, before any preamble?
2. Voice (AI-judged) — confident on world claims (opinionated, attributed data) and hedged on self (no overclaiming)?
3. Quotable claim density (computed) — specific numbers, named entities, concrete prices per section. Walls of reasoning score low.
4. Extraction shape (computed) — tables, named tiers, FAQ, bolded factor lists, bullets — the machine-extractable structure.
5. Recency signals (computed) — a current year in the title or first paragraph, and a prominent “Last Updated” date.
6. Substance / thinness (computed) — enough length and substance for multiple quotable claims. Thin pages score low.

​

The worklist

The worklist rolls up per-page scores into a cross-page, impact-ranked list of fixes. A dimension becomes a fix when its score is below 70. Each fix shows the affected pages, a severity, an estimated score lift, and an effort tag (low, med, high) so you can pick the cheap wins first. The headline number is the projected overall lift — how many overall-score points you could recover across the site.

​

Plans and allowances

Two enforcement levers, both tiered. Numbers below are the source of truth from the plan config. The first lever is pages per run — how many pages a single run may score. The second is a calendar-month pooled page allowance. AI calls themselves are not capped — a page is one batched AI call, so the page allowance already bounds your usage.

​

The page allowance

Each run uses pages from your monthly allowance. A run scores up to your per-run cap or your remaining monthly pages, whichever is smaller — so a run near the end of the month may score fewer pages than your cap. A run that would use more than you have left is clamped to what’s left, not blocked. The allowance resets on the calendar month.

​

Free-tier detail

A Free org can run an audit and see every page’s score plus the prioritized worklist — the scope of the problem is visible. The actionable detail is locked: the impact × effort matrix and cross-page recommendations show as a blurred upgrade preview, and the per-page problem breakdown, AI rewrite drafts, and PDF export require a Starter plan or above. Locked detail is stripped server-side before it reaches your browser; it is never just hidden.

​

API

These routes back the Content Optimization surface. They are not part of the REST API reference.

• POST /api/content-audit/run — start an audit (whole-site or single-page).
• GET /api/content-audit/run — poll one audit’s full result.
• GET /api/content-audit/runs — list run history for a project.
• POST /api/content-audit/rewrite — generate a per-page AI rewrite draft.
• GET /api/content-audit/report/[auditId]/pdf — download a run’s PDF.

​

How to use it

• Read the overall score and the projected lift first, then drill into the top-ranked fixes.
• Use a single-page run to check one page fast without spending your whole allowance.
• On Free, the worklist is a real taste of the problems; upgrade for the matrix, cross-page recommendations, per-page detail, rewrite drafts, and PDF.
• Re-run after making changes — unchanged pages are cached, so a re-audit only re-scores what actually changed.