No. Six of the forty faymas pages we fetched on 26 October 2026 put their <title>, meta description and canonical link outside the head — buried in the body, hundreds of kilobytes after </head> closes. The three faymas.in prompt pages we tested place their title at byte 437,957 to 446,807 of a 544–556 KB document, which is roughly 80% of the way through. On faymas.net the same thing happens on /prompts, /pricing and /ai-image-generator. And on faymas.net it is not even stable: we fetched /prompts six times and got two different documents, one with the title at byte 3,923 inside the head and one with it at byte 315,599 in the body.
This guide analyses published prompt text. No generation tests were run.
What we measured
Forty page URLs, taken from each site's own navigation and internal links: twelve from faymas.in, twelve from faymas.net, twelve from faymas-in.com, and four from faymas.com.in — four is all that domain's own links expose. Sixty-five GETs in total on 26 October 2026, following redirects, no JavaScript, one Chrome user agent except where stated.
For each saved response we recorded the byte offset of five things: the opening <head>, the closing </head>, the <title>, the meta name="description", the link rel="canonical" and the og:image. Then we asked one question per tag: does it appear before </head> or after it? That is the whole method. Every number on this page comes out of those forty saved documents.
Six pages put their own title in the body
| Page | </head> at | <title> at | % into document | Document size |
|---|---|---|---|---|
faymas.in/prompt/icy-blue-panel-3b1bed0f | 5,427 | 446,807 | 80.4% | 555,726 B |
faymas.in/prompt/mahindra-suv-7xo-14844328 | 5,427 | 438,266 | 80.2% | 546,742 B |
faymas.in/prompt/tv-prompt-36a6c29e | 5,427 | 437,957 | 80.4% | 544,629 B |
faymas.net/prompts | 4,009 | 315,599 | 33.1% | 952,076 B |
faymas.net/pricing | 4,046 | 59,308 | 37.7% | 157,507 B |
faymas.net/ai-image-generator | 4,076 | 32,180 | 24.5% | 131,370 B |
Three of twelve on each of the two Next.js sites. Zero on the two WordPress sites. On all six, the meta description and the canonical link are out there in the body too — the page's entire self-description travels as one late-arriving block.
The thirty-four pages that do it conventionally are not subtle about the contrast. Their titles sit between byte 242 and byte 5,917. faymas-in.com's four article pages all put <title> at byte 242. There is no middle ground anywhere in the sample: either a tag is in the first six kilobytes or it is past the thirty-thousandth byte.
The size of the gap matters. A prompt page on faymas.in is 555,726 bytes and opens </head> at 5,427. So the head is 1% of the document and the identity is 80% of the way down it. Anything that reads the head, stops at </head>, or truncates a response finds a page with no name.
The same URL can hand you two different documents
Our first hypothesis was bot detection — the obvious explanation for a title that moves. It is wrong, and the test that killed it is worth reporting.
We fetched faymas.net/prompts six times within about four minutes. Four responses were 952,076 bytes with the title at 315,599, in the body. Two were 951,746 bytes with the title at 3,923, inside a head that closes at 5,460. Both variants appeared under a Chrome user agent, and both appeared under a Googlebot user agent: one Googlebot fetch got the body version, another Googlebot fetch got the head version. We fetched faymas.net/pricing five times. Four put the title at 59,308 in the body; one put it at 3,960 inside the head.
So faymas.net is not deciding who you are. It is racing itself. Whichever finishes first — the metadata or the shell — wins, and the loser gets appended wherever it lands. A crawler cannot know which of the two documents it will receive, because the site does not know either.
faymas.in does not have this problem, but only because it always loses the race. We fetched one prompt page five times — four with a Chrome user agent, one with Googlebot — and all five returned 555,726 bytes with the title at byte 446,807. Deterministic, and deterministically in the body. That is the shape of the site with more than twenty thousand prompt URLs in its sitemap: every one of them announces itself four hundred kilobytes late.
Four domains, four brand names, and one of them is not Faymas
| Domain | og:site_name | Pages carrying it |
|---|---|---|
faymas.in | Faymas | 9 of 12 |
faymas.net | Faymas AI | 9 of 12 |
faymas-in.com | faymas in | 12 of 12 |
faymas.com.in | Onstream APK | 4 of 4 |
The fourth one is not a typo we introduced. Every page on faymas.com.in — home, About Us, Contact Us, Privacy Policy — declares to Facebook, X, Slack and every other Open Graph reader that the site is called "Onstream APK". Its <title> says something else ("Faymas In - Copy Ai Prompts for Photo & Video Editing 2026"). Its H1 says something else again ("Faymas – Copy Ai Prompts for Photo & Video Editing"). Three names on one page, and the one that travels with the link preview belongs to a different website.
faymas.in has a quieter version of the same split. Its homepage <title> is six characters: Faymas. The og:title on that exact page is forty-four: Faymas | The Creator Platform for AI Prompts. Whoever wrote the positioning wrote it in the tag that humans never see and forgot the one they do.
What the head says on the pages that actually exist
Thirteen of the forty pages have no meta description in the head at all. Three of the ones that have one are placeholders: faymas-in.com/category/prompt/ describes itself as "Your blog category" (18 characters, the unedited theme default), faymas.com.in/privacy-policy/ uses "Last Updated: October 1, 2026" (29), and faymas.com.in/contact-us/ uses "We would love to hear from you." (31). faymas.net/blog runs 37: "Latest news and updates from our team".
Two pages declare a canonical that points somewhere else. faymas.in/creator-league/leaderboard canonicalises to https://faymas.in — its own homepage. faymas.com.in/contact-us/ has no canonical tag at all and carries meta robots of follow, noindex, while sitting in the site's own navigation.
Then there is faymas-in.com, where five of the twelve URLs we requested do not exist. /about-us/, /contact-us/, /disclaimer/, /privacy-policy/ and /terms-and-conditions-2/ each answer 301 and land on the homepage. All six requests — those five plus the homepage itself — return the same 70,101-byte document, with the same 16-character title "Home - faymas in", the same canonical, the same two H1s. The site links to a legal page set that is not there.
Heading counts are inconsistent in the same way. faymas-in.com's homepage has two <h1> elements; its two category pages have none. faymas.in's leaderboard and search pages have none. Favicons: faymas.in declares four, faymas.net three, faymas.com.in three copies of the same JPG from its uploads folder, and faymas-in.com none at all. Only sixteen of forty pages carry an og:image inside the head — two on faymas.in, nine on faymas.net, four on faymas-in.com, one on faymas.com.in.
hreflang: zero out of forty
Four domains, one word, all four serving English to an audience that is largely Indian. Not one of the forty pages carries a single link rel="alternate" hreflang. None of them acknowledges that the other three exist.
That is the cleanest signal on the page. A genuine multi-regional operation — one brand running .in, .net and two .com variants — would cross-declare, because the whole point of the tag is telling a search engine which of your own URLs to show in which country. Four look-alike domains with zero hreflang between them are not four arms of one business. They are four separate sites that happen to share a name, and the head tags confirm what the og:site_name values already suggested.
We are not claiming to know who runs any of them. We did not ask, and we consulted no registry. We are reporting what forty documents say about themselves.
Who is allowed to read any of it
We sent one request with a GPTBot user agent to each domain. All four refused: faymas.in, faymas.net and faymas-in.com each returned 403 with the same 25-byte body, "Your request was blocked."; faymas.com.in returned 403 with a 1,242-byte HTML block page. So for one class of reader the head placement question never comes up — there is no document to read.
What we did not measure
Forty URLs is a sample drawn from each site's own navigation, not a census; faymas.in has more than twenty thousand prompt pages and we read three. We ran no JavaScript, so anything assembled in the browser is invisible to us — and for the six pages above, what we measured is precisely what a non-rendering client receives. We did not test how any search engine treats a <title> in the body; the HTML parser will still set a document title, so a rendering crawler may well see it, and we are not going to guess what any specific one does. The two faymas.net variants were reproducible across repeated fetches but we cannot say what fraction of requests each represents. We consulted no traffic, ranking or revenue service. Every figure here comes from the sixty-five responses we saved.
FAQ
Do faymas pages put their title tag in the head?
Thirty-four of the forty pages we tested do. Six do not: the three faymas.in prompt pages, which place it at byte 437,957 to 446,807, and faymas.net's /prompts, /pricing and /ai-image-generator, which place it at 315,599, 59,308 and 32,180 respectively. On all six the meta description and canonical link are in the body as well.
Is the title placement different for Googlebot?
Not on faymas.in — five fetches across two user agents returned byte-identical documents with the title at 446,807. On faymas.net the placement varies between identical requests rather than by user agent: we got both the in-head and in-body versions of /prompts under a Chrome UA and under a Googlebot UA.
Which faymas site calls itself something other than Faymas?
faymas.com.in. All four of its pages set og:site_name to "Onstream APK", while its title tag says "Faymas In - Copy Ai Prompts for Photo & Video Editing 2026" and its H1 says "Faymas – Copy Ai Prompts for Photo & Video Editing".
Do any of the four faymas domains use hreflang?
None. Zero of the forty pages we fetched contain a link rel="alternate" hreflang tag, and none of the four domains references any of the others.
Do faymas pages have meta descriptions?
Twenty-seven of forty do. Thirteen have none in the head, including all six pages that bury their tags in the body and six of the twelve faymas-in.com URLs, five of which redirect to the homepage. Three of the descriptions that do exist are placeholders, the shortest being the 18-character "Your blog category".