Just Ask by SEORCE

Hi Product Hunt 👋 I'm Sudhirr, founder of SEORCE. Over the last year we've been building an SEO + GEO platform, and one thing kept bothering us: every SEO tool expects you to open a dashboard before you can get an answer. People ask Claude and build skills, talk to ChatGPT - all without your brand or website context. Without context all advice is just generic content. So we wondered - what if SEO worked more like ChatGPT / Claude? That's Just Ask. Now you can message your SEO / AIO / GEO platform on WhatsApp and ask things like: • Which pages are losing traffic? • How do we compare in ChatGPT? • What should I fix first? • Show me pages with high impressions but low CTR. SEORCE reads your live SEO, Analytics, Backlinks, Technical Audit and AI Visibility data and replies in seconds - then tells you what to fix, not just what's wrong. The dashboard is still there and becoming powerful by the day. But a lot of questions don't need one anymore. Try it free: sign up at seorce.com, link your WhatsApp, then text "Hi" to +1 (363) 200-3169. We're excited (and slightly nervous!) to hear what you think. Every comment, suggestion and criticism will help shape where we take this next. What would you ask it first? I'll be here all day. Thanks for checking us out 🙏 Show more

Moving SEO into chat instead of a dashboard is an interesting shift. Curious how you see the split long-term - does WhatsApp become the main place people work, or more of a quick layer on top of the dashboard? Congrats on the launch!

How does the AutoFix SLM actually decide what to change and what to leave alone, especially for sites where on-page edits could affect existing rankings?

the WhatsApp interface is a genuinely nice idea, way lower friction than opening a dashboard. security question though - what's the pairing step between a WhatsApp number and a brand's live SEO/analytics data? WhatsApp numbers get recycled and SIM-swapped, so I'd want to know it's more than "whoever texts from this number gets the data" before connecting anything real to it

@galdayan Great question. We don't rely solely on the WhatsApp number. Every WhatsApp number is linked to an authenticated SEORCE account, but beyond that we also have session verification in place. We verify the session before serving account data, so simply having access to the phone number isn't sufficient to establish a trusted session. If a user changes their number, loses access to their device, wants to switch numbers, they can update or revoke the linked WhatsApp number directly from their SEORCE account. As we roll out more enterprise features, we'll continue strengthening this with additional controls such as PIN-based verification for sensitive operations and admin policies. The goal is to keep the experience frictionless for everyday use while providing the security enterprises expect.

This feels like such a natural next step for SEO tools. Most of the time, you don’t want another dashboard. You just want a clear answer like “what dropped?”, “what should I fix first?”, or “where are we missing visibility?” Bringing SEO + GEO + AI visibility data into WhatsApp makes the whole process feel much faster and easier. Excited to see Just Ask by SEORCE launch today. This could save teams a lot of time and make seo decisions way more actionable.

@i_love_my_india4 In a few geographies, businesses use Whatsapp as the primary communication platform, it was a natural extension for our AI Agent to be available and be closer to our users.

@jared_salois Many thanks for the appreciation and your conviction.

Getting a straight answer without opening a single dashboard sounds like a small mercy. Dashboards always leave me feeling like I have been handed homework.

@amine_aziz_alaoui Dashboards have been replaced by AI and conversations. ChatGPT, Claude made this interface handy and usual. We decided to bring this to the communication platform that is used by businesses in general. Thanks for your appreciation.

@senamelekavm8u Great question... AutoFix SLM doesn’t just randomly change pages. It first looks at the crawl data, page context, technical issues, and ranking impact. Then it focuses on safe, clear fixes like schema, meta tags, alt text, headings, and canonicals. For anything that could affect existing rankings in a bigger way, it doesn’t blindly push changes. It prioritizes the issue, shows the context, and keeps the fix controlled so teams can act with confidence. So basically fix what is clearly broken, avoid unnecessary changes, and protect what is already working.

