Website Recycling

Source-of-truth pitch

Why we tell you the truth · even when it doesn't sell.

Most AI-visibility shops will quote you for any package on their menu. We won't. If your site's real problem is somewhere we can't reach · the host blocks crawlers, the platform strips schema, the domain itself is the issue · we'll say so out loud. We'd rather lose your $2,500 today than take it and fail to fix you.

The M&M shell · plain English

Think of your website as a candy with three layers · the shell, the coating, the inside. When an AI engine (ChatGPT, Claude, Perplexity, etc) tries to read your site, it has to get past all three before it can quote you. We can rebuild the inside and the coating · but if the shell (your hosting platform, your CDN's bot rules) is locked, the AI engine never reaches the candy.

  • Shell · the hosting layer. WP Engine, GoDaddy shared, Wix, Squarespace, Cloudflare Bot Fight Mode. The bouncer at the door · sometimes it lets AI bots in, sometimes it doesn't. We don't control it.
  • Coating · the platform layer. WordPress, Webflow, Shopify · the software that builds the page. Some platforms strip structured-data tags or force JavaScript that crawlers never run. We can route around it on most platforms · not all.
  • Inside · your content and structured data. The schema.org JSON-LD tags, the llms.txt file, the robots.txt allowlist. This is where we live. We rebuild this layer pixel-for-pixel so AI engines can read your business.

If the shell or coating is the real problem on your site, we'll say so during the free scan · before you pay anything. Fixing the inside on a blocked shell doesn't move the needle.

The live bot-fetch test we run

During your free scan we don't just look at your HTML · we actually pretend to be each of the major AI crawlers (ClaudeBot, GPTBot, PerplexityBot) and re-fetch your site with their User-Agent string. If your server returns a different result, we see it. If your CDN blocks them, we see it. This is what shows up on your scan page ·

$ curl -A "ClaudeBot/1.0" https://yoursite.com

HTTP 200 · 12,453 bytes · ok

$ curl -A "GPTBot/1.0" https://yoursite.com

HTTP 200 · 12,453 bytes · ok

$ curl -A "PerplexityBot/1.0" https://yoursite.com

HTTP 403 · 287 bytes · blocked by host

When the third line says "blocked" · the schema fix on the inside layer won't help. That's a host-level (shell) problem · we'll show it on your scan report and tell you what to do about it.

When a competitor would serve you better

We are not the only AI-visibility shop on the market. If you're shopping around, here's what we know about the alternatives · honestly ·

  • GEORaiser · audit-only product. They sell a one-time audit for around $999 plus an ongoing subscription that hovers near $79/month for monitoring (pricing source · georaiser.com/pricing). If you have an in-house developer who can act on a report, they're a fine option. We can quote that same scope honestly · we just don't recommend it unless you have someone to implement the fixes.
  • Profound · enterprise observability. They monitor AI citations across engines · pricing is sales-led and lands well into five figures per year. Right tool if you're a brand with a budget for analytics dashboards. Wrong tool if you're a 4-person business that just needs to be visible.
  • DIY · the honest free option. If you're technical, you can add schema.org tags, write an llms.txt, update your robots.txt, and ship it yourself. We'll send you the free scan report that tells you exactly which fixes apply. The whole point of the scan is you don't need us to do the implementation · only if you want to.

We'd rather lose your business to GEORaiser today than take your money and fail to fix you.

Run the free scan first. It tells you which of the three layers (shell, coating, inside) is the real problem on your site · before any money changes hands. If we can fix it, we'll quote you. If we can't, we'll tell you who can.