Hypothetical example: A publisher manages two WordPress websites: one helps beginner gardeners, while the other offers advice for independent craft sellers. Both need clear explanations and carefully supported claims, but their readers have different questions and vocabularies. How can the publisher reuse useful instructions without making both websites sound alike or cover interchangeable topics?
The practical way to evaluate Yodon features is by configuration scope: what establishes the publishing destination, what provides reusable guidance, what belongs to one article, and what supports recurring work. That distinction helps you decide which instructions should remain consistent and which need fresh attention with every assignment.
Start with the scope of each setting.
The map below is an editorial explanation, not Yodon’s official architecture or a documented settings hierarchy. Yodon supports account and website preferences, presets, editorial rules, standalone articles, article editing, and scheduled automations. Their availability does not establish which instruction takes precedence when settings conflict, or whether changing one setting updates existing work.
| Feature group | Question it helps answer | What to check |
|---|---|---|
| Website connection | Where should the article go? | The intended WordPress site and chosen connection method. |
| Account/website preferences | What recurring context matters? | Which guidance is shared and which is specific to a site’s readers. |
| Presets and editorial rules | What instructions are worth reusing? | Repeatable assignment requirements and boundaries that should remain clear. |
| Standalone articles | What does this particular assignment need? | The reader’s question, article scope, and unique requirements. |
| Scheduled automations | What publishing work should recur? | Whether the recurring need and proposed cadence suit the website. |
For the hypothetical publisher, “explain unfamiliar terminology” might be useful across both sites. Gardening examples, however, should not drift into an article about presenting handmade products. Treat shared guidance as a foundation, not a substitute for identifying the reader and purpose of each assignment.
Yodon’s article capabilities include AI-written text with web research, optional citations, featured images, categories, tags, and Yoast/Rank Math SEO metadata. These are parts of the article package to inspect, rather than reasons to assume that a broad preference settles every content decision. Explore Yodon’s WordPress publishing features for the product overview.
Connect WordPress before configuring content.
A sensible first step is to establish the destination. Yodon supports two connection routes: an Application Password and the Yodon Connector pull plugin. The homepage documents the Application Password route; the Connector is an alternative supported method. A plugin is therefore not always required.
According to WordPress’s official Application Passwords documentation, Application Passwords let integrations authenticate without using the user’s main password. They can also be revoked. That separation lets you withdraw an integration’s credential without treating your everyday login password as the connection credential.
Choose the supported route that fits your setup, but do not assume that either method determines the article’s audience, tone, or subject. Connection and content configuration answer different questions. Nor should the existence of the Connector be taken as evidence of particular polling intervals or compatibility with every hosting arrangement.
A practical connection checklist
This checklist is editorial guidance, not a sequence of interface instructions:
- Identify the intended site. Confirm which WordPress destination should receive the work, especially when managing multiple websites.
- Choose a supported method. Use the Application Password route or the Yodon Connector pull plugin.
- Keep credentials private. Do not put connection secrets in article briefs, reusable writing instructions, or shared editorial documents.
- Inspect an initial test article’s destination. Confirm that it reached the intended website before relying on the connection for further publishing.
Tip: Test the gardening destination with a clearly gardening-specific assignment. The purpose is to verify the destination, not to infer that all reusable content instructions are correct.
Key takeaways
- Separate destination, reusable guidance, article-specific requirements, and recurring work.
- Do not assume settings inherit, override, or automatically update one another.
- Verify the connection before expanding publishing activity.
A working connection establishes the destination, while reusable instructions establish the content’s direction.
Reuse the instructions that should stay consistent.
With the destination established, decide which instructions deserve reuse. Account preferences, website preferences, presets and editorial rules are supported Yodon features. The approach below is an editorial recommendation for using those tools, not a claim about settings precedence or how changes affect existing assignments. Keep shared standards broad enough for both websites, while making audience-specific guidance concrete.
Preferences for recurring context
Start by separating publisher-wide expectations from website identity. Clear explanations and supported factual claims may matter everywhere. Vocabulary, examples and assumed reader knowledge usually need closer attention at the website level. Account and website preferences provide places to consider recurring guidance; do not assume that one automatically overrides the other.
Yodon’s product overview supports audience, tone, language and theme selection. Here, themes mean content subject areas, not WordPress design themes. Planning subjects such as container gardening also differs from choosing WordPress categories, which organize published posts. These are useful configuration considerations, but not every example below represents an exact named field.
For our hypothetical publisher, beginner gardeners need unfamiliar growing terms explained. Independent craft sellers need examples grounded in making and presenting products. A shared instruction to “be practical” cannot express those differences.
Suggested editorial instructions, not interface field names. Hypothetical gardening site: “Write for beginner gardeners. Explain unfamiliar terms plainly, and use examples that account for limited balcony or patio space. State relevant space assumptions rather than assuming every reader has a garden.”
Suggested editorial instructions, not interface field names. Hypothetical craft-business site: “Write for independent craft sellers. Explain specialist terminology and state assumptions about the products and working setup. Use clearly labeled hypothetical examples; never invent sales results.”
Presets for repeatable assignments
Presets are useful to consider when an assignment format recurs. Rather than treating every gardening article as identical, draft reusable guidance for a particular format: a beginner explainer might introduce one concept, explain its practical relevance and finish with a checklist. The next assignment still needs its own question and limits.
The following four-step exercise is a recommended configuration method, not a prescribed Yodon onboarding sequence:
- Identify shared guidance. List standards that apply across the publisher’s work, such as explaining unfamiliar terminology and avoiding unsupported claims.
- Separate site-specific decisions. Define each audience, suitable tone and relevant examples without importing the other site’s assumptions.
- Draft reusable format instructions. Describe the structure and depth needed for one recurring article type, leaving its individual topic open.
- Test one article. Inspect whether its wording, examples and scope match the intended guidance before reusing the configuration more widely.
Editorial rules for boundaries
Use editorial rules to express boundaries you want to maintain, such as labeling hypothetical examples and avoiding invented outcomes. Prefer actionable wording over vague ambitions: “state the assumptions behind an example” is easier to evaluate than “make it authoritative.” This is recommended instruction design, not a guarantee that every generated passage will comply.
Reusable or article-specific?
| Guidance | Recommended scope |
|---|---|
| Audience | Reusable site context; specify a narrower reader when needed. |
| Terminology | Reusable explanation standards, with topic-specific terms in the brief. |
| Source expectations | Reusable evidence standards; identify assignment-specific source needs separately. |
| Reader’s immediate question | Article-specific: state the problem this piece should answer. |
| Unique exclusions | Article-specific: name what this assignment must leave out. |
| Original example supplied for one assignment | Article-specific: include the example and its intended use explicitly. |
Unique details belong explicitly in the article brief. Broad preferences cannot communicate an unspoken exclusion or a particular example you want included.
Tip: Remove contradictory instructions before expanding automation. Compare your guidance manually; do not assume Yodon detects conflicts or resolves them in your preferred order.
For detailed review guidance, see a draft-first editorial workflow with Yodon. Reusable instructions establish consistency, but each article still needs a distinct reader problem and scope.
Understand what comes with an article.
Once an assignment has a distinct purpose, consider its complete output—not just the body text. Yodon supports standalone article creation and article editing, so a specific assignment does not require a recurring automation. These Yodon features let you evaluate an individual article before deciding whether its format suits repeated use.
The article package includes AI-written content with web research, optional citations, a featured image, categories, tags, and Yoast/Rank Math SEO metadata. Yodon’s article creation overview also describes research, imagery and SEO fields. Research support is not a guarantee of factual accuracy, and citations are optional rather than a mandatory element of every article.
| Component | Purpose | What to inspect |
|---|---|---|
| Article text and research | Answer the reader’s question with researched context. | Does the explanation answer the assigned question, and are factual claims supported? |
| Optional citations | Give readers a route to supporting sources. | Does each linked source support the precise claim beside it? |
| Featured image | Provide a visual introduction to the subject. | Does the visual match the topic without implying documentary evidence? |
| Categories and tags | Organize the post within WordPress. | Does the category fit the site’s existing organization, and are the tags relevant? |
| SEO title, description and focus keyphrase | Supply page-level SEO metadata. | Do the title and description accurately summarize the page, and does the keyphrase match its subject? |
Edit the article without assuming everything else updates.
Article editing is supported, but do not assume a text revision automatically regenerates the image or synchronizes every WordPress field. After substantial changes, inspect the text, image, taxonomy and metadata together. Yodon supports draft delivery and direct publication; either choice still calls for a coherent article package.
For the hypothetical gardening website, consider a narrow assignment: explain how a beginner can assess the available space before choosing balcony containers. Exclude plant-selection advice so the article remains focused on measuring and planning. Its presentation could distinguish the following elements:
- Illustrative reader-facing title: “How to Measure Your Balcony Before Choosing Plant Containers.” This tells readers what practical task the article addresses.
- Illustrative SEO title: “Measure Your Balcony for Plant Containers.” This expresses the same subject more concisely.
- Illustrative category: “Container Gardening,” if that category fits the website’s existing structure.
- Illustrative tags: “balcony gardening” and “space planning,” if those labels are useful within the site.
Tip: If the article changes from measuring space to arranging containers, revisit its title, description, image and taxonomy. Metadata should describe the finished article, not preserve an earlier assignment’s promise.
Separate publishing, sitemap submission and indexing.
Publishing places content on the website. Sitemap submission helps communicate available URLs to a search engine. Indexing is a separate decision: Yodon’s Google Search Console integration resubmits sitemaps, while Google decides whether and when pages are indexed.
Google’s guidance on building and submitting sitemaps explains that submitting a sitemap is a hint, not a guarantee that Google will download it or crawl its URLs. Treat submission as a discovery signal, not guaranteed crawling, indexing or ranking. It does not establish instant indexing or special priority for Yodon-created pages.
These distinctions matter when evaluating results. A published article and a resubmitted sitemap are not proof that the page appears in Google’s index. Likewise, supplying SEO metadata does not promise a particular ranking or an exact search-result presentation.
A reusable article-package check
- Text: Confirm the article answers its specific reader question.
- Evidence: Check important claims and any included citations.
- Image: Confirm relevance without misleading visual implications.
- Organization: Check categories and tags against the destination site.
- Metadata: Make sure SEO fields describe the final version.
Use this compact check before relying on a recurring schedule: repeatable production should begin with a package whose components fit together.
Choose standalone articles or scheduled automation.
With the article package checked, choose how production should recur. Standalone articles suit a specific one-off assignment; scheduled automations support recurring publishing needs. Neither mode replaces a clear reader problem, suitable instructions or an inspection of the finished content.
Standalone articles: A useful choice for an occasional special guide with its own scope and examples. In our hypothetical publisher’s gardening site, that could be a focused guide to planning a first balcony container layout.
Scheduled automations: A useful choice for a recurring educational series, such as explanations of product-presentation concepts for independent craft sellers. The constraint is editorial readiness: each installment still needs a worthwhile subject and appropriate review capacity.
Choose cadence according to the supply of suitable topics and the attention available to inspect them. A recurring schedule is a production choice, not a growth guarantee. Keep unusual assignments separate when their requirements differ substantially from the series.
Match the plan to article volume and website count.
Compare both article allowance and website count, rather than selecting a plan from article volume alone. For the hypothetical two-site publisher, the destination limit matters even when monthly output is modest.
| Plan | Price | Article allowance | Websites | Automation allowance specified |
|---|---|---|---|---|
| Free | Free | 5 articles once | 1 | 1 automation |
| Starter | $25/month | 25 articles | 3 | Not specified here |
| Growth | $69/month | 75 articles | 10 | Not specified here |
| Scale | $179/month | 200 articles | 25 | Not specified here |
Top-ups: $15 for 10 articles. The Free allowance is five articles once, not five articles every month. These figures describe capacity limits, not guaranteed publishing results.
Hypothetical selection example: A publisher needing 20 articles monthly across two websites fits the stated Starter allowances of 25 articles and three websites. That is a capacity comparison, not a promised return on investment. Before choosing, review Yodon’s available plans against your current requirements.
Count planned assignments across both websites, including occasional special guides. Do not treat unused capacity as a reason to publish topics that lack a clear purpose. A smaller, well-defined series is a more useful configuration test than filling every available slot.
Frequently asked questions
Do I need the Connector plugin?
No. The Yodon Connector pull plugin is one supported connection route, alongside Application Password. A plugin is not always required to connect WordPress.
Can I create an article without a recurring automation?
Yes. Standalone articles support individual assignments without a recurring automation. Use them when a topic needs its own brief or does not belong in an ongoing series.
Does sitemap submission guarantee indexing?
No. Yodon’s Google Search Console integration resubmits sitemaps, but Google decides whether and when pages are indexed. Google’s official sitemap documentation explains that a sitemap does not guarantee crawling or indexing.
Can I earn advertising revenue through Yodon now?
Monetizing enrollment is available on paid plans, but this is a planned program: ad delivery, click tracking and payouts are not live. Enrollment should not be treated as current advertising revenue or a guarantee of future income.
Conclusion: configure deliberately, then expand
- Establish reusable guidance while keeping each website’s audience and each assignment’s purpose distinct.
- Inspect the complete article package, including evidence, imagery, taxonomy and SEO metadata.
- Expand automation only after the configuration meets your needs, with a cadence your editorial capacity supports.
Use the one-time free allowance to evaluate a small configuration on one website. Once the Yodon features fit that test, evaluate automation’s effect on editorial capacity before expanding recurring production.