What Foliora does, controls, measures, and refuses to promise.

Foliora researches buyer questions and competitors, audits the search foundation, builds exact evidence-backed proposals, publishes approved changes through Shopify or GitHub, verifies the live result, and monitors Google and AI-answer visibility.

It is a product with an upgrade path to managed expertise. Starter, Growth, and Scale automate research, monitoring, approvals, and bounded execution. Managed plans add human strategy, review, and custom work.

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.

No. Google and AI systems are third parties. Foliora guarantees a controlled research, approval, publishing, and verification process—not inclusion, traffic, citations, or revenue.

Technical corrections can be verified immediately, but indexing, ranking, authority, and AI citation movement can take weeks or months. Foliora reports leading evidence without presenting short-term movement as a guaranteed outcome.

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.

The initial scope covers approved product, collection, page, article, metadata, redirect, and app-owned metafield changes. Foliora snapshots affected fields and requests write permissions progressively.

GitHub is the editing surface. Foliora opens a branch and pull request, runs checks, inspects the Vercel or Cloudflare Pages preview, and verifies production after merge.

Not for the initial citation product. The roadmap intentionally excludes customer and order scopes because they are unnecessary for research, publishing, and search verification.

Only low-risk typed actions can eventually be pre-authorized. New pages, redirects, claims, code or theme work, and regulated content require explicit approval in the initial product.

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.

Every execution retains an immutable before-state or Git history. Shopify field changes can be restored; code changes use a revert pull request alongside any deployment rollback.

The planned preview is a bounded scan of 10–20 public pages with foundational findings, sample buyer questions, and three opportunity previews. It does not connect accounts or mutate a site.

An action is a versioned, evidence-backed change set—not one field update. The limit keeps infrastructure and review predictable while giving a startup enough capacity to ship meaningful work each month.

Choose Managed when the work requires bespoke strategy, expert interviews, custom writing or code review, a large catalog, multiple sites or markets, regulated content, or authority-building beyond the site.

The roadmap target is a useful public preview in under five minutes and a first connected strategy within roughly 48 hours. Those are product goals for the beta, not contractual SLA guarantees.

No. Ahrefs and other providers are internal research infrastructure. You receive Foliora's evidence, strategy, proposed diffs, verification, and outcome history—not a replicated third-party dashboard.