Compare
SiteRune vs Surfer, Clearscope, and 'AI SEO' writers
· Configuration notes, not a newsroom.
Those tools score keyword coverage in a draft. SiteRune scores whether an answer engine is allowed to fetch you and can ground an entity. NLP density is not GEO.
SUA draft is not robots.txt
Surfer will tell you to mention 'best crm' 14 times. SiteRune will tell you GPTBot is Disallow: /, llms.txt 404s, and there is no Organization JSON-LD. You can win the Surfer grade and stay invisible to ChatGPT browsing.
Use a writer. Then scan the origin.
Question-shaped H2s help both. After publish, run SiteRune so the template, headers, and bot policy match the essay. We will not sell you a content calendar or Reddit threads.
Capability table
| Capability | SiteRune | Surfer / Clearscope |
|---|---|---|
| Draft keyword coverage | No | Yes |
| Origin fetchability (robots, llms.txt) | Yes | No |
| Entity / FAQ / Article schema | Yes | Partial |
| Security headers / ship files | Yes | No |
FAQ
Does SiteRune replace surfer?
No. Use the comparison table. SiteRune is a hosted configuration brief with CMS dialect and ship files. It does not replace rank tracking, backlink graphs, lab Core Web Vitals, or a desktop site-wide crawl.
What does a SiteRune scan actually fetch?
HTML and headers from this vantage point, robots.txt, sitemap, llms.txt, security.txt, and a polite walk of same-origin interiors. No headless Chrome. No exploits.
Run it on a live URL
Same scan engine. Guest scans stay free.