Simpyll / Built in the open

Simpyll Pulse

STATIC OBSERVATORY · V1

An interactive look at how Simpyll grows, connects, and performs.

Report date · source commit dateInside the project ↗

01 / The current picture

A small site, measured honestly.

Published content · build snapshot

Published articles

8

Currently public canonical articles.

Indexable pages

26

Public pages in the rendered build.

Contextual connections

0

Unique directed article-to-article links in body content.

Articles with inbound links

0

Articles referenced by another article’s body.

Contextual-link orphans

8

No inbound article-body links; still discoverable through site navigation.

Technical findings

10

Automated findings, including editorial review opportunities.

Search & audience

Google Search performance

Validated Google reporting data. Last successful refresh: 2026-11-11. Timezone: America/Los_Angeles. Recent four days excluded for reporting delay.

Search clicks

4.0002026-10-25: 2.002026-10-26: 2.002026-10-27: 0.002026-10-28: 4.002026-10-29: 0.002026-10-30: 0.002026-10-31: 0.002026-11-01: 0.002026-11-02: 0.002026-11-03: 0.002026-11-04: 0.002026-11-05: 0.002026-11-06: 0.002026-11-07: 0.002026-10-112026-11-07

Search impressions

22.0002026-10-25: 11.002026-10-26: 7.002026-10-27: 11.002026-10-28: 22.002026-10-29: 11.002026-10-30: 11.002026-10-31: 10.002026-11-01: 3.002026-11-02: 3.002026-11-03: 9.002026-11-04: 5.002026-11-05: 1.002026-11-06: 2.002026-11-07: 1.002026-10-112026-11-07

CTR (%)

28.5702026-10-25: 18.182026-10-26: 28.572026-10-27: 0.002026-10-28: 18.182026-10-29: 0.002026-10-30: 0.002026-10-31: 0.002026-11-01: 0.002026-11-02: 0.002026-11-03: 0.002026-11-04: 0.002026-11-05: 0.002026-11-06: 0.002026-11-07: 0.002026-10-112026-11-07

Average search position (lower is better)

8.0002026-10-25: 6.182026-10-26: 4.712026-10-27: 6.092026-10-28: 5.092026-10-29: 6.732026-10-30: 7.912026-10-31: 8.002026-11-01: 7.332026-11-02: 8.002026-11-03: 6.562026-11-04: 6.002026-11-05: 2.002026-11-06: 2.002026-11-07: 1.002026-10-112026-11-07
View google search performance daily data
Google Search performance · missing dates are unreported, never assumed zero
DateSearch clicksSearch impressionsCTR (%)Average search position (lower is better)
2026-10-2521118.186.18
2026-10-262728.574.71
2026-10-2701106.09
2026-10-2842218.185.09
2026-10-2901106.73
2026-10-3001107.91
2026-10-3101008
2026-11-010307.33
2026-11-020308
2026-11-030906.56
2026-11-040506
2026-11-050102
2026-11-060202
2026-11-070101

Period comparison unavailable: both periods need every reported date.

Website traffic (GA4)

Connected; no reported rows in this period. Last successful refresh: 2026-11-11. Timezone: America/Chicago. Recent four days excluded for reporting delay.

Daily active users

Sessions

Page views

Engagement rate (%)

Engagement seconds per session

View website traffic (ga4) daily data
Website traffic (GA4) · missing dates are unreported, never assumed zero
DateDaily active usersSessionsPage viewsEngagement rate (%)Engagement seconds per session

Period comparison unavailable: both periods need every reported date.

Google metrics methodology

A Search Console click leads from Google Search to the site; an impression is an eligible search-result appearance. CTR is clicks divided by impressions. Average position is the impression-weighted topmost site result position; a lower number is generally better. These are search metrics, not total traffic.

GA4 active users are distinct engaged users within each reported day. Daily users overlap and are never summed as period unique visitors. Sessions are visits; views include repeated page views. Engagement rate is engaged sessions divided by sessions. An engaged session lasts beyond the configured threshold, has a key event, or includes two or more page/screen views. Engagement duration measures foreground engagement; this dashboard divides seconds by sessions.

