How RootSmith works
The core records in RootSmith, such as teams, sites, brand profiles, page types, questions, ideas, and content, and how a page moves from idea to published.
Teams and roles
Everything belongs to a team. Each person has a role in the team: Owner, Admin, or Member. Everyone can plan, write, review, and publish content. Owners and admins also manage sites, publishing settings, members, and billing. A connected agent has the same access as the person who connected it.
Sites
A site is one website on one primary domain. Each site has its own:
- Brand profile: business facts, audience and purpose, and writing guidance, plus the prices and key facts articles may state. RootSmith drafts it from your site and its store listings, and you confirm it.
- Competitors: companies to compare against on comparison pages and in AI answers. Other pages name only your brand.
- Page types: kinds of pages, such as Blog article, each with a fixed URL prefix, a purpose, an outline of sections a page can use, and research guidance. Turn off suggested ideas for any type your team writes itself.
- Publishing settings: how approved pages reach your site, the approval mode, and the default schedule.
- Integrations: Google Search Console.
- Country: where most of your customers are. Ideas and articles use
Google results and search demand from this country. A site on a country
domain, such as
.caor.co.uk, starts with that country, and other sites start with the United States. Change it in the site's Settings. RootSmith writes in English for every country.
Each time RootSmith reads your site, it also checks its AI readiness:
whether AI search crawlers and assistants can reach your pages, read them
without JavaScript, and identify your business. The site's Overview
shows a score out of 100 and what to fix. Choose Copy fixes for your
agent to give the list to your coding agent, then choose Check again.
RootSmith doesn't score llms.txt, because Google says AI search doesn't
need it.
Questions and AI visibility
A tracked question is something your buyers ask AI assistants. RootSmith checks the answers from AI engines every week and records which brands and sources they name. The gaps feed new ideas.
From idea to published page
Ideas and pages are the same record at different stages:
| Status | Meaning |
|---|---|
opportunity | A new idea. Write it or remove it. |
writing | RootSmith is researching, writing, and checking it. |
dismissed | A removed idea. You can restore it. |
draft | A draft you can edit. |
in_review | Ready for review. |
approved | Approved and ready to publish. |
scheduled | Set to publish at a chosen time. |
retired | A page that was merged into another page and redirects. |
Each save creates a new version. Publishing makes one approved version public. Editing a published page creates a new draft and leaves the live version in place until you publish again.
A page counts as live when RootSmith finds that exact version on your site. The SDK and MDX export add a hidden marker for this check. See version markers.
Fact checks and approval
When RootSmith writes a draft, it reads the top search results in your site's country and other sources first. It prefers official and independent pages, and it reads competitors' sites only for a comparison page. It checks each fact in the draft against the source it came from, your brand profile, your notes, and your change requests. A fact about your business must come from your brand profile, your own site, or your team. When a fact can't be confirmed, RootSmith searches for a source and edits only that sentence, once. If it still can't confirm the fact, it leaves the sentence as it is and adds a flag. Problems it can't fix, such as a misleading paraphrase, also show as flags.
Open What we checked on a draft to see the facts, their sources, and any flags. Answer a flag with a fact or a source link to revise the claim to match, change the sentence yourself, or choose OK. When a flagged claim about your business is true, choose That's true: RootSmith adds it to your brand profile's facts, so later articles can state it, and leaves the draft as it is. Flags don't block your approval. Your own edits aren't checked again unless you choose Check facts.
Choose Request changes to have RootSmith revise the parts you name. A fact you state in the request, such as a rate or a fee, counts as your team's own: it doesn't get a flag, and later checks of the page still accept it. RootSmith reads any link in the request and searches for products or facts the request asks it to add. When it can't do part of the request, for example because no source describes a product you named, the rest of the text stays as it is and a flag says which part and why. Where they differ, your writing preferences and your request win over the brand profile's voice, What makes you different, and stated limits, and over the usual page rules.
RootSmith keeps the general rules from your feedback as your site's writing
preferences, on the Brand page. It checks each new draft against them,
fixes a sentence that breaks one, and flags what it couldn't fix. Feedback
that only fixes one article isn't saved. After you give feedback, the
editor shows what was added to your preferences. An agent can read the same
thing in the learned field of get_content.
When your site publishes right away by default and has a publishing method, the approve button reads Approve and publish and publishes the page.
In Publishing, the approval mode is Approval required or Automatic. With Automatic, drafts from automations are approved and published with the default schedule. A draft with open flags waits for a person's review instead, unless its only flags are about your writing preferences.
Outcomes
For each published or refreshed page, RootSmith records AI citations and Google clicks before publication and at 14, 30, 60, and 90 days.
Quickstart
Add your website, check your brand profile, choose your questions, get your first ideas, write your first page, and connect your website from the RootSmith dashboard.
Choose how to publish
Pick the way approved RootSmith pages reach your website. Use the Next.js SDK, the client package, a static site deploy hook, WordPress, a signed webhook, or MDX export.