Implementation report: https://www.bewakoof.com/contact-us

Something is currently stopping Google from properly reading this page at all: most of its content only shows up after JavaScript runs, and many crawlers never wait for that. We audited https://www.bewakoof.com/contact-us and it scores 57 out of 100, which we're calling Critical issues present, meaning at least one problem is actively blocking results. There are 37 things to fix below, starting with the 5 most valuable.

The 5 biggest problems (fix these first)

1. Google may see almost nothing here: only 58 of your 364 words load before JavaScript runs

Current: Crawlers see 58 words before JavaScript runs, 364 after.

Google and AI assistant crawlers often read the raw HTML your server sends first. If the real content only appears after JavaScript finishes running, many of them give up before they ever see it, so the page looks almost empty to them even though a browser shows 364 words.

Fix:

Server render (or pre render) the main FAQ content of /contact-us so it's present in the initial HTML your server sends.
Check it worked by viewing the page source (or running curl on the URL) and confirming the FAQ text appears without running any JavaScript.

Who: a developer, likely 1 to 3 days depending on how the page is built.

2. The page opens with a chat prompt, not an answer, so nobody learns what you sell in the first sentence

Current: MEN WOMEN ACCESSORIES | LOGIN Hello there! Need help? Talk to us! WhatsApp Us We're here 24/7. Smart Assistant Instant help Frequently Asked Questions!

Google and AI engines scan a page's opening sentences to decide what it's about, and often quote them directly in answers. Right now those sentences are navigation menu items and a live chat prompt, nothing about "online fashion shopping," so there's nothing on topic for engines to grab onto.

Fix: add this as the opening paragraph, before the nav and FAQ chrome:

Bewakoof is an online fashion shopping destination where men and women can browse thousands of T-shirts, dresses and accessories, compare prices and get doorstep delivery with cash on delivery and a 15-day return window.

Who: a writer to draft it (about 30 minutes), a developer to move it above the nav and chat prompt.

3. There's no main heading at all, so nothing tells Google or visitors what this page is

Current: no H1 found.

Google weighs the H1 heading heavily as the clearest single statement of what a page is about, and AI assistants often quote it as a page's title. With none here, engines have to guess between "homepage," "contact form" and "FAQ."

Fix:

Add one <h1> at the top of the content, for example Bewakoof Contact Us: Order, Delivery and Returns Help.
Make sure it's the very first heading in the page's code.
Check with your browser's inspector that exactly one H1 exists on the page.

Who: a developer, under an hour.

4. No structured data at all tells Google what kind of page this is

Current: no structured data of any type present on the page

Schema (a small snippet of code that labels page elements for search engines) is what tells Google "this is a contact page" or "this is a FAQ," and it's what unlocks expandable FAQ results in search. With none, this page competes on looks alone.

Fix:

Add ContactPage schema identifying this as Bewakoof's contact page.
Add FAQPage schema wrapping each visible question and answer (order status, cancellations, refunds, and so on).
Check it worked with Google's Rich Results Test, confirming both types are detected with no errors.

Who: a developer, about half a day.

5. None of your links sit inside the FAQ answers, so Google can't connect questions to the right support pages

Current: internal_hrefs are all footer/nav category and policy links (e.g. "/men-t-shirts", "/privacy-policy-and-disclaimer"); main_text shows no body prose with inline links

Links placed inside real sentences, not footer menus, are how Google learns which topic connects to which destination page, so it can route the right FAQ answer to the right support page in search or an AI summary. Footer links carry almost none of that signal.

Fix:

Under "How do I check the status of my order?", link the words "Track Order" to the tracking page the first time they appear.
Do this once per topic, for example the first mention of "returns" links to the returns page, not every time the word appears.
Check by reading the rendered FAQ answers and confirming each has at most one contextual link to a matching page.

Who: a developer, a few hours.

Also worth fixing

For a developer

No real subheadings on the FAQ topics: turn the tab labels ("Cancellations," "Refunds & Returns," "My Bewakoof Wallet," "Offers and Combos," "TriBe Membership") into actual heading elements phrased as questions, e.g. "How do cancellations, refunds and returns work?"
Missing basic site identity schema: add Organization, BreadcrumbList and WebSite schema so Google has the core business signals every page should carry.
No JSON-LD anywhere on the page: add at least one valid block, starting with the FAQ schema from problem 4 above.
Can't confirm robots.txt allows your page's styling and scripts to load: manually check it for any rule blocking CSS or JS bundle paths, which would stop Google rendering the page correctly.
The same FAQ tab has two working URLs: /contact-us/order-delivery-payment and a version with a ?pageId= parameter both work with no canonical tag pointing between them. Pick one URL, add a self-referencing canonical tag to it, and redirect the other.
No dates anywhere in the page's code: once schema is added, include a published date and a last-modified date that match a visible date on the page.
No canonical tag on this page at all: add one in the page's head pointing to this exact URL, https://www.bewakoof.com/contact-us, to avoid duplicate-URL confusion.
Two image files have generic names: rename them to descriptive, hyphenated, lowercase filenames, for example bewakoof-contact-support.jpg.

