Honest score.
Real render.
The fix, in a pull request.
Most audit tools either measure a synthetic estimate, or report the truth and stop there. ifySEO does neither — it renders the page for real, scores it with math you can read, and then closes the loop in your repo.
The math is on the page.
Every issue costs severity points × category weight, the penalties add up, the score is 100 minus the total, clamped at zero. The numbers below are not marketing copy — they are read straight out of the scoring engine.
A broken canonical (HIGH × Technical SEO) costs 12 points. A faint console warning (LOW × Code quality) costs 1. They are not equivalent — and the score reflects that.
- CRITICAL
- −25 pts
- HIGH
- −12 pts
- MEDIUM
- −5 pts
- LOW
- −2 pts
- INFO
- −0 pts
- Technical SEO
- × 1.00
- Content SEO
- × 1.00
- Security
- × 1.00
- GEO / LLMO
- × 1.00
- Performance
- × 0.85
- Accessibility
- × 0.85
- Code quality
- × 0.50
A synthetic estimate is not a measurement.
The cheaper way to build an audit is to read your HTML and guess. ifySEO opens a real Chromium, throttles it to a mobile-slow4g profile, lets the page actually load, and reads what the browser reports.
| Question | Static / synthetic tools | ifySEO |
|---|---|---|
| Where do Core Web Vitals come from? | Estimated from source analysis or a Lighthouse run. | Measured by Google's `web-vitals` library in a real throttled Chromium. |
| Does the audit run JavaScript? | Often not — the HTML is parsed, but the page never runs. | Yes. A real headless render: scripts execute, the DOM mutates, axe sees it. |
| Are console errors captured? | Rarely — needs a real browser to observe. | Every console error and uncaught exception during the render is captured. |
| Is the WCAG audit on the source or the page? | Source-level rules miss anything injected by JS or styled with CSS. | axe-core runs against the live DOM, with computed styles and ARIA. |
| How are findings prioritized? | Flat lists. You guess what to fix first. | Severity × category weight, surfaced with a single 0–100 score. |
| What happens after the report? | You read it. The fix is yours. | An AI engine reads the report, edits your source, opens the PR. You merge. |
Note: CDP throttling is not Lighthouse's simulated throttling. Our numbers are directionally comparable to PageSpeed Insights but will not match it exactly. Thepipeline page → has the engineering detail.
The only audit that closes the loop in your repo.
Every other tool stops at the report. ifySEO has a second engine: install the GitHub App, pick the issues, and an AI agent edits your source on a fresh clone and opens a pull request. You review the diff. You merge.
Free is read-only. Growth runs 10 fix runs a month, Pro runs 50. The merge decision is always yours.
What ifySEO is not.
A clear product is as much what it doesn't do as what it does. So that nothing here surprises you:
- Not a rank trackerWe do not pull SERP positions for keywords. There are good rank trackers; this is not one.
- Not a keyword research toolWe measure how findable and how well-formed your pages are, not which keywords to target.
- Not a backlink crawlerWe do not map off-site links to your pages. The audit is the page itself, top to bottom.
- Not a CMS pluginifySEO scans any public URL. There is no WordPress plugin, no Shopify app, no install step.
- Not a competitor scraperThe fix engine works on a repo you own and the GitHub App is installed on. We scan competitors as comparison only — never to extract their assets.
See an honest score on your page.
Free, no card. The fix engine is one plan up.