WeSearch

I tried "GEO" on my indie tool — it was just SEO (here's the GSC data)

·6 min read · 0 reactions · 0 comments · 2 views
I tried "GEO" on my indie tool — it was just SEO (here's the GSC data)

I read one contrarian source, opened Google Search Console, and found the real bottleneck wasn't markup — it was discovery. The 3 SEO fixes that mattered, and 2 pitfalls.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3915788) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Lucas Posted on Jun 14 I tried "GEO" on my indie tool — it was just SEO (here's the GSC data) #webdev #seo #nextjs #opensource Every other newsletter this year told me my SaaS needed GEO — Generative Engine Optimization. Write an llms.txt. Add "AI-only" schema. Chunk your content for the models. So before sinking a weekend into it, I read one contrarian source, opened Google Search Console for my tool, and looked at the actual numbers.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)