How To Build A Stack Builder From Claude / ChatGPT
This builds a tiered network of pages across your cloud accounts, all linking toward your target URL — driven entirely by chat prompts once YACSS is connected to Claude or ChatGPT.
Create The Draft
A stack needs a client and a tier structure. Tier sizes are multiplied, not added.
Read the page count it gives you back. Tiers of 2, 3, 2 do not make 7 pages. They make 2, then 6, then 12 — 20 pages, plus 1 target page, so 21. The number the draft reports is the real one.
Pick How Much You Want Done For You
A stack can be built two ways, and you can mix them.
- Fully automatic — YACSS writes the meta titles and the page content for you. Fastest, and the one to use if you just want the stack live.
- Your own content — You write the titles and the article in the chat, and YACSS assembles the pages around them. Costs no YACSS AI credits and you control every word.
Both still need the same two things before generating: a title for every page, and content. Automatic content does not include automatic titles — they are separate steps.
Give Every Page A Title
This is the step most people miss, and it's why a stack can finish with nothing on it. A stack builds one page per meta title. If the titles don't match the page count, generation has nothing to build.
First, ask how many pages you actually have.
To have them written for you (uses AI, counts against your usage, one title per page):
To write them yourself:
Either way, check before going further:
Choose How The Content Is Written
Four routes, cheapest first.
Route A — Write it yourself in the chat. No YACSS AI used.
That last part matters: it tells YACSS to spin the article you supplied across the pages rather than writing new ones.
Route B — Let YACSS write it once, then spin it. One AI call.
That uses the same generator as the AI Content Generator page, then varies the text across the pages.
Route C — Supply your own file. No AI at all, useful for approved copy.
Route D — Let YACSS do it all. No article needed from you.
| Mode | What it does | Cost |
|---|---|---|
| Fully automated | YACSS writes the content itself | Automatic |
| Longform article in spintax | Spins the one article you supplied | Cheapest, one article total |
| AI article for each page | A fresh article on every page | Expensive, one call per page |
| Content file, random sentences | Pulls from a file you upload | None |
| Multiple content files | A different file per page | None |
Whichever you pick, confirm it landed:
If that comes back empty, the content did not attach. Fix it before generating.
Add The Extras
All optional, none of them cost AI credits.
Check Before Generating
Four things must be true: page count and title count match, content field has real text, tiers are what you asked for, and clouds are selected.
Generate
Then:
Publish
Covered in the Upload a Cloud Site tutorial: pick the client, check the buckets exist, then publish.
If Something Goes Wrong
| What you see | What to do |
|---|---|
| Completed, but 0 pages generated | Titles missing or not matching the page count, or content1 empty. Check both, fix, regenerate. |
| Published page is an empty template | Same cause. An empty shell means generation produced no pages, so the upload published the template only. |
| Far more pages than expected | Tier sizes multiply. 2, 3, 2 is 21 pages, not 7. Ask for smaller tiers. |
| "You exceed page limit" | The total is over your plan cap. Use smaller tiers. |
| Titles don't match page count | Ask for titles to be regenerated to the exact number the stack reports. |
| content1 shows empty after setting it | Set it again and re-read it before generating. |
| Cost far more than expected | The mode was AI article for each page. Switch to fully automated or longform spintax and regenerate. |