Something wrong with SEO?
Hello everyone,
Almost a month ago I launched datanext.app (WebApp built with Wasp) but I'm experiencing serious problems with Google SEO.
I have uploaded the sitemap https://datanext.app/sitemap.xml at Google Search Console and 6 pages were successfully indexed.
But, if I search for the domain datanext.app on google.com, the site doesn't come up, only the social channels, posts, etc. come up.
And if I search https://datanext.app/btc-wallet-balance I see only one result but with wrong logo, title and description (foto attached).
In the Caddy file I have write:
Any idea why google don't consider me? Mauve something wrong in caddy configuration?
Thank you!
DATA NEXT - Your gateway for data
DATA NEXT is a powerful online scraping tool for lead generation, market research, product analysis, and more. Utilize our Google Maps Scraper, Amazon Product Finder, Meta Ad Library, and other advanced services to gain valuable insights and enhance your marketing strategies.
7 Replies
Hi @DanjelDurmo. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the information provided in the knowledge sources, I don't have enough specific details to fully diagnose your SEO issues with datanext.app. However, I can provide some general insights about SEO and Wasp that may be helpful:
1. Wasp and SEO: Wasp, being based on Vite, creates Single Page Applications (SPAs) by default. SPAs can sometimes face SEO challenges because they rely heavily on JavaScript for content rendering, which can be problematic for search engine crawlers. Discord thread (https://discord.com/channels/686873244791210014/1219684155072184440)
2. Meta Tags: One approach to improve SEO for Wasp apps without implementing full Server-Side Rendering (SSR) is to use meta tags. Wasp allows you to add Open Graph (OG) tags in the
head
property of the main.wasp
file. This can help with SEO and social media sharing. Discord thread (https://discord.com/channels/686873244791210014/1219684155072184440)
3. SSR Plans: While Wasp doesn't currently have built-in SSR support, it's on their roadmap. For now, they've been focusing on apps that are primarily behind authentication. Github Issue (https://github.com/wasp-lang/wasp/issues/911)
4. Alternative Approaches: Some developers have had success with SEO in Wasp apps without SSR. For example, the CoverLetterGPT app (https://coverlettergpt.xyz) ranks well in Google searches despite being a Wasp SPA. Discord thread (https://discord.com/channels/686873244791210014/1219684155072184440)
5. Hybrid Approach: Some developers use a hybrid approach, using a static site generator like Next.js or Astro for the landing page and public-facing content, while using Wasp for the main application. This can help with SEO for critical pages. Discord thread (https://discord.com/channels/686873244791210014/1219684155072184440)
Regarding your specific Caddy configuration, I don't have enough information in the provided knowledge sources to comment on its correctness or potential issues.
To improve your SEO, you might want to:
1. Ensure you're using appropriate meta tags in your Wasp app.
2. Double-check that your sitemap is correctly formatted and includes all relevant pages.
3. Verify that Google is able to crawl and index your JavaScript content correctly.
4. Consider using a tool like Google's Mobile-Friendly Test or Rich Results Test to see how Google views your pages.
If problems persist, you might want to consider the hybrid approach mentioned earlier or wait for Wasp's upcoming SEO improvements.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @DanjelDurmo, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@NEROX is our local SEO expert so he might have some good ideas.
As in general, check out this Github issue and links in it: https://github.com/wasp-lang/wasp/issues/1910 -> Wasp's SEO story is still sometihng we are working, but with react-helmet and some other tweaks you should be able to get relatively far.
GitHub
Add "SEO" section in our docs · Issue #1910 · wasp-lang/wasp
Explain the state of SEO in Wasp, explain how they can set the meta tags for the landing page right now via head, and say also what we are planning for the future. Related convo: https://discord.co...
Let's do some checks:
✅ Sitemap looks correct, don't touch it.
"...6 pages were successfully indexed. But, if I search for the domain datanext.app on google.com, the site doesn't come up..."Yep, SEO takes time, especially in new domains. I see that your main problem is with the meta-data of each page, I really strong recomend you use
react-helmet-async
to set each page because now as I see:
view-source:https://www.datanext.app/
view-source:https://www.datanext.app/blog
They are showing the same meta-data.
"...with wrong logo, title and description (foto attached)."Regarding the wrong logo, don't worry Google will update it at some point. The same thing happened to me, I published the domain with the default OpenSaaS logo and it took me about 3 (almost 4) weeks to change (Search Console finally updated the logo yesterday or today morning).:laughboi:
This is an example of how I'm handling the Meta-Tags of my main page of toograded.com
https://validator.schema.org/#url=http%3A%2F%2Ftoograded.com
And here a VERY complete example of what you can achieve: https://validator.schema.org/#url=http%3A%2F%2Ftoograded.com%2Fsgpa-calculator
@NEROX thank you very much for your time and for your comprehensive answer.
I'm going to use react-helmet-async as per your suggestion.
Anything I'm here!:wizardboi:
Thanks a lot @NEROX !