Repository navigation
SEO Audit Studio: a free web app that turns claude-seo audits into branded, multilingual PDF reports #353
nordkite
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone 👋
I use claude-seo for client audits, and the slow part was always what came after the audit: turning the findings into a branded PDF the client can read, in their language. So I built a free, open-source web app on top of claude-seo for that, and I'm sharing it in case it helps someone else.
Repo: https://github.com/nordkite/seo-audit-studio (MIT)
How it works
It's a local web app called SEO Audit Studio. You do everything in the browser:
What it adds to claude-seo's coverage
claude-seo does the auditing, and the app adds a few checks that claude-seo 2.4.2 doesn't run as part of an audit:
seo-auditnever callsseo-hreflang, andseo-pageonly checks that the tags exist, not reciprocity orx-default.seo-audithas no image subagent.twitter:image, and without it X shows shared links with no picture even whenog:imageis set.seo-pageis a single checklist, so the app also runs the technical, content, schema, performance, visual, GEO, agentic and SXO subagents on that one URL.It's also strict about coverage. If a check didn't run, the report lists it under "Not covered" rather than quietly showing a pass. Each addition is documented with the gap it fills, and gets removed once claude-seo covers that gap itself.
Google data (optional)
If you've connected Google through claude-seo (
/seo google setup), the report puts the data to use:The report's Method section shows which data sources were used and why any were missing. For client sites, the client just adds your service account to their Search Console property as a Restricted user.
Its own PDF, not claude-seo's
This is not claude-seo's built-in PDF report with a new logo. The app saves the findings as structured JSON and has its own renderer: an HTML/CSS print template turned into a PDF with headless Chrome (Puppeteer) and pdf-lib. So you get a different report: a branded cover, a findings overview, severity-grouped findings with evidence, metrics, your own custom sections, and a separate "Not covered" list. Because the data and the layout are kept apart, the same audit can be rendered in any language without re-running it.
Getting started
You need Node 22.18+ and Claude Code, installed and logged in. The app uses your Claude Code login to run audits.
Let me know if you have any questions or ideas for the improvements.
All reactions