Glossary

Need a definition? This glossary explains every PageFork concept in one sentence, with a link to the full article when one exists.

Core concepts

Site

A site is one PageFork project — one set of pages, one style, one domain. Every site has its own version history, its own leads and people, and its own plan.

Page

A page is a single URL inside a site (for example, the home page, an about page, or a pricing page). PageFork sites can be single-page or multi-page; you control this with prompts.

Generation

A generation is the first-time creation of a site from your prompt. Generation uses generation credits and typically finishes in under a minute.

Edit

An edit is any change you make to an existing site by typing an instruction in plain English. Edits use edit credits.

Prompt

A prompt is the natural-language instruction you type to generate or edit a site (for example, “Create a landing page for a dog-training business in Austin”).

Version

A version is a saved snapshot of your site at a point in time. Every generation and every edit creates a new version. You can preview any version, revert to it, or fork from it.

Fork

A fork is a branch of your version history. Forking lets you explore an alternative direction without losing the current one — useful when you want to try a redesign or test a different hero.

Fork tree

The fork tree is the full graph of versions and forks for a site. It’s how you navigate and compare directions.

AI & editing

Questions and edits

PageFork uses one chat composer for everything. Questions get a conversational reply without changing the site. Change requests apply your instruction and create a new version. See Questions and edits.

File upload

A file upload attaches an image, video, PDF, or other file to a prompt as a URL badge. PageFork reads it for context or places it on your site depending on your message. Uploads are saved to your media library. See File uploads.

Reference website

A reference website is a public URL you paste into chat so PageFork can map pages, read content, and screenshot the live site before generating or editing. See Reference websites.

Cookie consent modal

The cookie consent modal is PageFork’s built-in banner for gating analytics and marketing cookies. It stays off until you add cookie-setting trackers or ask for a banner. See Cookie consent and privacy.

Media library

The media library is your organization’s shared file storage — every upload and generated image is saved here for browsing, filtering, and reuse. See Media library.

AI image generation

AI image generation creates custom visuals on the Images page or inline in the site editor when Create Image is enabled. Generated images cost credits and are saved to the media library. See AI image generation.

Model tier

A model tier is the AI quality level for a generation or edit — Standard, Advanced, or Premium. Higher tiers usually cost more credits. See Model tiers.

Credits & billing

Credit

A credit is PageFork’s unit of AI work. Credits are consumed by generations and edits. Credits never expire and are shared by every site in your team; new accounts start with 25 free. See Credits explained.

Credit pack

A credit pack is a one-time purchase of credits: 100 for €10, 300 for €25, 750 for €50 or 2000 for €100. Buy them on the Credits tab of the Billing page. See Purchasing credits.

Auto top-up

Auto top-up buys a chosen credit pack with your saved card whenever your balance drops below a threshold you set — at most twice per calendar month. It’s off until you turn it on under Billing → Credits, and pauses itself if the card is declined.

Generation credit

A generation credit is spent the first time you turn a prompt into a site.

Edit credit

An edit credit is spent each time you change an existing site with a prompt.

Site plan

A site plan is the per-site monthly or yearly plan — Basic or Pro — that keeps a site live on PageFork’s CDN with SSL on your own domain. Each published site needs one; drafts don’t. Manage plans on the Subscriptions tab of the Billing page. See Basic and Pro plans.

Apex domain

An apex (or root) domain is the bare domain without a subdomain — for example, pagefork.ai. The opposite is www.pagefork.ai. See Apex vs WWW.

Publishing & domains

Publish

To publish a site is to make its current version live on a custom domain you own. It requires a verified domain and a plan (Basic or Pro) for the site. See Publishing overview.

Unpublish

To unpublish a site is to take it offline while keeping all its versions, submissions and leads intact.

Preview link

A private, revocable URL that shows a chosen draft version to anyone you send it to — free, and without a domain or plan. The way to share work before publishing. See Preview links.

Custom domain

A custom domain is any domain you own, connected to a PageFork site via two DNS records. See Connecting your domain.

SSL certificate

PageFork automatically issues and renews a free SSL certificate (via Let’s Encrypt) for every custom domain once DNS verification succeeds.

