Zeea
Help1. What Zeea reads from your website2. Credits and plans3. Channels and Buffer4. From a plan to a published month5. Your data: the trash, the export, and leaving

What Zeea reads from your website

What it takes from the site, what it keeps only with your say-so, and why one address can fail.

What it reads

Give a brand its website and Zeea reads it twice. The first pass reads for the brand: how the studio describes itself, the words it uses and avoids, the colours and type it seems to keep to, the people it names. The second pass reads for the work: every project or case study the site holds, with the facts its own page states and the pictures its own page shows.

Reading is free. It spends none of your credits, however large the site, and you can read a site again whenever it has changed.

What it keeps only with your say-so

Everything the brand pass finds arrives as a proposal. It sits in the brand library marked as proposed until you keep it, edit it, or drop it, and only what you kept is ever used to write a post. A machine reading a website can be wrong about what a studio sounds like; a proposal has no authority until you give it some.

Reading again never deletes what you kept, and never asks you the same question twice. A new read can only add proposals.

What counts as work

Portfolios come in two shapes and Zeea looks for both: a folder of project pages under one section, and a flat site where every project is its own top-level page listed from somewhere. It does not go by the words in the address, so a portfolio called /bouquets or /proiecte is found as readily as one called /work.

A site whose whole portfolio is one page is read as one page: Zeea looks at the pictures in the order the page shows them and asks which belong to the same piece of work. A page kept for its pictures rather than as a project is loose media: it is off by default, never picked for a campaign on its own, and holds at most six pictures from any one page, so a site with a thousand renders does not bury the twenty projects that matter.

The pictures

After a read, Zeea looks at the pictures themselves: for each project it says whether they are photographs, renders or drawings, what each one shows, and whether the work is finished, not yet built or in progress. That reading is shown in blue on the project in your library; tap it to correct it, and your answer turns green and stays through every later read. A campaign is written to it, so a render is never described as a photograph and a scheme not yet built is never described as standing.

Every post is built around your own pictures, taken from the site at the size the site serves them. Most website builders serve copies no wider than about 2,500 pixels, which is plenty for a feed post and tight for a tall story. Zeea lets you frame past the sharp size up to a declared limit, and tells you when a crop has gone soft rather than publishing it quietly.

Why an address can fail

  • A bare host. studio.example is not a page; https://studio.example is. Zeea now fills in the rest, but a site that answers only on www. still needs it typed.
  • A site that hides its pages. Some builders serve a blurred miniature as the first picture on a page and keep the real one elsewhere; Zeea knows where to look on the common ones. A site behind a login, or one that draws every page with a script and shows a crawler nothing, cannot be read.
  • No portfolio to find. A site with a homepage and a contact page reads fine for the brand and gives Zeea nothing to write about. The Planner says so rather than inventing projects.

If a site you know holds work comes back with nothing, tell us with Something is wrong… under your avatar and name the site. Every shape of portfolio Zeea reads today, it learned from one that failed.

NextCredits and plans
hello@zeea.aiTerms of ServicePrivacy PolicyRefunds & Cancellation