I see that the Right AI Buzz Cut term on the web is really trending these days, everyone is searching it, and yes, the main reason is random social media reels going viral, especially in the last few months as influencers keep trying them. Google Trends also evidenced it with an arrow_upward of >5,000% vs. the preceding 1 year. As a marketer and an SEO geek, I was fascinated by how the logic works.
Now when I searched Google, the first site is this one:
Now, as the purpose of my post is for those people who are searching to know how this site works, at first this site is built with the help of an AI bot, maybe Claude or GPT. At first glance, being in this field, I see the gradients and the colorings and it 100% smells of AI. No issue and no harm in it, it’s part of our life, so it’s confirmed that it’s a post AI era site in terms of writing the code, right!
What is the framework then?
Nuxt/Vue! The site is built on NUXT. As you go through the source code you see it contains multiple data-nuxt-data, __NUXT_DATA__, data-ssr="true", Pinia state, and Vue scoped data-v-* attributes, which are direct Nuxt/Vue fingerprints.
The source contains all of the major Nuxt/Vue fingerprints:
id="__NUXT_DATA__"data-nuxt-data="nuxt-app"data-ssr="true"/_nuxt/...assetsdata-nuxt-img- Vue scoped component attributes such as
data-v-879a768c - Pinia state embedded in the SSR payload
Now it doesn’t mean all sites that are built to serve the purpose of Right AI Buzz Cut shall follow Nuxt.
No, I shared it because I found it first on Google. Although NUXT is very popular among the AI tools site, you would have seen so many AI video generator, AI audio or similar other tools using NUXT.
If you see the second site is the overall AI tools site, Pixelbin, and Pixelbin is using React, so there is no limit on using Vue or React or going with the mighty Python.
So the framework and UI thing is simple here, go as per your expertise or ease!
The main concern is, is it using real time AI?
Instant answer for the use of real time AI, NO. See the image, I uploaded my LinkedIn photo. As I am male, instead of using any Grok image or GPT or Gemini API for images, it just randomly sent pre-built designs that were for either male or female, not detecting my gender in real time.
Like, I know the Buzz Cut search is mostly coming from the F gender side, but in order to confirm I had to use my own picture. Whereas, and I will add the image, Pixelbin is using Nano Banana, it took time to process and it applied the cut as per my search query idea.
Now I am not here to prove this exact site is using an API or not, neither is it the agenda. It’s the research we are doing and understanding, to build a site that you can create to enjoy the search volume and ranking on the keyword of #RightHairBuzzCut trend, and who knows for how long it will last.
Now two answers
I mean Pixelbin is burning the $ here, but the results are 100% up to the par as it is printing Nano Banana.
So with regard to the answer of using AI, using it is better in terms of results and good if you are going with a paid subscription model. RightHair also has an API connection, but at what level of burning of API it depends, like Nano Banana is expensive to use, right, each processing costs the amount.
So the logic is, offer 1 or 3 trials for free served via ads, and as the rate limit hits, ask for $10 for 50 generations, a model based concept.
What I found in their source
The interesting bit is sitting right there in their public Nuxt runtime configuration:
apiBase: "https://api.righthair.ai/api"
That same API hostname also shows up in the list of resources the site is contacting, so it is not just a leftover line in a config file.
Then I went looking for the realtime stuff, WebSocket, wss://, EventSource, socket.io, SSE, and none of it is there in the HTML I pulled. There is a wsUrl field but it is empty, and anyway that one belongs to Nuxt Content, so it tells you nothing about how they are generating images.
Their own marketing says results show up in under roughly 15 seconds, which lines up with what I saw.
If you go pre-built
If you go pre-built, feeding it is a must in order to fix it, like I am even doing QA for free for that first site, which is not even affiliated to me, neither am I their SEO or developer.
For pre-built sites remember it’s difficult and the quality is compromised, as each head, face or shape is different. With regard to gender, what you can do is:
- Ask for the gender upfront, and it would be narrowed down.
- Do some data entry based on popular searches, dividing the backend JavaScript by gender already.
- Keep at least 10 to 15 images per popular search for each gender.
- Then use a Vue library, or a connection of a Python module or pip, to provide bit better results.
