New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. The Permanent Struggle for Liberty (2019)(news.mit.edu ↗)
    discuss
  2. FoxSchema: Database schema diff and migration tool(github.com/tedious-code ↗)
    discuss
  3. We know what a world without work looks like(asteriskmag.substack.com ↗)
    discuss
  4. Dream-RSI: Recursive Self-Improvement Through Evolving Worlds(huggingface.co ↗)
    discuss
  5. TileDB Rebrands as Tile.ai(tile.ai ↗)
    discuss
  6. Apple Copland D11E4 booting in your Browser(pagetable.com ↗)
    discuss
  7. Combinators and the Story of Computation (2025)(wolframinstitute.org ↗)
    discuss
  8. Show HN: Zoom Meeting for Agent Sessions(sharednet.ai ↗)
    discuss
  9. The state of AI in 2026 [pdf](visualcapitalist.com ↗)
    discuss
  10. The mascots, design and visual history of Wikipedia(itsnicethat.com ↗)
    discuss
  11. Heather Cox Richardson(wikipedia.org ↗)
    1comments
  12. How and Why We Bought 4x DGX Sparks(alexellis.io ↗)
    discuss
  13. Show HN: Ctxwitch – Git tells you what changed; this tells you what it'll do(github.com/ctxwitch ↗)
    discuss
  14. The Frontier Act Is Congress' Best AI Regulation Bill Yet(thefai.org ↗)
    discuss
  15. Switched to Claude Code's open-source rival, stopped worrying about rate limits(xda-developers.com ↗)
    discuss
  16. Show HN: Ori, an agentic runtime for infrastructure that must ask before it acts(github.com/ori-platform ↗)
    discuss
  17. BBC Operations Dealt with 9/11 [correct URL](archive.org ↗)
    1comments
  18. Mojo 1.0 and the Open Road Ahead [video](youtube.com ↗)
    discuss
  19. Be the first human to review your own code(abhinavr.me ↗)
    discuss
  20. Reddit co-founder says tech industry has been 'tone deaf' in explaining AI(cnbc.com ↗)
    discuss
  21. An LLM from First Principles(twitter.com/ryanvogel ↗)
    discuss
  22. Arch-Based Omarchy 4.0.4 Makes Its Custom Linux Kernel the Default(linuxiac.com ↗)
    discuss
  23. Is There Alien Debris on the Moon? Some Scientists Plan to Find Out.(nytimes.com ↗)
    1comments
  24. How BBC Operations dealt with 9/11(bbc.co.uk ↗)
    3comments
  25. Why shared-database multi-tenancy isn't the compromise it looks like(medium.com/walexy85 ↗)
    discuss
  26. AI Agent Vercel Eve Web Interface = Amazing(medium.com/daniel-payne-keldan-systems ↗)
    discuss
  27. Replacing Pull Requests with Delta(zed.dev ↗)
    discuss
  28. Garda whistleblower unit members allege reforms undermined(rte.ie ↗)
    discuss
  29. Completing the banking stack: stablecoins, card issuing, multicurrency(column.com ↗)
    discuss
  30. SpartanX Solar lousy customer service
    discuss

AI writing patterns across 10,126 pages of real marketing copy

2 pointsby 1h agogetsitetell.com
1 comments
1h agoHN ↗

A bit of context before the post, I built SiteTell its a site scanner that scans for content that reads as AI generic. From this I've been able to gather data from over 10,000 pages and came to some interesting conclusions about the use of AI across websites. Google doesn't explicitly punish "AI writing" in its rankings, but it does punish generic, zero-value content that can be found in a hundred other places. I created a curated ruleset to catch these patterns, and so far, SiteTell has scanned 103 sites and 10,126 pages, flagging over 23,000 instances.

I collated the data, and it led to some counter-intuitive conclusions. 1. Structural habits give it away more than vocabulary

Everyone knows to delete the word "delve," but 58% of the items flagged so far aren't vocabulary—they are structural issues.

The Redundant Closing Paragraph (66% of sites): This is the most prevalent tell. LLMs love to write a summary conclusion that adds absolutely no new insight, merely repeating what the page already covered. Em-Dash Frequency & The Rule of Three (63% of sites): LLMs lean heavily on specific rhythmic crutches. (Obviously, some technical SaaS products use these structures naturally, so it's a general pattern rather than an isolated error). Paragraph Symmetry (10% of sites): A surprising tell, but once you see a page where every single paragraph is the exact same visual block length, you can't really unsee it.

2. Bigger sites score substantially worse

Sites with fewer than 200 pages typically score between 85-95/100. Once a site crosses the 200-page threshold, the average score drops to around 70.6. This forms part of the broader trend below but to be transparent there is a slight flaw with the analysis here. Most of my structural rules require a minimum of 100-150 words to run. A small landing page might not hit that threshold, saving it from structural penalties.

However, the broader trend is clear. It’s easy to hand-craft a 10-page site. But as a site scales, the owners inevitably turn to AI to churn out blog posts and resource pages, which introduces massive amounts of generic terminology.

So the question becomes how can you fix this?

If you don't want to use a tool, you can manually audit your site. This can most effectively be done with 3 checks:

Read your final paragraphs: Is it a meaningful conclusion, or just a regurgitation of the page above? AI loves to just repeat information in a closing paragraph. Conclusions should conclude and add insight, not just repeat.

Check for block symmetry: Are all your paragraphs the exact same length? Break them up.

The Competitor Test: Could a specific sentence sit on a competitor's website completely unchanged? If yes, it's generic, adds no unique value, and is less likely to rank. This, for me, is the most important of them all. If you're offering something unique, not found on competitors sites, then not only will it be more memorable it be less likely to read as generic content.

Fixing it at scale

Those manual checks work great for a homepage. Where it stops being viable is when you have 300 generated blog pages. Doing that by hand isn't realistic.

SiteTell crawls the whole domain, flags each instance with the specific rule that fired, and writes a replacement for it. You can export the whole thing as a CSV or JSON and feed it directly into an agent to fix your site in minutes.

I’d love for you to poke holes in the data, point out anything I've missed, or let me know what you think of the tool!