Implementation report: https://www.bewakoof.com/design-of-the-day

Something is stopping this page from being found at all: crawlers can barely see any content here before your code runs. We audited https://www.bewakoof.com/design-of-the-day and it scores 66 out of 100, flagged as "Critical issues present" because at least one problem blocks results outright. There are 29 things worth fixing in total; the 5 below matter most and are ordered first.

The 5 biggest problems (fix these first)

1. Google sees almost nothing when the page first loads, so it may not rank at all

Current: Crawlers see 11 words before JavaScript runs, 395 after

Google and AI crawlers often read the raw code sent by your server before any JavaScript runs. Right now that raw code has only 11 words, everything else appears only after JavaScript finishes. If a crawler doesn't wait for that, it sees a nearly empty page, which is a critical block on ranking or being cited anywhere.

Fix:

Confirm the page uses client-side rendering (content built by JavaScript in the browser).
Set up server-side or static rendering for /design-of-the-day so the product grid and any text appear directly in the first HTML response.
Check it worked by viewing the page source (not the rendered page) and confirming the product names appear without running JavaScript.

Who: A developer, likely 1 to 3 days depending on your current setup.

2. Your page never explains what "Design of the Day" actually is

Current: MEN WOMEN ACCESSORIES | LOGIN FREE SHIPPING on all orders above ₹399 Home Design Of The Day Design of The Day 2 Products Sort by : Popularity Filters...

Both Google and AI assistants look for a plain sentence near the top that answers what a visitor searching "design day shop new t" actually wants to know. Right now the first thing anyone (or any crawler) reads is navigation and filter labels, with no sentence saying what the program is. That costs you both relevance matching and the chance of ever being quoted as an answer.

Fix: Add this directly under the H1, before the filters: Design of the Day is Bewakoof's daily t-shirt drop: a new graphic tee goes live for 24 hours, then it's gone. Shop today's design before it sells out. Keep it to 1 to 3 sentences.

Who: A writer, about 30 minutes.

3. Your links don't tell Google or AI what this page connects to

Current: no body/prose copy with inline links; all 6 internal links are header/mega-menu/footer navigation (Home, Men, Women, Accessories, category footer links)

Links placed inside real sentences act as signals tying one topic to related ones. All 6 links on this page are nav or footer chrome, so none of them tell a search engine what "design of the day" relates to.

Fix:

Add the intro paragraph from problem 2 as real content on the page.
Inside it, link the first mention of "t-shirts" or "oversized tees" to your matching collection pages.
Check it worked by viewing the page source and confirming those links sit inside the paragraph text, not the nav bar.

Who: A developer working with a writer, under an hour once the paragraph exists.

4. No one is credited for this page, which hurts how much Google and AI trust it

Current: no author byline found

Google rewards pages that show who stands behind them and why they're qualified. A page with no named voice looks automated and is trusted less, both for ranking and for being quoted by AI tools.

Option A: add a simple byline like "Curated by Bewakoof's Design Team" linking to an About or team page. Gains a quick, low-cost fix. Costs a bit of personal credibility versus a named individual.

Option B: assign a specific writer to author this and similar pages by name with a short bio. Gains stronger trust and citability. Costs ongoing time to maintain.

The evidence favors Option A: this is a commercial listing page, not a health or finance page, so a lightweight team credit is enough to clear the bar without new hiring.

Who: A writer or marketing lead, about 15 minutes.

5. There are no headings guiding readers or AI to any answer on this page

Current: no H2 headings found

AI assistants and Google's answer boxes favor pages broken into clear, question-shaped subheadings, because they can lift one section as a standalone answer. With zero subheadings here, there's nothing an AI engine could confidently show someone who asks about this.

Fix: Add sections with headings such as What is Design of the Day?, How often does the design change?, and Today's featured design, each followed by 2 to 3 direct sentences.

Who: A writer, 1 to 2 hours.

Also worth fixing

For a developer

Your structured data is missing basic trust markup: add Organization, BreadcrumbList and WebSite schema so Google can build trust panels and breadcrumbs.
Your page carries no verifiable dates: add datePublished and dateModified to your structured data, matching one visible date on the page.

For a writer

