SEO
Titles, social cards, indexing, canonicals, links, sitemaps, hreflang, structured data, and JavaScript rendering.
Public beta · free while we test · 110 checks
A release check for every page of your website
Arachne renders each page in a real browser and finds what will cost you visitors: SEO gaps, slow pages, unreadable text, broken links, and missing security headers. Then it tells you how to fix them.
Arachne · example.com
Arachne
Report
OverviewSEO9Performance6Accessibility4Content1Security2PagesChangesCompared with last scan5 fixed · 2 new
example.com
Scan of 48 pages · compared with the previous scan
Health score82+6
Critical
21 fewer
Top issues
Ranked by impactSLOW_LCPcritical· Speed and Core Web Vitals · 3 pages
Synthetic lab Largest Contentful Paint is 3000ms (threshold: 2500ms)
Fix: Find the LCP element in the evidence. If it is an image, don't lazy-load it, give it fetchpriority="high", and serve it at its displayed size; if it is text, remove render-blocking resources ahead of it.
Source: web.dev
- BROKEN_INTERNAL_LINKSLinks and status codes · 2 pagesdevelopers.google.com
- IMAGES_WITHOUT_ALTImages · 7 pagesw3.org
- MISSING_CANONICALIndexing and canonicals · 4 pagesdevelopers.google.com
- MISSING_HSTSSecurity headers · 12 pagesdeveloper.mozilla.org
By category
Issue groups by severity
- SEO9
- Performance6
- Accessibility4
- Content1
- Security2
What Arachne checks
One scan that renders, reads, and ranks every issue on your site
Page checks run on every rendered page. Site checks look across all of them: duplicate titles, broken internal links, orphan pages, sitemap gaps, and canonicals that point the wrong way.
Performance
Core Web Vitals measured in a real browser, page weight, requests, and images.
Accessibility
Color contrast, document language, headings, form labels, and alt text.
Content
Thin, placeholder, duplicate, and near-duplicate content across the site.
Security
Security headers and mixed content on pages served over HTTPS.
Changes
Every finding has a fingerprint, so each scan shows what you fixed, what is new, and what is still open since the last one.
How it works
The checks a careful reviewer would run, on every page, every release
- 01
Render
Each page opens in headless Chromium at a mobile profile, the way Google indexes it. Links, the sitemap, and robots.txt decide what is crawled.
- 02
Analyze
110 checks read the rendered page and the raw HTML. Every finding carries its evidence, the source behind its severity, and a fix.
- 03
Compare
Issues are ranked by impact and matched with the previous scan, so a release shows exactly what it fixed and what it broke.
Counted from the registry, not from a slide
Every check is defined once in the engine, with its category, severity, basis, source, and fix. These numbers come straight from that list.
110
checks on every scan
Across 5 categories and 16 groups
77
backed by a published source
WCAG, Google Search Central, web.dev, MDN
29
site-wide checks
Duplicates, links, sitemaps, and canonicals across pages
Evidence, not opinions
Every severity has a source, every finding a fix
- Documented (77)
- Backed by a published standard or guide: WCAG, Google Search Central, web.dev, MDN. The source is linked on the finding.
- Heuristic (33)
- Good practice without a hard rule, labelled as such. A heuristic is never marked critical, so it never drowns out a real problem.
warningdocumentedaccessibility
INPUTS_WITHOUT_LABELS
2 input(s) missing associated labels
Fix
Associate each control with a <label for="…">, wrap it in a label, or give it aria-label.
Source
www.w3.org/WAI/WCAG22/Understanding/name-role-value(opens in a new tab)Sites, schedules, and teams
Every site you run
Each site is a project with its own scans and history, so a marketing site, an app, and a docs site each get their own baseline.
Scheduled scans
Run a scan daily or weekly. Each one is compared with the scan before it, so a regression shows up the day it ships.
Teams
Share a workspace with the people who ship the site, with owner, admin, and member roles and invitation links.
Public beta
Everything is free while we test
Arachne is in public beta. There are no plans and no billing yet: every check and every feature is free while we test it on real sites. Expect rough edges, and tell us when a report looks wrong.
Free scan
No account
- One scan of up to 10 pages
- All 110 checks, with sources and fixes
- Report kept for 7 days at a private link
- Up to 3 scans a day
Free account
Everything, free during the beta
- Crawls of up to 500 pages, across as many sites as you need
- Every scan compared with the previous one
- Daily or weekly scheduled scans
- Teams with owner, admin, and member roles, invited by link
- Page detail with the evidence for every finding
Frequently asked questions
How Arachne scans, what it checks, and where its severities come from.
Yes. Arachne is in public beta, so there are no plans, no billing, and no card to enter. Every feature is free while we test it on real sites.
Know what your next release breaks before your visitors do
Scan up to 10 pages now, free and without an account.