RELEVANT?
Does it matter to the brand?
A signal does not deserve content simply because it is new.
Your brand's AI editorial team
“The market grew by 40%.”
No sufficient authoritative evidence found for the 40% figure.
Illustrative UI showing the real claim-and-evidence gate. The 40% figure is not presented as a verified fact.
BlogYar monitors the sources you choose, builds a research brief, writes in your brand voice, assesses important claims and publishes only when the content and human approval are ready.
A different category
Most AI tools ask:
“What should I write?”
BlogYar asks first:
RELEVANT?
A signal does not deserve content simply because it is new.
SUPPORTED?
Model confidence is not a substitute for a credible, traceable source.
WORTH PUBLISHING?
Create a page, refresh an existing resource, publish selectively, or stop.
The editorial team
Four Greek characters, each with one clear responsibility. An internal verification layer works between writing and publication decisions; it is not a fifth public persona.
SignalBrand relevant
SourcesConfigured
DuplicateNo
InputResearch brief
StructureBrand rules
VoiceAligned
SEOReady
Internal linksReal
DecisionCREATE / REFRESH
ApprovalExact version
DestinationsIndependent
StatusReady
Brand intelligence
Brand Brain is more than a short prompt. It stores content structure, voice, approved terminology, brand entities and publishing policy as versioned knowledge.
Claims and evidence
Every important claim remains connected to its evidence and source. The model cannot mark a claim as verified simply by repeating its own output.
Editorial decision
A new URL is not the right answer to every new signal. When an authoritative existing page already covers the subject, BlogYar refreshes that resource and preserves its history.
REFRESH preserves the original URL and publication date; the modified date changes only when the content meaningfully changes.
SEO and machine-readable structure
Athena prepares SEO titles and descriptions, categories and tags, real internal links and structured data from the same content version. JSON-LD is validated before publication.
A clear boundary: BlogYar does not currently offer a separate GEO capability. This section shows only the implemented SEO and structured-data workflow.
A description generated from the same approved content.
Human governance
Approval is bound to the exact text version and selected destinations. A content, channel or high-risk decision change can require fresh approval.
ActionREFRESH
EvidenceReady for review
DestinationWordPress
The card, intent analysis and decision path are implemented and tested; the message receiver is not yet wired end to end.
Available product
BlogYar is currently a standalone plugin. Content, work queues and decision history remain on your WordPress installation, and output is built as editable Gutenberg blocks.
Independent delivery
Each destination has its own operation and state. Retrying one channel does not resend content to destinations that already succeeded.
Statuses are illustrative UI. WordPress, Telegram and Bale are supported; Eitaa currently supports text delivery.
Content provenance
Published content remains connected to its Brand Brain version, claim record, source set, human approval and publication operation. History is not rewritten.
source-setcontentapprovalpublishedA clear position
Product model
This page shows no fictional cloud dashboard, account system or subscription flow.
The plugin runs on your site and delivers the editorial pipeline, Brand Brain, claim control, approval, versioning and publishing there.
Explore the current productAccounts, subscriptions, credits, central key management and a hosted dashboard do not exist yet, and we are not announcing a release date.
Future roadmap · not an available productFrequently asked
Clear answers to the most important boundaries of the current product.
No. The current product is a standalone plugin installed on your own WordPress site. A hosted BlogYar service is part of the future roadmap and is not presented as an available product today.
No. Today it assesses claims against the sources already attached to that content record. Automatic web research for new evidence is not a currently available capability.
Approval is bound to an exact content version. Any change invalidates the previous approval, and the new version must be reviewed again.
WordPress, Telegram and Bale are supported. Eitaa supports text delivery. Each destination records its own state, so a failure in one channel does not erase a successful publication elsewhere.
See a real decision
In the demo, you will see a signal become a research brief, draft, claim review, human decision and WordPress publication.