How To Use The Masspage Builder From ChatGPT
Builds a multi-page site around one keyword and saves it as a draft you can review before anything is generated or published — you can also directly generate it.
- YACSS connected to ChatGPT (see the ChatGPT MCP connection tutorial).
- A keyword and a landing page URL for the site you're building.
Ask What The Builder Needs
Before anything else, have ChatGPT pull the current field list. It's long, and this keeps it from guessing.
You don't need to read all of it. It's for ChatGPT's benefit, so it fills the right fields rather than inventing them.

Create The Draft
Give it the basics: keyword, how many pages, your landing page, and the business details. Nothing is generated yet and no credits are spent.
ChatGPT will confirm the draft and give it a name. Everything after this is editing that draft.
Choose How The Content Gets Written
This is the one decision that drives what a build costs. There are three routes, cheapest first.
Route A — ChatGPT writes it, you attach it. No YACSS AI used. You already have ChatGPT in front of you, so let it do the writing, then put the text on the build. YACSS just assembles the pages around it.
Ask to see it back before moving on:

Route B — One YACSS AI article, spun across every page. Cheap. YACSS writes a single long article, then varies it per page. That's one AI call for the whole build, not one per page.

Route C — Use a content file. No AI at all. You supply a file of sentences or paragraphs and the builder pulls from it to vary each page. Useful when you already have approved copy.
| Route | Who writes it | AI cost | Best for |
|---|---|---|---|
| A. Attach your own | ChatGPT, in this chat | None in YACSS | Most builds |
| B. One article, spun | YACSS, once | One call per build | Hands-off, still cheap |
| C. Content file | You, up front | None | — |
Choose Where The Content Sits
Separate from who writes it, there are two page layouts.
- Seven Content — Seven fixed sections that appear on every page, filled from content one to content seven. This is the straightforward one, and it's what Route A fills.
- Dynamic Content — A flexible layout that arranges content blocks and images automatically. It reads a different set of fields, in particular a single content-images field rather than per-section images.

Or:

Add Your Special Content Blocks
Special content is the highlighted feature blocks on a page, each with a short heading, a line or two of text and an icon. ChatGPT writes them in the chat and attaches them to your build, so they cost you no AI credits.
There are two versions of this feature, and which one you get depends on the layout you picked earlier. They are stored differently and are not interchangeable.
| Your layout | Which special content you get |
|---|---|
| 7 Content | The standard one |
| 1 Content | The standard one |
| 7 Content Home Page / 1 Content Subpages | The standard one |
| Dynamic Content | The dynamic one |
If you are on 7 Content, 1 Content, or the mixed layout — this is the standard special content: a fixed set of up to four blocks that appear on your pages.

If you are on Dynamic Content — dynamic keeps each block as its own item, so you can have as many as you like and the builder chooses how many to show per page.

Add Your FAQs
Same idea. Written in the chat, attached manually, no credits used.

Add The Local Google Content
This is what makes the pages read as genuinely local: real nearby places, reviews, driving directions and photos pulled from the business's Google listing.
Start by pulling the business from Google.
You'll get back the business name, address, phone, website and its Google place ID. Check it's the right business before continuing, especially if the name is common.

Then attach it to the build.

Now choose what local content to pull in.

Add Wikipedia Content
Optional, and it costs no AI credits. It pulls and rewrites Wikipedia material about the city or topic.

Generate
This is the step that builds the pages.
Generation runs in the background. For 25 pages it usually takes a few minutes.
Publish It
Once it shows as generated, publish it to your clouds. That flow is covered in the "Upload a Cloud Site" tutorial: pick the client, pick the cloud account, check the bucket, then publish.
If Something Goes Wrong
| What you see | What to do |
|---|---|
| "You exceed page limit" | Your plan caps pages per build. Ask for fewer pages, or upgrade under My Subscription. |
| The content sections came back empty | Ask ChatGPT to show content one to seven on the draft. If they're blank, ask it to attach them again, then re-check before generating. |
| FAQs or special content didn't appear | They were probably left on automatic. Ask for them to be attached manually with the text ChatGPT wrote. |
| Images stopped showing after a layout change | The two layouts read different image fields. Say which layout you're on and ask for the images to be attached again for that layout. |
| The build used far more credits than expected | It was on Route C, a fresh AI article per page. Switch to Route A or B and regenerate. |
| The wrong business came back from Google | Search again with the city and state. If you have the Google place ID, give that instead, it's exact. |
| No local content on the pages | The business has no Google place ID set on the draft. Fetch the company again and add it to the build. |
| No nearby places, reviews or directions appear | Google may publish no location for that business, common for mobile trades. Set the city on the build so results can centre on the town. |
| Generation finished but pages look thin | Add more of your own content to the sections, make the articles long, and add Wikipedia or local content to give each page more substance. |
| "Requires the Expert plan or above" | The AI connector starts at the Expert plan. Upgrade under My Subscription. |