Forms & submissions

Form

A form is a lead-capture block on a page (contact, waitlist, booking). PageFork generates forms from your prompt; every submission becomes a person and a lead on the Leads page. See Forms overview.

Submission

A submission is one entry someone made by filling out a form on your site, stored exactly as it was sent. Each submission is filed under a person and attached to one of their leads, and can be exported to CSV.

Field schema

A field schema is the list of fields a form sends. PageFork uses it to tell which answers are the person’s name, email, phone and company, and which become custom fields. See Form field schemas.

Leads & people

Lead

A lead is one piece of potential business with a person — an enquiry you work from first contact to won or lost. A lead sits in a stage of the pipeline and collects submissions, notes and follow-ups. A person has at most one open lead at a time. See Leads overview.

Person

A person is one human being on one site: name, email, phone, company, tags and custom fields. A person can have many leads over time but stays one record, recognised by email and then by phone. See People.

Pipeline

The pipeline is a site’s ordered list of stages that leads move through. Each site has its own. See Lead pipeline.

Stage

A stage is one step in the pipeline. Every stage is either open (still being worked), won or lost. New sites start with New, Contacted, Qualified, Won and Lost; owners and admins can change them.

Follow-up

A follow-up is a to-do on a lead with a due date — “call back Tuesday”. Follow-ups appear on the lead and in the calendar until completed. See Follow-ups and tasks.

Activity

An activity is something you log against a lead: a note, call, email or meeting. Activities appear on the timeline of the lead and of the person, alongside submissions and the history of changes.

Custom field

A custom field is an extra detail kept on each person beyond the four built-in ones — budget, event date, service wanted. Fields are picked up from your forms or added by hand. See Custom fields.

Tag

A tag is a short free-form label on a person, such as vip or wedding. Tags are lower-case and belong to the person, so they show on all of that person’s leads. See Tags.

Merge

To merge is to fold two records for the same person into one, moving every lead, submission and note onto the record you keep. It can’t be undone. See Merging duplicates.

Erase

To erase a person is to permanently delete them together with their leads, submissions, notes and history. See Erasing a person.

Plans

Basic

Basic (€5/month or €50/year per site) publishes a site on your own domain with SSL. Forms capture every submission; the Leads page shows a plain list of submissions with CSV export, and you get the notification email. A site without Pro has Basic features. See Basic and Pro plans.

Pro

Pro (€14/month or €140/year per site) unlocks the full CRM for a site — the board, list, calendar and people views, lead records, custom fields, tags, import — plus destinations, Zapier and Make, the analytics dashboard, and no “Built with PageFork” footer. See Basic and Pro plans.

Pro trial

The Pro trial is the 14 days of full Pro features that every new site starts with. When it ends, the site shows the Basic view unless you upgrade; your submissions and leads are kept.

”Built with PageFork” footer

The Built with PageFork footer is a small credit shown at the bottom of every page of a published Basic site. Pro removes it.

Storage allowance

The storage allowance caps how much your team can keep in the media library: 100 MB or 100 files free, plus 500 MB / 500 files per Basic site and 2 GB / 2000 files per Pro site. When it’s full, uploads are refused until you delete files or add or upgrade a plan; nothing is deleted for you.

Integrations

Destination

A destination passes form submissions on to another tool as they arrive — a Google Sheet, email, Kit, Mailchimp, a webhook, Zapier or Make. Destinations are set per site, under the Forms tab of the editor. See Destinations overview.

Stage trigger

A stage trigger makes a destination fire when a lead moves into a chosen stage, instead of (or as well as) when a new submission arrives — for example, tell another system when a lead is won.

API key

An API key lets the PageFork Zapier and Make apps act on behalf of your team. Owners and admins create and revoke keys on the Team page; a key is shown only once. See API keys.

Managed hook (Zapier/Make)

A managed hook is a destination that the Zapier or Make app creates for you when you switch on a Zap or scenario. It is labelled Managed by Zapier or Managed by Make, and you change it in that tool rather than in PageFork. See Zapier app and Make app.

---

Missing a term? Email support@pagefork.ai and we’ll add it.