GHL Meets SEO — Header
[email protected] (828) 358-2389
Support Portal
TL;DR

Our content is human-led and AI-assisted. We choose the topics, perform the research, pull the data, run the reports, capture the source screenshots, write the notes and examples, choose the page structure, and make the final publishing decisions. AI primarily helps organize, polish, format, and assemble that work before a manual review and quality-control process.

Content Transparency

How We Use AI in GHL Meets SEO Content

AI is part of our publishing workflow, but it is not the source of our experience, client data, screenshots, examples, opinions, or final decisions. This page explains exactly where human work ends, where AI assistance begins, and what we manually verify before anything is published.

Human-Led Research Real Client Evidence AI-Assisted Assembly Manual Quality Control
Why We Disclose It

If AI Helped Create the Page, You Should Know How

Transparency is more useful than pretending modern content workflows do not use AI tools. Google's own people-first content guidance encourages publishers to make the who, how and why behind content clear when that context helps the reader. This disclosure is our answer to the “how.”

WHO
A Real Author Owns the Content Josh Cline develops the topics, source material, examples, opinions, process notes and final editorial direction.
HOW
AI Has a Defined Role It helps organize and assemble work that already has human research, evidence, direction and page requirements behind it.
WHY
The Goal Is Reader Value Pages are created because the topic is useful to HighLevel agencies, partners, clients or readers, not simply because a keyword exists.
This page is about the editorial content on this site. The point is not that AI-assisted content is a problem by default; the important distinction is whether AI assistance is being used to help create useful content for people or primarily to manipulate search rankings. It is also intentionally not a complete tutorial on AI search, content agents, page scheduling, or large-scale SEO content production. Those subjects are being covered separately so each page can stay focused on one purpose instead of repeating the same information across the site.
The Actual Workflow

What Happens Before an AI-Assisted Content Page Goes Live

AI normally enters the process after the important editorial decisions have already been made. On larger pages, the source material can include multiple documents, screenshots, reports and many pages of notes before an agent ever sees the project.

01

We Choose the Topic, Audience + Purpose

The process begins with a real reason to create the page. That might be a client result worth documenting, a recurring question from HighLevel agencies, a workflow we have tested, a business lesson from our agency, or a topic that needs a clearer explanation. We decide what the reader should leave knowing before we decide what the page should rank for.

Human Decision
02

We Gather the Source Material Ourselves

We pull the account data, run the reports, capture the screenshots, collect relevant URLs, record the specific metrics we want to explain, identify supporting examples, and organize whatever firsthand information is needed for that page. For strategy content, the source material usually comes from our own agency processes, client work, testing, support conversations, or systems we actively use.

Human Research
03

We Write the Notes, Insights + Page Direction

Before AI assembles a page, we write out the points that need to be made in note, list, outline, or paragraph form. That can be a short briefing for a simple page or dozens of pages of material for a large resource. Some projects have more than 35 pages of notes, screenshots, instructions, examples and data before the page body is assembled.

Human Source Copy
04

We Choose the Page Structure + Requirements

The layout is not left open-ended. We already know the page type, design system, heading hierarchy, content components, image placements, internal-link rules, responsive behavior, and the sections we want. Those structures come from our own experience building HighLevel websites and repeatedly testing what makes long-form content easier to understand, read and maintain.

Human Framework
05

AI Helps Organize, Polish + Assemble the Material

Once the evidence, notes and structure are defined, one of our custom agents can help turn that material into the requested page. Typical assistance includes organizing the supplied notes, removing unnecessary repetition, smoothing transitions, keeping terminology consistent, fitting content into the chosen components, and producing the HTML, CSS or other code needed for the finished body.

AI Assistance
06

We Manually Review, Edit, Test + Publish

The generated body is not treated as a finished page. We review the wording against the source material, inspect the code, add or rewrite paragraphs where needed, check the screenshots and links, proofread the page, test desktop and mobile layouts, and run our normal quality-control process. We also write and apply the page's final metadata ourselves. Only after that review is the page considered ready.

Human Final Approval
Decision Ownership

What We Decide vs. What AI Helps With

Our preference is to make as few important editorial decisions with AI as possible. The more consequential the decision is to accuracy, evidence, strategy, or meaning, the more likely it is handled directly by a person.

Human-Owned Research, Evidence + Editorial Decisions
  • Choosing the audience, topic, purpose and page type.
  • Selecting target topics, search intent and keyword direction.
  • Running client reports and pulling account data.
  • Capturing and selecting screenshots, examples and source media.
  • Writing the raw notes, observations, examples and conclusions.
  • Choosing the page structure, design system and component layout.
  • Deciding which claims, numbers and examples belong on the page.
  • Approving internal links, metadata and final published wording.
  • Completing the final fact check, proofread and quality-control review.
AI-Assisted Organization, Polish + Production Support
  • Organizing large sets of notes into the requested hierarchy.
  • Cleaning grammar, transitions and repetitive wording.
  • Fitting supplied content into established page components.
  • Helping maintain terminology and formatting consistency.
  • Converting approved content into HTML, CSS or structured markup.
  • Surfacing duplicated ideas, missing transitions or unclear sections for review.
  • Assisting with alternate phrasing when a human editor wants another option.
  • Creating occasional non-evidentiary thumbnails or preview graphics when appropriate.
  • Speeding up repetitive production work without owning final publication.
