What Foliora improves, publishes, and verifies.

Foliora researches buyer questions and competitors, audits the search foundation, builds exact evidence-backed proposals, publishes approved changes through Shopify, WordPress, Webflow, or a GitHub pull request, verifies the live result, and measures search demand plus visibility in ChatGPT and Gemini. If you skip a publisher, you still get the approved diff to apply yourself or through a customer-owned agent.

It is a managed software product with a plan for each website. Essential runs the research and improvement cycle monthly; Pro runs it weekly. Both include approval, publishing, and verification. Annual billing saves 20%.

Trackers primarily observe prompts and mentions. Foliora connects observations to source evidence, a strategy, exact proposed changes, approval, publishing, verification, and an initiative history.

Foliora can draft content, but volume is not the objective. New pages are based on buyer demand and real company evidence, remain reviewable, and require approval before publishing.

Foliora identifies technical, search-demand, and citation gaps in the public sources Google and AI systems evaluate. After approval it can publish content and metadata changes through Shopify, WordPress, Webflow, or a GitHub pull request, verify the live page, and continue measuring ChatGPT and Gemini. Off-site corroboration and work that needs human judgment stay visible as initiatives rather than automatic writes.

Foliora verifies technical and publishing improvements as soon as they are live. Indexing, ranking, authority, and AI citation movement build over time, so Foliora keeps measuring the same pages and buyer questions to show progress from the first verified change onward.

Foliora stores a reproducible panel with engine, prompt, market, date, answer, cited URLs, mentions, and competitors. Results are treated as samples with variance rather than a complete census.

Foliora can apply approved changes to products, collections, pages, articles, metadata, redirects, and metafields after re-reading the remote resource and preserving its before-state. It does not read customer or order data and does not mutate theme Liquid or checkout.

Foliora can apply approved changes to posts, pages, taxonomies, metadata, redirects, and SEO fields. It does not mutate theme PHP, install plugins, or read WooCommerce customer or order data. If you skip the WordPress connection, you still get the approved diff to apply yourself.

Foliora can apply approved changes to CMS items, static page SEO, metadata, and redirects. It does not edit the Designer canvas, custom code, hosting, or DNS. If you skip the Webflow connection, you still get the approved diff to apply yourself.

On a code-owned site connected through GitHub, Foliora opens a pull request. Preview deployments on Vercel or Cloudflare can be inspected before merge. After merge, Foliora verifies the rendered production page. Foliora does not auto-merge pull requests or write hosting, DNS, Workers, or edge configuration.

Foliora still researches the site, builds the exact approved diff, and keeps the before-state and audit trail. You can apply the change in your own workflow, or let a customer-owned agent manage the approved-change workflow through Foliora's MCP. A native connector is optional, not a prerequisite.

Yes. Customer-owned agents connect through Foliora's MCP to inspect the product, start humans on preview, and manage the approved-change workflow. Writes still require the same human approval, stale-state re-read, and audit trail as the dashboard path.

No. Foliora does not request customer or order scopes. They are unnecessary for research, publishing, and search verification.

No. Every change requires explicit customer approval of its stored diff and hash. New pages, redirects, and other material operations stay behind that same approval.

Foliora re-reads the remote resource before mutation. If it differs from the approved version, the proposal becomes stale instead of overwriting your team's work.

Execution retains an immutable before-state so an applied change can be reversed through the controlled rollback path. GitHub changes remain in ordinary pull-request and git history.

The preview is a bounded scan of 10–20 public pages with foundational findings, sample buyer questions, and three opportunity previews. Enter a public URL to start; the snapshot appears before account capture. It does not connect Shopify, WordPress, Webflow, or GitHub, or change the site.

Essential is $49.99 per site per month for a monthly research and improvement cycle. Pro is $149.99 per site per month for a weekly cycle. Both include ChatGPT and Gemini checks, research, supported drafts, approval-gated publishing, live verification, and receipts. Annual billing saves 20%.

Yes. Choose Essential or Pro for each website. Each site has its own complete package and cadence, with no pooled allowances. Manage multiple sites from one account. Annual billing saves 20%.

The beta is designed to return a useful public preview in under five minutes and a first connected strategy within roughly 48 hours. The strategy identifies the highest-priority buyer questions, source gaps, and exact proposed changes.

No. Foliora brings research, evidence, strategy, proposed diffs, publishing verification, and outcome history into one managed workflow.