@galdayan Tricky one. That's a fair concern, and we've designed it so it's not simply "whoever messages from this number gets the data." Your WhatsApp number is linked to your SEORCE account and can only be managed from within your authenticated account on https://seorce.com. If you change your phone number, switch devices, or want to use a different WhatsApp number, you simply log in and update it under Account Settings. In other words, the pairing is established through your authenticated SEORCE account - not by WhatsApp alone. The WhatsApp number is just the communication channel, while the account remains the source of authentication and access control.

@sudhirr_vashist makes sense for account-level access. the piece I'm still curious about is the whatsapp side specifically - if someone's phone gets compromised or the number gets sim-swapped before you notice and update it in settings, does seorce have any extra check in the chat itself (like a pin) before it hands over live data, or is it purely relying on you catching the swap first?

The "every tool makes you open a dashboard first" framing is the right wedge — I stopped opening most of mine for that exact reason. Where I get stuck is the GEO/AI-visibility half, and it's a measurement question, not an interface one. SEO you can ground: there's a SERP you can scrape and a rank stable enough to report. Being surfaced inside a Claude or ChatGPT answer is zero-click, personalized, non-deterministic, and there's no log you own — so when Just Ask tells me my AI visibility moved, what's underneath that number? Are you running a fixed prompt set against the models yourself and measuring mention frequency, or is there a signal I'm not seeing? Asking because a chat interface is only as trustworthy as the ground truth it reads back, and GEO is the layer where ground truth is hardest to come by.

@narek_keshishyan That's exactly the right question, and it's one we've spent a lot of time thinking about. We don't claim to know what every end user sees - no one does. Responses are personalized, non-deterministic; the AI providers don't expose impression logs or analytics. Our approach is to make the measurement consistent rather than absolute. We run a standardized prompt set across supported models, with controlled execution parameters, and track how often a brand, product, or URL appears, who gets cited instead, the position within the response, and how that changes over time. That's only one part of the picture, though. We also have access to a large corpus of ~280 million real user prompts, which gives us additional insight into how people actually search for brands, products, questions and services, not just how we think they might. That helps us build much more representative prompt sets and understand intent distribution across categories. We then marry that AI visibility data with traditional search signals. Search still reflects real user demand, topical authority, content relevance, so combining AI responses with search performance gives us a much stronger sanity check than relying on AI prompting alone. We believe GEO and SEO are converging, not diverging, and measuring them together produces a far more reliable picture. We also expose the underlying evidence the prompts, responses, citations, referenced URLs so users can inspect why the score changed instead of treating it as a black box. We think that's the most honest way to approach GEO today. Until the model providers expose first-party visibility data (if they ever do), the best approach is to combine consistent benchmarking, real-world query data, AI response analysis, search intelligence into a transparent measurement framework, rather than pretending there's a single "true" visibility number. Show more

@sudhirr_vashist  good to hear PIN-based verification is on the roadmap, that's the piece that would make me actually trust it for anything money-related. one more thing while I have you: is the account-revoke action itself gated behind anything (email confirm, existing session), or could someone who's already compromised the phone also revoke and re-link a new number before the real owner notices?

@senamelekavm8u Thanks for your question, All the changes suggested by the Autofix SLM go through an approval, nothing gets posted without your intervention or approvals. We work with some really large teams and websites and this comes about as a common concern. The good thing is that what took weeks now takes minutes to fix or optimise, with AI built in that learns your website and brand. Every fix compounds the learning.

@jared_salois  Thank you! We see WhatsApp as the conversational interface, not the replacement for the dashboard. The dashboard will remain the place for deeper analysis, visualisations, historical trends, configuration and taking actions. WhatsApp is designed for speed-asking questions, getting instant insights, alerts, summaries and recommendations without having to log in every time. Over time, we expect users to spend a lot more of their day-to-day interactions in chat, while the dashboard becomes the workspace for deeper investigation and execution. The two are designed to complement each other rather than compete.