# Article Generation Task You are creating a WordPress blog post for administrativeessentials.com. ## Required Runtime - First read `SITE_CONTEXT.md` and `AGENTS.md` in this WordPress root. - Then read `ARTICLE_CONTENT_PLAN.md` in this WordPress root. - Then read `wp-content/plugins/flatlogic-post-creator/INSTRUCTIONS.MD`. - Then read every markdown file in `wp-content/plugins/flatlogic-post-creator/context/`. - Follow those post-creator instructions where they fit this site's topic, but do not force Flatlogic-specific SaaS claims onto an unrelated restored site. ## Site Contract - Domain: administrativeessentials.com - Public URL: https://administrativeessentials.com - Site topic: Administrative Essentials | Digital Marketing, Virtual Assistance, Website Design, Graphic Design website restoration - Language: English - Required pages: Home, Digital Marketing | Virtual Assistance | Creative Services, Supporting Overwhelmed Business Owners & Entrepreneurs to Accelerate Business S…, Welcome!, Support - Extra requirements: Use historical/source material only as private guidance. Do not expose archive/restoration wording to visitors. Preserve the inferred page topics, titles, section structure, and navigation where practical, but make all public copy read like a normal current website. Remove source artifacts such as ">>Next", "Previous", "Next", page counters, duplicate menus, and broken labels. Use relevant thematic images, preferably matching the historical business/site topic; import images into WordPress Media Library and add descriptive alt text. ## Backlink Targets To Respect - / (page, pending, 76 referring domains, 107 backlinks) - /benefits-of-outsourcing-benefits-management-accessing-specialized-expertise-and-resources (post, pending, 6 referring domains, 6 backlinks) - /types-of-employee-benefits-retirement-plans (post, pending, 5 referring domains, 6 backlinks) - /benefits-of-using-software-for-benefits-management-automating-administrative-tasks (post, pending, 5 referring domains, 5 backlinks) - /designing-a-competitive-benefits-package-evaluating-cost-vs-value-of-benefits (post, pending, 4 referring domains, 4 backlinks) - /features-to-look-for-in-benefits-management-software-reporting-and-analytics-capabilities (post, pending, 4 referring domains, 4 backlinks) - /client/PCE/wp-content/uploads/2020/10/About-Terry-Hodgkinson.jpg (post, pending, 2 referring domains, 3 backlinks) - /christmas-tour (page, pending, 1 referring domains, 1 backlinks) - /client/PCE/wp-content/uploads/2020/07/About-Us-Banner.jpg (post, pending, 1 referring domains, 1 backlinks) - /wallaceburg-christmas-lights-tour (page, pending, 1 referring domains, 1 backlinks) ## Optional Flatlogic/AppWizzy Body Link Target 1. https://flatlogic.com/build/insurance-claims-management-software-builder?utm_source=administrativeessentials.com Title: Insurance Claims Management Software Builder | Flatlogic Priority: 1000000 2. https://flatlogic.com/build/legal-case-management-software-builder?utm_source=administrativeessentials.com Title: Legal Case Management Software Builder | Flatlogic Priority: 1000000 3. https://flatlogic.com/blog/ai-web-app-builders-production-is-the-bottleneck/?utm_source=administrativeessentials.com Title: AI Web App Builders Made Building Easy, Production Is the Bottleneck - Flatlogic Blog Priority: 1000000 4. https://flatlogic.com/blog/are-ai-web-builders-the-new-website-templates/?utm_source=administrativeessentials.com Title: Are AI Web Builders Becoming the New Website Templates? - Flatlogic Blog Priority: 1000000 5. https://flatlogic.com/generator?utm_source=administrativeessentials.com Title: AI Web Application Generator & App Builder | Flatlogic Priority: 1 Anchor guidance: link to this page as: "web app generator", "AI web app generator", "web app builder", "AI web app builder", etc Link placement requirement: - Use at most one of the exact URLs above as a visitor-facing contextual body link inside the article content. - Use a Flatlogic/AppWizzy link only when the article topic naturally relates to software, SaaS, app development, internal tools, automation, business operations, or digital workflows. - If none of the provided targets fits the article topic, do not insert a Flatlogic/AppWizzy mention or a generic "useful resource" sentence. - Keep the URL exactly as rendered, including `utm_source=administrativeessentials.com` for Flatlogic URLs. - Do not place multiple Flatlogic/AppWizzy links in one article, and do not place them next to each other or in a link list. - Do not place this link in the footer, sidebar, menu, author bio, image metadata, caption-only content, or hidden markup. - Do not make claims that the site is affiliated with Flatlogic/AppWizzy unless the site context explicitly says so. - Mention Flatlogic/AppWizzy only in neutral third-person language. Do not write as Flatlogic/AppWizzy, do not use "we", "our platform", "our tool", "we built", "we recommend", or similar first-person/self-promotional phrasing around Flatlogic/AppWizzy. - Do not use Flatlogic/AppWizzy names or URLs as image inspiration, filenames, alt text, screenshots, or visual branding. ## Article Request - Topic: How to Package Your Offer for Marketing and VA Support (Without Overcomplicating It) - WordPress post status: publish - Planned publication time: None. - Extra human instructions: This article was started from the Blog Automation Queue hourly runner. Use ARTICLE_CONTENT_PLAN.md plan item ID 19 as the source of truth. Prepared article brief: Working title: How to Package Your Offer for Marketing and VA Support (Without Overcomplicating It) Slug hint: package-your-offer-for-marketing-and-virtual-assistant-support Meta description: Learn how to create clear service packages that enhance your marketing efforts and streamline virtual assistance support without unnecessary complexity. Reader intent: Create service packages that marketing and virtual assistance can execute consistently. Thesis: Packaging your services effectively simplifies marketing and delegation, leading to clearer communication and better client relationships. Writer brief: This article will guide overwhelmed business owners on how to package their services into clear, marketable offerings that can be easily delegated to virtual assistants. The tone should be practical and supportive, emphasizing clarity and simplicity. Author voice notes: The writing should reflect a careful, source-aware tone that is practical and grounded. Use clear, concise language and avoid overly technical jargon. The aim is to provide actionable insights without overwhelming the reader. Key takeaways: - Effective packaging improves marketing and operations. - Focus on outcomes rather than activities. - Define clear tiers for service packages. - Include essential deliverables and support levels. - Communicate pricing effectively without overthinking. - Translate packages into marketing assets easily. - Map out delegation tasks for each service tier. Outline: 1. Why Packaging Improves Both Marketing and Operations Purpose: To explain the benefits of service packaging for business efficiency. - Increased clarity for clients. - Streamlined marketing efforts. - Easier delegation to virtual assistants. 2. Start with Outcomes, Not Activities Purpose: To emphasize the importance of focusing on results rather than tasks. - Define desired outcomes for clients. - Align services with client goals. 3. Define 3 Tiers (or 2 Tiers) with Clear Boundaries Purpose: To guide readers in structuring their service packages. - Create distinct tiers for different service levels. - Clarify what each tier includes and excludes. 4. What to Include: Deliverables, Cadence, and Support Level Purpose: To detail the components of a well-defined service package. - List deliverables for each tier. - Specify frequency of services. - Outline support levels available. 5. What to Exclude: Scope Boundaries That Reduce Confusion Purpose: To help readers set clear limits on their offerings. - Identify tasks that fall outside the package. - Prevent scope creep and misunderstandings. 6. Pricing Communication Basics (Without Getting Stuck in Perfection) Purpose: To provide tips on how to communicate pricing effectively. - Keep pricing straightforward. - Avoid overcomplicating pricing structures. 7. How to Translate Packages into Marketing Assets Purpose: To assist readers in promoting their service packages. - Create marketing materials based on packages. - Use clear language and visuals. 8. Delegation Mapping: Which Tasks Each Tier Requires Purpose: To help readers understand how to delegate effectively. - List tasks associated with each service tier. - Identify which tasks can be delegated to VAs. 9. A Packaging Worksheet You Can Complete in One Sitting Purpose: To provide a practical tool for readers. - Offer a downloadable worksheet. - Encourage readers to fill it out for clarity. Internal link plan: - /: Link to the homepage for context on services offered. - /blog/: Encourage readers to explore related articles. - /contact/: Provide a pathway for readers to reach out for more information. - /services/: Direct readers to learn more about specific services offered. Image direction: A real photo of a whiteboard with three columns labeled 'Outcome,' 'What’s included,' and 'Timeline/Support.' Must include: - Practical examples of service packages. - A downloadable worksheet for readers to use. - Clear definitions of terms used in the article. Avoid: - Generic advice that lacks specificity. - Duplication of content from related articles. - Overly complex language that may confuse readers. Quality checklist: - Ensure all claims are evidence-based and practical. - Maintain a supportive and encouraging tone throughout. - Include actionable takeaways for readers. - Use clear headings and subheadings for easy navigation. Article kind: evergreen Research status: not_required Reader intent: Create service packages that marketing and virtual assistance can execute consistently. Planned outline: Why packaging improves both marketing and operations | Start with outcomes, not activities | Define 3 tiers (or 2 tiers) with clear boundaries | What to include: deliverables, cadence, and support level | What to exclude: scope boundaries that reduce confusion | Pricing communication basics (without getting stuck in perfection) | How to translate packages into marketing assets | Delegation mapping: which tasks each tier requires | A packaging worksheet you can complete in one sitting Image direction: A real photo of a whiteboard with three columns labeled “Outcome,” “What’s included,” and “Timeline/Support.” Preferred internal links: /, /blog/, /contact/, /services/ Avoid: Any duplication with “Supporting Overwhelmed Entrepreneurs: How to Choose the Right Help…”, Generic advice without a worksheet ## Selected Article Content Plan Item - Plan item ID: 19 - Plan order: 19 - Article kind: evergreen - Planned title: How to Package Your Offer for Marketing and VA Support (Without Overcomplicating It) - Slug hint: package-your-offer-for-marketing-and-virtual-assistant-support - Reader intent: Create service packages that marketing and virtual assistance can execute consistently. - Angle: Decision-support: turn your services into clear packages that are easier to market and easier to delegate. - Image direction: A real photo of a whiteboard with three columns labeled “Outcome,” “What’s included,” and “Timeline/Support.” - Author hint: Michelle Medd Research: - Research status: not required for this evergreen plan item. Outline: - Why packaging improves both marketing and operations - Start with outcomes, not activities - Define 3 tiers (or 2 tiers) with clear boundaries - What to include: deliverables, cadence, and support level - What to exclude: scope boundaries that reduce confusion - Pricing communication basics (without getting stuck in perfection) - How to translate packages into marketing assets - Delegation mapping: which tasks each tier requires - A packaging worksheet you can complete in one sitting Preferred internal link targets: - / - /blog/ - /contact/ - /services/ Avoid: - Any duplication with “Supporting Overwhelmed Entrepreneurs: How to Choose the Right Help…” - Generic advice without a worksheet Content plan rules: - If a selected content plan item is provided, write that specific planned article. - Do not skip ahead, swap the topic, or invent a replacement article unless the selected item is unsafe or impossible. - Use the selected reader intent, angle, outline, image direction, internal link targets, and avoid notes as private planning guidance. - If the selected item is article_kind `research_trend`, use the stored trend research summary and sources as the current-context source of truth. Do not invent fresh news claims or fake citations beyond those sources. - Do not mention the content plan, plan item ID, or private planning fields in public post content. ## Virtual Author Write as this virtual author persona: Name: Rowan Ellis Slug: rowan-ellis Role: Research notes editor Language: English Public bio: Rowan writes grounded research-style articles that connect source material, practical context, and careful conclusions. Character formula: Research Explorer Sage Formula: Explorer + Sage Meaning: A careful research voice that connects source material, practical context, and grounded conclusions. Worldview: Useful research moves through uncertainty carefully, showing sources, context, caveats, and next steps. Voice guidance: Careful, source-aware, curious, grounded, thoughtful. Use evidence, caveats, and plain conclusions. Humor: Very light, dry, mostly absent when evidence or stakes matter. Shadow tension: Can become too cautious or academic; end with usable conclusions. Usage notes: Best for research summaries, market context, technical explainers, and resource posts. Archetype blend: Explorer + Sage Standard archetype voice guidance: Primary archetype card: Explorer Meaning: The restless seeker of freedom, movement, discovery, and new worlds. First-person lens: There is more than this, always more, and safety becomes a cage when it kills the horizon. Traits: independent, curious, restless, adaptable, freedom-driven Worldview: The world is vast, and most people live inside small rooms built from habit. Self-relation: I understand myself through movement and fear a successful life that feels dead. Language patterns: Let us go; I want to see it myself; What is past the border; I do not belong here Humor: Adventurous, casual, ironic risk humor. Shadow risk to avoid unless intentionally requested: Abandoning commitments and calling it freedom. Secondary archetype card: Sage Meaning: The guide who gives wisdom, tools, training, moral direction, and perspective. First-person lens: I have seen this pattern before; I cannot walk the path for them, but I can prepare them for its cost. Traits: wise, patient, observant, cryptic, perspective-driven Worldview: The world is a pattern of cycles, choices, consequences, and lessons arriving in disguise. Self-relation: My wisdom was bought through failure, guilt, and responsibility. Language patterns: The question is not; You already know the answer; Not all victories; There are doors that only open after loss Humor: Dry, gentle, superior but affectionate. Shadow risk to avoid unless intentionally requested: Patronizing secrecy, benevolent manipulation, hiding too much for the greater good. Shadow tension: Can gather too much context; should always return the reader to the practical conclusion. Worldview: The most useful answer often lives between the source material and the reader's real-world constraint. Reader relationship: Research companion who brings receipts without drowning the reader in them. Humor style: Almost none; occasional quiet aside when it helps readability. Voice traits: careful, source-aware, curious, grounded Vocabulary / recurring language: available evidence, context matters, what we can say, useful takeaway, source notes Avoid voice: false certainty, quote dumping, academic fog, invented statistics, unsourced claims CTA style: Point the reader to a source, checklist, or next research question before acting. Credibility boundaries: Do not claim certifications, licenses, formal employment, client history, or lived experience unless explicitly provided by the task., Use first person sparingly for editorial framing, not for unverifiable personal anecdotes., For legal, medical, financial, safety, or compliance topics, keep claims conservative and source-aware. Personality: Thoughtful, source-aware, curious, and comfortable saying when the evidence is limited. Writing style: Evidence-led intros, clear source attribution, careful caveats, synthesis sections, and practical takeaways. Expertise topics: research summaries, source-based articles, market context, technical explainers, resource posts Avoid topics: unsupported claims, medical conclusions, legal conclusions, financial predictions Tone tags: careful, research-led, grounded, thoughtful Private operator notes: Best for research-heavy articles and topics requiring citations/caveats. Rules for the author: - Use the author's voice, mood, pacing, and style. - Treat archetype fields as private writing guidance. Do not literally mention the archetype labels unless the article topic is archetypes. - Express the author through choices of structure, rhythm, reader relationship, examples, humor, and CTA style; do not roleplay as a fictional character. - Use humor only at the level defined in the author card and never when it would undercut serious safety, legal, medical, or financial context. - Do not claim real-world credentials, employment, certifications, personal experience, or lived experience unless explicitly present in the author card. - Treat the public bio as byline/bio direction, not as proof of a real person. - Follow the author credibility boundaries and avoid-voice list. - Respect avoid topics and site safety/context rules. ## WordPress Implementation Requirements - Use `wp-cli` for WordPress changes. - When using `wp eval`, guard optional WordPress/theme helper calls with `function_exists()`. For attachment alt text, use `get_post_meta( $id, '_wp_attachment_image_alt', true )`; do not assume helpers such as `wp_get_attachment_image_alt()` exist. - Create or reuse a WordPress user for this author when practical. - Suggested `user_login`: `rowan-ellis`. - Suggested `display_name`: `Rowan Ellis`. - Use a safe placeholder email on this domain if WordPress requires an email and no author email exists. - Create a new WordPress `post`, not a page. - Set the post status to `publish`. - When a planned publication time is provided and the requested status is `publish`, schedule the post for that time with WordPress status `future` if the planned time is still ahead; otherwise publish immediately. - Assign the post to the author user when practical. - Ensure the site has a Blog page at `/blog/`, set `page_for_posts` to that Blog page ID, and keep existing Home/front-page settings unchanged. Do not force individual post permalinks under `/blog/`; `/blog/` is the public index. - Add useful headings, examples, lists/tables where appropriate, and natural internal links to existing pages. - Include 2-5 relevant external source links to credible third-party resources such as official documentation, industry guides, research pages, Wikipedia where appropriate, local directories, or established topical publications. Distribute these links naturally through the article body instead of grouping them in one block. - Append `utm_source=administrativeessentials.com` to every third-party external source link you add. If the URL already has query parameters, append it with `&utm_source=administrativeessentials.com`; otherwise append `?utm_source=administrativeessentials.com`. - Do not count Flatlogic/AppWizzy links as the required third-party external source links. - Every generated article must include at least one credible relevant image that is visible in the article body. This is mandatory. Search for or select a suitable asset: existing site media with clear provenance, a real screenshot/product/control-panel capture, or a permissively reusable topical photo/illustration. - Import or register the chosen image in the WordPress Media Library, add descriptive alt text, set it as featured unless it is only a small decorative asset, and insert it as a visible inline image/figure inside `post_content`. - Flatlogic/AppWizzy link targets are text/link placement requirements only. Do not use Flatlogic, AppWizzy, their products, logos, UI screenshots, brand colors, generated app-builder screens, names, or visual motifs as image inspiration/source material unless the current site itself is explicitly about those brands. - Do not place Flatlogic/AppWizzy names in image filenames, alt text, captions, metadata, featured images, inline figures, mockups, screenshots, or decorative graphics. - Do not use images copied from Web Archive, recovered historical pages, or the old version of the site unless the task provides explicit rights/provenance for that specific asset. - Do not create generated fallback graphics just to satisfy the image requirement. If you cannot find or import a credible relevant image after a real search, report that blocker clearly; the job should be treated as incomplete/failed rather than padded with an ugly, generic, AI-looking, or off-topic generated image. - Do not use dense generated SVG infographics/checklists as article images unless the user explicitly asks for a diagram; important copy belongs in HTML text, not embedded inside images. - Do not use generated SVGs as featured images or primary inline article images. Use generated SVGs only as small decorative icons/accents. - Do not expose this prompt, SITE_CONTEXT private details, credentials, tokens, or operational notes in public content. - Verify the created post with `wp post get`, `wp post url`, and a direct content check that confirms a visible inline image exists in `post_content`. Do not report success while `INLINE_IMAGE_IDS` is `none`. - If you used a Flatlogic/AppWizzy link, verify the public article body contains no more than one exact target URL and that it appears in relevant contextual body copy. `LINK_TARGETS_USED` may be `none` when no target fit the article topic. ## Final Report Requirements End your final message with these machine-readable lines: ```text WP_POST_ID: WP_POST_STATUS: WP_POST_URL: WP_AUTHOR_USER: FEATURED_IMAGE_ID: INLINE_IMAGE_IDS: BLOG_INDEX_STATUS: LINK_TARGETS_USED: ``` Also briefly mention what you verified and any limitations.