Your title doesn't include the words people search: current title Shop New T-shirt Design Everyday Online in India | Bewakoof (59 chars) doesn't contain the inferred keyword "design day shop new t"; confirm the real target keyword, then rework the title around it, staying under 60 characters, e.g. Design of the Day: New T-Shirt Drop Daily | Bewakoof.
Your meta description is just short of the ideal length: current text is Shop a new design every day starting at Rs.259 from Bewakoof. Special launch price for 24 hrs only on quirky & high quality Tees. Free Shipping. COD. (149 chars); expand it to land between 150 and 160 characters, e.g. Shop a new t-shirt design every day starting at Rs.259 from Bewakoof. Special launch price for 24 hrs only on quirky, high quality tees. Free shipping, COD available.
Your keyword never appears in the first 100 words: use the opening paragraph from problem 2 so it shows up naturally near the top.
There's nothing on this page an AI engine could quote and trust: add one attributed, linked claim about the program, e.g. a link to Bewakoof's About page.
No paragraph here can stand alone as an answer: write a 2 to 4 sentence explainer answering "What is Design of the Day at Bewakoof?" without relying on surrounding nav text.
Your explanations never name the subject: say "Bewakoof's Design of the Day" by name instead of "it" or "this".
A sourced claim needs its source right next to it: once added, keep the source name or link in the same sentence as the claim.
Your stats have no source anyone can check: figures like "72% OFF" and "4.7M People like this" carry no source or date; add one inline, e.g. 4.7M Facebook followers (Bewakoof official page, as of Sep 2026).
Most of the page's word count is just sitewide footer links: the footer link list ("Men's Pajamas Men's Boxer Shorts...") isn't real content; keep it as standard navigation and add real on-topic copy instead.
Your facts read as filter labels, not sentences: add lines like "Bewakoof releases a new Design of the Day t-shirt every 24 hours" instead of leaving everything as facet labels.
"Day" and "Week" contradict each other: the H1 says Design of The Day but both products are labeled DESIGN OF THE WEEK with no date anywhere; pick one name and show a refresh date near the H1, e.g. Design of the Week, updated Sep 15, 2026.
No one is credited for reviewing this page: add a reviewer name, credential and last-reviewed date.
There's no date showing this page is current: add an accurate dateModified.
Your H1 doesn't say who you are: current H1 is Design of The Day; change it to Design of The Day: New T-Shirts & Hoodies at Bewakoof so the brand and product type are clear right away.
Bewakoof isn't named until deep into the page: open the body copy with a brand-naming sentence before any filter or navigation text.
The "Buy 3 get 10% off" offer has no source: add a source or remove the claim (Women's T-shirt product offer section).
The 72% OFF badge has no source: add a source or remove the claim (Stranger Things Women's Jet Black T-shirt listing).
The 59% OFF badge has no source: add a source or remove the claim (Stranger Things Men's Fudgesickle Brown Hoodie listing).
The 15 day return policy claim has no source: add a source or remove the claim (footer).
No independent site backs up your figures: not urgent for a listing page, but once editorial claims are added, seek outside coverage that corroborates them.

For you

This page has nothing unique a competitor's listing doesn't already have: it's two products in a filter shell, with no dated release info, real sales numbers, or a quote from your team. Option A: invest in one dated, sourced detail per drop (real release date or verified units sold), which meaningfully helps AI engines and Google treat this as more than a generic listing. Option B: leave it as a plain product listing and accept it won't be a strong candidate for AI answers. The evidence favors Option A since the page already frames itself as a recurring drop, though note the competitor pages supplied for comparison didn't actually match this keyword, so there's no outside benchmark yet.

What to add to the page

Add: a short intro under the H1 explaining what "Design of the Day" is and how often it refreshes.
Add: a visible freshness marker that resolves the "Day" versus "Week" naming conflict.
Expand: per-product design story (collaboration background, release date, fabric or fit notes) for each of the two featured items, beyond just title and price.
Add: one sourced, dated specific per drop, such as a real release date, verified units sold, or a quote from the design team.
Cut: reliance on the large sitewide footer link list as if it were page content; keep it as standard navigation only.
Add: a periodic check that the listed prices and discounts are still accurate.

What is already working

Loads securely and lets search engines index it: HTTP 200 over https, no noindex, Googlebot not blocked.
Has one clean, self-referencing canonical URL and a correctly sized title (59 characters).
Your structured data matches what's on the page: the schema name "Design of The Day" matches the H1, and the schema description matches the meta description word for word.
Already has real link authority: 6,176 referring domains and 26,634 backlinks.
No keyword stuffing and no invented numbers: your discount and follower figures read as ordinary store data, not fabricated claims.

How AI assistants see this page

AI visibility score: 0 out of 100, based on 2 questions tested. For "best design day shop new t," the answer said: "The search results don't contain information about design day shops or t-shirt retailers in India." For "what is design day shop new t," the answer said: "The search results contain nothing about 'Design Day Shop' or a product matching 'design day shop new t'." This comes from one engine tested on one date (Sep 18, 2026), so treat it as directional only.

Try these by hand: chatgpt, copilot, perplexity, ai_overviews, ai_mode, gemini and claude, each with the query "best design day shop new t," and again with "what is design day shop new t."

Claims to double check

"72% OFF": no matching source found. Add a source or remove the claim.
"59% OFF": no matching source found. Add a source or remove the claim.
"15 Days Return Policy": no matching source found. Add a source or remove the claim.
"Buy 3 get 10% off": no matching source found. Add a source or remove the claim.

None of these were flagged as needing a human to check them manually, but none currently have a source either.

Since the last audit

1 problem got fixed: the missing reviewer bio issue. Nothing got worse. 17 new issues appeared, mostly around AI-visibility signals (sourced claims, standalone passages, entity naming) and unsourced discount stats. 12 problems are still open from before, including the JavaScript rendering issue, the missing keyword in the title, and the missing author byline.

What we could not measure

Page speed (Core Web Vitals) wasn't measured because no performance tool was connected; the free fix is to run PageSpeed Insights on this URL yourself. We also don't know how many clicks deep this page sits from your homepage, or whether other pages link to it, since that needs a full site crawl (Google Search Console's links report is a free way to check). We didn't check whether Bewakoof has a Wikipedia entry or knowledge panel, or how the brand is mentioned across forums, video and news; both need a manual search. And we can't confirm today's listed prices and discounts are still accurate, since the page snapshot carries no capture date.

A claims ledger for Bewakoof doesn't exist yet. Setting one up would let this skill state real facts about pricing, policies and past claims instead of flagging them all 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 Self-referencing canonical, absolute, no conflict: self-referencing canonical: "https://www.bewakoof.com/design-of-the-day"
Pass No nosnippet / max-snippet:0: no nosnippet/max-snippet:0 directive
Pass Title length 50-60 chars: title "Shop New T-shirt Design Everyday Online in India | Bewakoof" is 59 chars
Pass Exactly one H1, keyword-bearing, first heading in the DOM: one H1: "Design of The Day"
Pass Heading hierarchy valid, no skipped levels: 1 H1, 0 H2, 0 H3
Pass URL slug flat, lowercase, hyphenated, keyword-bearing: URL path: "/design-of-the-day"

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 Contextual body links first-mention, one link per concept See finding
content Visible author byline + credential above the fold See finding
content Answer-first sections, question-shaped H2s, key-takeaway box 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: None of the tested answers use this page yet. Work the Content and Structured data findings, which are what AI engines pull answers from.

0/100AI visibility

2questions tested

0answers cite this page

"best design day shop new t"

AI search (web + model) Not mentioned

Not mentioned: the answer did not use or name this page.

What the AI answered: The search results don't contain information about design day shops or t-shirt retailers in India.

"what is design day shop new t"

AI search (web + model) Not mentioned

Not mentioned: the answer did not use or name this page.

What the AI answered: The search results contain nothing about 'Design Day Shop' or a product matching 'design day shop new t'.

citability sample is one engine (web search plus this company's model), directional only, on 2026-09-18.

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 16 failing checks first, then the 13 warnings

Dimension	Score	Measured of applicable	Weight
Technical SEO	85	6 of 10	18
On-page SEO	80	12 of 12	14
Content quality	40	5 of 5	10
Structured data	89	8 of 8	14
Links	64	3 of 4	14
Performance	incomplete	0 of 8	14
Trust and expertise	55	4 of 4	8
Freshness	19	2 of 3	8
Data	58	5 of 5	8

Technical SEO851 fail

Fail Main content present in server-rendered raw HTML
Observed: "Crawlers see 11 words before JavaScript runs, 395 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
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 Self-referencing canonical, absolute, no conflict
Observed: "self-referencing canonical: "https://www.bewakoof.com/design-of-the-day""

Expected: The canonical tag points to this exact URL.
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/design-of-the-day" identical to requested url; http_status 200"

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

Recommendation: No action needed; keep serving this URL directly without redirecting it.

Location: HTTP response

Not measured this run (5)

Needs data No crawl traps: session-ID or internal-search links, unmanaged parameters
Observed: "Filters sidebar: Gender, Category, Sizes, Brand, Color, Pattern, Fit, Price, Collaboration, Offers, Discount, Ratings, More Filters"

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

Recommendation: Apply a filter (e.g. Gender=Men) and inspect the resulting URL/canonical tag; confirm facet URLs self-canonicalize to /design-of-the-day or carry noindex.

Location: filter sidebar
N/A Paginated pages self-canonicalize
Observed: ""2 Products" listed, no pagination controls in main_text"

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

Recommendation: No action needed.
Needs data robots.txt well-formed, does not block CSS/JS, declares a sitemap
Observed: "robots.txt fetched (status 200), declares sitemaps https://www.bewakoof.com/sitemap_index.xml and .../blog/sitemap_index.xml; only bot-level allow rules supplied, no Disallow directives shown"

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

Recommendation: Pull the full robots.txt text and confirm no Disallow rule targets /css/, /js/ or bundled asset paths; the sitemap declaration itself already looks correct.
Needs data URL is in the sitemap, reachable in <=3 clicks, not orphaned
Observed: "sitemap includes_url: true; page's own top nav only shows Home, Men, Women, Accessories, Login — no homepage-to-page link path confirmed"

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

Recommendation: Verify via a site crawl or manual check that the homepage (or a top-level banner/menu) links to /design-of-the-day within 3 clicks; add a homepage banner link if it's missing.
Needs data No cloaking, no near-duplicate/staging mirror
Observed: "raw HTML word count 11 vs rendered word count 395 (js_dependency: full); no cached/staging mirror comparison data available"

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

Recommendation: Compare the Google Search Console URL Inspection 'rendered HTML' against the live page, and confirm no staging/duplicate domain serves identical content.

On-page SEO803 warn

Warn Title present, keyword-bearing, not stuffed
Observed: "title "Shop New T-shirt Design Everyday Online in India | Bewakoof" does not contain the keyword "design day shop new t" (keyword inferred from the page, confirm it)"

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

How to verify: Re-run the audit: SR-ONP-01 reads pass
Warn Meta description unique, 150-160 chars, keyword present
Observed: "meta description is 149 chars: "Shop a new design every day starting at Rs.259 from Bewakoof. Special launch price for 24 hrs only on quirky & high quality Tees. Free Shipping. COD.""

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 "design day shop new t" 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
Pass Title length 50-60 chars
Observed: "title "Shop New T-shirt Design Everyday Online in India | Bewakoof" is 59 chars"

Expected: Title is 50-60 characters long.
Pass Exactly one H1, keyword-bearing, first heading in the DOM
Observed: "one H1: "Design of The Day""

Expected: Exactly one H1 is present.
Pass Heading hierarchy valid, no skipped levels
Observed: "1 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: "/design-of-the-day""

Expected: The URL path is lowercase, hyphenated, with no dates/IDs/params.
Pass Image alt present on all images
Observed: "all 1 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; main_text repeats only structural/nav terms ("Design of The Day", category labels) with no artificial repetition"

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

Recommendation: No action needed.
Pass Title-rewrite risk: not so long/generic/stuffed the engine replaces it
Observed: "title: "Shop New T-shirt Design Everyday Online in India | Bewakoof" (59 chars)"

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

Recommendation: Check Search Console's Titles report for this URL periodically; if Google is rewriting it, lead the title with the unique value proposition instead of the generic 'Shop New T-shirt Design'.

Not measured this run (1)

N/A Each H2 a distinct user sub-question, not a vague label
Observed: "h2: [] — zero H2 headings present on the page"

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

Recommendation: If editorial/body copy is added to explain the 'Design of the Day' concept, structure it under H2s phrased as distinct customer questions (e.g. 'How does Design of the Day work?', 'When does a new design drop?').

Content quality402 fail

Fail Direct answer up top (BLUF)
Observed: "Main text opens with 'MEN WOMEN ACCESSORIES | LOGIN FREE SHIPPING on all orders above ₹399 Home Design Of The Day Design of The Day 2 Products Sort by : Popularity Filters...' — no sentence anywhere explains what 'Design of the Day' is or answers what a visitor searching that phrase wants to know."

Expected: First content block should state, in one or two plain sentences, what the 'Design of the Day' program is (e.g. a rotating daily/weekly featured design drop) before the filter/nav chrome.

Recommendation: Add a 1-2 sentence intro under the H1 explaining the concept and cadence of 'Design of the Day' before the filter/product grid.

Location: top of main content, before product grid

Before: Design of The Day 2 Products Sort by : Popularity Filters Clear All Gender Men (1) Women (1)...
After: Design of the Day showcases one new limited-run graphic tee or hoodie release, updated regularly. This week's drop: [current items].

How to verify: Re-run the audit: SR-CNT-01 reads pass
Fail Not thin/padded, density over length
Observed: "The bulk of the 395-word count is a repeated sitewide footer link list ('Men's Pajamas Men's Boxer Shorts Men's Shorts Men's Jogger Men's Cargo Joggers Men's Old Money Outfits...') unrelated to the 'Design of the Day' topic, not organic depth about the two products shown."

Expected: Word count should reflect density of on-topic content, not templated sitewide navigation repeated across every category page.

Recommendation: Exclude/collapse the giant footer sitemap from on-page word count consideration; keep it as site-wide nav in a collapsed or lower-weight block, and let unique product/editorial text carry the page's substance.

Location: footer link block

How to verify: Re-run the audit: SR-CNT-03 reads pass
Pass Depth matches intent; under 300 words is thin
Observed: "395 words"

Expected: Word count is at least 300, or a narrow intent is fully answered.
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 395 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 Readability in the audience band
Observed: "Page content is composed of nav labels, filters, and product title/price fragments (e.g. 'Bewakoof X Stranger Things Women's Jet Black Stranger Things Logo Typography Oversized T-shirt ₹409 ₹1,499 72% OFF') with no full sentences or paragraphs to score for reading grade."

Expected: Readability scoring requires prose sentences; none are present.

Recommendation: Once an explainer paragraph is added (see SR-CNT-01), keep sentences under 35 words and around an 8th-10th grade reading level.
N/A Varied sentence rhythm (burstiness)
Observed: "No multi-sentence prose exists on the page to assess sentence-length variation; content is label/fragment based (filters, product names, prices)."

Expected: Burstiness requires actual sentences.
N/A AI-writing tells within the light-edit band
Observed: "No generated prose is present to check for AI-writing tells; content is UI chrome and product data fields."

Expected: AI-tell density is scored on written copy, which this page does not have.
N/A Fact-density adequate on claim-making pages
Observed: "The only quantitative claims are transactional (e.g. '72% OFF', 'Get it for as low as ₹339', '4.7M People like this') tied to live pricing/social widgets, not editorial assertions needing citation."

Expected: Fact-density scrutiny applies to claim-making editorial sections, which this page lacks.

Structured data891 fail · 1 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
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 JSON-LD present and valid
Observed: "1 JSON-LD block(s) present: CollectionPage"

Expected: At least one valid JSON-LD block is present; an FAQ visible on the page has FAQPage schema.
Pass No schema misuse, no retired @type
Observed: "1 JSON-LD type(s): CollectionPage"

Expected: No Product/Review type without matching content; no retired @type.
Pass @graph well-formed
Observed: "1 JSON-LD block(s) parsed without structural errors"

Expected: A single @context, @id-linked entities, one root, no orphans or circular refs.
Pass Category page has list markup
Observed: "category schema present: CollectionPage"

Expected: The category page carries an ItemList or CollectionPage node.
Pass Primary schema type matches page purpose
Observed: "JSON-LD @type: "CollectionPage" with mainEntity ItemList (numberOfItems: 2)"

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

Recommendation: No action needed.
Pass Schema content matches visible content
Observed: "schema name "Design of The Day" matches visible H1 "Design of The Day"; schema description matches the meta description verbatim; the 2 ItemList entries match the 2 products shown"

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

Recommendation: No action needed.

Links641 fail

Fail Contextual body links first-mention, one link per concept
Observed: "main_text has no body/prose copy with inline links; all 6 internal links are header/mega-menu/footer navigation (Home, Men, Women, Accessories, category footer links)"

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

Recommendation: Add a short intro paragraph under the H1 explaining the 'Design of the Day' concept and link at first mention to related collections.

Before: (no body copy present)
After: Every day we drop a new graphic tee design for 24 hours — browse our full range of printed t-shirts or oversized tees once today's drop sells out.

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: "All visible anchors (e.g. "Men's T-Shirts", "Women's Dresses", "Oversized T-Shirts for Men") are mega-menu/footer navigation labels, not body-content anchors"

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

Recommendation: If body copy is added (see SR-LNK-03), vary anchor phrasing naturally rather than reusing exact category-page titles every time.
N/A Outbound links working, authoritative, to primary sources
Observed: "external_hrefs are all social/app links (Facebook, Instagram, Twitter, Pinterest, Snapchat, App Store, Play Store); no citation-style outbound links in body content"

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

Recommendation: No action needed; if sizing/fabric/sourcing claims are added, link out to authoritative primary sources there.

Trust and expertise551 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
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
Pass Trust signals: citations, working outbound links, policy pages, HTTPS
Observed: "about, contact and privacy pages linked"

Expected: About, contact and privacy pages are linked, and the page is served over HTTPS.
Pass Legal name, address and grievance officer
Observed: "not on this page; /contact-us is linked, check that it carries the legal name, address and grievance officer"

Expected: The legal name and address of the business, and a grievance officer's name and contact, are on the page.

Recommendation: Add the business's legal name and address and a grievance officer's name and contact, per the Consumer Protection (E-Commerce) Rules, 2020 (rules 4 and 5) and the DPDP Rules, 2025. Confirm with your counsel.

Based on: Consumer Protection (E-Commerce) Rules, 2020, rules 4 and 5; DPDP Rules, 2025 (contact for data queries) (reviewed 2026-09)

Not measured this run (3)

N/A Affiliate/commercial disclosure above the fold
Observed: "no affiliate/third-party partnership language on the page; products (own-brand Bewakoof x Stranger Things collab) are sold directly by the retailer"

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

Recommendation: No action needed.
N/A No regulatory superlatives on regulated topics
Observed: "page content is t-shirts/hoodies pricing and offers; no financial, medical, or legal claims present"

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

Recommendation: No action needed.
N/A E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
Observed: "no Trust/Expertise/Authority/Experience banded roll-up or similar labeling appears anywhere on this commerce page"

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

Recommendation: No page-level action; ensure the accompanying audit report labels its own E-E-A-T roll-up as a heuristic quality concept, not an actual Google ranking signal.

Freshness191 fail · 1 warn

Fail Freshness-sensitive (QDF) topics are genuinely recent
Observed: "The H1 and page name is 'Design of The Day', but both listed products are individually labeled 'DESIGN OF THE WEEK', and no date, week number, or 'last updated' marker appears anywhere in the extracted content."

Expected: A recurring/rotating drop page ('of the Day') should be internally consistent and show a visible freshness signal (date, week label, or 'updated on X') so users and crawlers can trust the content is current.

Recommendation: Pick one consistent name ('Day' or 'Week') and display an explicit refresh date or 'week of [date]' label near the H1.

Location: H1 and product badges

Before: Design of The Day ... DESIGN OF THE WEEK Bewakoof X Stranger Things Women's...
After: Design of the Week — updated Sep 15, 2026

How to verify: Re-run the audit: SR-FR-02 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

Not measured this run (1)

Needs data No outdated statistics on a dynamic topic
Observed: "Pricing/discount figures (₹409/₹1,499, 72% OFF; ₹1,499/₹3,699, 59% OFF) are shown but the underlying page snapshot carries no capture date, so currency of these specific prices/discounts cannot be verified from the given data."

Expected: Dynamic commercial figures (price, % off) should be verifiably current at crawl time.

Recommendation: Confirm via live re-check that both listed SKUs and discount percentages are still active before/at next crawl; add an automated stock/price freshness check for this template.

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: "The extracted content is a run of nav links, filter facet labels, and product-card fragments ("Sizes XS (1) S (2) M (2)..."); there is no self-contained passage that answers an implied question."

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

Recommendation: Add a short standalone explainer paragraph (2-4 sentences) that fully answers 'What is Design of the Day at Bewakoof?' without depending on surrounding nav text.

Location: main_text

How to verify: Re-run the audit: AI-EXT-01 reads pass
Fail Entity context retained in each passage
Observed: "No prose passage names the subject; the only entity-bearing text is embedded in product-card titles ("Bewakoof X Stranger Things Women's Jet Black...") rather than explanatory sentences that could be extracted alone."

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

Recommendation: Write an explainer section that repeats "Bewakoof's Design of the Day" by name rather than relying on UI labels.

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 on the page (per AI-GATE-02), so no claim carries attribution inside its own passage."

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

Recommendation: Once claims are added, keep the source name/link in the same sentence or immediate line as the claim.

Location: main_text

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

AI citationsincomplete5 fail · 3 warn

Fail Claims attributable: inline sources on load-bearing facts
Observed: "Main content is entirely navigation, filter facets, and product listing cards ("Bewakoof X Stranger Things Women's Jet Black Stranger Things Logo Typography Oversized T-shirt ₹409 ₹1,499 72% OFF"); there is no attributed claim and no outbound link to any source anywhere in the extracted text."

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

Recommendation: If this page is meant to answer 'what is Design of the Day', add a short editorial block explaining the program with at least one attributed, linked claim (e.g., linking to Bewakoof's about page or press coverage).

Location: main_text (entire page body)

Before: Design of The Day 2 Products Sort by : Popularity Filters Clear All...
After: Design of the Day is Bewakoof's daily rotating t-shirt drop, launched in [year] (source: Bewakoof About page, linked).

How to verify: Re-run the audit: AI-GATE-02 reads pass
Fail Corroborated on an independent trusted domain
Observed: "No independent trusted-domain corroboration is available for any claim on the page; pricing/discount/rating figures are self-reported only, and no external source data was supplied for this audit."

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

Recommendation: Not critical for a transactional listing page; if editorial claims are added per AI-GATE-02, seek independent coverage (press, review sites) corroborating the program.

Location: n/a — no external corroboration data available

How to verify: Re-run the audit: AI-GATE-06 reads pass
Fail Key facts as semantic triples, consistent naming
Observed: "Content is filter-facet labels and catalog navigation ("Category T-Shirt (1) Hoodies (1) Sizes XS (1) S (2)...") rather than full sentences; no subject-verb-object factual statements are present to check for consistent naming."

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

Recommendation: Add declarative sentences, e.g., "Bewakoof releases a new Design of the Day t-shirt every 24 hours," using the brand name consistently rather than pronouns.

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: "Statistics appear without any named source: "72% OFF", "59% OFF", product rating "4.5", and "4.7M People like this" / "1M People like this" carry no attributed source, credential, or organization."

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

Recommendation: For figures worth surfacing (e.g., social following counts), state the source and as-of date inline (e.g., "4.7M Facebook followers as of [date], per Bewakoof's official page").

Location: main_text (footer social/rating stats)

Before: 4.7M People like this
After: 4.7M Facebook followers (Bewakoof official page, as of Sep 2026)

How to verify: Re-run the audit: AI-CITE-01 reads pass
Fail Information gain: a sourced specific the consensus lacks
Observed: "The page contains no editorial content at all — only a product grid, filter facets, and sitewide nav/footer. There is no design-story detail, no artist/collaboration background beyond the product title itself, no sourced sales data, and no dated specifics. Note: the three competitor URLs supplied (a generic coupon-aggregator page for an unrelated printery shop, a fashion-designer profile 'TAO – FRAME', and a streetwear-designer blog post on Jun Takahashi/Undercover) do not match this keyword or page type, so a reliable competitor-based coverage comparison could not be performed for this rule — flagging as a data gap rather than inferring competitor coverage."

Expected: Commercial category pages should carry at least one concrete, sourced specific (L3+ ideally, L2 minimum) — e.g., named collaboration release date, verified units sold, or a quoted designer/brand statement — rather than being pure listing chrome.

Recommendation: Add a short, dated section per drop: exact collab release date, limited quantity/units sold if tracked internally (sample size + date range), or a one-line attributed quote from the design/merchandising team explaining the pick. Do not fabricate figures — pull from actual sales/inventory systems.

Location: whole page

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
Warn Entity-dense: claims pinned to named things
Observed: "Title names the brand and category ("Shop New T-shirt Design Everyday Online in India | Bewakoof"), but H1 is generic ("Design of The Day") with no brand or product-type name, and the first_100_words open with nav/filter boilerplate (MEN WOMEN ACCESSORIES | LOGIN...) before any entity is named."

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

Recommendation: Change H1 to something like "Design of The Day: New T-Shirts & Hoodies at Bewakoof" and open the body copy with a brand-naming sentence before the filter UI.

Location: h1 / first_100_words

Before: H1: "Design of The Day"
After: H1: "Bewakoof Design of The Day – New T-Shirt Drops"

How to verify: Re-run the audit: AI-GATE-03 reads pass
Warn Entity floor + salience
Observed: "The primary entity 'Bewakoof' does not appear until deep into the first_100_words (after nav/filter boilerplate: "MEN WOMEN ACCESSORIES | LOGIN FREE SHIPPING...Filters Clear All Gender..."); named entities present are mostly the 'Stranger Things' collab and product taxonomy terms rather than sentence-level entities."

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

Recommendation: Move a brand-naming sentence ahead of the filter/nav chrome in the extractable content order.

Location: first_100_words

How to verify: Re-run the audit: AI-ENT-01 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.
Pass Citable without reputational risk
Observed: "No fabricated statistics, no wrong YMYL figures, and no banned superlative language observed; discount/rating figures ("72% OFF", "4.5", "4.7M People like this") read as standard e-commerce merchandising copy."

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

Recommendation: No action needed.

Location: main_text (product cards)
Pass No fabricated or unverifiable statistic or quote
Observed: "Figures present (discount percentages, star rating, follower counts) read as ordinary self-reported store/catalog data rather than fabricated third-party facts; nothing YMYL is asserted."

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

Recommendation: No urgent action; if precision matters, keep discount/rating figures in sync with actual catalog data.

Location: main_text
Pass Authoritative declarative tone, with the YMYL hedging exception
Observed: "Not a YMYL page; tone throughout is plain transactional listing copy (prices, filters, product names) with no vague hedging language observed."

Expected: Tone is declarative; a YMYL page hedges with "as of [date]" rather than vague hedging.

Recommendation: No action needed.

Location: main_text
Pass Training-only blocks presented as a documented trade-off
Observed: "AUTO FINDINGS (AI-BOT-01, AI-BOT-03) show no crawler blocks and no unknown bot tokens in robots.txt, so there is no training-only block present to mischaracterize."

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

Recommendation: If a training-only block (e.g., a bot opt-out) is added later, document it explicitly as a deliberate trade-off, not as a ranking risk.

Location: robots.txt (per AUTO FINDINGS)

Not measured this run (5)

Needs data Knowledge-graph presence
Observed: "No knowledge-base entry, encyclopedia path, or knowledge-panel check for the Bewakoof brand was supplied as part of this audit; the citability sample's cited domains (goodsearch.com, en.wikipedia.org, tipntag.com, covetedition.com, lonelyplanet.com, blog.footdistrict.com) never include bewakoof.com or an en.wikipedia.org/wiki/Bewakoof-style path."

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

Recommendation: Founder/manual check: search 'Bewakoof' on Google for a knowledge panel and check for a Wikipedia article; escalate as a gap if absent.

Location: n/a — requires manual knowledge-graph check
Needs data Per-engine backend presence and crawler access
Observed: "CITABILITY SAMPLE supplies only one grade/answer per target question, not broken out per engine; no per-engine backend-presence data was provided for chatgpt, copilot, perplexity, ai_overviews, ai_mode, gemini, or claude individually."

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

Recommendation: Founder/manual check: run the two target questions separately against each of the 7 listed engines and log per-engine domain citations.

Location: n/a — CITABILITY SAMPLE not segmented by engine
N/A llms.txt and IndexNow carry low/zero weight, never a gate
Observed: "No llms.txt or IndexNow data was supplied in this audit."

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

Recommendation: Optionally check for llms.txt/IndexNow presence and note it informationally; do not weight it in the overall verdict.

Location: n/a — not audited
Needs data Knowledge-graph footprint (web search sample)
Observed: "The citability sample's cited domains for both target questions (goodsearch.com, en.wikipedia.org, tipntag.com, covetedition.com, lonelyplanet.com, blog.footdistrict.com) never include bewakoof.com, but no dedicated knowledge-graph/web-search check for the 'Bewakoof' entity itself was run."

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

Recommendation: Founder/manual check: search 'Bewakoof' directly (not the garbled target queries) to confirm Wikipedia/knowledge-panel presence.

Location: n/a — requires manual brand-level search
Needs data Brand-mention sample on AI-visibility-correlated platforms
Observed: "No forum, video, news, or professional-network brand-mention sample was supplied for this audit."

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

Recommendation: Founder/manual check: sample Reddit, YouTube, and news coverage for 'Bewakoof' mentions.

Location: n/a — not audited

Programmatic pagesincompletenot measured

Not measured this run (3)

N/A Every page carries genuinely unique data
Observed: "page shows a rotating 2-product daily drop under a single unique URL; no evidence it is one of a mass-produced template set"

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

Recommendation: If Bewakoof runs many similar single-purpose promo pages, re-assess this rule once that inventory is confirmed.
N/A No two pages share >80% of their field content
Observed: "no cross-page field-content comparison data provided"

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

Recommendation: Only relevant if this page is confirmed part of a templated rollout; run a similarity check across that set if so.
N/A Scale governance: review at 100+, justification at 500+
Observed: "no evidence this page belongs to a >100-page templated rollout"

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

Recommendation: No action needed unless site-wide category/filter pages are confirmed as a governed programmatic rollout.

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
FREE SHIPPING on all orders above ₹399	Pass	-
72% OFF	Warn	Add a source or remove the claim
59% OFF	Warn	Add a source or remove the claim
15 Days Return Policy	Warn	Add a source or remove the claim
Buy 3 get 10% off	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 6 gaps listed below

Add: A short intro paragraph (1-3 sentences) directly under the H1 explaining what 'Design of the Day' is and how often it refreshes
Add: A visible, consistent freshness marker (date or 'week of' label) reconciling the 'Day' vs 'Week' naming conflict between H1 and product badges
Expand: Per-product design story/context (collaboration background, release date, fabric/fit notes) for each of the two featured items, beyond title + price
Add: One sourced, dated specific per drop — e.g. verified release date, real units-sold/stock figure, or an attributed quote from the design team — to clear the information-gain gate
Cut: Reduce reliance on the massive repeated sitewide footer link list as de-facto page content; keep it as standard site nav but do not count on it for topical substance
Add: Verify current price/discount accuracy for both listed SKUs at crawl time and log a periodic freshness check for this template

Information gain: L0 (below consensus-restating): the page is a bare product-listing/filter shell with no editorial narrative, quotes, or data about the 'Design of the Day' concept — it doesn't even restate commonly-known facts, it simply lists two SKUs. to L2–L3: add a named, dated specific per drop (verified collaboration release date, real sales/stock number with sample size and date range, or an attributed quote from the design/merchandising team) so the category page offers at least one fact a competitor or generic listing page wouldn't have. Note: competitor set provided for this keyword was topically mismatched (coupon aggregator, unrelated fashion designer profiles), so no reliable 'what winners already have' baseline was available — this target is set from the ruleset's YMYL/commercial floor, not from competitor coverage, and should be revisited once relevant SERP data is available.

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 29 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 main content, before product grid	See finding	Re-run the audit: SR-CNT-01 reads pass
High	Add internal link	Links	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	AI answers	At least half of H2 headings are question-shaped.	Re-run the audit: AI-EXT-04 reads pass
High	Fix	Main text (entire page body)	See finding	Re-run the audit: AI-GATE-02 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 (footer social/rating stats)	See finding	Re-run the audit: AI-CITE-01 reads pass
High	Rewrite section	Footer link block	See finding	Re-run the audit: SR-CNT-03 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	Whole page	See finding	Re-run the audit: AI-GATE-04 reads pass
Medium	Fix	Main text	See finding	Re-run the audit: AI-ENT-02 reads pass
Medium	Fix	H1 and product badges	See finding	Re-run the audit: SR-FR-02 reads pass
Medium	Fix	N/a — no external corroboration data available	See finding	Re-run the audit: AI-GATE-06 reads pass
Critical	Fix meta	On-page SEO	A <title> tag exists and contains the target keyword.	Re-run the audit: SR-ONP-01 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
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
High	Fix	H1 / first 100 words	See finding	Re-run the audit: AI-GATE-03 reads pass
High	Fix	First 100 words	See finding	Re-run the audit: AI-ENT-01 reads pass
Medium	Fix stat	Women's T shirt product offer section	See finding	Re-run the audit: data-fc-5 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	Bewakoof X Stranger Things Women's Jet Black T shirt product listing	See finding	Re-run the audit: data-fc-2 reads pass
Medium	Fix stat	Bewakoof X Stranger Things Men's Fudgesickle Brown Hoodies product listing	See finding	Re-run the audit: data-fc-3 reads pass
Medium	Fix stat	Footer section	See finding	Re-run the audit: data-fc-4 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: No regressions since the last audit.

Fixed

Trust signals: citations, working outbound links, policy pages, HTTPS

Regressed

none

New

Claims attributable: inline sources on load-bearing facts
Entity-dense: claims pinned to named things
Corroborated on an independent trusted domain
Each passage stands alone
Entity context retained in each passage
Attribution survives inside the passage
Entity floor + salience
Key facts as semantic triples, consistent naming
Every statistic/quotation attributes to a named source
Direct answer up top (BLUF)
Not thin/padded, density over length
Freshness-sensitive (QDF) topics are genuinely recent
Information gain: a sourced specific the consensus lacks
Claim has no source
Claim has no source
Claim has no source
Claim has no source

Still standing

Main content present in server-rendered raw HTML
Title present, keyword-bearing, not stuffed
Meta description unique, 150-160 chars, keyword present
Primary keyword naturally within the first 100 words
Baseline trio: Organization/LocalBusiness + BreadcrumbList + WebSite
Dates: one visible date; datePublished and dateModified in JSON-LD
Visible author byline + credential above the fold
Reviewer name + credential + last-reviewed date
Visible last-updated date, accurate against schema dateModified
Fresh where it matters
Answer-first sections, question-shaped H2s, key-takeaway box
Contextual body links first-mention, one link per concept

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.
disclosure checks ran as a none business in IN (founder); change it under Marketing, SEO analysis, if that is wrong.
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.