What AI tools can do

A reference to the areas of BrightSite a connected AI tool can work on, and what limits apply.

A connected AI tool can call well over a hundred separate actions across BrightSite. You do not need to learn their names. You describe what you want and the tool picks. This page is a reference for what is covered, so you know what to ask for.

What is covered

  • Pages: list, read, create, update, publish, unpublish, and delete pages. Also duplicating a page and running find-and-replace across content.
  • Blog posts: the same lifecycle for posts, plus blog settings.
  • Blog design: the templates that control how listings, post cards, and related posts look.
  • Docs: documentation pages, their nesting, and docs settings.
  • Components: reusable blocks used across your site.
  • Layouts: the frames pages are rendered inside.
  • Forms: creating and editing forms, and reading submissions.
  • Media: listing files and folders, uploading, moving, and deleting.
  • Redirects: creating and managing redirects, which is how you avoid broken links after a migration.
  • Staging: creating a staging site, comparing it with live, and promoting or discarding it.
  • Site identity and SEO: site details, tracking settings, error pages, and global code.
  • Domains: listing and adding domains, DNS instructions, and promoting a domain to primary.
  • Google Reviews: the review settings, checking the connection status, and pulling in the latest reviews.
  • Team and roles: listing members, inviting people, changing roles, and managing custom roles.
  • Analytics: reading your traffic data so a tool can report on it or act on what it finds.
  • Versions: listing past versions of an item and restoring one.

The list grows as BrightSite does, so treat this as a map of the territory rather than a fixed inventory. If you are unsure whether something is covered, ask your tool to list what it can do.

Read, write, delete

Actions fall into three groups, and the difference matters when you decide what to let a tool do.

  • Read: listing and fetching. Nothing changes. Safe to run freely, and the right way to start any job: look before you touch.
  • Write: creating, updating, publishing. These change your site. Draft changes are recoverable through version history; publishing puts them in front of visitors.
  • Delete: removing pages, posts, forms, files, redirects. Treat these as the sharp end. Ask a tool to list what it intends to delete before it deletes anything.

A useful pattern for bulk work: ask for a read-only report first, check it, then ask for the changes.

Your role gates every call

Every action checks your permissions in the organization named in the request. A tool cannot do anything you could not do yourself in the app.

If a tool reports that it is not allowed to do something, the fix is a role change in your team settings, not a change to the tool. This applies to keys as well as to browser sign-in, so giving someone a key never grants them more than their role allows.

Subscription required

An active subscription is required for the organization you are working on. If a subscription lapses, calls against that organization stop working until billing is sorted out.

Docs tools are limited release

The documentation actions are not yet available to everyone. If your tool cannot see them, that is why. Contact support to ask about access. Everything else listed above is generally available.

Last updated September 9, 2026