Your brand's AI editorial team

BlogYar won't publish
just anything.

Pre-publication review EVALUATING
CANDIDATE CLAIM

“The market grew by 40%.”

EVIDENCE STATUS

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.

Available now: a standalone plugin on your WordPress

A different category

Most AI tools ask:
“What should I write?”

BlogYar asks first:

“Should this be published at all?”

01

RELEVANT?

Does it matter to the brand?

A signal does not deserve content simply because it is new.

02

SUPPORTED?

Is there enough evidence?

Model confidence is not a substitute for a credible, traceable source.

03

WORTH PUBLISHING?

What is the right action?

Create a page, refresh an existing resource, publish selectively, or stop.

The editorial team

Not one tool.
An 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.

Argos Panoptes, the many-eyed guardian and BlogYar scout
01 SCANNING
ARGOSThe Scout

Argos finds what matters.

SignalBrand relevant

SourcesConfigured

DuplicateNo

Hermes, the mythic messenger and BlogYar writer
02 DRAFTING
HERMESThe Writer

Hermes turns information into stories.

InputResearch brief

StructureBrand rules

VoiceAligned

Internal verification layerCLAIM → EVIDENCE → SOURCE
GATE
Athena, goddess of wisdom and BlogYar strategist
03 OPTIMIZING
ATHENAThe Strategist

Athena makes every article smarter.

SEOReady

Internal linksReal

DecisionCREATE / REFRESH

Atlas, bearer of the heavens and BlogYar publisher
04 CONTROLLED
ATLASThe Publisher

Atlas gets it published.

ApprovalExact version

DestinationsIndependent

StatusReady

Brand intelligence

It knows your brand before it writes.

Brand Brain is more than a short prompt. It stores content structure, voice, approved terminology, brand entities and publishing policy as versioned knowledge.

  • Products, people and subjects with explicit identities
  • Voice, terminology and required article sections
  • Publishing rules and brand-specific constraints
YOUR BRANDActive knowledge version
ProductsWhat you make
PeopleWho represents you
VoiceTerms and tone
AudienceMarkets and intent
Editorial rulesContent structure
Publishing policyControl and limits

Claims and evidence

AI can write.
BlogYar needs 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.

Claim ledger
Verified Review Stop
Supported claimCredible, traceable sourceVERIFIED
!Expired evidenceRequires human reviewEXPIRED
×Unsupported figureCannot pass the evidence gateUNVERIFIED
CLAIMAn important article claimCurrent content version
EVIDENCERecorded supporting statementInside its validity window
SOURCEA configured sourceTraceable identity

Editorial decision

It does not always create another article.

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.

NEW SIGNALA fresh, relevant signal
CHECKDoes an authoritative existing resource cover this subject?
YES
REFRESHUpdate the existing pageSame URL
NO
CREATEBuild a new resourceNew URL

SEO and machine-readable structure

Good content must be packaged correctly.

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.

Page preparationVALID
example.com / authority-pageA precise title aligned with search intent

A description generated from the same approved content.

Title and description Real internal links Article / NewsArticle Validated JSON-LD

Human governance

Automation without giving up control.

Approval is bound to the exact text version and selected destinations. A content, channel or high-risk decision change can require fresh approval.

WordPress approval desk AWAITING DECISION
Proposed topicMEDIUM RISK

Refresh an existing authority page

ActionREFRESH

EvidenceReady for review

DestinationWordPress

ApproveReviseReject
EXPERIMENTAL Conversational Telegram approval
BlogYarA new version is ready for review

“Make the tone more formal and publish on the website only.”

Revision requested. The new version cannot publish without fresh approval.

The card, intent analysis and decision path are implemented and tested; the message receiver is not yet wired end to end.

Available product

Runs on your WordPress.

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.

STANDALONEYOUR AI PROVIDERYOUR CONTENT
  • Create a new post or refresh an existing resource
  • Categories, tags, evidence, SEO and structured data
  • Monthly cost ceiling and a traceable operator queue
BlogYarEditorial operations desk
PIPELINE READY
Awaiting decisionContent version
Evidence stateControlled
Next actionOperator approval
Refresh authority pageREFRESH · WordPress
REVIEW
+
New content draftCREATE · WordPress
DRAFT

Independent delivery

One failure does not undo every publication.

Each destination has its own operation and state. Retrying one channel does not resend content to destinations that already succeeded.

Example status for one publication operationOPERATION · SAMPLE
ATLASPublication package validated
W
WordPressCanonical website
PUBLISHED
T
TelegramChannel variant
PUBLISHED
B
BaleIndependent retry
RETRY
E
EitaaText delivery only
SCHEDULED

Statuses are illustrative UI. WordPress, Telegram and Bale are supported; Eitaa currently supports text delivery.

Content provenance

Every version knows where it came from.

Published content remains connected to its Brand Brain version, claim record, source set, human approval and publication operation. History is not rewritten.

Previous versionMeaningful changeApprovalPublication
CONTENT PROVENANCETRACEABLE
  1. Research versionSources and claims recorded
    source-set
  2. Content versionBuilt with the active Brand Brain
    content
  3. Human decisionThis exact version approved for WordPress
    approval
  4. PublicationContent, metadata and schema synchronized
    published

A clear position

What BlogYar is — and what it is not.

BLOGYAR IS
  • An AI editorial system
  • Brand-aware
  • Evidence-aware
  • Human-governed
  • WordPress-first
  • SEO and structured-data aware
BLOGYAR IS NOT
  • A ChatGPT wrapper
  • An article spinner
  • An uncontrolled publishing bot
  • A simple social scheduler
  • A source-free content factory
  • A hosted SaaS already for sale

Product model

We keep today separate from the future.

This page shows no fictional cloud dashboard, account system or subscription flow.

AVAILABLE NOW

Standalone BlogYar for WordPress

The plugin runs on your site and delivers the editorial pipeline, Brand Brain, claim control, approval, versioning and publishing there.

Explore the current product
FUTURE

BlogYar.com SaaS Control Plane

Accounts, 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 product

Frequently asked

Before you request a demo.

Clear answers to the most important boundaries of the current product.

Is BlogYar a hosted cloud service today?

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.

Does BlogYar search the web for evidence for every claim?

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.

What happens if content changes after approval?

Approval is bound to an exact content version. Any change invalidates the previous approval, and the new version must be reviewed again.

Which publishing channels does BlogYar support?

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

Bring one source.
Let BlogYar decide.

In the demo, you will see a signal become a research brief, draft, claim review, human decision and WordPress publication.