For a writer

No named author anywhere: add a byline, for example "Written by the Bewakoof Customer Care team," linking to a bio or team page.
Nothing on the page is phrased as a question with a direct answer: once headings exist, phrase at least half of them as questions, each followed by a 2 to 3 sentence answer.
No fact on the page links to where it came from: add a short guide section with real, sourced facts and outbound links.
The brand name and topic don't show up until deep in the page: open the first real paragraph with "Bewakoof" and "online fashion shopping for men and women" together.
FAQ questions have no answers under them: write a self-contained 40 to 80 word answer under each question that makes sense read on its own.
Answers don't name the brand or topic: say "Bewakoof" and "online fashion shopping" by name inside each answer instead of "we" or "this."
No sourced claim keeps its source attached: when you add a sourced fact, put the source in the same sentence, not a separate footnote.
The body is roughly 80 category links in a row with no real writing: Men's T-Shirts Men's Hoodies & Sweatshirts Oversized T-Shirts for Men Men's Long Sleeve T-shirts.... Keep that list in navigation only and replace the body copy with written guide text that references categories in context.
Your Contact Us page reuses the homepage title word for word: current title, Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com, describes the homepage, not this page, so Google is likely to rewrite it. Replace with something like Contact Bewakoof: Order, Delivery and Returns Help, kept under 60 characters.
The title is 66 characters, too long to show in full: shorten it to land between 50 and 60 characters, for example Contact Bewakoof: Order and Returns Help.
No plain sentence on the page states a fact about Bewakoof: write statements like Bewakoof offers free 15-day returns on men's and women's clothing, using the full brand name instead of "we."
No claim exists yet that could be checked elsewhere: once you add sourced facts, make sure at least one also appears on an independent trusted site.
Claims like fast delivery and easy returns have no numbers behind them: add the real delivery timeframe, return rate or catalog size instead of bare menu items.
No reviewer or last-reviewed date: add a reviewer name, credential and a last-reviewed date near the policy claims.
The keyword never appears in your first 100 words: work "online fashion shopping" naturally into the opening paragraph (see problem 2's fix above).
No date shows the FAQ content is current: add a genuine last-updated date near policy answers like returns and cash on delivery.
This page would score poorly on expertise and first-hand experience if judged as an article: attribute the content to the CX or support team and treat it as a support page in your reporting, not an editorial one.
The brand name isn't prominent early on: make sure "Bewakoof" and "online fashion shopping" appear together in your opening sentence, not buried in category menu text.
No visible last-updated date anywhere on the page: add one near the top of the policy content and keep it under 18 months old.
"4.7M People like this" has no source: link to where that count comes from, or remove the number.
"1M People like this" has no source: same fix, link to a source or remove it.
"100% SECURE PAYMENT" is an unsupported claim: link to the payment provider's security certification, or remove the badge text.
Your meta description is twice as long as Google will show: it's 311 characters, Online Shopping Site for Men, Women & Accessories. Choose from the best in Men Clothing and Women Fashion Wear.... Replace with something like Contact Bewakoof for help with orders, delivery, payments, cancellations and returns. Shop online fashion for men and women with free shipping and easy 15-day returns., kept between 140 and 160 characters.

For you

Nothing on this page gives anyone a reason to cite it over a competitor: fixing this needs real order data (top categories, delivery time, return rate) pulled from your own records, with a stated sample size and date range. That's a call about what internal data you're willing to publish, not something a writer can invent.

What to add to the page

A short opening paragraph that directly answers what online fashion shopping for men and women offers.
A written buying guide covering sizing, fabrics, trends, payment and delivery options.
Cut the roughly 80-item category link list from the body copy; keep it only as navigation.
Full-sentence answers under each FAQ question, not just question titles.
A section with real first-party numbers: top-selling categories, delivery time, return rate, with a stated sample size and date range.
Comparison content helping shoppers choose between styles, price tiers or brands.
Attributed customer or expert quotes, not just vague "people like this" counts.
A last-updated or last-reviewed date for policy claims like returns, payment and security.

What is already working

The page loads over HTTPS, returns a normal 200 status, and isn't blocked from being indexed.
The title already contains the keyword "online fashion shopping men women."
All 4 images on the page have alt text.
robots.txt is well formed, allows all crawlers, and declares your sitemaps.
The page is listed in your sitemap (61,432 URLs) and linked directly from the footer under "Contact Us," so it isn't orphaned.

How AI assistants see this page

Query	Used this page?	Quoted answer
best online fashion shopping men women	No	"you would need broader search results covering other popular platforms like Amazon Fashion, Myntra, Flipkart Fashion, and others"
what is online fashion shopping men women	No	"Online fashion shopping for men and women is purchasing clothing, footwear, accessories, and beauty products through internet-based websites"

Right now this page scores 0 out of 100 for being cited by AI assistants. That number comes from a single engine's test on one date, 2026-09-18, so treat it as directional only, not a verdict.

To check by hand, try each of these in the named tool: "best online fashion shopping men women" in ChatGPT, Copilot, Perplexity, Google AI Overviews, Google AI Mode, Gemini and Claude; then "what is online fashion shopping men women" in the same seven tools.

Claims to double check

"4.7M People like this": no source found for this number. Add a source or remove the claim.
"1M People like this": no source found for this number. Add a source or remove the claim.
"100% SECURE PAYMENT": no source found for this claim. Add a source or remove it.

Since the last audit

One issue was fixed since the last audit (an author-related check). Nothing got worse. 21 new issues showed up this time, mostly around missing schema, missing body content and unsourced claims. 15 issues are still standing from before, including the JavaScript-content problem, the missing canonical tag, the title and meta description length, the missing main heading, and the missing structured data.

What we could not measure

Page speed wasn't measured because no performance tool is connected; check it free at pagespeed.web.dev by pasting in the URL. We also don't know how many clicks deep this page sits in your site or whether other pages link to it, which needs a full site crawl (a free trial of a tool like Screaming Frog can produce one). The AI-visibility numbers above come from one engine's single test, not a full sweep, so the manual checks listed are the free way to fill in the rest by hand.

You don't have a claims ledger yet, a simple list of verified facts about Bewakoof. Building one would let this skill check claims like "100% SECURE PAYMENT" and the follower counts against real sources automatically instead of just flagging them for someone to verify by hand.

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: "/contact-us"
Pass Image alt present on all images: all 4 images carry alt text
Pass Open Graph + Twitter card present: og:title, og:description, og:image present

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: 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 online fashion shopping men women"

AI search (web + model) Not mentioned

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

What the AI answered: you would need broader search results covering other popular platforms like Amazon Fashion, Myntra, Flipkart Fashion, and others

"what is online fashion shopping men women"

AI search (web + model) Not mentioned

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

What the AI answered: Online fashion shopping for men and women is purchasing clothing, footwear, accessories, and beauty products through internet-based websites from home rather than physical stores.

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 20 failing checks first, then the 17 warnings

Dimension	Score	Measured of applicable	Weight
Technical SEO	76	9 of 10	20
On-page SEO	67	13 of 13	12
Content quality	38	6 of 6	20
Structured data	44	5 of 5	10
Links	64	3 of 4	10
Performance	incomplete	0 of 8	10
Trust and expertise	47	4 of 4	14
Freshness	50	1 of 1	4
Data	70	5 of 5	8

Technical SEO761 fail · 3 warn

Fail Main content present in server-rendered raw HTML
Observed: "Crawlers see 58 words before JavaScript runs, 364 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
Warn No crawl traps: session-ID or internal-search links, unmanaged parameters
Observed: "final_url carries "?pageId=%2Fcontact-us%2Forder-delivery-payment" while the same content area is also linked at "/contact-us/order-delivery-payment""

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

Recommendation: Standardize on one URL per FAQ tab (e.g. /contact-us/order-delivery-payment) and add a self-referencing canonical; redirect or canonicalize the ?pageId= variant to it.

Location: URL parameters

How to verify: Re-run the audit: SR-CR-06 reads pass
Warn 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; all crawlers allowed via wildcard"

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

Recommendation: Manually inspect the full robots.txt Disallow rules to confirm no /static/, /_next/ (CSS/JS bundle) or similar asset paths are blocked.

Location: robots.txt

How to verify: Re-run the audit: SR-CR-08 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 URL is in the sitemap, reachable in <=3 clicks, not orphaned
Observed: "sitemap includes_url: true (61,432 URLs); /contact-us is also linked directly from the footer under "CUSTOMER SERVICE ... Contact Us""

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

Recommendation: No action required; keep the footer Contact Us link in place.
Pass No cloaking, no near-duplicate/staging mirror
Observed: "Rendered content (364 words) is a superset of raw HTML (58 words), consistent with normal client-side rendering rather than cloaking; no staging/mirror domain indicators present"

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

Recommendation: Periodically diff Googlebot's rendered HTML (via Search Console URL Inspection) against the live page to confirm parity.

Not measured this run (2)

Needs data Redirects to the page are clean, no meta-refresh, no mixed-protocol hop
Observed: "final_url "https://www.bewakoof.com/contact-us?pageId=%2Fcontact-us%2Forder-delivery-payment" differs from requested url "https://www.bewakoof.com/contact-us""

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

Recommendation: Check server response headers for /contact-us to confirm whether the pageId param is added via a single 301/308 or via client-side JS routing; if JS-based, serve the tab content directly at a static path instead.

Location: HTTP response / URL
N/A Paginated pages self-canonicalize
Observed: "No pagination markup or paginated series exists on this contact/FAQ page."

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

Recommendation: None needed.

On-page SEO673 fail · 4 warn

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 detected anywhere on the page"

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

Recommendation: Convert the visible tab labels ("Cancellations", "Refunds & Returns", "My Bewakoof® Wallet", "Offers and Combos", "TriBe Membership") into real <h2> elements phrased as questions.

Location: FAQ tab section

Before: Cancellations Refunds & Returns
After: <h2>How do cancellations, refunds and returns work?</h2>

How to verify: Re-run the audit: SR-ONP-04 reads pass
Fail Title-rewrite risk: not so long/generic/stuffed the engine replaces it
Observed: "title: "Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com" — the generic homepage title, reused verbatim on /contact-us"

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

Recommendation: Give /contact-us a unique, page-specific title.

Location: <title> tag

Before: Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com
After: Contact Us – Order, Delivery, Payment & Returns Help | Bewakoof

How to verify: Re-run the audit: SR-ONP-12 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 Image filenames descriptive, hyphenated, lowercase
Observed: "2 generic/messy filenames"

Expected: Image filenames are descriptive, hyphenated, lowercase.

How to verify: Re-run the audit: SR-ONP-09 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: "/contact-us""

Expected: The URL path is lowercase, hyphenated, with no dates/IDs/params.
Pass Image alt present on all images
Observed: "all 4 images carry alt text"

Expected: Every image carries alt text (empty alt is fine for a decorative image).
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: count 0, density_pct 0 for target keyword "online fashion shopping men women""

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

Recommendation: No stuffing fix needed. Separately, this page's actual intent (contact/support) doesn't match the assigned keyword and should be re-targeted rather than stuffed.

Content quality383 fail

Fail Direct answer up top (BLUF)
Observed: "Main_text opens with: "MEN WOMEN ACCESSORIES | LOGIN Hello there! Need help? Talk to us! WhatsApp Us We're here 24/7. Smart Assistant Instant help Frequently Asked Questions!""

Expected: The first paragraph should directly answer the query 'online fashion shopping men women' within a sentence or two, no throat-clearing or nav chrome.

Recommendation: Add a 2-3 sentence BLUF answering what online fashion shopping for men and women offers (selection, pricing, delivery, returns) before any nav/FAQ content.

Before: MEN WOMEN ACCESSORIES | LOGIN Hello there! Need help? Talk to us! WhatsApp Us We're here 24/7.
After: Online fashion shopping lets men and women browse thousands of T-shirts, dresses, and accessories, compare prices, and get doorstep delivery with cash-on-delivery and a 15-day return window.

How to verify: Re-run the audit: SR-CNT-01 reads pass
Fail Not thin/padded, density over length
Observed: ""Men's T-Shirts Men's Hoodies & Sweatshirts Oversized T-Shirts for Men Men's Long Sleeve T-shirts Men's White T-shirts Men's Crew Neck T-shirts Men's Half Sleeve T-Shirts Men's Printed T-shirts..." — an unbroken enumeration of ~80 internal category links with no explanatory text between them."

Expected: Density over length: sections should carry genuine explanatory content, not a raw list of internal links padding the word count.

Recommendation: Move the raw category list to a dedicated nav/sitemap element and replace body copy with a written guide that references categories in context.

Location: category link block

How to verify: Re-run the audit: SR-CNT-03 reads pass
Fail Fact-density adequate on claim-making pages
Observed: "No factual claims or data points appear anywhere in main_text — content is limited to nav labels, category names, unanswered FAQ question titles ('How do I check the status of my order?'), and a corporate address."

Expected: Claim-making sections (delivery times, return policy specifics, catalog scope) should carry sourced or verifiable data points, not bare labels.

Recommendation: Add specific, sourced facts — actual delivery SLAs, documented return-rate figures, catalog size — instead of bare menu items.

How to verify: Re-run the audit: SR-CNT-09 reads pass
Pass Depth matches intent; under 300 words is thin
Observed: "364 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 364 words (0.0/1,000w)"

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

Not measured this run (4)

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: "Text is composed of link labels and fragments (e.g. 'Need help? Talk to us! WhatsApp Us We're here 24/7.') rather than connected prose paragraphs."

Expected: Grade 8-10 reading ease across coherent sentences, none over 35 words.

Recommendation: Once BLUF/guide prose is added, run a readability check and target grade 8-10.
N/A Varied sentence rhythm (burstiness)
Observed: "No connected sentence sequences exist in main_text to assess rhythm; content is nav labels and link strings."

Expected: Sentence length should vary across real prose so the page doesn't read as flat, unedited text.

Recommendation: Convert to full paragraphs with a mix of short and long sentences once prose content is added.
N/A AI-writing tells within the light-edit band
Observed: "No extended prose passages exist to scan for AI-writing-tell phrasing; content is limited to labels and fragments."

Expected: Fewer than 6 AI-writing-tell flags per 1,000 words of body prose.

Recommendation: When prose is written, light-edit to avoid stock AI transitions ('in today's fast-paced world', 'moreover', etc.).

Structured data442 fail · 2 warn

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

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

How to verify: Re-run the audit: SR-SCH-05 reads pass
Fail Primary schema type matches page purpose
Observed: "jsonld: [] — no structured data of any type present on the page"

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

Recommendation: Add ContactPage schema plus FAQPage schema for the visible Q&A accordion (order status, cancellations, refunds, etc.).

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: "No JSON-LD exists to compare against visible content (jsonld: [])"

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

Recommendation: Once FAQPage/ContactPage schema is added, ensure its question/answer text matches the visible accordion text verbatim.

Links641 fail

Fail Contextual body links first-mention, one link per concept
Observed: "internal_hrefs are all footer/nav category and policy links (e.g. "/men-t-shirts", "/privacy-policy-and-disclaimer"); main_text shows no body prose with inline links"

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

Recommendation: Inside the FAQ answer text (e.g. under "How do I check the status of my order?"), add an inline contextual link to "Track Order" the first time it's mentioned, separate from the footer link.

Location: FAQ answer body

How to verify: Re-run the audit: SR-LNK-03 reads pass
Pass Body internal-link count scales with length
Observed: "7 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: "7 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: "No body-prose anchors exist to evaluate; visible links are nav/category labels such as "Men's T-Shirts", "Women's Dresses""

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), use varied, descriptive anchors rather than repeating the same phrase everywhere.
N/A Outbound links working, authoritative, to primary sources
Observed: "external_hrefs are all owned social/app-store profiles (Facebook, Instagram, Twitter, Pinterest, Snapchat, App Store, Play Store); no third-party citation links present"

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

Recommendation: No action needed now; if FAQ content later references consumer-protection or shipping regulations, link to the authoritative primary source.

Trust and expertise471 fail · 2 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
Warn E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
Observed: "Trust signals present (HTTPS, about/contact/privacy linked) but no author byline, no reviewer date, and no first-hand experience markers; domain has 6,176 referring domains / DR 346 while this specific page has no distinguishing authority signals"

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

Recommendation: Track this as a qualitative internal heuristic, not a literal Google ranking score; for this page, close the gap by attributing content to the CX/support team and reclassifying it out of the "article" bucket in reporting.

How to verify: Re-run the audit: SR-EAT-06 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.

Not measured this run (2)

N/A Affiliate/commercial disclosure above the fold
Observed: "No affiliate or sponsored-content indicators found; this is the retailer's own first-party contact/support page."

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

Recommendation: None needed.
N/A No regulatory superlatives on regulated topics
Observed: "Page covers apparel-ecommerce order/delivery/payment support topics; YMYL flag for this run is "no"."

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

Recommendation: None needed.

Freshness501 warn

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

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

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

Not measured this run (2)

N/A Freshness-sensitive (QDF) topics are genuinely recent
Observed: "No dates, season references, or 'as of'/'last updated' markers appear anywhere in the content."

Expected: Evergreen topics need at least an honest last-updated date; QDF-style topics need demonstrable currency.

Recommendation: Add a last-updated/last-reviewed date if this page is meant to be treated as editorial content.
N/A No outdated statistics on a dynamic topic
Observed: "The only numeric figures present are social-proof counts: '4.7M People like this' and '1M People like this', with no date attached."

Expected: Statistics on a dynamic topic should be current and dated so they can be fact-checked.

Recommendation: Date-stamp any quantitative social-proof figures shown, or remove them if they can't be kept current.

Performanceincompletenot measured

Not measured this run (8)

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

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

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

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

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

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

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

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

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

AI answersincomplete4 fail

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

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

How to verify: Re-run the audit: AI-EXT-04 reads pass
Fail Each passage stands alone
Observed: "main_text is a flat run-on of nav items, category names, and FAQ titles ('How do I check the status of my order?' with no answer shown) with no self-contained answer passages."

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

Recommendation: Write short, self-contained answer paragraphs (40-80 words) under each heading that fully answer that heading's question on their own.

Location: main_text

How to verify: Re-run the audit: AI-EXT-01 reads pass
Fail Entity context retained in each passage
Observed: "Where any sentence-like content exists (e.g., FAQ titles), it does not name the entity ('Bewakoof') or the topic ('online fashion shopping') within the same span."

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

Recommendation: Repeat 'Bewakoof' and 'online fashion shopping for men and women' explicitly inside each answer passage rather than relying on pronouns or page context.

Location: main_text

How to verify: Re-run the audit: AI-EXT-02 reads pass
Fail Attribution survives inside the passage
Observed: "No sourced claims exist anywhere in main_text, so none can carry an inline source within the same passage."

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

Recommendation: When adding claims, place the source/credential in the same sentence or immediately adjacent line, not in a separate footnote section.

Location: main_text

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

AI citationsincomplete5 fail · 2 warn

Fail Claims attributable: inline sources on load-bearing facts
Observed: "The fetched content is a homepage/category shell: nav links (MEN/WOMEN/ACCESSORIES), FAQ headings with no answer text, a corporate address, and a sitemap of product category links. No sentence in main_text makes a factual claim with an inline source or outbound link."

Expected: At least one attributed claim per 500 words, with a real outbound link to a source.

Recommendation: Add an editorial section (e.g., a 'What is online fashion shopping?' explainer or buying guide) that states specific facts and links out to named sources for any statistic or claim.

Location: main_text (site-wide nav/FAQ shell)

Before: Frequently Asked Questions! Orders, Delivery & Payments ...
After: According to a 2025 Statista report on Indian e-commerce, online apparel sales grew 18% YoY <a href="...">source</a>.

How to verify: Re-run the audit: AI-GATE-02 reads pass
Fail Entity-dense: claims pinned to named things
Observed: "h1 is an empty array (no H1 present anywhere on the page). The title does name the entity ('...Bewakoof.com'), but first_100_words is nav/menu text ('MEN WOMEN ACCESSORIES | LOGIN Hello there! Need help?...') that does not name the entity until 'My Bewakoof® Wallet' appears deep in FAQ nav links."

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

Recommendation: Add a visible H1 that names the brand and topic (e.g., 'Bewakoof: Online Fashion Shopping for Men & Women') and open the first real paragraph with the brand name.

Location: h1 / first_100_words

Before: h1: [] ; first words: 'MEN WOMEN ACCESSORIES | LOGIN Hello there!...'
After: h1: 'Bewakoof – Online Fashion Shopping for Men & Women' ; first paragraph: 'Bewakoof is an online fashion shopping destination for men and women in India, offering...'

How to verify: Re-run the audit: AI-GATE-03 reads pass
Fail Corroborated on an independent trusted domain
Observed: "main_text contains no load-bearing factual claims (only nav labels, category names, and unanswered FAQ headings), so there is nothing on the page that could be cross-checked against an independent trusted domain."

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

Recommendation: Once AI-GATE-02 content is added, ensure at least one such claim (e.g., market-size or fit stats) also appears on an independent, trusted third-party source.

Location: main_text

How to verify: Re-run the audit: AI-GATE-06 reads pass
Fail Key facts as semantic triples, consistent naming
Observed: "main_text is composed almost entirely of noun-phrase menu labels ('Men's Jeans', 'Women's Co-ord Sets') with no subject-verb-object sentences stating facts about Bewakoof or online fashion shopping."

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

Recommendation: Add declarative sentences, e.g., 'Bewakoof offers free 15-day returns on men's and women's clothing', using the full brand name consistently rather than 'we'/'us'.

Location: main_text

How to verify: Re-run the audit: AI-ENT-02 reads pass
Fail Information gain: a sourced specific the consensus lacks
Observed: "Entire page content is navigation links, category names, unanswered FAQ question titles, and footer boilerplate (address, social counts); no named first-hand example, expert quote, original data set, or forward-looking analysis appears anywhere in main_text."

Expected: Commercial pages should reach information-gain rung L3+ (aggregated original data with sample size and date range) or above.

Recommendation: Collect and publish first-party data currently absent from the page: e.g. top-selling men's/women's categories by unit volume, average delivery time in days, average return/exchange rate by category, computed from a full quarter of actual order data (sample floor: several thousand orders) with an explicit date range (e.g. 'Jan–Jun 2026 order data'), presented with a brief methodology note rather than an invented figure.

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 floor + salience
Observed: "Many named entities appear (Men's T-Shirts, Women's Dresses, Marvel, Disney, Avengers, Star Wars, Batman, Superman, Joker, Bewakoof Wallet, TriBe Membership), but they are category/nav labels, not entities grounding an answer to either target question, and 'Bewakoof' itself is not salient until deep into the text."

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

Recommendation: Restructure so 'Bewakoof' and 'online fashion shopping' co-occur in the opening sentence(s), rather than entity density coming entirely from category-menu noise.

Location: main_text

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, banned superlatives, or misleading claims were found in the supplied content — but this is largely because the page contains almost no substantive prose to make such claims in the first place."

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

Recommendation: When adding the editorial content required by AI-GATE-02, keep new claims verifiable and avoid unqualified superlatives like 'best' without support.

Location: main_text

Not measured this run (9)

Needs data Knowledge-graph presence
Observed: "No data was supplied on Wikipedia/Wikidata presence, a knowledge panel, or other knowledge-base entries for the Bewakoof brand."

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

Recommendation: Manually check Wikipedia/Wikidata and Google Knowledge Panel for 'Bewakoof' and report as a founder-level check.

Location: external (not observable from page data)
N/A Every statistic/quotation attributes to a named source
Observed: "No statistics or quotations appear anywhere in the supplied main_text — content is limited to navigation labels, category names, and unanswered FAQ titles."

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

Recommendation: If/when statistics are added (e.g., customer counts, delivery-time claims), attribute each to a named source on the same line.

Location: main_text
N/A No fabricated or unverifiable statistic or quote
Observed: "No statistic or quote is present in main_text to assess as fabricated or unverifiable."

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

Recommendation: Apply this check once statistical/quoted claims are added per AI-CITE-01.

Location: main_text
N/A Authoritative declarative tone, with the YMYL hedging exception
Observed: "There is essentially no declarative prose in main_text to assess tone against — content is nav labels and unanswered FAQ titles. Topic is marked non-YMYL, so the hedging exception does not apply."

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

Recommendation: Once editorial paragraphs are added, write them in a direct, declarative voice.

Location: main_text
Needs data Per-engine backend presence and crawler access
Observed: "The CITABILITY SAMPLE provides one ungraded (GRADE: X) answer per question without identifying which of the 7 target engines (chatgpt, copilot, perplexity, ai_overviews, ai_mode, gemini, claude) produced it, so no per-engine backend presence can be reported."

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

Recommendation: Re-run the citability sample with engine attribution captured per row so presence/absence can be reported per target engine as required.

Location: citability sample metadata (engine field missing)
N/A Training-only blocks presented as a documented trade-off
Observed: "AUTO FINDINGS report no unknown/blocked bot tokens in robots.txt (AI-BOT-03 pass); no training-only crawler block is present to evaluate as a stated trade-off."

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

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

Location: robots.txt
N/A llms.txt and IndexNow carry low/zero weight, never a gate
Observed: "No llms.txt or IndexNow data was supplied in AUTO FINDINGS or page data."

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

Recommendation: Optionally check for llms.txt/IndexNow and note the result informationally; do not treat as a scored gate.

Location: site root (not checked)
Needs data Knowledge-graph footprint (web search sample)
Observed: "No web-search sample of Bewakoof's cross-platform or knowledge-base presence was supplied beyond the two citability-sample answers, neither of which surfaced bewakoof.com in domains lists (shopclues.com, gatamagazine.com, demonssouls.wikidot.com / easily61.blogspot.com, steelworld.com.ph, sprayonyx.com., besttool85.blogspot.com, demonssouls.wikidot.com, keywords84.blogspot.com)."

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

Recommendation: Run a dedicated brand-name web-search sample (manual check) for 'Bewakoof' to confirm knowledge-graph and cross-platform presence.

Location: external (not observable from supplied data)
Needs data Brand-mention sample on AI-visibility-correlated platforms
Observed: "The domains cited in the citability sample (shopclues.com, gatamagazine.com, demonssouls.wikidot.com, easily61.blogspot.com, steelworld.com.ph, sprayonyx.com., besttool85.blogspot.com, keywords84.blogspot.com) are low-authority/unrelated sites, not forums, video, news, or professional-network mentions of Bewakoof specifically; no dedicated brand-mention sample was supplied."

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

Recommendation: Run a dedicated brand-mention sample for 'Bewakoof' across Reddit, YouTube, news, and LinkedIn as a manual check.

Location: external (not observable from supplied data)

Programmatic pagesincompletenot measured

Not measured this run (3)

N/A Every page carries genuinely unique data
Observed: "Page is a single, standalone Contact Us/FAQ page, not one of a templated set."

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

Recommendation: None needed.
N/A No two pages share >80% of their field content
Observed: "Page is a single, standalone Contact Us/FAQ page, not one of a templated set."

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

Recommendation: None needed.
N/A Scale governance: review at 100+, justification at 500+
Observed: "Page is a single, standalone Contact Us/FAQ page, not one of a templated set."

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

Recommendation: None needed.

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
15 Days Return Policy	Pass	-
4.7M People like this	Warn	Add a source or remove the claim
1M People like this	Warn	Add a source or remove the claim
We're here 24/7	Pass	-
100% SECURE PAYMENT	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 8 gaps listed below

Add: BLUF paragraph directly answering 'online fashion shopping men women' before any nav/FAQ content
Add: Editorial buying-guide prose covering how to shop online for men's and women's fashion (sizing, fabrics, trends, payment/delivery options)
Cut: Raw ~80-item category link enumeration from body copy; retain only in a nav/sitemap element to avoid it reading as filler and to reduce cannibalization risk against the individual category landing pages it links to
Add: Full-sentence answers under each FAQ question (currently only titles like 'How do I check the status of my order?' with no answer text)
Add: First-party data section: top-selling categories, delivery time, return rate, with stated sample size and date range
Add: Comparison content: how to choose between brands/price tiers/styles for men's vs. women's fashion (comparison journey stage, currently absent)
Add: Validation content: attributed customer reviews or expert styling quotes (validation journey stage, currently only vague 'People like this' counts)
Add: Last-updated/last-reviewed date for policy claims (return policy, COD, security)

Information gain: L0 — the page restates no consensus and contains no facts, examples, quotes, or data about online fashion shopping; it is site navigation, category link labels, and unanswered FAQ titles. to L3 — publish aggregated first-party data (e.g., top-selling men's/women's categories, average delivery time, return rate) with an explicit sample size and date range, supplemented with a real buying guide and at least one attributed customer/expert quote (L2.5) to support commercial trust signals.

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 37 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	Content quality	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	FAQ answer 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	AI answers	At least half of H2 headings are question-shaped.	Re-run the audit: AI-EXT-04 reads pass
High	Fix	FAQ tab section	See finding	Re-run the audit: SR-ONP-04 reads pass
High	Fix	Main text (site wide nav/FAQ shell)	See finding	Re-run the audit: AI-GATE-02 reads pass
High	Fix	H1 / first 100 words	See finding	Re-run the audit: AI-GATE-03 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-01 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-02 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-EXT-03 reads pass
High	Rewrite section	Category 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	AI citations	See finding	Re-run the audit: AI-GATE-04 reads pass
Medium	Fix	<title> tag	See finding	Re-run the audit: SR-ONP-12 reads pass
Medium	Fix	Main text	See finding	Re-run the audit: AI-ENT-02 reads pass
Medium	Fix	Main text	See finding	Re-run the audit: AI-GATE-06 reads pass
Medium	Rewrite section	Content quality	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
Medium	Fix	On-page SEO	Image filenames are descriptive, hyphenated, lowercase.	Re-run the audit: SR-ONP-09 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	Robots.txt	See finding	Re-run the audit: SR-CR-08 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	Trust and expertise	See finding	Re-run the audit: SR-EAT-06 reads pass
High	Fix	Main text	See finding	Re-run the audit: AI-ENT-01 reads pass
Medium	Fix	URL parameters	See finding	Re-run the audit: SR-CR-06 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	Middle section, 'CONNECT WITH US'	See finding	Re-run the audit: data-fc-2 reads pass
Medium	Fix stat	Middle section, 'CONNECT WITH US'	See finding	Re-run the audit: data-fc-3 reads pass
Medium	Fix stat	Bottom section, above app download	See finding	Re-run the audit: data-fc-5 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

No crawl traps: session-ID or internal-search links, unmanaged parameters
robots.txt well-formed, does not block CSS/JS, declares a sitemap
Each H2 a distinct user sub-question, not a vague label
Title-rewrite risk: not so long/generic/stuffed the engine replaces it
Primary schema type matches page purpose
Contextual body links first-mention, one link per concept
E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
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
Direct answer up top (BLUF)
Not thin/padded, density over length
Fact-density adequate on claim-making pages
Information gain: a sourced specific the consensus lacks
Claim has no source
Claim has no source
Claim has no source

Still standing

Main content present in server-rendered raw HTML
Self-referencing canonical, absolute, no conflict
Title length 50-60 chars
Exactly one H1, keyword-bearing, first heading in the DOM
Meta description unique, 150-160 chars, keyword present
Primary keyword naturally within the first 100 words
Image filenames descriptive, hyphenated, lowercase
JSON-LD present and valid
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

Evidence and glossary

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

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

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

Evidence

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

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.