# Editorial Policy | AiSeoCourse.net

> How lessons on AiSeoCourse.net are written, tested, sourced and reviewed, how corrections are handled, and which commercial relationships are disclosed.

URL: https://aiseocourse.net/editorial-policy/

would turn main into a scroll container and break every \`position: sticky\` inside it. --> 

Skip to main content

[#main-content →](#main-content)

# Editorial policy

This page explains how the lessons are written and reviewed, what standard a claim has to meet before it is published, and what to do when you find something wrong. It applies to every lesson, guide, checklist item and glossary entry on this site.

![Fact-checking workflow with dated source cards, a review stamp and a correction loop](/images/maps/flat-editorial-illustration-of-a-fact-checking-wor.webp)

science

## Tested before published

Every tactic is run on a live client site or a test domain before it appears in a lesson. If a result was mixed, the lesson says it was mixed.

event

## Every number sourced and dated

Figures carry the date they were observed and where they came from. A claim without a source does not go in.

autorenew

## Reviewed at least monthly

AI search behaviour changes quickly. The full curriculum is reviewed monthly, and pages that have moved get a new updated date.

block

## No vendor sponsorship

No SEO software company pays for a mention, a review or a ranking on this site. No tool is recommended in exchange for payment.

campaign

## Relationships disclosed in place

LocusPilot publishes this course and appears in Lesson 5. The AI SEO Rainmakers link is a Skool referral link. Both are stated wherever they appear, not buried here.

edit\_note

## Corrections are welcome

Send corrections to hello@aiseocourse.net with the page URL and what looks wrong. Substantive fixes are logged on the changelog.

## How a lesson gets written

A lesson starts from a question that came up repeatedly during LocusPilot builds or in reader email. The draft is written by Adam Yong, who then tests each recommendation on a live client site or a test domain and records what happened. Claims that survive testing go in. Claims that do not either get cut or get written up with the caveat attached.

Before publishing, the draft is checked against three things: whether each factual claim has a source and a date, whether the reader can act on it from a single location with limited hours, and whether anything reads as a promise of rankings or citations. Nothing here guarantees a citation, because no one can.

## What counts as a source

-   Observed behaviour on a live domain, with the date of observation.
-   Google Search Console data, including AI Overview impressions, with the window it covers.
-   Server logs showing named crawlers such as GPTBot, ClaudeBot, PerplexityBot and OAI-SearchBot.
-   Published documentation from the platform being discussed, linked where it exists.

Aggregate figures from LocusPilot's build history, such as the 200+ local business sites built since December 2025, are stated as what they are: a count from one publisher's own work, not an industry study.

## Review cycle

The whole curriculum is reviewed at least monthly. A review checks whether anything named in a lesson has changed: a profile field, a crawler user agent, a platform feedback route, an interface that no longer looks the way the lesson describes. Pages that change get a fresh updated date, and anything a reader would want to know about is recorded on the 

changelog

[/changelog/ →](/changelog/)

.

## Corrections

If something here is wrong, email 

hello@aiseocourse.net

[mailto:hello@aiseocourse.net →](mailto:hello@aiseocourse.net)

 with the page URL and the problem. Factual errors are fixed as soon as they are confirmed, and material corrections are noted on the changelog with the date. We do not quietly rewrite a claim and pretend it was always worded that way.

## Commercial relationships

Two relationships exist and both are disclosed on every page where they come up. LocusPilot, an AI website builder for local businesses, publishes this course and is used as an example in Lesson 5. The AI SEO Rainmakers link on the homepage and in Lesson 8 is a Skool referral link to a paid community run by Charles Floate. No SEO software vendor sponsors this site, and no tool is recommended in exchange for payment.

## AI use in writing

Drafting tools are used in production, which would be an odd thing to hide on a site about AI search. What matters is that a person tested every recommendation, checked every figure against its source, and is accountable for the result. That person is 

Adam Yong

[/author/adam-yong/ →](/author/adam-yong/)

.

Open access · Immediate start

## Start the course today

All 8 lessons, the 90-day checklist and the glossary are open. No signup, no paywall, no email capture.

Start Lesson 1 (Free) arrow\_forward

[/lessons/how-ai-search-picks-local-businesses/ →](/lessons/how-ai-search-picks-local-businesses/)

 

View the 90-Day Checklist

[/checklist/ →](/checklist/)

No signup. No paywall. 8 lessons, ~80 minutes.
