pagegrade

September 18, 2026 · View on GitHub

Grade page sections for clarity, writing and on-page SEO. WXT + TypeSafe AI Jev.

Kitze Made by Kitze
kitze.io · X · YouTube


More projects by Kitze

Zero To Shipped logo
Zero To Shipped
A full-stack starter kit for web and mobile apps.
Sotto logo
Sotto
Voice-to-text for macOS. Local AI, one-time purchase.
Tinkerer Club logo
Tinkerer Club
A private community for builders, self-hosters, and AI tinkerers.
Sizzy logo
Sizzy
The browser for web developers.
Supermac logo
Supermac
A macOS command center for everyday workflows.
DMX logo
DMX
A focused desktop client for X.

Support this project

Buy me a coffee   Sponsor on GitHub

Sponsors

Postiz logo
Postiz
Schedule social posts with AI agents.
FounderStack logo
FounderStack
A SaaS stack for your business, without subscriptions.
Matte logo
Matte
3D mockups, screen recordings, and video editing.
HTML/CSS to Image logo
HTML/CSS to Image
Turn HTML/CSS into images, PDFs, and screenshots.
NameMyVenti logo
NameMyVenti
Get your brand shouted out at Starbucks.



PageGrade

A WXT Chrome extension that grades readable page sections with TypeSafe AI Jev through Vercel AI Gateway. Each section gets ten rubric scores; the page gets an A–E grade and a breakdown you can inspect.

MIT licensed. Bring your own Vercel AI Gateway key. No backend or analytics.

Install locally

Requires Bun and Chrome 120+ (Manifest V3).

bun install --frozen-lockfile
bun run build
  1. Open chrome://extensions and enable Developer mode.
  2. Click Load unpacked and select .output/chrome-mv3 inside this checkout.
  3. Open a normal web page and click PageGrade's toolbar icon. Chrome's native side panel opens alongside the page (its side follows your Chrome preference).
  4. Save your Vercel AI Gateway API key under Connection. Gateway credits and Jev access may be required.
  5. Click Analyze sections to consent to sending that page's extracted content for evaluation.

Section scores appear progressively in the side panel and as A–E badges on the actual page. Hover or focus a badge to outline its section; click it to select the breakdown in the panel. Show scores on page toggles overlays. Badges track scrolling/resizing; changed text invalidates affected grades.

The panel follows the active tab. Each tab keeps its own session report. Click the toolbar icon on a newly selected page to grant activeTab access if prompted. No all-sites access is requested.

Browse grades, expand rubrics, use Locate on page, or Export JSON. Stop retains completed section scores; an individual request failure does not discard other sections. Clear removes report and overlays. Source navigation or closing clears its report.

Assess whole page is optional, available after every extracted section is scored and the full text fits within 60,000 characters. Larger pages still get their section scores, a clearly labeled scored sections average, word/section counts and local on-page checks—not a fabricated whole-page grade.

bun run zip creates the unpacked archive under .output/. This is not a Chrome Web Store listing or a signed CRX.

Scoring

Jev answers typed score questions with five explicit ordered anchors. Fractional scores are valid: normalize its 0–4 result to 0–100 by multiplying by 25. These values are rubric positions, not confidence probabilities.

Per-section metrics

MetricWeight
Clarity15%
Concision10%
Specificity10%
Explanation15%
Usefulness15%
Readability10%
Flow8%
Claim support7%
Writing quality5%
Search intent5%

Exact questions, all five anchors, and fixed improvement guidance live in lib/rubric.ts. Jev does not generate rewrites or free-form advice.

Section average and optional whole-page score

sectionQuality = weighted mean of section scores
section weight = sqrt(min(max(wordCount, 1), 500))

composition = 30% section structure
            + 25% length fit
            + 20% focus / non-repetition
            + 25% purpose coverage

overall = round(70% sectionQuality + 20% composition + 10% onPageChecks)

Length and section count are judged against the page's apparent purpose. No minimum word count, no universal ideal section count, no reward for padding. A brief landing page and a long guide can both score well. Capped square-root weighting prevents both tiny fragments and one huge section from dominating.

Local on-page checks equally weight title presence, description presence, H1 convention, heading hierarchy, image alt-attribute presence and document-language presence. They do not claim to predict search rankings. Empty image alt is allowed for decorative images; meaningful alternative text is not evaluated.

GradeScoreColor
A85–100Dark green
B70–84Light green
C55–69Yellow
D40–54Orange
E0–39Red

