MOUSA·BATARSEHIndependent AEO review · Salt Security

Sec. 01 — Overview · for the Website Manager role

Found by people. Quoted by machines.

Salt is repositioning around agentic security and answer engines — but its pages give machines nothing to quote. 57 of 60 sampled pages carry no structured data. There's no FAQPage anywhere, even where the H2s are questions. llms.txt is a 404. And the sitemap submits 720 URLs that robots.txt disallows. Here's the answer layer I'd build in Webflow.

57 / 60
sampled pages with no JSON-LD
0
FAQPage blocks — even on question-form H2s
720
sitemap URLs robots.txt disallows
404
llms.txt
Coverage

The selling pages are silent

The homepage (Corporation) and blog posts (BlogPosting) carry schema. /platform, /demo-request, every use-case and comparison page don't.

Extractability

Q&A with no markup

/api-security-101 already asks and answers in H2s. Wrapped in FAQPage, it becomes something an answer engine can lift.

Signals

Mixed crawl instructions

2,929 sitemap URLs, 720 of them under disallowed paths; 32 noindex customer stubs; titles still say “API Security.”

Scope salt.security · 60 pages sampledMethod page source, sitemap, robots, llms.txtPlatform WebflowIndependent — not affiliated with Salt Security