What we publish
One kind of article: documentation of a single GoHighLevel feature, written for someone who has to make it work this week. Almost all of it sits at the automation and workflow end of the platform, which is where the setup work is.
The recurring angle is deliberate. We write about what breaks. A guide that only restates the happy path in HighLevel’s release notes is not worth publishing, because HighLevel already published it. The value we can add is the AND-only filter with no OR option, the Labs toggle that behaves differently once snapshotted, the quota nobody documented. If we cannot find something a reader would trip over, we generally do not run the piece.
Where the facts come from
- HighLevel’s own published documentation and release notes, and the product interface itself.
- Where a limit, default, or beta status comes from HighLevel’s documentation, the guide attributes it in the text — “HighLevel’s own support article states…” — so you can tell our reading of a feature apart from the vendor’s statement about it.
- Where the documentation does not answer a question, we say so rather than filling the gap with a confident guess. Several guides end on an open question for exactly this reason.
Where automation is involved
This site is produced with a substantial amount of automation. We would rather set out precisely what that means than bury a vague line in the Terms, so:
- Which content: all of it. Every guide in the Guides section, not an unspecified “some articles”.
- What is automated: tracking HighLevel’s product releases and documentation updates to choose topics, producing the first draft, formatting, internal linking, and scheduling publication.
- What automation is not permitted to produce: pricing, numeric limits, quotas, availability, or beta status that cannot be pointed to in HighLevel’s own documentation or observed in the product. Invented specifics are the failure mode of automated writing, and they are the thing this rule exists to stop.
- What is never automated: claims about us — our fees, what we are affiliated with, and what we earn. Those are written by hand and appear on about and disclosure.
- Who is accountable: publication under the house byline GoHighLevel Partners Editorial means we take responsibility for the output regardless of how it was drafted. “The tool wrote it” is not a defence we will offer you.
Why we work this way: HighLevel ships constantly, much of it behind Labs toggles and betas that change again within weeks. Automation is what lets a small operation document a feature in the days after it appears instead of the quarter after. The trade-off is that drafting speed can outrun verification, which is why the rule above draws the line at unverifiable specifics, and why the corrections route below is public.
Beta and Labs features
Some of what we cover is explicitly in beta or sits behind a Labs toggle. Where that is true the guide says so and names the toggle. Treat those guides as accurate on their publication date and provisional after it — beta behaviour changes without notice, and our standing advice is not to snapshot a beta feature into a client sub-account and walk away from it.
Accuracy, updates and corrections
- Every guide shows its publication date. Judge it against that date.
- When we correct something material, we change the guide rather than quietly deleting it.
- To report an error: email support@gohighlevel.partners, or leave a comment on the guide. Comments are open on every article and a public correction is often more useful than a private one, because the next reader sees it.
- If you show us a guide is wrong, we would rather fix it than defend it. Point at HighLevel’s documentation or the product and we will take that over our own draft.
Independence and commercial influence
- We do not accept payment for coverage — no sponsored guides, no paid placement, no paid links, no gifted access in exchange for a favourable write-up.
- HighLevel has no involvement in what we publish. It does not review, approve, fund, or see this site in advance, and we are not affiliated with it.
- We earn no referral commission from HighLevel, and there is no affiliate or referral link anywhere on this site.
- We do have a commercial interest, and it is this: we sell GoHighLevel setup services, so guides that make the platform tractable are good for our business, and so is a reader deciding they want help with it. That interest is disclosed in full on the disclosure page. It is also the reason we hold the line on documenting the platform’s problems — a guide that hides a trap to keep the software looking good would be worth less than the client it might win.