Bulk Updating Pages

When you need to apply the same change across multiple pages -- updating a footer, swapping a CTA button, changing a color, or adding a new section -- you don't need to do it page by page. Just tell the chat what you want and which pages it should apply to. Flint handles the rest.

Bulk updates work through the chat, the same way any other edit does. The difference is that you're directing the change at more than one page at once.

Flint reads the relevant pages, applies the change to each one, and confirms when it's done. You can review the results on any of the updated pages immediately.

You don't need to be on a specific page to trigger a bulk update. The chat works across your entire site.

Update all pages:

• •"Add a banner to the top of every page announcing our new pricing"
• •"Update the footer CTA button to say 'Book a demo' across all pages"
• •"Change the nav bar's sign-in link to point to /login on every page"

Update a specific set of pages:

• •"Update the hero headline on all landing pages to mention our new Enterprise plan"
• •"Remove the 'Coming soon' badge from the features section on the pricing page and the product page"
• •"On all the ABM pages, change the CTA button color to match the new brand blue"

You can refer to pages by name, by type, by section, or by any shared characteristic. Flint will figure out which pages match and apply the change to each one.

Be specific about the change. The more precisely you describe what to change, the more accurate the result. "Update the footer" is less reliable than "change the footer's copyright year from 2024 to 2025 on all pages."

Describe the scope clearly. If you want the change on every page, say "all pages." If you only want it on a subset, describe that subset -- by page name, by section type, by URL pattern, or however makes sense for what you're doing.

You can always undo. If a bulk update doesn't look right, use undo to step back. Bulk changes are reversible the same way individual edits are.