# GlowUp
## AI-native resume-to-website builder

> From resume to hiring-agent-ready website.
> Premium, SEO/AEO-ready candidate sites that humans and AI sourcing agents can both read.

## What GlowUp is
GlowUp is an AI-native resume-to-website builder. It takes a resume (or practice description) and generates a premium personal site built for two audiences at once: humans who read it in a browser, and AI agents that fetch it on behalf of recruiters or hiring teams.

Generated sites are designed for discoverability, not lock-in. They are candidate-owned, exportable, and built on open AEO conventions (llms.txt, agent.json, JSON-LD) rather than proprietary formats.

## Who it is for
- **Candidates** who want a premium, recruiter-readable site instead of just a PDF resume.
- **Consultants and solo practices** who need a conversion-focused practice page, not a CV.
- **Recruiters, hiring teams, and AI sourcing agents** who need fast, structured access to candidate proof, FAQ, and contact endpoints.

## What GlowUp creates
- A SEO/AEO-ready candidate website with role-fit positioning.
- Semantic HTML with crawlable, prerendered copy.
- Stacked JSON-LD: Person or Organization, WebSite, ProfilePage, FAQPage.
- A machine-readable candidate profile at `/candidate.json` (JSON-Resume-shaped).
- An agent manifest at `/.well-known/agent.json` describing capabilities and endpoints.
- Long-form markdown dumps at `/llms.txt` and `/llms-full.txt`.
- A sitemap and a robots policy that allows AI/answer-engine crawlers known at publish time.
- Recruiter Q&A surfaces (FAQPage on the rendered site, plus Q&A in the markdown dumps).

## Why it gets found
GlowUp sites are written to be readable by non-JS fetchers, not just modern browsers. That means:

- The site includes public AI-readable files and a non-JS fallback so crawlers and agents can access core GlowUp context even when they do not execute the full app.
- Structured data is inline so search engines and AEO scanners can parse it without executing JavaScript.
- Public AI-readable files (`llms.txt`, `llms-full.txt`) are available for crawlers, answer engines, and agents that support these conventions.
- An agent manifest at `/.well-known/agent.json` advertises what the site represents and how to engage it.

This improves the odds of discovery and citation by AI answer engines and recruiter agents. Discovery is improved, not guaranteed — third-party indexing and ranking remain outside our control.

## Privacy and ownership
- Generated sites are candidate-owned. GlowUp does not claim ownership of the published site.
- Private evidence, target job descriptions, and any testimonials flagged as private are filtered out of every public asset (HTML, JSON-LD, llms.txt, llms-full.txt, candidate.json, agent.json).
- Only derived, role-focus signals are surfaced publicly — the raw target JD is never exposed.
- GlowUp does not require accounts to read public AEO files. Interactive endpoints (Ask, Match, beta request, render, export) are rate-limited and protected, but the public landing files remain crawlable.

## Recruiter and AI-agent readiness
GlowUp sites are written so a recruiter or sourcing agent can answer "should we contact this person?" without reading the whole site:

- **Hero and role-fit** — what the person does and the roles they fit, at the top.
- **Capability proof** — capability buckets with proof and source, when provided.
- **Recruiter Q&A** — common questions answered inline (FAQPage JSON-LD), readable by both humans and agents.
- **Recruiter-readable proof** — testimonials marked public are surfaced; private ones are stripped from public assets.
- **Contact** — generated candidate sites may expose public-safe contact preferences and LinkedIn links when the candidate chooses to make them public.

For sourcing agents on **generated candidate sites**:
- Start at `/.well-known/agent.json` to discover endpoints.
- Read `/llms-full.txt` for full public context.
- Use `/candidate.json` for structured profile data on candidate sites.
- Contact via public-safe channels listed in the manifest when the candidate exposes them.

## Solo practice and consultant support
For consultants and solo practices, GlowUp shifts the template:
- Uses Organization JSON-LD instead of Person.
- Generates a conversion-focused practice page (value-first hero, capability proof, engagement model) rather than a chronological resume.
- Keeps the same AEO surface (llms.txt, agent.json, sitemap, JSON-LD) so the practice is equally readable to AI agents and search.

## Lovable handoff
Generated sites can be exported and handed off so the candidate can host and own the site themselves. GlowUp is the builder; the output is the candidate's. The export contains the static site plus all public AEO files so discoverability follows the site wherever it is hosted.

## Public files on this domain
- `/` — GlowUp homepage
- `/llms.txt` — short AEO summary (this file's short form)
- `/llms-full.txt` — this document
- `/sitemap.xml` — sitemap
- `/robots.txt` — crawler policy and sitemap directive
- `/.well-known/agent.json` — agent manifest

## What this file does not contain
- No system prompts.
- No proprietary builder logic.
- No private evidence, raw resumes, or target job descriptions.
- No API keys, secrets, or backend URLs.
- No Lovable editor or project state.
- No claims of guaranteed search or AI-answer-engine ranking.