u/dr-dimitru

Hi all! For the past two years I’m running a B2B SaaS that helps websites improve SEO, grow organic traffic, and get discovered in AI chats (SEO/AEO/GEO).

Disclosure: this is feedback request only. No links, no brand names, no promo.

B2B difficult to scale with long sales cycles, onboarding, and manual configuration and integrations. It funded a team and some savings. Now I want to make it self-serve for a broader public. Also automating most of the things we were doing manually for the clients.

What we wanted to solve is integration in a few clicks. That forced the service to become a proxy in front of client’s sites, which meant issuing TLS certs, managing DNS, and operating as a CDN. The SEO tool became edge infrastructure at that very moment.

What it’s designed to do:
- Fast discovery by crawlers and AI agents: Serve fast, clean HTML to AI agents and crawlers so new sites are readable by LLMs from day one
- Add meta tags on the fly: Fill missing metadata in responses to bots, crawlers, and agents
- Speed up discovery in search engines: Automatic IndexNow submission of new and changed URLs
- AI agents analytics and insights: Cookie-free, JS-free analytics for crawlers, bots, and AI-agents.

Questions that I need help with:

1. Is “readable by AI + indexed fast” a real pain for new projects, or a nice-to-have?
2. Would you put a proxy/CDN in front of your site for this?
3. What would you expect from a free tier?

Hi all! During the last two years I’m running a B2B SaaS that helps websites with SEO, increase organic traffic, and get discovered by AI chats (SEO/AEO/GEO).

Disclosure: this is feedback request only. No links, no brand names, no promo.

B2B works well, but it pains to scale, has long sales cycles, onboarding, manual configuration and integration. It funded a team and brought us some savings. Now I want to make it self-serve SaaS for a broader public.

Our main shift from expensive manual integration to integration in a few clicks. That changed service a lot and it has to sit as a proxy in front of a website, which means issuing TLS certs, managing DNS, and operating as a CDN. The SEO tool became edge infrastructure at that moment.

What it does:
- Fast discovery by crawlers and AI agents: Serve fast, clean HTML to AI agents and crawlers so new sites are readable by LLMs from day one

- Add meta tags on the fly: Fill missing metadata in responses to bots, crawlers, and agents

- Speed up discovery in search engines: Automatic IndexNow submission of new and changed URLs

- AI agents analytics and insights: Cookie-free, JS-free visitor analytics for crawlers, bots, and AI-agents.

Questions:

1. Is “readable by AI + indexed fast” a real pain for new projects, or a nice-to-have?
2. Would you put a proxy/CDN in front of your site for this?
3. What would you expect from a free tier?

View Poll

Hi all! For the past two years I’m running a B2B SaaS that helps websites improve SEO, grow organic traffic, and get discovered in AI chats (SEO/AEO/GEO).

Disclosure: this is feedback request only. No links, no brand names, no promo.

B2B worked, but it meant long sales cycles, onboarding, and manual configuration and integration. It funded a team and some savings. Now I want to make it self-serve for a broader public.

First goal: integration in a few clicks. That forced the service to sit as a proxy in front of client sites, which means issuing TLS certs, managing DNS, and operating as a CDN. The SEO tool became edge infrastructure at that moment.

What it’s designed to do (pre-launch, nothing production-proven yet):
- Fast discovery by crawlers and AI agents: Serve fast, clean HTML to AI agents and crawlers so new sites are readable by LLMs from day one

- Add meta tags on the fly: Fill missing metadata in responses to bots, crawlers, and agents

- Speed up discovery in search engines: Automatic IndexNow submission of new and changed URLs

- AI agents analytics and insights: Cookie-free, JS-free visitor analytics for crawlers, bots, and AI-agents.

Questions:

1. Is “readable by AI + indexed fast” a real pain for new projects, or a nice-to-have?
2. Would you put a proxy/CDN in front of your site for this?
3. What would you expect from a free tier?

I’m working on “SEO-focused alternative to Cloudflare”. Please share your thoughts, I have two questions now:

1. What would make you try a new paid CDN service while you have free and well established Cloudflare?
2. Have you ever wanted to move off Cloudflare? Why? And have you moved or stayed at the end?

I don’t need you to sign up (it’s still in development) just want to know what do you think

I’m on x20 plan. Last and current weeks I burn through limits just in 3-4 days, while I wasn’t able to get to 100% ever before. Even dropping down to Sonnet this week to make it last longer, but already at 50% less than 24 hours after my last weekly cycle.

Same setup, same project, same skills and subagents, same kind of tasks.

Do you feel and observe the same? What do you do about it? Any tips and tricks to last longer?

If your development environment has project scoped skills and subagents settings. It doesn’t mean it will be utilized on every run.

When needed add at the end of the prompt:

Use available skills and dedicate work to subagents as needed.

Am I only one feeling pressure in pushing more things done when weekly limits are about to revolve and I haven’t reached 100%?

Even if I’m at 98% and have a few hours left before reset I’m trying to squeeze as much as I can, opening parallel session, getting to tasks that were waiting for a while, etc. getting rushed and overwhelmed.

In other cases when I reached my limits earlier when expected I let myself rest until weekly reset, feeling like that were productive sessions and a week.

How do you feel about limits? What do you do after reaching them? And how do you feel when not reaching 100% before week revolves?

And yes, my workflows are mostly about coding.

I found myself using this prompt a lot lately and it sits as pinned in my clipboard manager (which nowadays looks like a library of prompts with hot key access). It saves tokens, limits and my time.

Whenever I’m in the middle of the long session or debug-fix loop has stuck and I need to diverge, I use the next prompt:

“Write short and concise prompt for the next phase as per current plan in terse and to the point manner with no fluff, so I can resume in a new session.”

Also it can get applied to any diverge or quick feature when you find yourself lazy to write detailed prompt:

“Write short and concise prompt for the {{your-task}} in terse and to the point manner with no fluff, so I can start in a new session.”

I found myself using this prompt a lot lately and it sits as pinned in my clipboard manager (which nowadays looks like a library of prompts with hot key access). It saves tokens, limits and my time.

Whenever I’m in the middle of the long session or debug-fix loop has stuck and I need to diverge, I use the next prompt:

“Write short and concise prompt for the next phase as per current plan in terse and to the point manner with no fluff, so I can resume in a new session.”

Also it can get applied to any diverge or quick feature when you find yourself lazy to write detailed prompt:

“Write short and concise prompt for the {{your-task}} in terse and to the point manner with no fluff, so I can start in a new session.”