Implementation report: https://www.bewakoof.com/ (homepage)
Something on your homepage is stopping it from being read properly right now: your real content only exists after JavaScript runs, and not every crawler waits for that. The overall score is 55 out of 100, rated as having critical issues present. There are 27 things worth fixing below, ordered from most to least valuable.
The 5 biggest problems (fix these first)
1. Google may only be seeing 10 words of your homepage, not your real content
Current: Crawlers see 10 words before JavaScript runs, 28 after
When a search engine or AI tool first grabs your page, some read only the raw HTML before any JavaScript runs. If your real homepage content is injected by JavaScript afterward, those tools can end up seeing almost nothing, even though a browser shows a full page. That's a direct risk to whether this page gets indexed and ranked at all.
Fix:
- Check whether your homepage's main content (hero, categories, copy) appears in the raw HTML response, not just after the page's JavaScript runs.
- If it's JavaScript-only, turn on server-side rendering or static generation for the homepage so the real content is present before any script executes.
- Confirm it worked by viewing the page's raw source (not "inspect element") and checking your real copy is there.
Who: a developer, likely a few days depending on how the site is built.
2. Your homepage opens with menu links, not a sentence that says what you sell
Current: Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 2 Crores+ Customers Bought 10 Crores+ Products Sold MEN WOMEN [28 words]
Both Google and AI assistants look for a clear opening statement to work out what a page is for. Right now all they find is navigation labels, nothing that says this is a fashion retailer for men and women. That costs you rankings for "online fashion shopping" and any chance of being quoted by an AI assistant.
Fix: add a heading and a short opening line stating the offer, before any menu text.
Online Fashion Shopping for Men and Womenas the headingShop the latest men's and women's fashion online: clothing, footwear and accessories from hundreds of brands, with easy returns and store pickup nationwide.as the opening line
Who: a writer, about 30 minutes to draft; a developer under an hour to place it.
3. There's no main heading on the page at all
Current: no H1 found
The main heading (H1) is the strongest single signal telling Google what a page is about. Without one, the page has nothing pinning it to "fashion shopping," which weakens every other ranking signal on the page.
Fix:
- Add exactly one heading tag to the template, positioned as the very first heading in the page.
- Use the wording drafted in problem 2 above.
- Confirm only one such heading exists on the page.
Who: a developer, under an hour once the wording exists.
4. Search engines have no structured data telling them this is a store
Current: "jsonld":[] (no structured data of any type present)
Structured data (schema: a hidden code snippet describing your business) tells Google "this is a retailer, here's the name, logo and search box." Without it, you're not eligible for the extra search features, like a site search box under your listing, that competitors with schema can get.
Fix:
- Add a JSON-LD code block to the page's head with type "Organization" (name, logo, url, social links) and "WebSite" (url, plus a search action).
- Test it with Google's Rich Results Test tool.
- Confirm the type matches your business: a retail storefront.
Who: a developer, about half a day including testing.
5. With no body copy, there are no links guiding shoppers to your key categories
Current: Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 2 Crores+ Customers Bought 10 Crores+ Products Sold MEN WOMEN
Links inside real sentences (not the top menu) help both shoppers and Google understand how your pages relate to each other. With zero body copy, there's nothing to link from, so your category pages get no extra signal from the homepage.
Fix:
- Once the copy from problems 2 and the new sections below exists, link each category name at its first mention: "Men's" to /men-clothing, "Women's" to /women-clothing, "Accessories" to /accessories.
- Keep these separate from the top navigation links.
- Confirm each key category gets at least one such link from the homepage body.
Who: a developer, about an hour once a writer supplies the copy.
Also worth fixing
For a developer
- No baseline structured data at all: add the standard trio (Organization, BreadcrumbList and WebSite) alongside the schema fix in problem 4.
- No canonical tag: add a self-referencing canonical tag pointing to
https://www.bewakoof.com/in the page head, so search engines don't split ranking credit across URL variants. - No JSON-LD anywhere: once problem 4's schema is added and validated, this passes too; if you ever add an FAQ section, give it its own schema.
- No dates in your structured data: once JSON-LD exists, add a "date modified" and "date published" field that match a single visible date on the page.
For a writer
- No author byline anywhere on the page: add a name and credential, linked to a bio page.
- About, contact and privacy pages aren't linked from the homepage: add visible links to them, a footer is fine.
- No question-shaped headings for AI tools to quote: add sections like
Which fashion brands does Bewakoof carry?so an AI assistant has a clean sentence to lift. - No section headings at all, so the page has no scannable structure: add headers below the hero, for example
Shop Men's Fashion,Shop Women's Fashion,Why Shop at Bewakoof. - Your "2 Crores+ Customers" and "10 Crores+ Products Sold" badges have no date: add a timestamp, for example "as of [your real figure]," and refresh it on a set schedule.
- Those same two numbers have no source: add a date and a link to a page (About or investor page) that backs them up, or remove them.
- "2 Crores+ Customers Bought" has no source: add a source or remove the claim.
- "10 Crores+ Products Sold" has no source: add a source or remove the claim.
- Your meta description is far too long: current is
Online Shopping Site for Men, Women & Accessories. Choose from the best in Men Clothing and Women Fashion Wear. Trendiest designs and styles available at Bewakoof.com. Select from a diverse range of clothes online. Shop from the best online shopping site for clothes. Free Shipping, Easy Returns, COD Available![311 characters]. Replace with something likeShop trendy fashion for men, women and accessories online at Bewakoof: quality clothing, free shipping, easy returns and cash on delivery., keeping it between 140 and 160 characters. - Your title is 66 characters, a bit long: replace
Online Fashion Shopping for Men, Women, Accessories - Bewakoof.comwithBewakoof: Trendy Men's & Women's Fashion Online, keeping it under 60 characters. - That same long, generic title risks Google rewriting it in search results: the shorter title above,
Bewakoof: Trendy Men's & Women's Fashion Online, fixes this too by being specific rather than a generic category list. - No reviewer name or last-reviewed date: this matters most on medical, legal or financial pages; your page isn't flagged as one of those, but add it if you want the extra trust signal.
- Your keyword phrase doesn't appear in the first 100 words: once the opening line from problem 2 is added, work "fashion shopping" naturally into it and this is fixed.
- No genuine "last updated" date shown anywhere: add one once it exists, and keep it accurate.
- Only 28 words of real content on the whole homepage: aim for at least 300 words of real copy (category intros, featured collections, why shop here) beyond menu labels.
- Your "Offers" menu link doesn't say if deals are current: add an offer validity date or a last-refreshed timestamp near it.
For you
- Nothing on this homepage that a competitor doesn't also have: decide whether to invest in something genuinely original, like a real "trending this month" or best-seller module, or dated brand-scale numbers with a source. That's what it takes to be picked up as a citation by Google or an AI assistant instead of a content-rich competitor page.
What to add to the page
- A heading and opening paragraph stating what's sold, for whom, and why shop here.
- Roughly 300 words of real homepage copy beyond nav labels: category intros, featured collections, why-shop-here.
- Proper written sections for Men, Women and Accessories, not bare menu links.
- Dates and sources for the customer and product-sold counters.
- A visible freshness signal (an offer window or last-updated date) near the Offers link.
- A stated, disclosed refresh schedule for your growth and sales statistics.
- A genuine original data feature, such as a sourced "trending this month" or best-seller module with sample size and date range.
What is already working
- Robots.txt is set up correctly and lists your sitemap for search engines to find.
- The page is indexable: no noindex tag, Googlebot isn't blocked, and AI retrieval crawlers are allowed too.
- All 7 images carry descriptive alt text and filenames.
- You have 6,176 referring domains and 26,634 backlinks pointing at the site.
- The homepage is in your sitemap, loads cleanly at its final URL, and has no redirect chain.
How AI assistants see this page
This run couldn't test how AI assistants actually answer these queries (the check failed because no browser session was available), so there's no live answer or score to show today. In general, tools like ChatGPT, Perplexity, Gemini, Claude, and Google's AI Overviews and AI Mode fetch a page's content and quote back a short passage when it directly answers a question. Given how little written content this homepage currently has (see problems 1 and 2), there would be little for them to quote even once tested.
Try these by hand:
- "best online fashion shopping men women" on: a web search plus AI model, ChatGPT, Copilot, Perplexity, Google AI Overviews, Google AI Mode, Gemini and Claude.
- "what is online fashion shopping men women" on the same eight.
Claims to double check
2 Crores+ Customers Bought: no source found for this figure. Add a source or remove it.10 Crores+ Products Sold: no source found for this figure. Add a source or remove it.
What we could not measure
Page speed (Core Web Vitals) wasn't measured this run, no performance service is connected; run it free at pagespeed.web.dev. Whether this page is an orphan or how many clicks deep other pages sit wasn't measured either, that needs a full site crawl export (Google Search Console's coverage report is a free starting point). AI-assistant answers weren't tested this run due to a technical failure on our end; use the manual checks above in the meantime.
No claims ledger exists yet for Bewakoof. Once one does, this skill can check specific product, pricing and customer claims directly instead of just flagging the two numbers above as unsourced.
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 Title present, keyword-bearing, not stuffed: title "Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com" present, contains keyword "online fashion shopping men women"
- Pass Heading hierarchy valid, no skipped levels: 0 H1, 0 H2, 0 H3
- Pass URL slug flat, lowercase, hyphenated, keyword-bearing: URL path: "/"
- Pass Image alt present on all images: all 7 images carry alt text
- Pass Image filenames descriptive, hyphenated, lowercase: image filenames are descriptive
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 developer Main content present in server-rendered raw HTML See finding
- content Direct answer up top (BLUF) 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 13 failing checks first, then the 14 warnings
| Dimension | Score | Measured of applicable | Weight |
|---|---|---|---|
| Technical SEO | 79 | 8 of 10 | 18 |
| On-page SEO | 71 | 13 of 13 | 16 |
| Content quality | 41 | 5 of 5 | 12 |
| Structured data | 44 | 5 of 5 | 14 |
| Links | 64 | 3 of 4 | 16 |
| Performance | incomplete | 0 of 8 | 10 |
| Trust and expertise | 18 | 3 of 3 | 8 |
| Freshness | 31 | 3 of 3 | 6 |
| Data | 50 | 2 of 2 | 8 |
Technical SEO
- Fail Main content present in server-rendered raw HTML
Observed: "Crawlers see 10 words before JavaScript runs, 28 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 "https://www.bewakoof.com/" is identical to the requested url, http_status 200"
Expected: Any redirect chain into this URL is a single clean 301/308, same protocol.
Recommendation: Periodically verify with a redirect-chain tool (e.g. httpstatus.io) that http://, non-www, and any legacy URLs 301 straight to this HTTPS URL in one hop.
Location: https://www.bewakoof.com/
- Pass robots.txt well-formed, does not block CSS/JS, declares a sitemap
Observed: "robots.txt fetched (status 200); all listed bots allowed via wildcard; 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: Manually spot-check the raw robots.txt for any Disallow rule on /static/, /assets/, *.js or *.css paths, since only bot-level allow results (not path rules) were available here.
Location: https://www.bewakoof.com/robots.txt
- Pass URL is in the sitemap, reachable in <=3 clicks, not orphaned
Observed: "sitemap includes_url: true (https://www.bewakoof.com/sitemap_index.xml, 61,432 URLs)"
Expected: The URL appears in the XML sitemap and is reachable within three clicks of the homepage.
Recommendation: No action needed; keep the homepage listed in sitemap_index.xml.
Not measured this run (3)
- Needs data No crawl traps: session-ID or internal-search links, unmanaged parameters
Observed: "internal_hrefs on this page: ["/","/men-clothing","/women-clothing","/accessories","/login","/wishlist"] — no session IDs or search params visible here"
Expected: No session-ID or internal-search links; faceted URLs are canonicalized or noindexed.
Recommendation: Crawl the /men-clothing, /women-clothing and /accessories facet/filter URLs to confirm they carry canonical tags back to the clean category URL or are noindexed.
Location: site-wide category/filter navigation (not visible from homepage sample)
- N/A Paginated pages self-canonicalize
Observed: "Page is the homepage ("/"), not part of a paginated series"
Expected: A paginated page canonicalizes to itself, never to page 1, and is never blanket-noindexed.
Recommendation: n/a
Location: https://www.bewakoof.com/
- Needs data No cloaking, no near-duplicate/staging mirror
Observed: "js_dependency "full": raw HTML has 10 words vs 28 rendered words; no cached/indexed snapshot or staging-domain check was available"
Expected: What's served matches what's indexed; no staging mirror or near-duplicate exists.
Recommendation: Use Search Console URL Inspection → "View Crawled Page" to compare Google's rendered snapshot with the live DOM, and confirm no staging/preview subdomain is indexable.
Location: https://www.bewakoof.com/
On-page SEO
- 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 anywhere on the page"
Expected: Each H2 covers a distinct sub-question in the reader's own words.
Recommendation: Add H2-level section headers below the hero, e.g. "Shop Men's Fashion", "Shop Women's Fashion", "Why Shop at Bewakoof", instead of leaving the page headingless.
Location: homepage body, below the hero banner
How to verify: Re-run the audit: SR-ONP-04 reads pass
- Warn Title length 50-60 chars
Observed: "title "Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com" is 66 chars"
Expected: Title is 50-60 characters long.
How to verify: Re-run the audit: SR-ONP-01b reads pass
- Warn Meta description unique, 150-160 chars, keyword present
Observed: "meta description is 311 chars: "Online Shopping Site for Men, Women & Accessories. Choose from the best in Men Clothing and Women Fashion Wear. Trendiest designs and styles available at Bewakoof.com. Select from a diverse range of clothes online. Shop from the best online shopping site for clothes. Free Shipping, Easy Returns, COD Available!""
Expected: A meta description exists, 150-160 characters long.
How to verify: Re-run the audit: SR-ONP-03 reads pass
- Warn Primary keyword naturally within the first 100 words
Observed: "keyword "online fashion shopping men women" does not appear in the first 100 words"
Expected: The keyword appears within the first 100 words.
How to verify: Re-run the audit: SR-ONP-07 reads pass
- Warn Title-rewrite risk: not so long/generic/stuffed the engine replaces it
Observed: ""Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com" (66 characters)"
Expected: The title is specific and well-formed enough that Search Console shows it unrewritten.
Recommendation: Shorten the homepage <title> to ~55-60 characters, leading with the brand name and one clear differentiator.
Location: <title> tag
Before: Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com
After: Bewakoof: Trendy Men's & Women's Fashion OnlineHow to verify: Re-run the audit: SR-ONP-12 reads pass
- Pass Title present, keyword-bearing, not stuffed
Observed: "title "Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com" present, contains keyword "online fashion shopping men women""
Expected: A <title> tag exists and contains the target keyword.
- 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: "/""
Expected: The URL path is lowercase, hyphenated, with no dates/IDs/params.
- Pass Image alt present on all images
Observed: "all 7 images carry alt text"
Expected: Every image carries alt text (empty alt is fine for a decorative image).
- Pass Image filenames descriptive, hyphenated, lowercase
Observed: "image filenames are descriptive"
Expected: Image filenames are descriptive, hyphenated, lowercase.
- Pass Open Graph + Twitter card present
Observed: "og:title, og:description, og:image present"
Expected: og:title, og:description and og:image are present.
- Pass Body density natural, no confirmed keyword stuffing
Observed: "keyword_stats: density_pct 0, count 0 across 28 rendered words"
Expected: Keyword density reads naturally; >2% warns, confirmed stuffing across headings/alt/sentences fails.
Recommendation: No stuffing fix needed; address the underlying thin-content gap (see word-count finding) by adding real, naturally-written body copy.
Location: rendered homepage text
Content quality
- Fail Direct answer up top (BLUF)
Observed: "Full extracted main_text (28 words) is entirely nav/UI chrome: 'Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 2 Crores+ Customers Bought 10 Crores+ Products Sold MEN WOMEN' — no H1, no H2, no lead paragraph of any kind."
Expected: First paragraph directly answers the query intent (what's sold, for whom, why shop here) with no throat-clearing.
Recommendation: Add an H1 and a 1-2 sentence lead stating the core offer (categories, audience, value proposition) before any nav/UI text.
Location: top of page / missing H1
Before: Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 2 Crores+ Customers Bought 10 Crores+ Products Sold MEN WOMEN
After: Shop the latest men's and women's fashion online — clothing, footwear and accessories from hundreds of brands, with easy returns and store pickup nationwide.How to verify: Re-run the audit: SR-CNT-01 reads pass
- Fail Fact-density adequate on claim-making pages
Observed: "Page states '2 Crores+ Customers Bought' and '10 Crores+ Products Sold' with no date, no citation, and no link to a verifiable source."
Expected: Claim-making sections carry sourced data points, not bare assertions.
Recommendation: Attach a date and source to both figures, or link to a verifiable page (About/investor page) backing the numbers.
Location: trust counters near top of page
Before: 2 Crores+ Customers Bought 10 Crores+ Products Sold
After: Over 2 crore customers have shopped with us and 10+ crore products have been sold as of March 2026 (source: internal transparency report).How to verify: Re-run the audit: SR-CNT-09 reads pass
- Warn Depth matches intent; under 300 words is thin
Observed: "28 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 Comparisons as real HTML tables, steps as ordered lists
Observed: "0 tables, 2 lists present"
Expected: Tabular comparisons use a real <table>; sequential steps use an ordered list.
- Pass No invisible watermark chars; em-dash frequency <=4/1,000w
Observed: "0 em-dashes over 28 words (0.0/1,000w)"
Expected: No invisible watermark characters; at most 4 em-dashes per 1,000 words.
Not measured this run (5)
- 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.
- N/A Not thin/padded, density over length
Observed: "Only 28 words are present and all of it is navigational/UI labels and counters — there is no prose section to evaluate for padding versus density."
Expected: Substantive sections carry information proportional to their length; no filler.
Recommendation: Once body copy is added, audit it for density before publishing — avoid restating the same value proposition across multiple sections just to add length.
- N/A Readability in the audience band
Observed: "No full sentences exist in the extracted text, only nav labels and numeric badges (e.g. 'Track Order', '2 Crores+ Customers Bought')."
Expected: General-web reading ease roughly grade 8-10; no sentence over 35 words.
Recommendation: Re-score readability once the lead paragraph and category copy exist.
- N/A Varied sentence rhythm (burstiness)
Observed: "No sentences present to assess for length variation — content is a flat list of nav/UI strings."
Expected: Sentence length varies; page doesn't read as flat, unedited machine text.
Recommendation: Assess sentence rhythm once real paragraphs are written.
- N/A AI-writing tells within the light-edit band
Observed: "No prose exists to scan for AI-writing tells (e.g., hedging phrases, listicle throat-clearing) — only UI labels."
Expected: Fewer than 6 AI-writing-tell flags per 1,000 words.
Recommendation: Run the AI-tell check as part of QA once the new homepage copy is written.
Structured data
- 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 of any type present"
Expected: The primary @type matches the page's purpose (Article/Product/LocalBusiness/FAQPage/...).
Recommendation: Add JSON-LD Organization and WebSite (with SearchAction) schema in the <head>, matching the homepage's e-commerce storefront purpose.
Location: <head>, JSON-LD
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 blocks exist to compare against visible content"
Expected: Schema name/headline/author overlaps the visible content by at least 60%; no schema-only FAQs/ratings.
Recommendation: Once Organization/WebSite schema is added, ensure its "name" matches the visible brand "Bewakoof" and no fabricated ratings/FAQ content is included.
Location: <head>, JSON-LD
Links
- Fail Contextual body links first-mention, one link per concept
Observed: "main_text: "Offers Fanbook Download App Find a store near me Contact Us Track Order MEN WOMEN ACCESSORIES | LOGIN 2 Crores+ Customers Bought 10 Crores+ Products Sold MEN WOMEN""
Expected: Contextual body links appear at first mention; nav/footer links don't count.
Recommendation: Add an introductory body section (e.g. featured-category or "About Bewakoof" copy) with genuine first-mention contextual links to key collection pages, distinct from the top nav.
Location: homepage body
How to verify: Re-run the audit: SR-LNK-03 reads pass
- Pass Body internal-link count scales with length
Observed: "6 internal, 0 external links"
Expected: The page has at least one internal link; roughly 4-10 for a ~1,500-word page.
- Pass No broken internal links or redirect chains, not nofollowed
Observed: "6 internal links, 0 of 0 external links nofollowed"
Expected: Internal links resolve directly and are not nofollowed.
Not measured this run (3)
- 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: "Only global nav anchors exist: "MEN", "WOMEN", "ACCESSORIES", "LOGIN""
Expected: Anchor text is varied and descriptive; no generic "click here" or exact-match stuffing.
Recommendation: Once contextual body links are added (see SR-LNK-03), vary their anchor text descriptively rather than repeating exact category names verbatim.
Location: global navigation
- N/A Outbound links working, authoritative, to primary sources
Observed: "external links: 0, external_hrefs: []"
Expected: Outbound links resolve and point to authoritative, primary sources.
Recommendation: No action needed for the homepage; apply this check to blog/guide content pages that make factual claims instead.
Location: n/a
Trust and expertise
- 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: "image alt "official collabs" banner present; no visible affiliate/sponsorship disclosure text found"
Expected: Affiliate or commercial relationships are disclosed above the fold.
Recommendation: No action needed unless the "official collabs" banner represents a paid brand partnership requiring disclosure; confirm with the brand partnerships team.
Location: homepage hero banner
- N/A No regulatory superlatives on regulated topics
Observed: "Page sells fashion apparel/accessories; run classified as non-YMYL"
Expected: No "best/guaranteed" language on regulated finance/health topics; required disclosures present.
Recommendation: n/a
Location: n/a
- N/A E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
Observed: "No on-page Trust/Expertise/Authority/Experience roll-up, badge, or score is displayed anywhere in the rendered content"
Expected: A banded Trust 30 / Expertise 25 / Authority 25 / Experience 20 roll-up, honestly labeled a quality concept.
Recommendation: No page change needed; this criterion governs how the audit itself presents its E-E-A-T verdict, not the page's own content.
Location: n/a
Freshness
- Fail No outdated statistics on a dynamic topic
Observed: "The '2 Crores+ Customers' / '10 Crores+ Products Sold' counters carry no date stamp, so currency can't be verified — they may be static figures reused indefinitely."
Expected: Statistics on a dynamic (sales/customer-growth) topic are current and dated, feeding the fact-check.
Recommendation: Timestamp these counters (e.g., 'as of [month/year]') and refresh on a defined, disclosed cadence.
How to verify: Re-run the audit: SR-FR-03 reads pass
- 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
- Warn Freshness-sensitive (QDF) topics are genuinely recent
Observed: "An 'Offers' nav entry implies time-sensitive promotions, but no visible date, 'last updated' marker, or offer-validity window appears anywhere in the extracted content."
Expected: Evergreen topics need at least an honest date; promo/QDF content needs genuine currency signals.
Recommendation: Show offer validity dates or a last-refreshed timestamp at or near the Offers entry point.
How to verify: Re-run the audit: SR-FR-02 reads pass
Performance
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 answers
- 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
AI citations
- Fail Information gain: a sourced specific the consensus lacks
Observed: "The only content is nav chrome plus two undated, unsourced counters — no named/dated example, no expert quote, no aggregated original data with sample size or date range. This sits below L1 (doesn't even organize public facts into prose). Note: the competitor set itself is noisy — one result is a broken/scraped JS snippet and one (a Demon's Souls armor wiki) is topically unrelated to fashion, which weakens confidence in the exact 'ideal page' shape but not in the conclusion that this page has no information gain."
Expected: Commercial, high-competition homepage should climb to information-gain ladder L3+ (aggregated original data with sample size and date range) to pass the hard gate.
Recommendation: Add genuine original data — e.g., an internally-aggregated 'trending categories this month' or 'top sellers' module disclosing sample size and date range — or publish sourced, dated brand-scale metrics (customers served, SKU count, average return rate) refreshed on a stated cadence. Do not fabricate figures; source from actual internal analytics and disclose the collection window.
How to verify: Re-run the audit: AI-GATE-04 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
- 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.
Programmatic pages
Not measured this run (3)
- N/A Every page carries genuinely unique data
Observed: "Page type: single homepage URL ("/"), not one of a templated set"
Expected: The data on the page is the value; it's not an interchangeable template shell.
Recommendation: n/a
Location: https://www.bewakoof.com/
- N/A No two pages share >80% of their field content
Observed: "Page type: single homepage URL, not part of a templated rollout"
Expected: Cross-page field-content similarity stays under 80%.
Recommendation: n/a
Location: https://www.bewakoof.com/
- N/A Scale governance: review at 100+, justification at 500+
Observed: "Page type: single homepage URL, not part of a templated rollout"
Expected: Templated rollouts past 100 pages have had human review; past 500 have documented justification.
Recommendation: n/a
Location: https://www.bewakoof.com/
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 |
|---|---|---|
| 2 Crores+ Customers Bought | Warn | Add a source or remove the claim |
| 10 Crores+ Products Sold | Warn | Add a source or remove the claim |
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: Close the 7 gaps listed below
- Add: H1 plus a lead paragraph stating what's sold, for whom, and the core value proposition
- Add: At least ~300 words of real homepage body copy beyond nav labels (category intros, featured collections, why-shop-here)
- Expand: Descriptive category sections for Men / Women / Accessories rather than bare nav links
- Add: Dates and sources for the '2 Crores+ customers' and '10 Crores+ products sold' trust counters
- Add: Visible freshness signal (offer validity window or last-updated date) near the Offers nav entry
- Add: Defined, disclosed refresh cadence and timestamp for growth/sales statistics
- Add: Original, sourced data module (e.g., trending categories/best-sellers with sample size and date range) to reach information-gain L3
Information gain: Sub-L0 — the page contains no organized informational content at all, only navigational/UI labels and two undated, unsourced numeric trust badges; it does not even reach L1 (organizing public facts). to L3 — aggregated original data with a disclosed sample size and date range (e.g., a sourced 'trending this month' or best-seller module, or dated, sourced scale metrics), which is the floor expected for a commercial, high-competition homepage.
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 27 changes in priority order
| Priority | Type | Target | Detail | Verify |
|---|---|---|---|---|
| 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 |
| Critical | Rewrite section | Top of page / missing H1 | See finding | Re-run the audit: SR-CNT-01 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>, JSON LD | See finding | Re-run the audit: SR-SCH-02 reads pass |
| High | Add internal link | Homepage 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 | 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 | Homepage body, below the hero banner | See finding | Re-run the audit: SR-ONP-04 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 |
| High | Fix | AI citations | See finding | Re-run the audit: AI-GATE-04 reads pass |
| Medium | Fix | Freshness | See finding | Re-run the audit: SR-FR-03 reads pass |
| Medium | Rewrite section | Trust counters near top of page | See finding | Re-run the audit: SR-CNT-09 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 meta | On-page SEO | Title is 50-60 characters long. | Re-run the audit: SR-ONP-01b 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 | On-page SEO | The keyword appears within the first 100 words. | Re-run the audit: SR-ONP-07 reads pass |
| High | Fix | AI citations | dateModified is accurate and genuine on freshness-sensitive topics. | Re-run the audit: AI-GATE-05 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 | Fix | <title> tag | See finding | Re-run the audit: SR-ONP-12 reads pass |
| Medium | Fix | Freshness | See finding | Re-run the audit: SR-FR-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 | Header section | See finding | Re-run the audit: data-fc-1 reads pass |
| Medium | Fix stat | Header section | See finding | Re-run the audit: data-fc-2 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.
- AI visibility step failed: No desktop is online for org cmu5ok66k0001qc07q82za632, user cmu5ok66b0000qc074t0wn8dg.
- citability sample is one engine (web search plus this company's model), directional only, on 2026-09-18.
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.