AI is useful because it can process and organize a large amount of material quickly. It is not useful to us as a substitute for the evidence, experience, judgment or accountability behind the page.
Evidence Standards

Client Reports and Case Studies Use Real Evidence

The role of AI changes when a page contains client performance data. The numbers and report images have to come from the actual source, not from a generated approximation of what a report could look like.

What We Use as Source Evidence

Our public our published case studies are built from real client work. Business names and private account details may be anonymized, but the underlying report data and screenshots are not recreated with AI.

01
Raw Account Screenshots We capture the real interfaces, reports and measurements used to support the page.
02
Third-Party Reporting Tools Local ranking reports and similar evidence come from the reporting systems that generated them.
03
Saved Source Reports We retain the fuller report or source material behind screenshots used in our published cases.
04
Human Interpretation We identify the specific data points worth explaining and add context around what the numbers do and do not show.
GHL Zone Agents

Our Content Agents Follow the Same Human-Controlled Principle

This disclosure covers the editorial content on this site first. The agents we use for client and partner websites are a separate product workflow, but the underlying idea is similar: AI-assisted production should work from controlled inputs, real business context and human checkpoints.

Inputs Humans Can Control the Source Material

Topics, research, keywords, business information, custom copy, links, images and other page inputs can be selected or supplied before the page is assembled.

Images Real Client Media Is Preferred

We encourage clients to keep real business photos in HighLevel media storage so agents can select from authentic images first. If no suitable real image exists, a generated image may be used until a better real image can replace it.

Control AI Involvement Can Be Reduced

A user can provide more of the writing manually and use an agent primarily to organize content into the approved page structure, rather than asking it to generate the substance from scratch.

You can see the current tools in the GHL Zone Agents hub. More detailed pages about AI, content production, page scheduling, and the exact agent workflows will live in their own resources so this disclosure remains focused on one question: how this site produces and reviews content.
What Still Requires a Person

The Parts We Do Not Want AI to Replace

Faster production is useful only when the page still has something real behind it. These are the parts of the process where firsthand work and human accountability matter most.

01 Firsthand Experience The lessons come from running the agency, using the systems, helping clients and observing what happens in practice.
02 Source Verification Numbers, screenshots, client facts and report findings are checked against the source that produced them.
03 Editorial Judgment A person decides what deserves emphasis, what needs context, what should be removed and what may be misleading without explanation.
04 Client Context A metric rarely means much without understanding the business, market, campaign, website, history and conditions around it.
05 Accountability A published page belongs to us. “The AI wrote it” is not an excuse for a factual error, bad recommendation or unclear claim.
06 Final Approval Nothing is considered finished simply because a model produced a clean draft or valid code.
Manual Quality Control

What We Check Before Publishing

The review is both editorial and technical. A useful page can still fail the reader if a number is wrong, a screenshot is misleading, a link is broken, or the mobile layout makes the content difficult to use.

Facts + NumbersCompare key claims, dates and metrics back to the supplied source material.
Screenshots + MediaConfirm the image belongs to the correct section and supports the point being made.
Claims + CaveatsRemove overstatements and add context where a result could be misread as typical or guaranteed.
Repetition + ReadabilityTighten duplicated ideas, awkward transitions and sections that are longer than their value requires.
Links + Page FlowConfirm URLs, internal-link relevance, anchors, buttons and page flow.
Desktop + MobileReview page width, cards, images, headings, tables and responsive stacking.
MetadataWrite and apply a descriptive title, meta description and canonical for the finished page.
Final Human ReadRead the finished page as a visitor before treating it as complete.
Our Practical AI Content Policy Six Rules We Want Readers to Be Able to Hold Us To
1. Real Evidence Stays Real We do not use generated reports or fabricated screenshots as proof of client performance.
2. AI Does Not Create Our Experience Strategy and examples should trace back to real work, research, testing or clearly identified outside sources.
3. Important Decisions Stay Human Topics, evidence, meaning, context, page direction and final approval belong to a person.
4. Generated Images Are Not Proof Decorative AI imagery may be used, but it is not presented as a real client screenshot or measured result.
5. The Finished Page Is Our Responsibility We review the result before publication and remain responsible for correcting errors or unclear information.
Disclosure Should Match the Workflow We encourage agencies using AI-assisted content systems to describe their own process accurately rather than copy a disclosure that does not reflect how they actually work.
This policy applies to our current publishing workflow and can evolve as the tools change. The principle should remain the same: explain what is human, explain what is assisted, and never let AI-assisted production blur the difference between real evidence and generated material.
Want to know who is responsible for the content? Read the Creator + Author story for Josh Cline, including the agency background and firsthand experience behind this site.
Transparency Over Mystery

Use AI Where It Helps. Keep the Human Work Visible.

That is the balance we are trying to maintain across this site: use AI tools to reduce repetitive production work without outsourcing the experience, evidence, judgment and accountability that make the content worth publishing in the first place.