Working Notes on Agent Systems/Brad Zhang

@teach_fireworks / X longform

Run the SEO/GEO visibility loop once a week. The SEO/GEO visibility loop in the Loop Li...

Run the SEO/GEO visibility loop once a week. The SEO/GEO visibility loop in the Loop Library is very suitable for content-based products, developer tools and SaaS official websi...

June 22, 2026 · 1 min read

Run the SEO/GEO visibility loop once a week. The SEO/GEO visibility loop in the Loop Li...
Figure 1 / source image

Run the SEO/GEO visibility loop once a week.

The SEO/GEO visibility loop in the Loop Library is very suitable for content-based products, developer tools and SaaS official websites.

It covers a wider scope than traditional SEO: crawlability, indexation, page intent, title, internal links, structured data, source citations, answer-first content are all in it.

Then sort by impact, fix the highest leverage problems first, and then crawl and benchmark again.

The growth of the official website will be increasingly affected by GEO.

In the future, users will not only come from search engines, but also from AI answer engines.

Whether the page can be understood, quoted, and attributed will directly affect the way the product is discovered.

This kind of thing is difficult to solve with one major optimization, and is more suitable for weekly fixed runs.

Only fixing one or two of the most critical issues at a time will reduce a lot of losses that “should have been seen but were not seen” in the long run.

This is more like content infrastructure in the AI ​​era and cannot be treated as just a marketing move.

The video starts here: Corresponding loop: Open source project:

Visual summary

Article argument map

Generated from the post's content graph

FORMATTOPICCAPABILITYMARKETcoverscoverscoverscoverssignalssignalssignalssignalsFORMATlongform noteTOPICtechnical distributionTOPICretrievalTOPICevaluationTOPICtoolingCAPABILITYdeveloper toolingCAPABILITYevaluationCAPABILITYproduct surfaceCAPABILITYtechnical distributionMARKETopen-source builders
Mermaid outline
flowchart LR
  format-long_post["longform note"]
  topic-technical-distribution["technical distribution"]
  topic-retrieval["retrieval"]
  topic-evaluation["evaluation"]
  topic-tooling["tooling"]
  capability-developer-tooling["developer tooling"]
  capability-evaluation["evaluation"]
  capability-product-surface["product surface"]
  capability-technical-distribution["technical distribution"]
  market-open-source-builders["open-source builders"]
  format-long_post -->|covers| topic-technical-distribution
  format-long_post -->|covers| topic-retrieval
  format-long_post -->|covers| topic-evaluation
  format-long_post -->|covers| topic-tooling
  format-long_post -->|signals| capability-developer-tooling
  format-long_post -->|signals| capability-evaluation
  format-long_post -->|signals| capability-product-surface
  format-long_post -->|signals| capability-technical-distribution

Visual structure

Essay structure map

Built from summary and key paragraph positions

Run the SEO/GEO visibility loop once a week. The SEO/GEO visibility loop in the Loop...THESISRun the SEO/GEOvisibility loop once aweek. The SEO/GEOvisibility loop in theSIGNALRun the SEO/GEOvisibility loop once aweek.OPERATORIn the future, userswill not only comefrom search engines,but also from AIIMPLICATIONThe video starts here:Corresponding loop:Open source project:
Mermaid outline
flowchart LR
  thesis["Run the SEO/GEO visibility loop once a week. The SEO/GEO visibility loop in the Loop Library is very suitab..."]
  signal["Run the SEO/GEO visibility loop once a week."]
  operator["In the future, users will not only come from search engines, but also from AI answer engines."]
  implication["The video starts here: Corresponding loop: Open source project:"]
  thesis -->|frames| signal
  signal -->|develops| operator
  operator -->|lands in| implication

Source: View the original post