CMS
Weebly Website Audit
Weebly audit: Square's hosted builder, same limits
· Configuration notes, not a newsroom.
Weebly fingerprints from their runtime strings. SiteRune will not pretend there is an .htaccess. Proxy for headers; publish real text.
WEWhat SiteRune checks on this stack
- CMS / framework fingerprint from HTML, headers, cookies, and generator tags — fingerprint-based, not a plugin inventory
- Titles, meta descriptions, canonicals, H1, and robots on the homepage and walked interiors
- Security headers a crawler can see: HTTPS, HSTS, CSP, framing, nosniff, Referrer-Policy, Permissions-Policy
- HTML TTFB, compression, and Cache-Control on the document — not a Lighthouse filmstrip
- AI-bot robots policy, llms.txt, and Organization / FAQ / Article JSON-LD
Common problems
- Marketing homepage looks finished; interior templates ship empty titles or leftover noindex
- Hosted CMS cannot set HSTS/CSP, so the brief tells you to put a proxy in front instead of inventing an admin UI
- A security plugin's 'block AI' preset Disallows GPTBot on a site that wanted citations
- Session cookies or no-store on every anonymous GET, so the CDN never caches HTML
Hosted builder rules apply
Missing security headers → CDN in front. Thin HTML → put words in the page, not only in an image. Robots and llms.txt if the host lets you upload them; otherwise a reverse proxy that can serve files.
What we will not do
We will not recommend migrating to WordPress as a SiteRune finding. If you stay on Weebly, the brief is the configuration you can still change. If you cannot change it, the finding stays until a proxy does.
FAQ
How do you know this is my stack?
Fingerprints in HTML, headers, cookies, and generator tags. Confidence is a score, not a certificate. Unknown stacks stay generic — we will not invent a CMS.
Do I need an account?
Three guest scans, no card. Create a free account when you want history and more interiors.
Run it on a live URL
Same scan engine. Guest scans stay free.