Published articles
8Currently public canonical articles.
Simpyll / Built in the open
An interactive look at how Simpyll grows, connects, and performs.
01 / The current picture
Currently public canonical articles.
Public pages in the rendered build.
Unique directed article-to-article links in body content.
Articles referenced by another article’s body.
No inbound article-body links; still discoverable through site navigation.
Automated findings, including editorial review opportunities.
Validated Google reporting data. Last successful refresh: 2026-11-11. Timezone: America/Los_Angeles. Recent four days excluded for reporting delay.
| Date | Search clicks | Search impressions | CTR (%) | Average search position (lower is better) |
|---|---|---|---|---|
| 2026-10-25 | 2 | 11 | 18.18 | 6.18 |
| 2026-10-26 | 2 | 7 | 28.57 | 4.71 |
| 2026-10-27 | 0 | 11 | 0 | 6.09 |
| 2026-10-28 | 4 | 22 | 18.18 | 5.09 |
| 2026-10-29 | 0 | 11 | 0 | 6.73 |
| 2026-10-30 | 0 | 11 | 0 | 7.91 |
| 2026-10-31 | 0 | 10 | 0 | 8 |
| 2026-11-01 | 0 | 3 | 0 | 7.33 |
| 2026-11-02 | 0 | 3 | 0 | 8 |
| 2026-11-03 | 0 | 9 | 0 | 6.56 |
| 2026-11-04 | 0 | 5 | 0 | 6 |
| 2026-11-05 | 0 | 1 | 0 | 2 |
| 2026-11-06 | 0 | 2 | 0 | 2 |
| 2026-11-07 | 0 | 1 | 0 | 1 |
Period comparison unavailable: both periods need every reported date.
Connected; no reported rows in this period. Last successful refresh: 2026-11-11. Timezone: America/Chicago. Recent four days excluded for reporting delay.
| Date | Daily active users | Sessions | Page views | Engagement rate (%) | Engagement seconds per session |
|---|
Period comparison unavailable: both periods need every reported date.
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 snapshot02 / Follow the connections
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
| Article | Category | Inbound | Outbound | Explore |
|---|---|---|---|---|
| Learning Python #001: Functions, Variables, and My First CLI Tool | Python | 0 | 0 | |
| A Hospital Is the Most Complicated Computer I've Ever Used | Ideas | 0 | 0 | |
| AI Is Already in Healthcare. What Is It Actually Doing? | Healthcare | 0 | 0 | |
| Can Clinical Guidelines Be Converted Into Code? The Challenges of Algorithmic Medicine | Healthcare | 0 | 0 | |
| Hello, World. | Journal | 0 | 0 | |
| Starting Over Without Starting From Zero | Field Notes | 0 | 0 | |
| The Art of Reading Code: Inside Simpyll’s New Journal Experience | Engineering | 0 | 0 | |
| Why Simpyll? A Name, a Philosophy, and the Beauty of Doing Less | Personal | 0 | 0 |
03 / Technical quality
| Category | Critical | Warning | Informational | Breakdown |
|---|---|---|---|---|
| Metadata | 0 | 0 | 3 | |
| Canonicals | 0 | 0 | 0 | |
| Sitemap & indexing | 0 | 0 | 0 | |
| Structured data | 0 | 0 | 0 | |
| Content structure | 0 | 0 | 0 | |
| Images | 0 | 0 | 0 | |
| Internal links | 0 | 0 | 7 |
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
Cumulative publication dates of articles that are public today. This is not a historical inventory of the site.
| Month | Published | Updated | Cumulative |
|---|---|---|---|
| 2026-10 | 8 | 0 | 8 |
05 / Editorial rhythm
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.
Published · Hello, World.
06 / Where the ideas live
The notes behind the numbers
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.
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.
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.
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.