Compare
SiteRune vs BuiltWith and Wappalyzer
· Configuration notes, not a newsroom.
Those extensions list technologies. SiteRune fingerprints a CMS to write a dialect — then scores the origin. A logo cloud is not a playbook.
BUDetection vs a brief
BuiltWith and Wappalyzer are good at 'this page loaded GTM and Cloudflare'. SiteRune uses similar signals (and more headers) to pick WordPress vs Shopify vs Next, then changes the header fix and the bootcamp item. Unknown stack stays generic. We will not invent a CMS to look smart.
What they will not attach
Ship files, interior noindex, GPTBot policy, competitor homepage compare. Use Wappalyzer in the browser if you like the icons. Use SiteRune when you need the week of work in order.
Capability table
| Capability | SiteRune | BuiltWith / Wappalyzer |
|---|---|---|
| Technology logo cloud | Fingerprint for dialect | Yes |
| Scored origin (SEO/security/perf/AEO) | Yes | No |
| Ship files in the CMS dialect | Yes | No |
| AI-bot / llms.txt chapter | Yes | No |
FAQ
Does SiteRune replace builtwith?
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.