What is Existence Compiler?

It is an analysis system that takes your project URL and returns a Digital Existence Score plus an actionable report. It evaluates technical presence, semantic clarity, AI readability, trust signals, and distribution readiness.

What is the Digital Existence Score?

It is a score from 0 to 100 calculated by deterministic rules. It measures how detectable, understandable, and shareable your project is for search engines, AI agents, and social platforms.

Does it guarantee traffic, sales, or indexing?

No. Existence Compiler diagnoses technical and semantic gaps. Improving those conditions increases the likelihood of being discovered, but does not guarantee specific outcomes.

Which pages does it analyze?

In the current MVP it analyzes the main page of the URL you provide, plus checks for common pages such as /about, /pricing, /faq, /contact, /docs, /changelog, /security, /privacy, and /terms.

Yes. The Free plan is completely free and requires no account. You can analyze any URL and download the report in Markdown or JSON.

Does it store my data?

Existence Compiler stores minimal analysis metadata server-side to enable before/after comparisons, such as URL, score, timestamp and a compact report summary. Shared reports are stored with a 30-day TTL. It does not store raw HTML, full page text, raw schema dumps or unnecessary crawl payloads. No account is required for the free analysis flow.

Does it work with SPAs or React/Vue/Angular apps?

The analysis may be incomplete for JavaScript-rendered apps. The crawler fetches the initial HTML without executing JavaScript, so metadata injected only at runtime may not be detected.

It is a simple text file that helps AI systems understand what your project is and how to reference it. Existence Compiler generates a ready-to-use llms.txt snippet based on your detected content.

Does it use AI for analysis?

The main analysis is deterministic (rule-based). An optional AI enhancement layer can generate a deeper semantic summary if enabled, but the core report and score do not require it.

Example

Digital existence roadmap

The action plan from an Existence Compiler analysis is not a list of suggestions. It is a phased roadmap with concrete tasks, estimated effort, and projected score impact. Here is what a typical execution plan looks like.

Starting point

A new product with a live domain, basic HTML, no metadata, no Open Graph, no schema.org, and no trust pages typically scores 8–18 / 100 on the Digital Existence Score. The roadmap below shows a realistic path to 60+.

Execution roadmap

Phase 1 — Foundation (1–2 hours)

+15–20 pts

·Set a clear, keyword-relevant <title> tag
·Write a 140–160 character meta description
·Add <link rel="canonical">
·Create /robots.txt
·Create /sitemap.xml with main pages

Phase 2 — Social & AI layer (2–3 hours)

+18–24 pts

·Add Open Graph: og:title, og:description, og:image, og:url
·Add Twitter Cards meta tags
·Add schema.org JSON-LD block (WebApplication or WebSite)
·Create /llms.txt with product summary and key links

Phase 3 — Trust & structure (3–5 hours)

+12–18 pts

·Create /about page with clear product description
·Create /privacy policy page
·Create /terms of service page
·Add HTTP security headers (X-Frame-Options, X-Content-Type-Options)
·Create /faq page with structured FAQ schema

Phase 4 — Distribution readiness (ongoing)

+8–12 pts

·Add favicon and apple-touch-icon
·Set og:image with 1200×630 branded preview image
·Create /changelog or /updates page
·Submit sitemap.xml to Google Search Console

What the roadmap does not include

This roadmap covers technical and structural existence signals. It does not cover off-page signals (backlinks, citations, social mentions), content marketing, or paid acquisition. Score projections are estimates based on deterministic rules, not guarantees of search performance.

Generate your roadmap More examples

AI product brief →Landing page metadata →Turn idea into MVP →