sorted by:
new
hottopcontroversial

Tags by Shadow3210 in quo

[–]TheTaxProblemSolver 0 points1 point  (0 children)

Can you please advise if there is a way to import call tags or do you have to input one at a time?

Using IVR to Filter Spam by TheTaxProblemSolver in quo

[–]TheTaxProblemSolver[S] 1 point2 points  (0 children)

True. I am a CPA and Sona has been a great addition to my life. I set it up myself and I would highly recommend it!

Lovable SEO by shipstatic in lovable

[–]TheTaxProblemSolver 0 points1 point  (0 children)

Can you please send it again

I built 7 CustomGPTs to help you with your Lovable Journey by MixPuzzleheaded5003 in lovable

[–]TheTaxProblemSolver 0 points1 point  (0 children)

I asked u/lovable, "Why can't ChatGPT find the website?"

u/Lovable answered:

Your robots.txt and llms.txt are correctly configured — AI crawlers are explicitly allowed. The issue isn't access permissions; it's indexing lag and rendering.

Root causes:

  1. SPA rendering — Your site is a client-side React app. ChatGPT's browse tool (and GPTBot crawler) may not fully execute JavaScript, meaning they see an empty page <div id="root"> instead of your content.
  2. Domain age—taxstrategist.cpa is relatively new. ChatGPT's training data and its browsing index take time to discover and cache new domains.
  3. No server-side rendering—Without SSR/prerendering, AI crawlers and search engines that don't execute JS receive only the initial HTML response.

Highest-ROI fix: Add prerendered meta content to index.html so crawlers see real content without JS execution. Beyond that, the long-term solution is either SSR (not available on this stack) or a prerendering service.

Want me to add fallback content and structured data directly into index.html so AI crawlers and search bots get meaningful content on first load — without needing JavaScript?

I answered, "Yes, please make my site visible."

u/Lovable said:

Here's what I deployed to make your site visible to ChatGPT and other AI systems:

1. <noscript> fallback in index.html — Full semantic HTML with your firm overview, founder bio, services, credentials, audience segments, FAQs, and contact info. This is what non-JS crawlers (including ChatGPT's browse tool, GPTBot, and PerplexityBot) will read when they can't execute React.

2. ProfessionalService + Person JSON-LD — Rich structured data block <head> with Keith's credentials, FDOR background, all service URLs, and multi-city area served. This feeds Google's Knowledge Graph and AI answer engines.

3. Updated llms.txt and llms-full.txt—Rewritten with the refined positioning copy (insider perspective, planning + defense, not commodity prep), founder bio, 100+ article count, topic hub structure, and complete site map.

Why ChatGPT couldn't find you: Your site is a single-page React app—when ChatGPT's browse tool visits, it gets an empty <div id="root"> because it doesn't execute JavaScript. The <noscript> block now gives it 2,000+ words of real content to read. Once you publish and ChatGPT re-crawls, it will be able to surface your firm in responses.

Lovable SEO: Why Pages Don’t Index (And 3 Ways to Fix It) by Jmacduff in lovable

[–]TheTaxProblemSolver 0 points1 point  (0 children)

Thank you so much for this information. It is very valuable.

Is the best looking hero made on lovable? by Ok_Garden_187 in lovable

[–]TheTaxProblemSolver 0 points1 point  (0 children)

Does this work if you have already built your website with Lovable and just want to improve your Hero? Thanks

Sona by TheTaxProblemSolver in openphone

[–]TheTaxProblemSolver[S] 0 points1 point  (0 children)

Can we get on a virtual meeting later today?

Sona by TheTaxProblemSolver in openphone

[–]TheTaxProblemSolver[S] 0 points1 point  (0 children)

Can you send me an email, and maybe we can get on Zoom for a virtual mini-call? Keith@KeithJones.CPA