Implementation report: https://www.bewakoof.com/tribe

Before anything else: something is stopping this page from being found at all. It has no page title, and search engines currently see none of its content in the raw page code they read before JavaScript runs. Your page scores 53 out of 100, which means critical issues are present, and there are 35 things to fix here, ordered from most valuable to least.

The 5 biggest problems (fix these first)

1. Your page has no title: Google has nothing to show as the headline in search results

Current: no <title> tag

The title tag is what Google shows as the clickable blue headline in search results, and it is one of the strongest signals Google uses to understand what a page is about. Without one, Google will invent its own title from whatever text it can find, usually something generic, and this page loses control of how it's presented and what it ranks for.

Fix: Add a <title> tag in the page's <head> naming the Tribe program and the brand, kept under 60 characters:

Bewakoof Tribe: Join the Community & Unlock Exclusive Deals

Who: You or a writer, about 5 minutes once someone has access to the page template.

2. This page is invisible to search engines: they see 0 words, even though visitors see 37

Current: Crawlers see 0 words before JavaScript runs, 37 after.

Google and most AI answer engines read the raw HTML a server sends back, and not all of them wait for JavaScript to finish building the page. Right now the words a visitor sees only appear after the browser runs JavaScript, so crawlers that don't wait see an empty page. That means this page can be effectively absent from search and AI answers no matter how good its content becomes.

Fix:

Confirm with your developers that /tribe renders its main content client side only, in JavaScript.
Switch this page to server-side rendering or static generation so the text is present in the HTML the server sends, before any JavaScript runs.
Check it worked by viewing the page's raw source (or running curl on the URL) and confirming the visible words appear there directly.

Who: A developer, likely half a day to a day depending on how the site is built.

3. There's no main heading: nothing tells Google or readers what this page is about

Current: no H1 found

The H1 heading is the clearest label of what a page covers, for both readers scanning it and search engines confirming its topic. With none at all, there's no anchor signal saying "this page is about the Tribe program," which weakens ranking and how confidently an AI assistant can describe this page.

Fix:

Add one <h1> element as the first heading on the page, reading Bewakoof Tribe: Join the Community.
Make sure it appears before any other heading in the page code.
Check it worked by viewing the page source and confirming exactly one <h1> tag exists.

Who: A developer, about 30 minutes.

4. The page has no structured data at all, so Google can't confirm what kind of page this is

Current: jsonld: [] (no structured data blocks found)

