Article guidelines (how we write, and how your agent should)

This is the public working copy of how we write articles, and how your agent should write them. You do not need anyone to send you a private playbook. You do not need the plugin to follow this page.

I want a stranger, or someone else’s agent, to find the process from a public URL. That URL is this one. The Local Service Spotlight plugin is how the skill packs stay current. Install it if you can. If you cannot, keep reading.

Start with GCT

GCT is Goal, Content, Targeting. Write it in that order. If you skip it, you get a generic article that could sit on anyone’s site.

• Goal: what this page is supposed to do. Rank for a customer question, prove a method, support a service page. “Post content” is not a goal.
• Content: the one insight the source actually supports. The article may only claim what the video, the call, or the proof file contains.
• Targeting: who this is for, in their words. The keyword is usually the customer’s question, not our jargon.

GCT sits inside the 9 Triangles method. You do not need the whole framework to write one article. You do need those three lines at the top of the working doc.

Watch the video. Do not fake the watch.

The number one writing failure is the same every year. Someone dumps a transcript into ChatGPT and publishes an essay they did not earn. The article is vague. Names are wrong. The point of the video is missing.

Watch the whole thing. A transcript is a helper, not a substitute. While you watch, write down:

• The sentence that should open the article
• The actual takeaway, in one line
• Who it is for
• Names, companies, and numbers, 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 for the keyword before you create a URL. If a page already owns that topic, add the new proof to that page. A second article on the same keyword is our own pages fighting each other.

That is the SEO Tree rule. Leaves hang off a branch. They do not start a second trunk. The money tree is the measured version of the same idea: which pages actually get internal links, and which money pages are bare.

New work publishes here, on the person, or on the vertical. Keep the method links on blitzmetrics.com when those pages are still the definitive ones. Do not tell anyone to hire BlitzMetrics.

First person. Author is the person.

On a personal-brand site, write as that person. “I recorded this with Marko” not “Dennis sat down with Marko.” The byline visitors see must match the name on the site.

Set the WordPress author to the person. Never admin. Never a team email. Never a generic username. This applies to every post on that site, not just the new one.

On a company site, third person is fine. The test is simple: would the owner be embarrassed to read this out loud as themselves?

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. Do not write a title that makes them look weak.

Hook, then answer in the first paragraph

The first line has to earn the second. After that, answer the question the title promised. If the title is “How long does it take to build a pool in South Florida,” the first paragraph says the range and the variables. Readers and search snippets both take the top.

Do not put a generic process diagram above the first H2. The Content Factory four-stage picture is useful later, not as the lead. The lead visual is specific to this article: a screenshot, the source video, a photo of the person, or a topic diagram people can click.

Lead visual above the fold. No stock photos.

Every page we publish needs something to look at without scrolling. A wall of text fails on a phone. The featured image in WordPress is not enough, because a lot of themes hide it in the body.

Use a screenshot from the video, a real photo, or an HTML diagram with links. Upload through the Media Library. Add a caption and alt text. Do not paste from Google Docs. Do not pull random images from Google. Do not use stock.

Green boxes mean what good looks like. Red boxes mean what to stop. That is the same pattern as this page.

Before a personal-brand site goes live, it still has to pass the website QA audit. Writing a pretty article on a broken site is wasted work.

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.”

• People we know: their personal site. Dennis is dennisyu.com.
• Companies in the network: their real site.
• Our methods: the definitive article. Content Factory, GCT, SEO Tree, money tree, website QA.
• Tools and outside brands: our article about how we use them, if we have one. Do not dump link equity on a homepage you do not own.

Anchor text is 3 to 6 words and says what the reader gets. “Strategies to trigger a Knowledge Panel” beats “Knowledge Panels.” We only link to web pages, not PDFs or files.

Embed the source

If the article came from a video, embed that video near the top, after the hook. One sentence of context: who is speaking and why this recording exists. Readers should not have to guess where a quote came from.

The article and the video should point at each other. The YouTube description links back here.

Proofread. No AI fluff.

Read it out loud. Cut anything the source did not say. Keep paragraphs to a few lines. Use active voice. One H1 (the title). H2s for real sections. No heading every three lines.

Banned filler: “beacon of,” “delve into,” “digital landscape,” “unlocking the power of,” “intricacies,” “in today’s fast-paced world.” If a sentence could sit on a stock-photo blog, delete it.

Use a grammar tool if you want. Do not let it sand off the speaker’s voice. Check names against the video. Tools love to “correct” Marko Sipila into Marco.

This is the Process stage of the Content Factory: turn a real recording into a page that belongs on the tree. You are not the expert. The person in the video is.

Verification checklist

Public-safe items. If any box fails, the article is not done.

• [ ] GCT is written: Goal, Content, Targeting, in that order
• [ ] I watched the source. I did not generate the article from an unwatched transcript
• [ ] I searched for an existing page. I enhanced it, or I can say why this URL is new
• [ ] First person on personal-brand sites. WordPress author is the person, not admin
• [ ] The first paragraph answers the title
• [ ] A real visual sits above the fold. No stock. Captions and alt text are on
• [ ] No framework diagram above the first H2
• [ ] Source video is embedded, with one line of context
• [ ] Entity links follow the tree. Anchors are specific. Links were click-tested
• [ ] No AI fluff, no heading abuse, no weasel words, no rhetorical questions
• [ ] Proofread against the source. Names and numbers match
• [ ] Title matches the article. Slug is short and readable

Keep the process current

I recommend installing the Local Service Spotlight plugin so the skill packs stay current. You can still follow this page without it. The plugin is the box. The skills are the jobs. This page is the readable process either way.

The pack list is at skill packs. The source repository is github.com/dennisyu/blitzmetrics-skills. Refresh from that address. Do not assume last month’s file is this month’s rule.

Where the older copy lives

This Local Service Spotlight page is the working copy. The older BlitzMetrics page stays as the archive and SEO leaf: blitzmetrics.com/blog-posting-guidelines. That page keeps its content. We do not delete BlitzMetrics pages. We do not noindex them.

Internal transcription tools, shared drives, and client-notification steps stay with the team. They are not required to write a public article that follows this page.

If you are writing for us, or you handed this URL to your own agent, start at the tiles and work down. Proof beats adjectives. The tree beats a new URL.