you want
that helps
who need it
This guide is for people and AI agents who turn real work into useful articles. It shows how to write a clear opening, show the proof, and link each page to the right guide. Use it to help readers understand the work and take the next step.
Before you hit publish — if any line fails, the article is not done.
- Write the result we want, the material we will use, and who it serves — our Goals, Content, Targeting (GCT) brief, for both the article and the project. “Post content” is not a goal.
- The hook matches this GCT — what the target actually cares about. A cute duration or process detail is not the point. Worked example: John Assaraf. Wrong hook: “15 minutes.” Right hook: a figurehead who buys performance ads sat down and called the work a game changer.
- Amplify trust — show the relationship. Do not advertise how thin it is, and do not announce “this is not a stunt / not paid / not a pitch.” A denial plants the doubt. Full rule.
- The opening answers the title at eighth-grade reading level or below. In 2–3 short sentences, say who this is for, what it does, why it matters, and what the reader can do next. Explain each new term in plain words and link its owned explainer on first mention; put technical detail later.
- The lead visual works in the first screen — the topic-specific photo, picture, diagram, or player is visible and readable after the site header and title on desktop and mobile. A colored shell, empty SVG, broken image, hidden featured image, or loading placeholder fails. A transcript pane is not a player.
- Source is a player — YouTube nocookie embed, or hosted
<video>until it is on YouTube. A pasted Short/watch URL or a still is not an embed. If a transcript stays, every speaker has a name. “Speaker 1” is unpublished. - First-mention entity links — people to their real site (if we manage the personal brand, that site), companies to the company site. Fetch the URL. A lookalike personal-name domain can be a different person.
- Our training comes first — search our guides before linking a tool or concept to a provider help page. Keep precise primary citations and required download or sign-in links when they help.
- The SEO Tree (how content links to its main topic) works — the page has a clear parent topic, supporting proof links up to its guide, and related guides help the next task. Verify links in the body.
- How-we pages have two doors — we can do it for them, and they can do it themselves. Both URLs return 200.
- A task guide passes the recipe check. Trigger, inputs, linked prerequisites, ordered steps, measurable output, pass/fail checks, and downstream handoff are complete. Review the recipe requirements.
- The execution has a written meta article (a record of one task run). Link the canonical task, recipe revision, and run evidence. Record its actual publication status. Review the run-record rule.
- Proofread against the source. Names and numbers match. No AI fluff.
The loop (same steps for a human or an agent)
- Write GCT.
- Watch the source. Draft from what you saw.
- Search the site. Enhance an existing URL, or say why this one is new.
- Draft: hook → visual → proof → links.
- Walk the card above. Fix every fail.
- Open this page again. Publish through the authorized rail, then fetch the live URL and confirm the card still passes on the served HTML.
- Write the execution’s meta article with the canonical task and run evidence. Publish it only within the existing authorization, and feed supported lessons back into the recipe.
Do this
- Write GCT, then the hook
- Watch the source yourself
- Enhance the existing page when one already ranks
- First person on personal-brand sites; WordPress author is the person
- Show the relationship. Name the people. Name the speakers.
- Embed the YouTube player (9:16 for Shorts)
- Link the site we actually run for a managed personal brand
- On how-we pages, link the product and the DIY pack
- Re-read this page, then verify the live HTML
Do not do this
- Lead with a cute time-math or process detail when the GCT is a peer endorsement
- Paste a transcript into ChatGPT and ship the essay
- Invent a new URL next to a page that already covers the topic
- Write third person on dennisyu.com
- Title a thin connection, or volunteer “this is not a stunt / not paid / not a pitch”
- Lead with unlabeled Speaker 1 / Speaker 2, or a transcript pane instead of a player
- Paste a youtube.com/shorts or watch URL as the video
- Ship a poster in place of the player
- Link a lookalike domain you did not fetch (jasonamato.com is lighting design; Jason Amato / Power Crew is jasongamato.com)
- Show how we did it with no we-do-it link and no DIY link
Start with GCT
GCT means Goals, Content, Targeting. Write those three lines for every article and project before work begins. They name the result, the source-backed content that helps achieve it, and the people it serves.
- Goal: what this page is supposed to do. Rank for a customer question, prove a method, land a peer endorsement. “Post content” is not a goal.
- Content: the one insight the source actually supports. Claim only what the video, the call, or the proof file contains.
- Targeting: who this is for, in their words. The hook is for them, not for us.
The hook is the compelling claim for this target. It is not the punchiest line on the tape if that line is a process detail. Assaraf’s closer was “fifteen minutes / fifteen months.” The GCT was a well-known operator who spends on Facebook ads, on camera, after a performance-advertising call. Other high-powered entrepreneurs care about who is speaking. They do not care how long the Zoom was. Keep his duration line as a quote. Do not make it the title.
Write for a reader who is new to the topic
Keep the first 2–3 sentences and the initial explanation at US eighth-grade reading level or below. Use short sentences, familiar words, and a clear action. Say who needs the guide, what it helps them do, why that matters, and what success looks like. A reader should not need to know what “GCT” means to understand the opening.
On the first meaningful mention of a new term, give its plain meaning and link our verified explainer. For example, explain the result, material, and audience before using the label “Goals, Content, Targeting.” If no suitable owned page exists, define the term here and record the content gap. Do not invent a link.
Example for a shared-memory guide: “Use this guide if you work with more than one AI assistant and keep repeating the same facts. It shows how to give them one set of notes, so each assistant can pick up where the last one stopped.”
Save the exact opening and its readability result in the review. Then have a reviewer name its audience, task, reason, and outcome. A low reading score alone does not prove clear meaning. Put commands and deeper technical terms after this short start and its useful visual.
Watch the video. Do not fake the watch.
Do not dump a transcript into ChatGPT and publish an essay you did not earn. Watch the whole thing. A transcript is a helper. Write down the opening sentence, the actual takeaway, who it is for, and names spelled the way the speaker said them.
If you were not in the room, say how we know the person and why the recording exists. Honor them. Do not make the article about the writer.
Do not duplicate. Enhance the tree.
Search the site and Google before you create a URL. If a page already owns that topic, add the new proof there. That is the SEO Tree rule. Keep method links on blitzmetrics.com when those pages are still the definitive ones. Do not tell anyone to hire a sunset brand.
Give each page one primary topic owner. Supporting stories and worked examples link up to that guide. The guide links back to useful proof and across to related guides that help the next task. Use the final canonical URL, even when it lives on another site we own. A footer link or a listing in a directory does not replace these links in the article body.
Where these writing rules apply
Use these rules when turning real source material into an article in Process, then checking and releasing it in Post. A particular assignment uses its own task recipe for the starting conditions, inputs, measurable result, and next handoff.
Keep the goal, content, and audience clear, use the definitive-article checklist for a task recipe, and write the meta article that records the execution. Register the actual task and its evidence in the Task Library (our directory of tasks and recipes).
A task guide is a recipe someone else can follow
Choose the page’s role before calling it definitive. A task-definitive article is the one maintained recipe for a repeatable task. A topic, person, or framework hub explains its subject and links to the task guides it owns. A story, opinion, tool comparison, reference, historical post, or record of one run has a different role. Fixing its opening or visual does not turn it into a task recipe.
A task recipe must include these parts, with links and proof that let another worker repeat the work:
- When to start: the trigger, starting state, and who does the task.
- What to bring: required inputs, access, and linked prerequisite tasks with the outputs they must produce.
- What to do: ordered steps and the decisions that change the next step.
- What to deliver: the measurable output and observable checks that decide pass or fail.
- What happens next: the next task, receiving owner or function, and handoff artifact.
- Where it belongs: its canonical record in the Task Library and its parent in the Content Factory (our four-stage process for using real content), our process for turning source content into useful assets.
Do not invent a prerequisite, threshold, or next task to complete the list. Record the missing information and hold task-definitive status until the source supports it. See the definitive article creation guide for the full review standard.
Show where the task fits
Keep the topic-specific visual in the first screen. Lower in a Content Factory task guide, add a responsive context diagram with the maintained stages: Produce → Process → Post → Promote. Highlight only the work this task performs. Link the prerequisites, this task, and the next task; show the run record feeding lessons back into the recipe. Keep access and tracking before the factory and measurement after it where those boundaries apply. Reuse the accepted map and labels. If placement is unknown, state the gap instead of inventing a box.
Write a record for every task run
Every time a person or agent executes a task, write a meta article, the record of one task run. Follow the meta-article writing guidelines. Link the exact canonical task, the recipe or skill revision used, and the evidence from the run. Include a distinct execution ID, trigger, inputs, steps, decisions, output, pass/fail checks, lessons, and next owner. Record time, steps, tokens, and cost when measured; mark unavailable figures UNKNOWN.
Writing is required. Publication follows the existing authorization. Save a complete draft when the run is not authorized or safe to publish. A failed or partial run still gets a record with its true result. An internal note or task comment can support the meta article, but does not replace it. Keep private evidence in an authorized location.
Compare this record with earlier runs and the recipe. When evidence shows a missing input, unclear step, weak check, or broken handoff, propose a correction to the maintained recipe and skill. Link accepted changes to the run that taught the lesson. A clean run does not require a rewrite.
Count distinct task executions, using their IDs. Edits, translations, copies, and retries within one run do not create more executions. Keep failed, partial, and unpublished runs in internal history with their statuses. Track verified execution frequency for a stated period separately from dated public-example volume. An older reviewed article count remains useful historical proof even when its articles lack execution IDs; it does not prove that many distinct runs. Preserve its evidence and audit date. Missing IDs leave execution frequency UNKNOWN or PARTIAL, not zero. Writing the run’s meta article is part of that execution; it does not start an endless chain of new meta articles.
First person. Author is the person.
On a personal-brand site, write as that person. Set the WordPress author to the person. Never admin. On a company site, third person is fine.
If the piece features a client or a figurehead, make it about them. Use their name in the title. Link their name to their site. Start with why they are worth listening to.
Amplify trust. Do not volunteer the opposite.
These articles exist to make a real relationship stronger in public. Friendly fire is copy that does the reverse.
Do not advertise how new or thin the connection is. Do not volunteer “this is not a stunt,” “this is not paid,” “this is not a pitch,” “what this is not,” or “this is not a generated photo.” The reader did not bring that doubt. The disclaimer planted it. Show who was there and what they did together. A title that names the people beats a title that names the gap.
The same rule covers transcripts. “Speaker 1” and “Speaker 2” are unpublished. Write the person’s name on every line of dialogue. A Descript share that opens on unlabeled dialogue is a transcript pane, not a player — put a hosted <video> or a YouTube embed first.
Hook, then answer
The first line has to earn the second. Then answer the question the title promised. Do not put a generic system diagram above the first H2 unless that diagram is the article’s subject.
Lead visual above the fold. No stock photos.
The article-specific player, photo, chart, or diagram may lead or appear immediately after the short opening, without scrolling on desktop and mobile. A decorative card or a featured image the theme does not render in the body does not count. A transcript pane with unlabeled speakers does not count. This is a hard publish gate.
Upload through the Media Library. Caption and alt text. No Google Images. No stock. Before a personal-brand site goes live it still has to pass the website QA audit.
Check a real first visit: open the public URL at 1440×860 and 390×844 before any click or scroll. Capture both first screens. Confirm meaningful visual content and readable labels appear, with no empty frame or sideways page overflow. The initial image or diagram must be present even if scripts are delayed. Save the viewport evidence separately from the WordPress read-back; a saved image tag or HTTP 200 is not proof that a visitor can see it.
Entity linking
Follow the entity linking tree. Link on the first mention. Do not stack the same URL twice in one paragraph. Do not use “click here.” Anchor text is 3 to 6 words. We only link web pages, not PDFs.
- People we know: their personal site. Dennis is dennisyu.com.
- Personal brands we manage: the site we actually run. Fetch it before you paste. Example: Jason Amato (Power Crew / Operations Mastery Lab, friend) → jasongamato.com. jasonamato.com is a different Jason (Austin lighting design). Do not invent a lookalike. Do not swap the two.
- Companies: the company site. Ninja HVAC → ninjahvac.com. Jason hosting that lab → jasongamato.com. Person and company are not the same link.
- Our methods: the definitive article. Content Factory, GCT, SEO Tree, money tree, website QA.
- Tools and outside brands: first search our Canonical Directory, Task Library, and site articles. Read the matching guide and link to it with honest text such as “our Obsidian setup guide.” If no useful owned guide exists, keep a passing mention plain or cite the exact primary source needed for the claim, and record the content gap. Never invent a URL.
Giuseppe has no personal site. Do not invent one.
Provider links still have a place. Use official technical documents to support specific claims and direct links for a required download, login, or setup step. Label those links by their purpose. They support our training; they do not replace our own explanation. Record each named tool or concept, the selected URL, and why it helps the reader. Do not replace citations just to hit an internal-link count.
Embed the source
If the article came from a video, embed that video after the hook. One sentence of context: who is speaking and why this recording exists. Name the people. The YouTube description links back here.
YouTube is a player, not a URL
If a YouTube URL exists, embed the player. Host youtube-nocookie.com. Query: rel=0, cc_load_policy=1, cc_lang_pref=en (or the page language). Autoplay with sound only after a click.
A poster JPEG or a pasted youtube.com/shorts/… / watch URL is not an embed. If you already have the iframe, delete the Short URL in the next sentence.
Hosted <video> is the fallback until the source is on YouTube. Then swap. Do not leave both. Do not invent a YouTube ID.
Shorts use a 9:16 player, not a 16:9 letterbox. Skip Smush lazy-load on the iframe (class="skip-lazy no-lazyload" on the tag). QA the served HTML: live iframe src=https://www.youtube-nocookie.com/embed/….
How-we articles: two doors
Whenever we show how we achieved a result — a meta article, a “how we ranked,” a before/after — include both:
- We can do it for them. The product page. Example: Knowledge Panel package and pricing.
- They can do it themselves. The skill packs and this page.
The Brady Sticker ranking article is the pattern. A clip that is only a scene does not need a product pitch. Verify both URLs return 200. Do not use gohighlevel.com/authority — it 301s to a 404 page.
Proofread. No AI fluff.
Read it out loud. Cut anything the source did not say. One H1 (the title). H2s for real sections. Banned filler: “beacon of,” “delve into,” “digital landscape,” “unlocking the power of,” “in today’s fast-paced world.”
This is the Process stage of the Content Factory. You are not the expert. The person in the video is.
Keep the process current
Install the Local Service Spotlight plugin so the skill packs stay current. You can follow this page without it. Packs: skill packs. Source: github.com/dennisyu/local-service-spotlight-skills.
Where the older copy lives
Working copy: this page. Archive / SEO leaf: blitzmetrics.com/blog-posting-guidelines. Internal transcription tools stay with the team. They are not required to follow this page.