Consent, blocked scripts, attribution, timezone and reporting definitions make GSC clicks and GA4 users different. Missing days are unavailable. Period CTR and position are impression-weighted; engagement is session-weighted. Reports exclude recent four days; processing may take longer. The period ends relative to each source’s last successful refresh. Granular top-content metrics are deliberately omitted pending owner privacy review of low-volume disclosure. No raw queries or visitor records are published.

Reviewed Google aggregate snapshot

02 / Follow the connections

Content Galaxy

Article-body links only · arrows point to destinations

Each point is a published article. Select a point or table row to explore its neighborhood. Related articles, breadcrumbs, and global navigation are excluded.

8 of 8 articles shown

Learning Python #001: Functions, Variables, and My First CLI Tool · Python1A Hospital Is the Most Complicated Computer I've Ever Used · Ideas2AI Is Already in Healthcare. What Is It Actually Doing? · Healthcare3Can Clinical Guidelines Be Converted Into Code? The Challenges of Algorithmic Medicine · Healthcare4Hello, World. · Journal5Starting Over Without Starting From Zero · Field Notes6The Art of Reading Code: Inside Simpyll’s New Journal Experience · Engineering7Why Simpyll? A Name, a Philosophy, and the Beauty of Doing Less · Personal8

03 / Technical quality

Checks, not a ranking score.

Offline audit of rendered public pages
Critical 0Warning 0Informational 10
Findings by technical category. Zero means no findings detected by the implemented checks.
CategoryCriticalWarningInformationalBreakdown
Metadata003
Canonicals000
Sitemap & indexing000
Structured data000
Content structure000
Images000
Internal links007

Warnings include review opportunities and structural findings. Automated checks do not establish accessibility compliance, content quality, or Google ranking potential. Detailed remediation remains in local owner reports.

04 / The publishing curve

Writing adds up.

Cumulative publication dates of articles that are public today. This is not a historical inventory of the site.

2026-10: 8 articles2026-10
View content growth data
Monthly publications and recorded updates
MonthPublishedUpdatedCumulative
2026-10808

05 / Editorial rhythm

Publishing activity

2026 · UTC calendar dates

Publications and explicit revisions, deduplicated per article and date. Automated Notion syncs are not events. Future calendar dates are unmeasured.

Filled cells mark activity. The date list below provides the same data without relying on color or hover.

Explore all recorded activity (6 dates)

06 / Where the ideas live

Topic distribution

Author-defined categories
  • Engineering1 article
    1 of 8
  • Field Notes1 article
    1 of 8
  • Healthcare2 articles
    2 of 8
  • Ideas1 article
    1 of 8
  • Journal1 article
    1 of 8
  • Personal1 article
    1 of 8
  • Python1 article
    1 of 8

The notes behind the numbers

Open data. Clear limits.

From the actual build

The existing SEO validator reads prerendered pages. Published article metadata supplies titles, taxonomy, dates, and explicit revisions. The report date is the source commit date; this is a static snapshot, not live activity.

Connections with context

The galaxy counts unique directed links between different published articles inside article bodies. Navigation, related articles, previous/next links, breadcrumbs, project links, and footer links do not become contextual edges. Site-navigation orphans are separately identified in local reports using approximate crawl depth from the homepage.

History without invention

Only currently published content appears. Revision records may be incomplete, and withdrawals are not backfilled. Publication curves cannot show past visibility or deleted articles. No technical trend comparisons are shown until independently recorded baselines exist.

A deliberate boundary

The content snapshot contains only approved article fields and aggregate technical counts. Google reporting uses a separate allowlisted daily aggregate snapshot, explained in Search & audience. Evidence, remediation, configuration, and raw diagnostics stay in ignored local reports. No visitor tracking or Google credentials are needed to explore Pulse.