Schema (a small code block that labels a page's purpose for machines) tells Google explicitly "this is a product page" or "this is a community page," instead of leaving it to guess from thin text. With zero schema present, this page is shut out of rich results and gives AI tools nothing structural to key off.

Fix, this needs one decision from you first about what Tribe actually is:

Option A: Tag it as basic Organization/WebSite schema. Gains a quick baseline signal and meets the minimum trust checks; costs nothing but doesn't describe Tribe specifically.

Option B: Tag it as a CollectionPage or Article type once real Tribe content exists. Gains a much more specific signal that matches what visitors are searching for; costs more developer time and only makes sense once the page has real content, not just menu items.

The evidence here, a URL called "/tribe" with nav links to men's, women's and accessories collections, points toward Tribe being a loyalty or community hub, so Option B is the better long-term fix, with Option A as the safe interim step.

Who: A developer to implement, with you confirming which page type is correct; about an hour once decided.

5. There's no real text on the page to link from, so it has zero pathways to related pages

Current: main_text contains no body prose or contextual links; only nav items ("MEN WOMEN ACCESSORIES | LOGIN") are present

Contextual links, links placed inside real sentences rather than the menu, tell Google which of your other pages are related and give readers and AI tools a path to follow. Right now there's no body text to place links in, so this page offers no route to your men's, women's or accessories collections.

Fix:

Once body copy about the Tribe program exists (see problem 2), link each named concept once, the first time it's mentioned, for example linking "men's collection" to /men-clothing.
Don't repeat the same link for the same concept elsewhere on the page.

Check it worked by viewing the page source and confirming links appear inside paragraph text, not just in the nav.

Who: A developer alongside a writer, once body copy is drafted; 1 to 2 hours.

Also worth fixing

For a developer

No baseline trust schema: add Organization, BreadcrumbList and WebSite structured data blocks; none of the three are present.
No canonical tag: add a self-referencing canonical tag pointing to https://www.bewakoof.com/tribe so Google doesn't get confused about which URL is the real one.
No structured data validates, because none exists: once you add schema (problem 4), make sure it's valid JSON-LD, and add FAQPage schema too if the page ever shows an FAQ.
Zero internal links in the body: add roughly 4 to 10 internal links once body copy exists, pointing to pages like /men-clothing or /women-clothing.
No dates in the page's structured data: add datePublished and dateModified to your JSON-LD, and show exactly one matching visible date on the page.

For a writer

No author named anywhere: add a visible author name and credential near the top of the page, linking to an author bio page.
Two headline stats can't be checked by anyone: source and date the sales and customer numbers, for example 10 Crores+ Products Sold (Bewakoof.com internal sales report, as of September 2026).
No links to About, Contact or Privacy pages: link to those pages so readers and search engines can verify who runs this page.
No question-style subheadings: add headings like What is Bewakoof Tribe? and How do I join? so AI assistants have direct answers to quote.
No subheadings on the page at all: add distinct subheadings each covering one reader question, for example What is Bewakoof Tribe?, How do I join the Tribe?, What perks do members get?.
No outbound links to any outside source: link to at least one relevant, authoritative outside source about the Tribe program.
Sales stats aren't attributed inline: keep the source and date for each number in the same sentence as the number, not in a separate footnote.
Nothing states plainly what this page is about: open the first paragraph with a sentence naming "Bewakoof.com" and what the Tribe program is.
No real paragraphs, only menu labels: write actual paragraphs explaining the Tribe program so there's something an AI tool could quote as an answer.
Brand name appears only once, in a menu fragment: mention "Bewakoof" or "Bewakoof.com" again in each new section you write, not just once.
Too few named things on the page: name specific products, collections or store locations in the new copy so the page reads as specific, not generic.
Stats have no named source line: add a named source and date beside each number, for example 10 Crores+ Products Sold (Bewakoof.com internal sales report, as of September 2026).
A blank title risks Google rewriting it anyway: once you add the title from problem 1, keep it specific to "Tribe" so Google shows it as written instead of substituting its own guess.
Facts aren't written as plain statements: write key facts as simple sentences, for example Bewakoof.com sells fashion apparel for men and women, using the same brand name every time.
Sales numbers have no outside backing: get the figures corroborated in press coverage or another trusted site and link to it.
No reviewer name or last-reviewed date: add who wrote or checked the page and when.
Customer count looks out of date: 2 Crores+ Customers Bought doesn't match a sourced figure of 10 million (1 crore) from an August 2021 article; update the number or add a current source.
No "last updated" signal anywhere: add a dateModified that reflects when the page's facts were actually checked.
Headline stats read as marketing, not fact: source and date both numbers so they read as verifiable claims rather than promotional copy.
Page is far too thin at 37 words: expand to at least 300 words that explain what Tribe is, how to join, and what members get.
No visible "last updated" date for readers: add one, and keep it under 18 months old.
"10 Crores+ Products Sold" has no source: add a source or remove the claim.

For you

Your meta description is only 33 characters: it currently reads Shop cool merchandise at Bewakoof [33 characters]. Replace it with something between 140 and 160 characters describing the Tribe program, for example: Join Bewakoof Tribe for exclusive merch drops, early access to new collections and member only deals. Sign up free and start earning Tribe rewards today.
No social preview image or description: only og:app_id is set. Add og:title, og:description and og:image so links shared on social or chat apps show a proper preview instead of a blank one.

What is already working

Your page loads cleanly over HTTPS with a 200 response, no broken redirect.
Search engines are allowed to crawl and index it: no noindex tag, Googlebot isn't blocked.
The web address itself is clean: /tribe, short, lowercase, easy to read.
You already have real authority behind the domain: 6,176 referring domains and 26,634 backlinks pointing at bewakoof.com.
Your robots.txt file is set up correctly and points search engines to your sitemaps.

Claims to double check

"10 Crores+ Products Sold": flagged as unsourced. Add a source, or remove the claim if you can't back it up.
"2 Crores+ Customers Bought": flagged as outdated. The most recent sourced figure found is a customer base of over 10 million (1 crore) as of an August 2021 article; no source confirms the 2 crore figure. Update the number or add a current source.

What we could not measure

Page speed (Core Web Vitals) wasn't measured because no performance tool is connected; run your URL through the free PageSpeed Insights tool at pagespeed.web.dev to check it by hand. Whether this page links to or from other important pages on your site is unknown without a full site crawl. Whether AI assistants like ChatGPT or Gemini currently cite this page wasn't tested this cycle, no questions were run. Whether you have an llms.txt file, and whether your brand has a knowledge panel or consistent presence across other sites, also weren't checked. One data step in this run was also interrupted by a system restart, so treat the content-related findings above as a solid first pass rather than fully exhaustive.

You don't have a claims ledger yet. Setting one up would let this skill state your product, pricing and customer facts directly instead of flagging every number for a manual check.

The full technical audit

Every check behind the report above, for whoever makes the changes.

What is working

What this is: The checks that already meet the bar on this page.

How to read it: Each line names the rule that passed and what was observed.

Your action: Keep these as they are while you work the list below.

Pass 200 over HTTPS, no soft-404: HTTP 200 over https
Pass Indexable: no noindex, Googlebot not blocked: no noindex directive, Googlebot not blocked
Pass No nosnippet / max-snippet:0: no nosnippet/max-snippet:0 directive
Pass Heading hierarchy valid, no skipped levels: 0 H1, 0 H2, 0 H3
Pass URL slug flat, lowercase, hyphenated, keyword-bearing: URL path: "/tribe"
Pass Primary keyword naturally within the first 100 words: keyword unknown, cannot check first-100-words placement
Pass No invisible watermark chars; em-dash frequency <=4/1,000w: 0 em-dashes over 37 words (0.0/1,000w)
Pass No schema misuse, no retired @type: 0 JSON-LD type(s): none

Start Here

What this is: The highest-impact-per-effort fixes, ranked, capped at five.

How to read it: A critical chip means the item is a hard gate: it blocks the score, not just lowers it.

Your action: Fix the 5 items under Start Here first

critical 5-min Title present, keyword-bearing, not stuffed See finding
critical developer Main content present in server-rendered raw HTML See finding
developer Exactly one H1, keyword-bearing, first heading in the DOM See finding
developer Primary schema type matches page purpose See finding
developer Contextual body links first-mention, one link per concept See finding

AI visibility

What this is: How often AI answers use this page for these questions.

How to read it: Each card is one question asked to an AI engine; the chip says whether the answer used this page.

Your action: No AI answers were tested for this page.

No AI answers were tested for this page.

SEO dimensions

What this is: The eight scored dimensions and every finding behind them, grouped by dimension.

How to read it: Within a dimension, fails come first, then warns, then unmeasured checks, then passes.

Your action: Work the 22 failing checks first, then the 13 warnings

Dimension	Score	Measured of applicable	Weight
Technical SEO	78	8 of 10	20
On-page SEO	34	9 of 9	12
Content quality	75	2 of 2	20
Structured data	44	5 of 5	10
Links	40	4 of 5	10
Performance	incomplete	0 of 8	10
Trust and expertise	18	3 of 4	14
Freshness	50	1 of 1	4
Data	50	2 of 2	8

Technical SEO781 fail · 1 warn

Fail Main content present in server-rendered raw HTML
Observed: "Crawlers see 0 words before JavaScript runs, 37 after."

Expected: The renderer confirms the raw HTML is not JS-only for the main content.

How to verify: Re-run the audit: SR-CR-03 reads pass
Warn Self-referencing canonical, absolute, no conflict
Observed: "no canonical tag present"

Expected: The canonical tag points to this exact URL.

How to verify: Re-run the audit: SR-CR-04 reads pass
Pass 200 over HTTPS, no soft-404
Observed: "HTTP 200 over https"

Expected: The page returns HTTP 200 over HTTPS.
Pass Indexable: no noindex, Googlebot not blocked
Observed: "no noindex directive, Googlebot not blocked"

Expected: No noindex directive and Googlebot is not blocked in robots.txt.
Pass No nosnippet / max-snippet:0
Observed: "no nosnippet/max-snippet:0 directive"

Expected: robots_meta carries no nosnippet or max-snippet:0 directive.
Pass Redirects to the page are clean, no meta-refresh, no mixed-protocol hop
Observed: "final_url matches url exactly: https://www.bewakoof.com/tribe, http_status 200"

Expected: Any redirect chain into this URL is a single clean 301/308, same protocol.

Recommendation: No action needed; periodically re-verify with a redirect trace (curl -IL) to confirm no future 302 or meta-refresh hops are introduced.

Location: HTTP response / redirect chain
Pass No crawl traps: session-ID or internal-search links, unmanaged parameters
Observed: "internal_hrefs: ["/", "/men-clothing", "/women-clothing", "/accessories", "/login", "/wishlist"]"

Expected: No session-ID or internal-search links; faceted URLs are canonicalized or noindexed.

Recommendation: No action needed on this sample; separately audit deeper category/filter URLs (e.g. /men-clothing?...) to confirm faceted params are canonicalized.

Location: Main navigation links
Pass robots.txt well-formed, does not block CSS/JS, declares a sitemap
Observed: "robots.txt status 200, sitemaps declared: https://www.bewakoof.com/sitemap_index.xml, https://www.bewakoof.com/blog/sitemap_index.xml"

Expected: robots.txt is well-formed, allows CSS/JS, and declares an absolute sitemap URL.

Recommendation: Inspect the full robots.txt body directly to confirm no Disallow rule targets /static/, /assets/, .css or .js paths.

Location: https://www.bewakoof.com/robots.txt

Not measured this run (3)

N/A Paginated pages self-canonicalize
Observed: "No pagination markup, rel=next/prev, or page-number parameters found on this URL."

Expected: A paginated page canonicalizes to itself, never to page 1, and is never blanket-noindexed.

Recommendation: No action needed.

Location: N/A
Needs data URL is in the sitemap, reachable in <=3 clicks, not orphaned
Observed: "sitemap.includes_url: true; link_graph: "unknown" (no crawl export available)"

Expected: The URL appears in the XML sitemap and is reachable within three clicks of the homepage.

Recommendation: Run a full-site crawl (e.g. Screaming Frog) from the homepage to confirm /tribe is linked within 3 clicks via actual navigation, not just present in the sitemap.

Location: Site navigation / crawl depth
Needs data No cloaking, no near-duplicate/staging mirror
Observed: "render.status=ran, js_dependency=full, raw_word_count=0, rendered_word_count=37"

Expected: What's served matches what's indexed; no staging mirror or near-duplicate exists.

Recommendation: Use Google Search Console's URL Inspection tool to fetch the live-rendered version Googlebot sees and diff it against this rendered snapshot.

Location: Full page render

On-page SEO344 fail · 2 warn

Fail Title present, keyword-bearing, not stuffed
Observed: "no <title> tag"

Expected: A <title> tag exists and contains the target keyword.

How to verify: Re-run the audit: SR-ONP-01 reads pass
Fail Exactly one H1, keyword-bearing, first heading in the DOM
Observed: "no H1 found"

Expected: Exactly one H1 is present.

How to verify: Re-run the audit: SR-ONP-02 reads pass
Fail Each H2 a distinct user sub-question, not a vague label
Observed: "h2: [] (zero H2 headings found on the page)"

Expected: Each H2 covers a distinct sub-question in the reader's own words.

Recommendation: Add H2 subheadings framing this as a Tribe community page, e.g. 'What is Bewakoof Tribe?', 'How do I join the Tribe?', 'What perks does Tribe membership include?'.

Location: Page body

How to verify: Re-run the audit: SR-ONP-04 reads pass
Fail Title-rewrite risk: not so long/generic/stuffed the engine replaces it
Observed: "title: null (no <title> tag present)"

Expected: The title is specific and well-formed enough that Search Console shows it unrewritten.

Recommendation: Add a specific, descriptive <title> tag naming the Tribe program and the brand.

Location: <head><title>

Before: (missing)
After: Bewakoof Tribe – Join the Community & Unlock Exclusive Merch Deals | Bewakoof

How to verify: Re-run the audit: SR-ONP-12 reads pass
Warn Meta description unique, 150-160 chars, keyword present
Observed: "meta description is 33 chars: "Shop cool merchandise at Bewakoof""

Expected: A meta description exists, 150-160 characters long.

How to verify: Re-run the audit: SR-ONP-03 reads pass
Warn Open Graph + Twitter card present
Observed: "og tags present: og:app_id"

Expected: og:title, og:description and og:image are present.

How to verify: Re-run the audit: SR-ONP-11 reads pass
Pass Heading hierarchy valid, no skipped levels
Observed: "0 H1, 0 H2, 0 H3"

Expected: Headings descend without skipping a level and are never used purely for styling.
Pass URL slug flat, lowercase, hyphenated, keyword-bearing
Observed: "URL path: "/tribe""

Expected: The URL path is lowercase, hyphenated, with no dates/IDs/params.
Pass Primary keyword naturally within the first 100 words
Observed: "keyword unknown, cannot check first-100-words placement"

Expected: The keyword appears within the first 100 words.

Not measured this run (4)

N/A Title length 50-60 chars
Observed: "no title to measure"

Expected: Title is 50-60 characters long.
N/A Image alt present on all images
Observed: "no images on the page"

Expected: Every image carries alt text (empty alt is fine for a decorative image).
N/A Image filenames descriptive, hyphenated, lowercase
Observed: "no images on the page"

Expected: Image filenames are descriptive, hyphenated, lowercase.
N/A Body density natural, no confirmed keyword stuffing
Observed: "main_text is 37 words of navigation/UI chrome ("Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN..."), not prose body content"

Expected: Keyword density reads naturally; >2% warns, confirmed stuffing across headings/alt/sentences fails.

Recommendation: Once real body copy is added, re-check that the target keyword distributes naturally without repeating in every heading/alt/sentence.

Location: Page body

Content quality751 warn

Warn Depth matches intent; under 300 words is thin
Observed: "37 words, under the 300-word thin-content floor"

Expected: Word count is at least 300, or a narrow intent is fully answered.

How to verify: Re-run the audit: SR-CNT-02 reads pass
Pass No invisible watermark chars; em-dash frequency <=4/1,000w
Observed: "0 em-dashes over 37 words (0.0/1,000w)"

Expected: No invisible watermark characters; at most 4 em-dashes per 1,000 words.

Not measured this run (2)

N/A Comparisons as real HTML tables, steps as ordered lists
Observed: "no tables or lists on the page"

Expected: Tabular comparisons use a real <table>; sequential steps use an ordered list.
N/A Video, where present, crawlable with VideoObject + transcript
Observed: "no video on the page"

Expected: Any video carries VideoObject schema and a server-rendered transcript.

Structured data442 fail · 2 warn

Fail Baseline trio: Organization/LocalBusiness + BreadcrumbList + WebSite
Observed: "baseline trio present: none"

Expected: Organization/LocalBusiness, BreadcrumbList and WebSite schema are all present.

How to verify: Re-run the audit: SR-SCH-05 reads pass
Fail Primary schema type matches page purpose
Observed: "jsonld: [] (no structured data blocks found)"

Expected: The primary @type matches the page's purpose (Article/Product/LocalBusiness/FAQPage/...).

Recommendation: Add JSON-LD matching the page's actual purpose — at minimum Organization/WebSite, or CollectionPage/Article if 'Tribe' is a loyalty/community content hub.

Location: <head> or before </body>, JSON-LD block

How to verify: Re-run the audit: SR-SCH-02 reads pass
Warn JSON-LD present and valid
Observed: "no JSON-LD structured data found"

Expected: At least one valid JSON-LD block is present; an FAQ visible on the page has FAQPage schema.

How to verify: Re-run the audit: SR-SCH-01 reads pass
Warn Dates: one visible date; datePublished and dateModified in JSON-LD
Observed: "no datePublished/dateModified found"

Expected: Exactly one visible date; both datePublished and dateModified are in JSON-LD and consistent.

How to verify: Re-run the audit: SR-SCH-07 reads pass
Pass No schema misuse, no retired @type
Observed: "0 JSON-LD type(s): none"

Expected: No Product/Review type without matching content; no retired @type.

Not measured this run (2)

N/A @graph well-formed
Observed: "no JSON-LD to check"

Expected: A single @context, @id-linked entities, one root, no orphans or circular refs.
N/A Schema content matches visible content
Observed: "jsonld: [] — no schema present to compare against visible content"

Expected: Schema name/headline/author overlaps the visible content by at least 60%; no schema-only FAQs/ratings.

Recommendation: N/A until schema is added; once added, ensure schema fields mirror the visible page content.

Location: N/A

Links402 fail · 1 warn

Fail Contextual body links first-mention, one link per concept
Observed: "main_text contains no body prose or contextual links; only nav items ("MEN WOMEN ACCESSORIES | LOGIN") are present"

Expected: Contextual body links appear at first mention; nav/footer links don't count.

Recommendation: Once body content is written, link each named concept (e.g. a specific collection or product line) once, at its first mention in the text.

Location: Page body

How to verify: Re-run the audit: SR-LNK-03 reads pass
Fail Outbound links working, authoritative, to primary sources
Observed: "external_hrefs: [] (0 external links)"

Expected: Outbound links resolve and point to authoritative, primary sources.

Recommendation: If this is a content/community page, add at least one outbound link to an authoritative source relevant to the Tribe program, where genuinely useful.

Location: Page body

How to verify: Re-run the audit: SR-LNK-06 reads pass
Warn Body internal-link count scales with length
Observed: "zero internal links found in the body"

Expected: The page has at least one internal link; roughly 4-10 for a ~1,500-word page.

How to verify: Re-run the audit: SR-LNK-02 reads pass
Pass No broken internal links or redirect chains, not nofollowed
Observed: "0 internal links, 0 of 0 external links nofollowed"

Expected: Internal links resolve directly and are not nofollowed.

Not measured this run (2)

Needs data Page belongs to a hub-and-spoke cluster, not an orphan
Observed: "link_graph is "unknown" without a crawl export"

Expected: A crawl export confirms the page is linked from at least one hub page.
N/A Anchors varied and descriptive, no exact-match over-optimization
Observed: "No body anchor text exists to evaluate; only nav labels ("MEN", "WOMEN", "ACCESSORIES") are present, which are excluded as nav links"

Expected: Anchor text is varied and descriptive; no generic "click here" or exact-match stuffing.

Recommendation: When adding body links, use descriptive, varied anchor phrases rather than repeating the same exact-match keyword each time.

Location: Page body

Trust and expertise182 fail · 1 warn

Fail Visible author byline + credential above the fold
Observed: "no author byline found"

Expected: An author byline is present and links to an author bio page.

How to verify: Re-run the audit: SR-EAT-01 reads pass
Fail Trust signals: citations, working outbound links, policy pages, HTTPS
Observed: "no about, contact or privacy page linked"

Expected: About, contact and privacy pages are linked, and the page is served over HTTPS.

How to verify: Re-run the audit: SR-EAT-03 reads pass
Warn Reviewer name + credential + last-reviewed date
Observed: "no reviewer/last-reviewed date found"

Expected: A reviewer name, credential and last-reviewed date are present (required on YMYL).

How to verify: Re-run the audit: SR-EAT-02 reads pass

Not measured this run (3)

N/A Affiliate/commercial disclosure above the fold
Observed: "Page promotes Bewakoof's own 'Tribe' program and merchandise; no third-party affiliate or sponsored content detected in the available text"

Expected: Affiliate or commercial relationships are disclosed above the fold.

Recommendation: No action needed unless Tribe involves paid third-party partnerships requiring disclosure.

Location: N/A
N/A No regulatory superlatives on regulated topics
Observed: "Page is fashion/apparel e-commerce content ("Online Fashion Shopping for Men, Women, Accessories"), not a regulated finance/health topic"

Expected: No "best/guaranteed" language on regulated finance/health topics; required disclosures present.

Recommendation: No action needed.

Location: N/A
Needs data E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
Observed: "Available signals: no author byline, no about/contact/privacy links, no dates, no schema, 37 words of chrome-only content"

Expected: A banded Trust 30 / Expertise 25 / Authority 25 / Experience 20 roll-up, honestly labeled a quality concept.

Recommendation: Treat any composite E-E-A-T score for this page as a low-confidence internal quality heuristic, not a Google ranking factor, and have an editor confirm before publishing a banded score.

Location: N/A

Freshness501 warn

Warn Visible last-updated date, accurate against schema dateModified
Observed: "no published, modified, or visible date found"

Expected: A visible, accurate last-updated date exists and is under 18 months old.

How to verify: Re-run the audit: SR-FR-01 reads pass

Performanceincompletenot measured

Not measured this run (8)

Needs data LCP < 2.5s, CLS < 0.1, INP < 200ms at p75
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: LCP, CLS and INP each meet the Core Web Vitals "good" threshold at p75.
Needs data All-three-Poor veto: LCP, CLS, INP all Poor
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: Not all three Core Web Vitals rate Poor at once.
Needs data TTFB <= 800ms, FCP <= 1.8s
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: TTFB is 800ms or under (warn to 1,800ms); FCP is 1.8s or under.
Needs data First 3 images not lazy-loaded, LCP image preloaded
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: The hero/LCP image is not lazy-loaded and is preloaded with high fetch priority.
Needs data Render-blocking budget: no sync head scripts, controlled weight
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: No synchronous head scripts; page weight and request count stay within budget.
Needs data Font strategy and deferred third-party scripts
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: font-display:swap, primary font preloaded, at most 6 font files; third-party scripts deferred.
Needs data Mobile: viewport meta, tap targets, font size, parity
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: A viewport meta tag is present and mobile usability audits pass.
Needs data Delivery hygiene: compression, HTTP/2+, cache-control, preconnect
Observed: "no performance service connected; run PageSpeed Insights by hand"

Expected: Responses are compressed, served over HTTP/2+, with cache-control and preconnect hints.

AI answersincomplete4 fail

Fail Answer-first sections, question-shaped H2s, key-takeaway box
Observed: "no H2 headings found"

Expected: At least half of H2 headings are question-shaped.

How to verify: Re-run the audit: AI-EXT-04 reads pass
Fail Each passage stands alone
Observed: "main_text is a single run-on string of navigation labels and fragments ("Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN ...") with no discrete passages that answer an implied question on their own."

Expected: Each passage answers its implied question without needing the paragraphs before it.

Recommendation: Add real body paragraphs (e.g. an "About Bewakoof.com" section) written so each paragraph fully answers one implied question on its own.

Location: main_text

How to verify: Re-run the audit: AI-EXT-01 reads pass
Fail Entity context retained in each passage
Observed: "The brand name "Bewakoof.com" appears exactly once, trailing at the end of the nav-text block, with no other passage in the given content naming the subject."

Expected: The named subject appears in the passage itself, not just "it"/"this".

Recommendation: Re-mention "Bewakoof.com" (or "Bewakoof") explicitly within each new content section added, not just once in the footer/title area.

Location: main_text

How to verify: Re-run the audit: AI-EXT-02 reads pass
Fail Attribution survives inside the passage
Observed: "No sourced claim exists in the given content, so none carries an in-passage attribution."

Expected: A sourced claim carries its source inside the same passage.

Recommendation: When adding sourced claims (e.g. sales figures), keep the source name/link in the same sentence or passage, not in a separate footnote section.

Location: main_text

How to verify: Re-run the audit: AI-EXT-03 reads pass

AI citationsincomplete7 fail · 2 warn

Fail Claims attributable: inline sources on load-bearing facts
Observed: "The only extracted content is site-chrome text: "Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 10 Crores+ Products Sold 2 Crores+ Customers Bought MEN WOMEN Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com". Neither of the two numeric claims ("10 Crores+ Products Sold", "2 Crores+ Customers Bought") carries an inline source or outbound link, and there is no other load-bearing claim on the page."

Expected: At least one attributed claim per 500 words, with real outbound links.

Recommendation: Replace nav-only chrome with real page copy: attribute the sales/customer figures to a dated, linkable source (press page, investor note, or verified counter) so the claim can stand as evidence.

Location: main_text

Before: 10 Crores+ Products Sold 2 Crores+ Customers Bought
After: Bewakoof.com has sold over 10 crore products to more than 2 crore customers as of FY2025-26 (source: Bewakoof internal sales data, linked here).

How to verify: Re-run the audit: AI-GATE-02 reads pass
Fail Entity-dense: claims pinned to named things
Observed: "title is null and h1 is an empty array; the brand "Bewakoof.com" appears only as a trailing fragment at the end of the nav string, not as the subject of the title, an H1, or an opening sentence."

Expected: The primary entity is salient in the title, H1 and first paragraph.

Recommendation: Add a descriptive <title> and a single <h1> that name the brand and category (e.g. "Bewakoof.com — Online Fashion Shopping for Men, Women & Accessories"), and open the first paragraph with a sentence stating what Bewakoof.com is.

Location: title / h1

Before: title: null, h1: []
After: <title>Bewakoof.com: Online Fashion Shopping for Men, Women & Accessories</title><h1>Bewakoof.com – Online Fashion Shopping in India</h1>

How to verify: Re-run the audit: AI-GATE-03 reads pass
Fail Corroborated on an independent trusted domain
Observed: "The two load-bearing marketing stats ("10 Crores+ Products Sold", "2 Crores+ Customers Bought") appear only on this page's own chrome text, with no visible corroboration on an independent trusted domain in the data provided."

Expected: Load-bearing claims are corroborated on at least one independent trusted domain.

Recommendation: Get the sales/customer figures corroborated on an independent trusted domain (press coverage, industry report, or a verifiable public filing) and link to it from the page.

Location: main_text

How to verify: Re-run the audit: AI-GATE-06 reads pass
Fail Entity floor + salience
Observed: "The extracted text contains almost no distinct named entities beyond "Bewakoof.com" and generic category labels ("MEN", "WOMEN", "ACCESSORIES", "Fanbook"); title and h1 (where salience would normally be established) are absent."

Expected: Enough distinct named entities per 100 words to ground the page; primary entity salient early.

Recommendation: Add named entities relevant to the business (brand name, product lines, notable collaborations, store locations) in a real title/H1/opening paragraph.

Location: main_text

How to verify: Re-run the audit: AI-ENT-01 reads pass
Fail Key facts as semantic triples, consistent naming
Observed: "No sentence in the given content forms a [subject][verb][object] factual claim; content is a list of nav/menu labels and two bare numeric fragments."

Expected: Key facts read as [subject] [verb] [object]; each entity is named consistently.

Recommendation: Write key facts as explicit triples, e.g. "Bewakoof.com sells fashion apparel for men and women" / "Bewakoof.com has sold 10 crore+ products," using the same brand name consistently.

Location: main_text

How to verify: Re-run the audit: AI-ENT-02 reads pass
Fail Every statistic/quotation attributes to a named source
Observed: ""10 Crores+ Products Sold" and "2 Crores+ Customers Bought" are stated with no source, credential, or organization named on the same line."

Expected: Every statistic or quotation names a source, credential and org on one line.

Recommendation: Attach a named source and date to each statistic, e.g. "(Bewakoof.com internal sales data, as of Sept 2026)" with a link.

Location: main_text

Before: 10 Crores+ Products Sold
After: 10 Crores+ Products Sold (Bewakoof.com internal sales report, as of September 2026)

How to verify: Re-run the audit: AI-CITE-01 reads pass
Fail No fabricated or unverifiable statistic or quote
Observed: "The two headline statistics on the page have no source or link in the extracted content, making them unverifiable as presented, even though they may be true internally."

Expected: No statistic or quote is fabricated or unverifiable on a claim-making page.

Recommendation: Make the sales/customer stats verifiable by sourcing and dating them (see AI-CITE-01 recommendation).

Location: main_text

How to verify: Re-run the audit: AI-CITE-02 reads pass
Warn Fresh where it matters
Observed: "no dateModified/datePublished found"

Expected: dateModified is accurate and genuine on freshness-sensitive topics.

How to verify: Re-run the audit: AI-GATE-05 reads pass
Warn Citable without reputational risk
Observed: "The page is not YMYL and contains no obviously wrong figures or banned superlatives visible in the given text, but the two headline stats ("10 Crores+ Products Sold", "2 Crores+ Customers Bought") are presented as bare, unsourced numbers rather than verifiable, credentialed claims."

Expected: Verifiable, credentialed, compliant; no wrong YMYL figures, no fabrication, no banned superlatives.

Recommendation: Source and date the sales/customer figures so they read as verifiable facts rather than marketing copy.

Location: main_text

How to verify: Re-run the audit: AI-GATE-08 reads pass
Pass Findable / readable by AI crawlers
Observed: "AI retrieval crawlers allowed, page is indexable and snippet-able"

Expected: AI retrieval crawlers are allowed, the page is indexable, and snippets aren't blocked.
Pass Retrieval/citation crawlers allowed; Googlebot/Bingbot never blocked
Observed: "retrieval crawlers, Googlebot and Bingbot are all allowed"

Expected: No retrieval/citation crawler is blocked, and Googlebot/Bingbot are never blocked.
Pass Unknown bot tokens flagged; retired anthropic-ai token removed
Observed: "no unknown bot tokens in robots.txt"

Expected: No unrecognized bot tokens in robots.txt; the retired anthropic-ai token is removed.
Pass Backlinks confirmed from a provider or upload
Observed: "6176 referring domains, 26634 backlinks via dataforseo"

Expected: A backlink provider or uploaded export confirms the backlink profile.

Not measured this run (7)

Needs data Knowledge-graph presence
Observed: "No web-search or knowledge-panel data was supplied for this run to confirm whether Bewakoof has an encyclopedia article, knowledge-base entry, or confirmed knowledge panel."

Expected: The entity has a knowledge-base entry, an encyclopedia article, or a confirmed knowledge panel.

Recommendation: Run a manual check for a Wikipedia/Wikidata entry and a Google Knowledge Panel for "Bewakoof" or "Bewakoof.com"; escalate to founder as a manual verification item.

Location: not available in provided data
Needs data Authoritative declarative tone, with the YMYL hedging exception
Observed: "The extracted content has no real prose sentences (only nav labels and stat fragments), so tone (declarative vs. hedged) cannot be assessed from what was provided."

Expected: Tone is declarative; a YMYL page hedges with "as of [date]" rather than vague hedging (not applicable here since page is marked non-YMYL).

Recommendation: Once body content is added, write it in a declarative tone; re-check this gate.

Location: main_text
Needs data Per-engine backend presence and crawler access
Observed: "TARGET QUESTIONS were "none derived" and the CITABILITY SAMPLE contains no rows, so no per-engine test (chatgpt, copilot, perplexity, ai_overviews, ai_mode, gemini, claude) was run this cycle."

Expected: The page is present in each target engine's retrieval backend, reported per engine.

Recommendation: Derive target questions for this page (e.g. "where to buy [X] online in India", "best online fashion stores India") and run the citability sample against each target engine before reassessing.

Location: CITABILITY SAMPLE (empty)
N/A Training-only blocks presented as a documented trade-off
Observed: "Auto findings show no unrecognized or training-only bot block; AI-BOT-03 passed with the retired anthropic-ai token removed and no other block reported."

Expected: Any training-only crawler block is a stated trade-off, never described as hurting rankings.

Recommendation: If a training-only crawler block is added in future, document it explicitly as a deliberate trade-off rather than leaving it unexplained.

Location: AUTO FINDINGS table
Needs data llms.txt and IndexNow carry low/zero weight, never a gate
Observed: "No information on llms.txt or IndexNow presence was included in the provided data."

Expected: llms.txt/IndexNow presence is noted informationally, never scored as a gate.

Recommendation: Check for llms.txt/IndexNow presence informationally only; do not treat as a scoring gate.

Location: not available in provided data
Needs data Knowledge-graph footprint (web search sample)
Observed: "No web-search sample was supplied to check for a knowledge-base entry, encyclopedia path, or consistent cross-platform presence for the brand."

Expected: A knowledge-base entry, encyclopedia path, or consistent cross-platform presence exists.

Recommendation: Run a web-search sample for "Bewakoof" across major platforms to confirm cross-platform presence; escalate as manual check.

Location: not available in provided data
Needs data Brand-mention sample on AI-visibility-correlated platforms
Observed: "No forum/video/news/professional-network mention sample was supplied for this run."

Expected: Earned brand mentions appear on forums, video, news or professional networks.

Recommendation: Run a brand-mention sample across forums, video, news and professional networks as a manual/tooling follow-up.

Location: not available in provided data

Programmatic pagesincompletenot measured

Not measured this run (3)

N/A Every page carries genuinely unique data
Observed: "No evidence this page is part of a templated/programmatic set; it's a single branded landing page (/tribe)"

Expected: The data on the page is the value; it's not an interchangeable template shell.

Recommendation: No action needed unless /tribe is confirmed to be part of a larger templated rollout.

Location: N/A
N/A No two pages share >80% of their field content
Observed: "Single standalone URL audited; no sibling-page corpus provided to compare field-content similarity"

Expected: Cross-page field-content similarity stays under 80%.

Recommendation: No action needed unless this page belongs to a templated set; if so, run a cross-page similarity check.

Location: N/A
N/A Scale governance: review at 100+, justification at 500+
Observed: "No evidence provided of a templated rollout count (100+/500+ pages) that this URL belongs to"

Expected: Templated rollouts past 100 pages have had human review; past 500 have documented justification.

Recommendation: No action needed unless this page is confirmed part of a large templated rollout, in which case verify review/justification records exist.

Location: N/A

Data validation

What this is: Every factual claim on the page that was checked against a source.

How to read it: Verdict is the check's status; a needs-human-verification chip means the model could not settle it alone.

Your action: No claims need manual verification.

Claim	Verdict	Recommendation
10 Crores+ Products Sold	Warn	Add a source or remove the claim
2 Crores+ Customers Bought	Warn	Update to Customer base of over 10 million (1 crore) as of an August 2021 article; no source confirms the current 2 crore+ figure (source: https://www.indianretailer.com/interview/retail-people/startup/how-bewakoof-used-social-media-as-a-tool-to-build-a-d2c-brand.i1879?utm_source=chatgpt.com)

Content gaps

What this is: Topics this page should add, expand or cut, plus where it sits on the information-gain ladder.

How to read it: Each line is one gap and the rule that flagged it.

Your action: No content gaps to close right now.

no content gaps found

Information gain: to

Change list

What this is: The full, ranked list of fails and warns turned into concrete edits.

How to read it: Verify names the check to re-run once the edit ships.

Your action: Work through the 35 changes in priority order

Priority	Type	Target	Detail	Verify
Critical	Fix meta	On-page SEO	A <title> tag exists and contains the target keyword.	Re-run the audit: SR-ONP-01 reads pass
Critical	Fix	Technical SEO	The renderer confirms the raw HTML is not JS-only for the main content.	Re-run the audit: SR-CR-03 reads pass
High	Fix	On-page SEO	Exactly one H1 is present.	Re-run the audit: SR-ONP-02 reads pass
High	Add schema	<head> or before </body>, JSON LD block	See finding	Re-run the audit: SR-SCH-02 reads pass
High	Add internal link	Page body	See finding	Re-run the audit: SR-LNK-03 reads pass
High	Fix	Trust and expertise	An author byline is present and links to an author bio page.	Re-run the audit: SR-EAT-01 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-CITE-02 reads pass
High	Fix	Trust and expertise	About, contact and privacy pages are linked, and the page is served over HTTPS.	Re-run the audit: SR-EAT-03 reads pass
High	Fix	AI answers	At least half of H2 headings are question-shaped.	Re-run the audit: AI-EXT-04 reads pass
High	Fix	Page body	See finding	Re-run the audit: SR-ONP-04 reads pass
High	Add internal link	Page body	See finding	Re-run the audit: SR-LNK-06 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-GATE-02 reads pass
High	Fix	Title / h1	See finding	Re-run the audit: AI-GATE-03 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-01 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-02 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-03 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-ENT-01 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-CITE-01 reads pass
Medium	Add schema	Structured data	Organization/LocalBusiness, BreadcrumbList and WebSite schema are all present.	Re-run the audit: SR-SCH-05 reads pass
Medium	Fix	<head><title>	See finding	Re-run the audit: SR-ONP-12 reads pass
Medium	Fix	Main text	See finding	Re-run the audit: AI-ENT-02 reads pass
Medium	Fix	Main text	See finding	Re-run the audit: AI-GATE-06 reads pass
Critical	Fix	Technical SEO	The canonical tag points to this exact URL.	Re-run the audit: SR-CR-04 reads pass
High	Fix meta	On-page SEO	A meta description exists, 150-160 characters long.	Re-run the audit: SR-ONP-03 reads pass
Medium	Fix	On-page SEO	og:title, og:description and og:image are present.	Re-run the audit: SR-ONP-11 reads pass
High	Add schema	Structured data	At least one valid JSON-LD block is present; an FAQ visible on the page has FAQPage schema.	Re-run the audit: SR-SCH-01 reads pass
High	Fix	Trust and expertise	A reviewer name, credential and last-reviewed date are present (required on YMYL).	Re-run the audit: SR-EAT-02 reads pass
High	Fix stat	Main page content, after products sold metric	See finding	Re-run the audit: data-fc-2 reads pass
High	Fix	AI citations	dateModified is accurate and genuine on freshness-sensitive topics.	Re-run the audit: AI-GATE-05 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-GATE-08 reads pass
Medium	Add internal link	Links	The page has at least one internal link; roughly 4-10 for a ~1,500-word page.	Re-run the audit: SR-LNK-02 reads pass
Medium	Rewrite section	Content quality	Word count is at least 300, or a narrow intent is fully answered.	Re-run the audit: SR-CNT-02 reads pass
Medium	Add schema	Structured data	Exactly one visible date; both datePublished and dateModified are in JSON-LD and consistent.	Re-run the audit: SR-SCH-07 reads pass
Medium	Fix	Freshness	A visible, accurate last-updated date exists and is under 18 months old.	Re-run the audit: SR-FR-01 reads pass
Medium	Fix stat	Main page content, after LOGIN	See finding	Re-run the audit: data-fc-1 reads pass

What changed

What this is: How this audit compares to the last one for the same page.

How to read it: Rule ids move between four buckets: fixed, regressed, new, or still standing.

Your action: Nothing to compare yet; this becomes useful on the next audit.

first audit of this page

Evidence and glossary

What this is: Every degraded or skipped step during this audit, plus the terms used above.

How to read it: An evidence line names what could not be measured and why.

Your action: Weigh the scores above against these gaps before treating them as final.

Evidence

renderer ran, JS dependency full.
Core Web Vitals not measured: no performance service connected; run PageSpeed Insights by hand.
backlinks measured via dataforseo: 6176 referring domains.
orphan status and click depth unknown: no crawl export.
robots.txt fetched.
sitemap: 61432 URLs, includes this page: yes.
citability sample is one engine (web search plus this company's model), directional only, on 2026-09-18.
content step failed: The OMA app's model executor restarted while this step was running..

Glossary

AEO: Answer Engine Optimization: making a page easy for an AI answer engine to quote directly.
GEO: Generative Engine Optimization: earning a citation inside a generative model's own answer, not just a search result.
Hard gate: A rule whose failure blocks the overall score outright rather than just lowering it.
Needs data: A check that could not run for lack of a measurement; not a pass and not a fail.
Citability sample: A small, directional set of AI-answer probes, not a statistically representative survey.
Information-gain ladder: The rungs from a bare mention to the deepest, most original coverage of a topic, used to grade content depth.
The eight journey stages: discovery, comparison, validation, fear/risk, community, transactional, post-purchase, troubleshooting: the stages a buyer moves through.