Getting started in depth

Use a URL you’re allowed to test—staging, preview deploys, or public marketing sites are ideal. The in-browser scan scores real page signals from fetched HTML (quality, security, and crawlability heuristics) and highlights issues found in that snapshot.

After each completed run, check Results for the bar chart (synced to that run), the activity line with URL and time, the table row for “last analyzed,” and—when the fetch succeeds—Fetched page HTML with the markup we pulled for that run (stored locally, may be truncated). On Run analysis, expand “View fetched page HTML” under findings for the same snapshot.

The three modules

Lint stands in for HTML, CSS, and front-end hygiene checks—messy markup, outdated patterns, and consistency issues that are easy to miss in review.

Shield represents security-oriented signals you’d normally chase in multiple tools: headers, cookies, mixed content, and similar basics that should be true on every deploy.

Crawl focuses on link and route health—broken internal links, obvious traps, and structural issues that confuse users and search engines.

Together they produce one overall score plus per-module scores so you can see whether you’re failing on quality, security, links, or a mix.

Scan settings (roadmap)

Scans run all three modules in one pass. Future controls will include module toggles, crawl-depth caps, and ignore lists (paths, third-party hosts, noisy rules) so larger sites remain manageable.

Plans, scans & billing

Pricing tiers on the Pricing page describe illustrative scans and history windows. The in-app Billing page reads your current plan label from user metadata when present; otherwise it shows “Free” and explains that payment methods and invoices appear once you connect a provider.

Account & security

Authentication uses Supabase email/password. Use a strong password and sign out from the header or sidebar when you’re on a shared machine. For processing and retention details, read the privacy policy.

Troubleshooting

• Stuck on sign-in after clicking Dashboard: Complete sign-in first; the app redirects back when a session exists.
• Results never update: Ensure the scan finishes (button returns to “Re-analyze”), and that third-party cookies or storage aren’t blocked for this origin.
• Blank workspace: Hard-refresh once; if a hash doesn’t match a known route, the app falls back to the marketing home.

Roadmap & integrations

We’re prioritizing the in-browser experience, honest empty states, and account-backed scan history. APIs, webhooks, Slack notifications, and org-wide policies are on the long list—if you have a concrete need (SSO, export format, CI token), email hello@areion.dev with your stack and timeline.

Need help?

Product questions and bug reports: support@areion.dev. We read everything; include your browser, the URL shape you scanned (domain only is fine), and what you expected versus what you saw.

About us

We’re a small team obsessed with the gap between “we should check that” and “we actually checked it.” Most teams know they should care about markup quality, headers, cookies, and broken links—but those checks are easy to defer until something breaks in production or an audit lands on someone’s desk.

Areion exists to shrink that gap. We care about clarity: scores and findings you can explain to a teammate, not jargon that only a specialist can parse. We care about focus: surfacing what matters for the URL you’re looking at, not a thousand noisy alerts. And we care about meeting you where you work—in the browser, with flows that feel fast and intentional rather than bolted on.

We’re early. The product will evolve, but the direction won’t: help builders ship sites they’re proud of, with fewer surprises after deploy.

What we care about

Actionable output. Every report should answer “what should I do next?”—with enough context to prioritize, not just enough data to feel overwhelmed.

Plain language. Security and quality matter to everyone on a team, not only to people who live in RFCs. We write for humans first and link to the deep cuts when you want them.

Respect for your time. Fast paths for common tasks, sensible defaults, and honest limits when something isn’t ready yet. No dark patterns, no fake urgency.

Privacy-aware design. We assume you’re scanning real URLs and real properties. We describe what we process, how long it might be retained, and how to ask questions—see our privacy policy for the details we publish today.

How we work

We ship in small iterations: tighten the scan experience, improve how results are explained, and expand coverage where it helps the most people. Feedback from people who run sites—agencies, indie makers, platform teams—shapes what we build next.

If you’re evaluating Areion for a team, we’re happy to talk through your workflow, what you’re trying to catch before release, and how we can fit (or where we’re not the right tool yet).

Contact

General & product questions: hello@areion.dev — Tell us what you’re trying to accomplish (e.g. pre-launch checks, ongoing monitoring, teaching a client). We read everything; response time varies but we aim to get back within a few business days.

Partnerships & integrations: Same inbox—use the subject line “Partnership” and include your company site, audience, and what you have in mind (integration, co-marketing, education, etc.).

Press & speaking: press@areion.dev — Pitches, fact checks, or interview requests. If you’re on a deadline, say so in the first line and we’ll do our best to respond quickly.

Security concerns: If you believe you’ve found a vulnerability in how we handle data or our product surface, email security@areion.dev with a short description and steps to reproduce. We take responsible disclosure seriously.

Privacy & data requests: privacy@areion.dev — Questions about the policy, deletion, or regional requests; we’ll route you to the right person.

We don’t publish a phone number or mailing address on this marketing page. If your procurement process requires a formal address or vendor form, mention that in email to hello@areion.dev and we’ll work with you.