Three levels, and not one deeper. We pulled every <h1> through <h6> out of forty-three pages across the four faymas domains and counted 683 headings: 43 h1, 372 h2, 268 h3, and zero h4, h5 or h6 anywhere. Four sites, four different stacks, same ceiling. Six of the forty-three pages have no h1 at all — including one 358,794-byte page that contains not a single heading tag of any level. Six others carry two h1s each, and on all six, neither one describes what the page is about.
This guide analyses published prompt text. No generation tests were run.
What we counted
We fetched each domain's homepage, took every same-domain link off it, and pulled up to thirteen of those pages. Thirteen on faymas.in, thirteen on faymas.net, thirteen on faymas-in.com, four on faymas.com.in — four is all that domain's own links expose. Forty-three unique pages, forty-seven requests in the main pass, fifty-nine in all. One Chrome user agent, redirects followed, no JavaScript, 28 October 2026.
Then we deleted every <script>, <style> and comment before matching anything. That step is not optional here. Two of these sites are Next.js apps that ship markup inside their inline payloads, and a heading string sitting in a JavaScript bundle is not a heading. Not one of the 683 came from inside a script block; every number below is markup a parser would treat as a heading.
Each surviving heading was recorded in document order with its level, its text stripped of nested tags, and its position relative to the heading before it. That gives us a tree per page rather than a bag of counts — which is how we found the two things worth reporting.
Because one of these sites served us two different documents for one URL two days ago, we re-fetched four pages three times each with the same user agent. faymas.net/nano-banana/nano-banana-2 returned 28 headings every time. faymas.in/ returned 22. faymas-in.com/category/ai-tools/ returned 11. faymas.com.in/ returned 30. Nothing moved.
| Domain | Pages | Headings | h1 | h2 | h3 | h4–h6 | h2 per h3 |
|---|---|---|---|---|---|---|---|
faymas.in | 13 | 176 | 10 | 144 | 22 | 0 | 6.5 |
faymas.net | 13 | 314 | 13 | 87 | 214 | 0 | 0.41 |
faymas-in.com | 13 | 141 | 16 | 108 | 17 | 0 | 6.4 |
faymas.com.in | 4 | 52 | 4 | 33 | 15 | 0 | 2.2 |
| Total | 43 | 683 | 43 | 372 | 268 | 0 | 1.4 |
Forty-three h1 for forty-three pages looks tidy until you check where they landed. Six pages have none. Six have two. The total only balances because the two groups cancel out.
Nothing goes below h3, and the four sites agree without coordinating
Zero h4. Zero h5. Zero h6. Across 683 headings on two Next.js sites and two WordPress sites, built by different people at different times, the deepest heading anyone writes is h3.
That is not the same as agreement on structure. Under the shared ceiling the four sites disagree completely about which level does the work. faymas.in writes 6.5 h2 for every h3. faymas-in.com writes 6.4. faymas.net writes 0.41 — inverted. It uses h3 as its workhorse and h2 only as a section label, which is roughly backwards from how the other three are built.
The consequence is that a tool reading these sites by level will read them differently, even though all four stop at the same depth. Depth is not the thing that breaks; level semantics are.
faymas.net runs one template eleven times
Eleven of its thirteen pages are model pages: /nano-banana/nano-banana-2, /veo/veo-3-1, /wan/wan-2-7, and so on. Each one carries an h1, six to eight h2, and exactly twenty h3. The twenty are the same twenty blocks with the model name swapped in.
| h2 section | h3 children |
|---|---|
| What [model] can do | Prompt-to-image creation · Reference-image editing · Three output sizes |
| Why use [model] in Faymas AI | Inputs and controls stay together · See the cost before you commit · Keep every result organized |
| Create with [model] in three steps | Choose an input workflow · Describe the result · Review credits and generate |
| Where [model] fits | Product concept variations · Editorial image direction · Social and campaign assets |
| Explore another workflow | Three sibling-model links |
| [model] FAQ | Five question headings |
Five of those h3 repeat across nine pages verbatim: "Inputs and controls stay together", "See the cost before you commit", "Keep every result organized", "Review credits and generate", "Explore another workflow". "Do I need an image to start?" appears six times. Question-form headings as a whole are heavily concentrated here: 55 of the 92 question headings across all four domains are on faymas.net, and most of them are these template FAQ slots.
The domain also writes the shortest headings of the four — 27.5 characters and 4.7 words on average, against 43.3 characters and 7.5 words on faymas-in.com. Short headings are what you get when the same slot has to accept eleven different model names.
faymas-in.com: two h1s on six pages, none on three
Six pages carry two h1 elements each: the homepage, four category pages (/category/ai-tools/, /category/templates/, /category/guides/, /category/tech-news/) and /about-us/. Both are the same on every one: "Faymas Prompt" and "Faymas – Discover the Best AI Tools, Prompts, Templates and Guides".
Neither names the page. One is the site's name; the other is its tagline. On a category page for AI tools, the top-level heading still says "Faymas Prompt".
It gets stranger. The tagline string appears twice on those same six pages — once as an h2, once as an h1. Twelve occurrences, six pages, one identical sentence rendered at two levels in the same document.
And the three category pages that do list posts — /category/trending/, /category/prompt/, /category/boys-prompt/ — have no h1 at all. They open straight into h2: "Trending Prompt", "prompt", "Boys Prompt", followed by 4, 3 and 1 post titles respectively. So on this one site, categories with posts have no h1, and categories without posts have two. We can report the split; we did not read the theme source, so we are not going to claim we know what produces it.
A 358,794-byte page with no headings in it
faymas.in/creator-league/leaderboard returns 358,794 bytes of HTML. It contains zero heading tags. Not a missing h1 — no h1, h2, h3, h4, h5 or h6, anywhere in the document.
faymas.in/favourites is the same. Two of thirteen pages on the largest of the four sites ship their entire UI with no heading element in the delivered markup.
We ran no JavaScript, so whatever these pages assemble in the browser is invisible to us, and it may well include a heading. That is exactly the point: the heading is not in the response. Anything that reads the response — a crawler, a reader, a text extractor, a screen reader working from the served document — gets 358 KB with no structural signal in it.
faymas.in/search is a milder version of the same thing: twenty-four h2 elements, no h1, and the first heading on the page is a search result titled "Couple photoshoot".
The one thing all four get right
Zero level skips. Across 43 pages and 683 headings, there is not one place where a heading jumps more than one level deeper than the one above it — no h1 followed directly by an h3, no h2 followed by an h4.
Zero empty headings too. Every one of the 683 has text in it, and none carries aria-hidden="true".
That is worth saying plainly, because audits of this kind usually find the opposite. The failures here are not nesting failures. They are about what the headings say: a level-1 heading that names the site instead of the page, a level-1 heading missing entirely, a whole document with none.
What we did not measure
Forty-three pages is a sample drawn from each site's own homepage, not a census — faymas.in lists more than twenty thousand prompt URLs and we read thirteen of its pages. We ran no JavaScript, so anything assembled client-side is outside these numbers, and we have flagged the two pages where that caveat matters most. We counted heading elements and their text; we did not measure how any search engine or assistive technology weighs them, and we are not going to guess. No traffic, ranking or revenue service was consulted. Every figure here comes out of the saved responses.
FAQ
How many headings do the faymas sites use?
683 across 43 pages: 43 h1, 372 h2, 268 h3, and zero h4, h5 or h6. The deepest heading on any of the four domains is h3.
Do any faymas pages lack an h1?
Yes, six of 43. faymas.in/creator-league/leaderboard and faymas.in/favourites have no heading tags of any level, faymas.in/search has 24 h2s and no h1, and three faymas-in.com category pages (trending, prompt, boys-prompt) open at h2.
Which faymas site uses h3 the most?
faymas.net, with 214 h3 against 87 h2 — a ratio of 0.41, inverted relative to the other three domains. Eleven of its pages are model pages built from one template with 20 h3 slots each.
Why do some faymas-in.com pages have two h1s?
Both h1s are site-level boilerplate, not page titles: "Faymas Prompt" and "Faymas – Discover the Best AI Tools, Prompts, Templates and Guides". They appear together on six pages, and the tagline is also rendered as an h2 on those same pages.
Do faymas headings skip levels?
No. Zero skipped levels across 43 pages and 683 headings, and zero empty or aria-hidden headings. The structural problem is what the headings say, not how they nest.