A variable, a table or a part?
When many pages share content, there's a right place to keep it. The wrong place works at first, then costs you hours. The question is: what changes, and how often?
| Question | Variable | Table | Part |
|---|---|---|---|
| Holds | One value per page, like a city or a headline | Rows of content, like locations or jobs | A whole section, like a header or a footer |
| Changes reach live pages | When you publish | In about a minute, no publish | When you publish the pages that use it |
| Edit it in | Data › Page variables | Data | Components |
| Best for | Pages that differ by a few words | Content that changes often, or that someone else edits | Sections that must look the same everywhere |
Use a variable when pages differ by a few words
Twenty city pages that differ only in the city name and phone number. A headline that matches the search someone typed.
Use a table when the content changes or grows
Store hours, prices, open jobs, an FAQ. Someone on another team can update the table without touching a page. Each row can also be its own page. See Make pages from a table.
Use a part when a section must stay the same everywhere
Your header, your footer, your legal text, your pricing block. Change it once. See Reuse sections across pages.
What not to do
Don't make a hundred copies of a page and edit each one. It works on day one. On day thirty, a price changes and you edit a hundred pages. Put the price in a table or a part instead.
Coming soon
Templates, for a whole page you start from again and again.Coming soon
Campaigns, which tailor a page you have to each ad group or ad, or make a page for each row of a list.Coming soon