---
name: business-boomer-seo
description: Create, review, improve, or publish Business Boomer SEO articles, Google Docs briefs, author/fact-checker trust blocks, FAQ sections, schema, internal links, and AI-generated article image plans. Use when working on Business Boomer blog SEO, content briefs for Vishwa, EEAT/trust improvements, featured images, or converting SEO docs into site articles.
---

# Business Boomer SEO

Use this skill for Business Boomer SEO execution: article planning, Google Doc drafts, site article updates, EEAT/trust polish, schema, FAQ cleanup, and image plans.

## Source of truth

- Repo: `/Users/nancy/.openclaw/workspace/business-boomer`
- Live site: `https://aibusinessboomer.io`
- Brand voice: practical, plain-English, implementation-first, no AI fluff.
- Primary offer: done-for-you AI automation, OpenClaw setup, lead follow-up systems, websites, and custom workflows for service businesses.
- Trust rule: use real author/profile signals only. Do not invent credentials, fake headshots, fake social links, or fake client proof.

## Before editing

1. Run `brv query` for the article/topic or Business Boomer SEO context.
2. Inspect the current article/page before changing it.
3. Check author/fact-checker metadata in `src/lib/authors.ts` before adding trust blocks.
4. Prefer one focused commit per batch of SEO/site changes.

## Article/page standards

Each article should have:

- One clear H1 supplied by page metadata/template.
- A direct answer in the first 1-2 paragraphs.
- Practical examples for service businesses when relevant.
- Internal links to related Business Boomer guides/services, with no more than one internal link in the same paragraph.
- One FAQ section only.
- FAQ heading should be exactly `FAQ` unless the user asks otherwise.
- A clear CTA to contact/book an automation call when commercially relevant.
- Real author and reviewer/fact-checker signals where available.

Avoid:

- Duplicate FAQ sections from both MDX body and template rendering.
- Long generic AI filler.
- Repeating the exact page title as an FAQ heading.
- Unsupported claims about revenue, rankings, clients, or credentials.

## Images

For site articles:

1. Prefer specific branded images, diagrams, workflow maps, frameworks, and useful stat callouts over generic stock-style graphics.
2. Use a useful featured image plus usually 2–3 in-content images/diagrams/stat graphics when the article has room and the visuals genuinely help the reader.
3. Published images should generally be WebP where practical; SVG is acceptable as a source/design format.
4. Store final web images under `public/blog-images/` or another appropriate `public/` path.
5. Use descriptive filenames and alt text.
6. Keep total article image payload under 2 MB whenever practical.
7. If using statistics, source them; do not invent numbers or unsupported claims.
8. If generating images with OpenAI/image tools, create practical business/automation visuals that match the article topic; do not generate fake people as real staff or fake testimonial screenshots.
9. Verify image dimensions, file size, and live rendering before claiming done.

For Google Docs:

- Use images as supporting visuals in the document only when they clarify the article brief or final article.
- If Google Docs tooling cannot insert images directly, include an `Image to insert:` line with the generated/uploaded image path or URL and placement instructions.
- Never use `file://` URLs in a user-facing doc.

## Schema/SEO checks

- Homepage should include Organization/WebSite schema and page schema.
- Articles should include Article schema, author/reviewer details, canonical URL, OG/Twitter metadata, and FAQ schema when FAQs exist.
- Validate by build plus HTML inspection for the target page.

## Verification

Before final reply:

1. Run `npm run build` from the repo root.
2. Inspect changed files with `git diff`.
3. For pages, verify rendered HTML via local `next start` + `curl` or browser snapshot.
4. If deployed, verify production URL returns HTTP 200 and contains the expected content/image/schema.