Editorial heuristic only. Not an official Nutri-Score, fact-check, comprehensive SEO audit, accessibility audit or ranking prediction. No affiliation with Nutri-Score. The rubric is not calibrated against human ratings yet. Scores may vary between runs.

Extraction and limits

  • Reads the first main / [role=main], otherwise the first article, otherwise body.
  • Uses headings and semantic section boundaries, without counting nested text twice.
  • Excludes navigation, footers, sidebars, forms, editable fields, controls, hidden content, scripts and iframes.
  • Does not inspect images/video meaning, canvas, shadow DOM or unloaded content.
  • Long sections are split at word boundaries into 6,000-character chunks; no ordinary section text is dropped. Ten metrics are evaluated for every chunk, then averaged by character count. The panel discloses chunked sections: these are passage-level judgments, not an assessment of cross-chunk flow.
  • Extraction safety guards: 250 sections, 2 million characters total, 100,000 visited DOM nodes. Hitting a guard is disclosed and prevents whole-page assessment. Coverage refers only to extracted text.
  • At most two model requests concurrently across section workers; chunks within a section run sequentially. One active page analysis globally. No automatic retries, background scanning or automatic paid work on tab switches.
  • Every required answer must be present, correctly typed, finite and in range. One failed chunk marks that section failed; other section results survive. Failed optional page assessment also preserves section scores. No fabricated fallback scores.
  • Text changes invalidate affected displayed grades. A full snapshot check at completion rejects a changed page; navigation clears the report. A worker restart shows an interruption message with completed section scores retained.

Privacy and security

  • Click-to-analyze only. Opening the panel extracts locally; network evaluation starts only after clicking Analyze sections or Assess whole page.
  • Sends extracted main-page text, section headings, page title, description and language to Vercel AI Gateway, which routes to TypeSafe AI Jev. Do not analyze sensitive pages. Provider retention policies apply; this project does not promise zero retention.
  • Does not send the source URL, query string, DOM selectors, form values or browser history to the model. Text and metadata themselves can still contain sensitive information.
  • API key stays in extension-local storage restricted to trusted extension contexts. It is not encrypted, synced, bundled or sent to source pages. Remove it under Connection.
  • Scores, headings and source origin are held in browser session storage, cleared on source navigation/close, browser exit or Clear. Extracted source text is not persisted in reports.
  • Exported JSON includes scores, headings and source origin; review before sharing.
  • Permissions: sidePanel, activeTab, scripting, storage, and access to https://ai-gateway.vercel.sh/*. No persistent all-sites permission, external messaging or remote code.
  • Page content is treated as untrusted evidence in all model questions. Model output never runs code or follows links. Isolated Shadow DOM overlays display validated scores without rewriting source content. Page-side messages can only select or invalidate known sections, never access keys or start paid analysis. Locate briefly highlights the selected section.

Development

bun run check   # TypeScript, lint, focused tests, formatting
bun run build
bun run zip

Run the optional live API smoke with a key supplied through your shell environment:

bun scripts/smoke-jev.ts

The smoke sends only a hardcoded synthetic basil-growing guide. It requires AI_GATEWAY_API_KEY and prints metrics/counts, never the credential. SMOKE_REPORT_PATH optionally writes its synthetic report locally.

No GitHub Actions are configured. No production secrets or real-page fixtures belong in this repository.


More projects by Kitze

Apps & tools

gifs.so
Search, copy, and download reaction GIFs.
Glink
Feedback, roadmaps, changelogs, and discussions.
Benji
Tasks, habits, calendar, health, and routines in one place.
Perkz
Sell and manage access to private GitHub repositories.
JustWrite
Distraction-free writing sprints for macOS, with time or word-count goals.
Releaseflow
App updates and downloads.
Passlock
A macOS password manager with time locks and unlock challenges.

Open source

Skillbox
A self-hosted, versioned skills library for AI agents.
Unclutter
Remove page clutter with AI-powered, reusable browser rules.
PageGrade
Grade page clarity, writing, and on-page SEO.
Council
Let your coding agents deliberate together before making a plan.
CodexMaxx
Manage Codex accounts, usage, and active sessions on macOS.
React Hanger
A collection of useful React hooks.
React Genie
Animate React elements as they enter the viewport.
MobX Router
A simple router for MobX and React apps.

All projects · GitHub · Follow on X · YouTube