How the Page Factory works
A client's 90 day strategy turns into 4 new pages a month. Each page wears the client's own look. Each one is built to be found in Google, on Maps and in AI answers. This page explains the whole run in plain words, who owns each step, and how long it takes.
Four pages a month, in their look
The plan comes from the strategy the client already approved. It names the searches people type and the pages the client is missing. The factory turns four of those rows into four finished pages every month. A service page sells one service. A location page covers one town or one set of venues.
Every page is written by our own agents. Search Atlas does not write our pages anymore (Justin, October 20, 2026). Every claim comes from the client's own site, the client, or a public source we keep on file.
The client owns every page. The page sits on their site, in their design, and keeps working if they ever leave us.
Two ways a page ships
The batch file for the month says which route the client is on. Everything up to Justin's approval is the same on both routes.
WordPress clients
Each approved page lands as an editable draft in the client's own WordPress, built with their page builder, so their team or ours can change a word later without us. We never publish it. Our WordPress team reads it and publishes.
Sites we build
The page goes into the site we built for the client. The copy, photos, gate and staged review run the same way. Placing the page into each site's own source is a step per site and has not been run yet.
The monthly run, step by step
Eleven steps, in this order. A step does not start until the one before it is done. The times are targets for one batch of 4 pages.
| Step | Owner | Time | What happens |
|---|---|---|---|
| 1. Batch from the strategy | Marshall | About 30 minutes, first week of the month | Four rows from the approved strategy go into the month's batch file: title, address, main search, why it matters, links to use and the route. |
| 2. Copy | Mason | About 1 hour a page | Our agents write every word. A town or venue page also gets a facts file with 8 or more sourced facts about that place. |
| 3. SEO review | Vega | About 30 minutes for the batch | Main search, title, description, internal links, questions and schema checked against the strategy and the live site. |
| 4. Copy and design review | Scarlett | About 30 minutes on the copy, again on the rendered pages | Plain words, nothing we cannot back up, the client's own voice. After the render, the look against the client's own pages. |
| 5. Render and gate | Mason | Minutes, one command | The factory picks the client's own photos, builds each page in the client's look and runs the gate. A failed check stops that page. |
| 6. Staged review | Marshall | Same day | Marshall puts the pages on the client's review address at swarmsystem.ai. Search engines are told not to list them. The desks review there. |
| 7. Justin's approval | Justin | One sitting | Justin reads the batch page and approves each page. Nothing goes into a client site before this. |
| 8. WordPress drafts | Mason | About 10 minutes a page | Each approved page is built as a draft in the client's WordPress with their page builder. Draft only, no address set, never published by us. On a site we build, the page goes into our build instead. |
| 9. Measured match | Mason, checked by Scarlett | Runs with step 8 | The draft is measured against the approved page on a laptop and a phone screen: headings, photos, cards, steps, questions and buttons. Every check must pass. |
| 10. Review and publish | Our WordPress team | About 15 minutes a page | The team opens each draft in WordPress, reads it and publishes it. Haven drafts the note to the client, and Justin approves the send. |
| 11. Publish day checks | Our WordPress team, with Mason | About 10 minutes a page | Set the address from the batch, take off any old redirect on that address, paste the schema snippet, then run the gate on the live page and check it is in the sitemap. |
The Hive Mind dashboard shows the same steps under Page Factory, How it works, and each client's batch under Batches.
What it copies and what it builds
Their look, automatically
- The header and the full menu, link for link
- The footer
- Their fonts and their colors
- Button, question and band colors from one reference page: a page of theirs we already like
- Business name, phone and service area from their site
The same strong page parts
- Photo and copy sections that switch sides as you scroll
- A row of cards with photos
- Numbered steps joined by a line
- 4 to 6 real questions in an open and close list
- A call band, and a call bar on phones
- Schema, so Google and AI tools read the business and the service
- Links to the client's own live pages
- 6 to 12 of the client's own photos, never one used twice in a month
The checks that block a bad page
The gate runs on every page before anyone reviews it. One failed check stops that page and names what to fix. These are the ones that catch the most.
- Contrast. Body text and notes must read at 4.5 to 1 or better on their background.
- No word alone on a line. Headings, paragraphs and buttons are checked at 5 screen widths, from a phone to a wide monitor.
- No dead links. Every link must answer on the live site. A link that redirects does not count.
- Photo rules. The client's own photos first, alt text on each, the top photo loads first, no captions, no photo used twice, and photos that look made by AI are left out unless a person clears them.
- Menu match. The page's menu must have the same links as the live site.
- Plain words. Short sentences, no banned words, no review counts or star ratings we cannot show.
- The WordPress measured match. On the WordPress route the draft must match the approved page on every measured check, on a laptop and a phone screen.
The first batch, Ventura
Ventura Rental was the first client through the whole run, in October 2026: four pages, two service pages and two venue guides.
What is proven and what is not yet
- WordPress with Elementor and the JupiterX theme
- Behind the Sucuri firewall
- Drafts that match the approved page on a laptop and a phone screen
- The client's own photos, look and menu
- A second theme or a second page builder
- Tablet widths, between a phone and a laptop, are not measured
- Some firewalls block schema sent in a draft. On Ventura the schema goes to our team as a snippet they paste in
- The route for sites we build, past the staged review
How to start a new client
- Pick the reference page. One page on their site whose look we like. Its colors win over the home page.
- Scan the site. The factory reads the header, menu, footer, fonts and business facts into the client's look file.
- Write the skin. Fonts, colors and the reference page go in one small file. Change that file, never the code.
- WordPress only: write the draft settings. Copy Ventura's file, then read the new site's own pattern page, theme, firewall and question widget into it.
- Write the first batch. Four rows from the approved strategy, with the route set. Then the monthly run starts at step 2.
Where everything lives
| What | Where |
|---|---|
| The month's plan | clients/<client>/page-factory/batches/<month>.json |
| What the batch run did | batches/<month>.receipt.json in the same folder |
| The words for each page | briefs/<page>.house-copy.json, plus briefs/<page>.city-facts.json for a town page |
| The client's look | style-profile.json, skin.json and facts-seed.json |
| WordPress draft settings | wp-draft.json |
| Draft ids and measured match | wp/drafts.json and wp/<page>/probe.md |
| Pages for review | stage/pages/, shown at <client>.swarmsystem.ai/pages/ |
| The factory's code | clients/_shared/page-factory/ |
| The procedure agents follow | sops/page-factory.md |
| The live view | Hive Mind, Page Factory: Batches, Clients and How it works |