Implementation report: https://www.bewakoof.com/faq
Something is stopping this page from being found at all: right now, Google's very first look at it only finds 58 of your 364 words, because the rest only appears after the page's code finishes running in the browser. Your FAQ page scores 52 out of 100, which the audit calls "critical issues present" since at least one problem is serious enough to block results. There are 39 things to fix in total; below are the five most valuable ones, then everything else grouped by who should do it.
The 5 biggest problems (fix these first)
1. Google's first pass at your page sees almost none of it
Current: Crawlers see 58 words before JavaScript runs, 364 after.
Google and AI assistants mostly read the plain HTML your server sends before any code runs. If your real content (the FAQ text) only shows up after JavaScript loads it in, most crawlers give up before they ever see it, so effectively only 58 of your 364 words count, no matter how good the rest is.
Fix:
- View the page's raw source (or fetch the URL with curl) and confirm only a fraction of the text is there before scripts run.
- Have a developer move the FAQ questions and answers into the HTML the server sends first, instead of loading them in afterward with JavaScript.
- Re-check the raw HTML afterward and confirm the word count matches what a visitor actually sees (364).
Who: A developer, likely a day or so depending on how the site is built.
2. Your page never actually answers "online fashion shopping for men and women"
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!
Search engines and AI assistants scan the opening lines of a page to decide what it's about and whether to quote it. Right now those lines are menu items and a chat-widget greeting, so there's no sentence anywhere for either to lift as an answer to your target phrase, even though the page has 364 words elsewhere.
Fix: Replace the opening with a direct-answer paragraph: Online fashion shopping for men and women lets you browse tops, bottoms and accessories by size, price and delivery speed from one storefront: here's how to choose what actually fits and ships fast.
Who: A writer, about 30 minutes.
3. Your page has no main heading at all
Current: (missing)
The main heading (H1) is the strongest single signal telling Google and screen readers what a page is about. With none, engines fall back to weaker signals, and this page's chance of ranking or being cited for its target phrase drops.
Fix:
- Add exactly one heading tag near the top of the visible content, containing the keyword:
<h1>Online Fashion Shopping for Men & Women | Bewakoof.com</h1>. - Make sure it's the first heading in the page's code.
Check it worked: view the page source and confirm exactly one <h1> appears with that text.
Who: A developer, under an hour.
4. There's no structured data telling Google this is an FAQ page
Current: jsonld: [] — no structured data blocks found on a page titled "Frequently Asked Questions!"
Structured data (a hidden code block describing what type of page this is) is what lets Google show expanded question-and-answer results in search, which take up more space and get more clicks. With none here, this FAQ page has no chance of that treatment.
Fix: Add FAQPage structured data for the rendered Q&A content, and/or Organization schema using the corporate address already shown on the page.
Who: A developer, a couple of hours.
5. There are no links inside your FAQ answers connecting related topics
Current: main_text is nav/category labels only (e.g. "Orders, Delivery & Payments")
When real answer text exists, linking a term the first time it's mentioned (for example, linking "Track Order" the first time it comes up) helps both readers and search engines find related pages. Right now there's no answer text to link from at all, only category labels and menu links, which engines discount because they're identical on every page of the site.
Fix: Once the FAQ answers are rendered as real text (problem 1), add one link at each concept's first mention, e.g. link "Track Order" the first time it appears in an answer, rather than only in the nav or footer.
Who: A developer and a writer together, a couple of hours once the content exists.
Also worth fixing
For a developer:
- No canonical tag anywhere on the page: add a tag pointing to this exact URL so Google knows which version is the real one.
- FAQ topics can spawn duplicate URLs: the
?pageId=...version of this page has no canonical tag, risking duplicate-content confusion; point it to a clean path or block it from indexing. - No structured data blocks exist at all: add a valid FAQPage code block once the answers are real text.
- Missing basic company schema: add Organization, BreadcrumbList and WebSite structured data so Google has a baseline signal for the whole site.
- No dates in structured data: once you add a visible "last updated" date, mirror it in the code as
datePublished/dateModified. - Two images have generic filenames: rename them to lowercase, hyphenated, descriptive names (e.g.
mens-hoodie-navy.jpg).
For a writer:
- No author on the page: add a visible byline linking to a bio page so readers know who wrote the answers.
- No section headings exist at all: turn each FAQ category into a heading phrased as a real question, e.g. "How do I check my order status?"
- FAQ categories are labels, not headings: give
Orders, Delivery & Payments,Cancellations Refunds & ReturnsandMy Bewakoof® Wallettheir own proper headings. - No sourced facts anywhere on the page: add a short "About Bewakoof" or buying-guide section with real, attributed facts and outbound links.
- The opening never names the business: start the visible content with a sentence naming Bewakoof and what it sells.
- Nothing on the page can stand alone as an answer: rewrite each FAQ topic as a self-contained paragraph.
- The brand name is never the subject of a sentence: once you add answers, say "Bewakoof" directly instead of "it" or "this."
- The whole content area is copied nav and footer text: delete it from the article body and write a real one in its place.
- No sentence variety, because there's no real writing yet: mix short and long sentences once content exists.
- Title is the homepage title copy-pasted onto this page (current:
Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com, 66 characters): replace withOrder, Delivery & Payment FAQs | Bewakoof Help Centre(keep it under 60 characters). - Meta description is far too long (current, 311 characters:
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!): replace withShop online fashion for men and women at Bewakoof: trendy clothing, footwear and accessories, with free shipping, easy returns and cash on delivery.(keep it between 140 and 160 characters). - Category lists aren't written as facts: turn lists like "Men's T-Shirts Men's Hoodies & Sweatshirts..." into sentences, e.g.
Bewakoof sells men's hoodies, joggers, and oversized T-shirts starting at ₹499. - No date shown anywhere on the page: add a visible "Last updated" date.
- No reviewer credited: add a reviewer name, credential, and last-reviewed date.
- Your target phrase never appears in the first 100 words: work it naturally into the opening paragraph (same fix as problem 2 above).
- No accurate "last modified" signal anywhere: once you add the visible date above, keep it genuinely current.
- Brand and category names sit in link lists, not sentences: move them into real sentences near the top of the page.
- Follower counts have no source (
4.7M People like this,1M People like this): add a source and date, or remove them. - Return-policy claim has no source (
15 Days Return Policy): add a source, or remove it. - Stats read as current facts with no date attached: timestamp the follower counts and return-policy figure, and set a cadence to refresh them.
For you:
- Adding one real, original data point: the audit found the page currently has zero article content, so it can't compete with real buying guides on this phrase. Closing that gap needs an aggregated, dated stat from your own order data (with sample size) plus one attributed expert quote, which is a resourcing call: does someone have access to that order data and time for an interview? The evidence here favors approving it, since it's the single biggest lever for both search ranking and AI-assistant visibility.
- Getting outside sites to corroborate your facts: once real content exists, seeking press or marketplace coverage that repeats the same facts about Bewakoof is a PR decision worth queuing, since nothing outside bewakoof.com currently backs up any claim about the brand.
What to add to the page
- Cut the raw nav/footer/category link dump currently standing in for article body.
- Add a direct-answer opening paragraph for "online fashion shopping for men and women" before anything else.
- Add editorial sections on shopping categories, sizing/fit guidance, and how to compare shopping options.
- Add actual answer text for the listed FAQ questions instead of bare titles.
- Add real customer reviews or an expert quote, and dated trust signals, instead of undated badges.
- Add a visible "last updated" date.
What is already working
- Your site loads over HTTPS with no soft-404s, and nothing blocks Google from indexing it.
- All 4 images on the page carry alt text.
- Open Graph and Twitter card tags (title, description, image) are all present.
- You have a strong backlink profile: 6,176 referring domains and 26,634 backlinks sitewide.
- Your robots.txt is well-formed, declares your sitemaps, and this page is in the sitemap and reachable within 3 clicks.
How AI assistants see this page
Bewakoof scored 0 for AI visibility across 2 test questions; this is one engine's answer on one date (2026-09-18), so treat it as directional only, not definitive.
- "best online fashion shopping men women": your page was absent from the answer, which instead said "ShopClues.com is the primary online fashion platform visible for men and women in India."
- "what is online fashion shopping men women": your page was absent again; the answer noted it "does not name any actual fashion retailers, e-commerce platforms, or services available in the Indian market where buyers can shop for men's."
To check by hand, try asking chatgpt, copilot, perplexity, Google AI Overviews, Google AI Mode, gemini and claude both "best online fashion shopping men women" and "what is online fashion shopping men women," and see if Bewakoof ever comes up.
Claims to double check
15 Days Return Policy: no source found for this claim. Add one or remove it.4.7M People like this: no source found. Add one or remove it.1M People like this: no source found. Add one or remove it.
Since the last audit
One issue from the last audit has been fixed (a trust-signal check). Nothing got worse. 18 new issues showed up, mostly about AI-assistant visibility (no sourced facts, no self-contained answers, entity names never used in real sentences) and freshness (no dates, no sources for stats). 20 problems from before are still unresolved, including the missing canonical tag, missing schema, missing H1, and no author byline.
What we could not measure
Page speed (Core Web Vitals) wasn't measured because no performance tool is connected; check it free at pagespeed.web.dev. How deep this page sits in your site's link structure, and whether it's an orphan page, is unknown without a full site crawl; Google Search Console's coverage report is a free way to check. The AI-visibility check above covered only one engine and two questions on one date; the free way to broaden it is to ask the seven assistants listed above by hand. Whether Bewakoof has any Wikipedia, Wikidata, or knowledge-panel presence, or gets mentioned on forums, video or news sites, wasn't checked either; a manual search on each covers that for free.
A claims ledger would let this skill say more, for example confirming the return-policy and follower numbers instead of flagging them as unsourced every time.
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.
"best online fashion shopping men women"
Not mentioned: the answer did not use or name this page.
What the AI answered: ShopClues.com is the primary online fashion platform visible for men and women in India.
"what is online fashion shopping men women"
Not mentioned: the answer did not use or name this page.
What the AI answered: does not name any actual fashion retailers, e-commerce platforms, or services available in the Indian market where buyers can shop for men's or women's clothing and accessories.
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 24 failing checks first, then the 15 warnings
| Dimension | Score | Measured of applicable | Weight |
|---|---|---|---|
| Technical SEO | 75 | 8 of 10 | 20 |
| On-page SEO | 67 | 13 of 13 | 12 |
| Content quality | 32 | 8 of 8 | 20 |
| Structured data | 44 | 5 of 5 | 10 |
| Links | 64 | 3 of 4 | 10 |
| Performance | incomplete | 0 of 8 | 10 |
| Trust and expertise | 36 | 4 of 4 | 14 |
| Freshness | 31 | 3 of 3 | 4 |
| Data | 50 | 3 of 3 | 8 |
Technical SEO
- 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
- Fail No crawl traps: session-ID or internal-search links, unmanaged parameters
Observed: "final_url query: "?pageId=%2Fcontact-us%2Forder-delivery-payment"; canonical: null"
Expected: No session-ID or internal-search links; faceted URLs are canonicalized or noindexed.
Recommendation: Add a canonical tag on every /contact-us?pageId=... variant pointing to a clean canonical path (e.g. /contact-us/order-delivery-payment), or noindex the query-parameterized variants.
Location: final URL query parameter + missing canonical tag
Before: https://www.bewakoof.com/contact-us?pageId=%2Fcontact-us%2Forder-delivery-payment (no canonical tag)
After: <link rel="canonical" href="https://www.bewakoof.com/contact-us/order-delivery-payment" />How to verify: Re-run the audit: SR-CR-06 reads pass
- Warn Self-referencing canonical, absolute, no conflict
Observed: "no canonical tag present"
Expected: The canonical tag points to this exact URL.
How to verify: Re-run the audit: SR-CR-04 reads pass
- Pass 200 over HTTPS, no soft-404
Observed: "HTTP 200 over https"
Expected: The page returns HTTP 200 over HTTPS.
- Pass Indexable: no noindex, Googlebot not blocked
Observed: "no noindex directive, Googlebot not blocked"
Expected: No noindex directive and Googlebot is not blocked in robots.txt.
- Pass No nosnippet / max-snippet:0
Observed: "no nosnippet/max-snippet:0 directive"
Expected: robots_meta carries no nosnippet or max-snippet:0 directive.
- Pass robots.txt well-formed, does not block CSS/JS, declares a sitemap
Observed: "sitemaps declared: https://www.bewakoof.com/sitemap_index.xml, https://www.bewakoof.com/blog/sitemap_index.xml; robots.txt fetched status 200, all major bots allowed via wildcard"
Expected: robots.txt is well-formed, allows CSS/JS, and declares an absolute sitemap URL.
Recommendation: No action needed now; periodically re-check that no Disallow rule targets /_next/static/ or other JS/CSS asset paths.
Location: https://www.bewakoof.com/robots.txt
- Pass URL is in the sitemap, reachable in <=3 clicks, not orphaned
Observed: "sitemap.includes_url: true; footer link href "/contact-us" present on this page"
Expected: The URL appears in the XML sitemap and is reachable within three clicks of the homepage.
Recommendation: Confirm the sitemap entry points to the clean canonical /contact-us path rather than a pageId-parameterized duplicate, consistent with the footer link already present.
Location: sitemap_index.xml + site footer navigation
Not measured this run (3)
- Needs data Redirects to the page are clean, no meta-refresh, no mixed-protocol hop
Observed: "url:"https://www.bewakoof.com/faq" final_url:"https://www.bewakoof.com/contact-us?pageId=%2Fcontact-us%2Forder-delivery-payment""
Expected: Any redirect chain into this URL is a single clean 301/308, same protocol.
Recommendation: Check server response headers to confirm /faq redirects to /contact-us via a single 301/308 HTTP redirect (not client-side JS or meta-refresh), and collapse any intermediate hops.
Location: redirect chain: /faq → /contact-us?pageId=...
- N/A Paginated pages self-canonicalize
Observed: "No pagination parameters, rel=next/prev, or page-number markup found on this URL."
Expected: A paginated page canonicalizes to itself, never to page 1, and is never blanket-noindexed.
Recommendation: No action needed.
Location: n/a
- Needs data No cloaking, no near-duplicate/staging mirror
Observed: "js_dependency:"full", raw_word_count:58, rendered_word_count:364; single fetch only, no bot-vs-browser comparison available"
Expected: What's served matches what's indexed; no staging mirror or near-duplicate exists.
Recommendation: Run a side-by-side comparison of Googlebot's rendered HTML (via URL Inspection tool) vs. a normal browser fetch, and search for staging/mirror subdomains to rule out cloaking or duplicate mirrors.
Location: whole-page technical check
On-page SEO
- Fail Exactly one H1, keyword-bearing, first heading in the DOM
Observed: "no H1 found"
Expected: Exactly one H1 is present.
How to verify: Re-run the audit: SR-ONP-02 reads pass
- Fail Each H2 a distinct user sub-question, not a vague label
Observed: "h2: [] (zero H2 elements); visible labels: "Orders, Delivery & Payments", "Cancellations Refunds & Returns", "My Bewakoof® Wallet""
Expected: Each H2 covers a distinct sub-question in the reader's own words.
Recommendation: Wrap each FAQ category and ideally each individual question (e.g. 'How do I check the status of my order?') in a proper <h2>/<h3> heading tag.
Location: FAQ category list, main content area
Before: Orders, Delivery & Payments (rendered as styled div/span, no heading tag)
After: <h2>Orders, Delivery & Payments</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" served on the FAQ/Contact-us page"
Expected: The title is specific and well-formed enough that Search Console shows it unrewritten.
Recommendation: Give /contact-us its own specific <title> reflecting its actual content instead of reusing the site-wide homepage title.
Location: <title> tag
Before: Online Fashion Shopping for Men, Women, Accessories - Bewakoof.com
After: Order, Delivery & Payment FAQs | Bewakoof Help CentreHow 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 inferred keyword "online fashion shopping men women""
Expected: Keyword density reads naturally; >2% warns, confirmed stuffing across headings/alt/sentences fails.
Recommendation: No action needed.
Location: whole page body text
Content quality
- Fail Direct answer up top (BLUF)
Observed: "The extracted body 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!' — pure site-chrome/nav, no sentence that answers the query."
Expected: First paragraph directly answers 'online fashion shopping for men and women' (what it is, key benefit/decision) with no nav throat-clearing.
Recommendation: Write an opening paragraph that states directly what online fashion shopping offers men and women shoppers (categories, sizing, delivery) before any nav content.
Location: start of main_text (no H1 present)
Before: MEN WOMEN ACCESSORIES | LOGIN Hello there! Need help? Talk to us!
After: Online fashion shopping for men and women lets you browse tops, bottoms and accessories by size, price and delivery speed from one storefront — here's how to choose what actually fits and ships fast.How to verify: Re-run the audit: SR-CNT-01 reads pass
- Fail Not thin/padded, density over length
Observed: "Entire main_text is navigation menus, footer links, an FAQ title list with no answer bodies, and a corporate address — zero editorial paragraphs."
Expected: Dense, purposeful content — not filler or boilerplate substituting for article body.
Recommendation: Cut the nav/footer text from the content area entirely and build an actual article body around it.
Location: footer block of main_text
Before: CUSTOMER SERVICE Contact Us Track Order Return Order Cancel Order COMPANY About Us Terms & Conditions Privacy Policy We are Hiring
After: (remove from article body; keep only in site template footer)How to verify: Re-run the audit: SR-CNT-03 reads pass
- Fail Readability in the audience band
Observed: "No coherent sentences exist to grade; text is fragments like 'Need help? Talk to us! WhatsApp Us We're here 24/7.' and long unbroken product-link strings."
Expected: Readable grade-8–10 prose, sentences under 35 words.
Recommendation: Add real sentences and paragraphs so readability can be measured and tuned to grade 8-10.
Location: main_text overall
How to verify: Re-run the audit: SR-CNT-04 reads pass
- Fail Varied sentence rhythm (burstiness)
Observed: "No sentence rhythm exists — content is a flat run-on list ('Men's Jeans Women's Wide Leg Jeans Women's Jeggings Women's Joggers...')."
Expected: Varied sentence length signaling edited human writing.
Recommendation: Write mixed short/long sentences once real content is added.
Location: category list section of main_text
How to verify: Re-run the audit: SR-CNT-06 reads pass
- Fail Fact-density adequate on claim-making pages
Observed: "'4.7M People like this 1M People like this' is presented as a factual claim with no source or date attached."
Expected: Claim-making sections carry sourced, dated data points.
Recommendation: Either drop the follower counts from article content or attribute + date them (e.g., 'X platform followers as of Sept 2026').
Location: social block of main_text
Before: 4.7M People like this 1M People like this
After: 4.7M Facebook followers and 1M Instagram followers (as of September 2026, per platform analytics).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 (2)
- 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 AI-writing tells within the light-edit band
Observed: "Page has no drafted prose (only nav/UI strings), so AI-writing-tell density cannot be assessed."
Expected: Fewer than 6 AI-writing-tell flags per 1,000 words.
Recommendation: Re-check this rule once editorial content is written.
Location: n/a
Structured data
- Fail Baseline trio: Organization/LocalBusiness + BreadcrumbList + WebSite
Observed: "baseline trio present: none"
Expected: Organization/LocalBusiness, BreadcrumbList and WebSite schema are all present.
How to verify: Re-run the audit: SR-SCH-05 reads pass
- Fail Primary schema type matches page purpose
Observed: "jsonld: [] — no structured data blocks found on a page titled "Frequently Asked Questions!""
Expected: The primary @type matches the page's purpose (Article/Product/LocalBusiness/FAQPage/...).
Recommendation: Add FAQPage JSON-LD for the rendered Q&A content, and/or Organization schema using the corporate address already shown on the page.
Location: page <head> / JSON-LD
How to verify: Re-run the audit: SR-SCH-02 reads pass
- Warn JSON-LD present and valid
Observed: "no JSON-LD structured data found"
Expected: At least one valid JSON-LD block is present; an FAQ visible on the page has FAQPage schema.
How to verify: Re-run the audit: SR-SCH-01 reads pass
- Warn Dates: one visible date; datePublished and dateModified in JSON-LD
Observed: "no datePublished/dateModified found"
Expected: Exactly one visible date; both datePublished and dateModified are in JSON-LD and consistent.
How to verify: Re-run the audit: SR-SCH-07 reads pass
- Pass No schema misuse, no retired @type
Observed: "0 JSON-LD type(s): none"
Expected: No Product/Review type without matching content; no retired @type.
Not measured this run (2)
- N/A @graph well-formed
Observed: "no JSON-LD to check"
Expected: A single @context, @id-linked entities, one root, no orphans or circular refs.
- N/A Schema content matches visible content
Observed: "jsonld: []"
Expected: Schema name/headline/author overlaps the visible content by at least 60%; no schema-only FAQs/ratings.
Recommendation: Once FAQPage schema is added, ensure each schema Question/Answer pair exactly mirrors an on-page visible question and answer — never add schema-only FAQ entries.
Location: page <head> / JSON-LD
Links
- Fail Contextual body links first-mention, one link per concept
Observed: "main_text is nav/category labels only (e.g. "Orders, Delivery & Payments"); faq_visible:false — no rendered answer prose with inline links"
Expected: Contextual body links appear at first mention; nav/footer links don't count.
Recommendation: Once FAQ answer content is rendered server-side, add contextual links at first mention (e.g. link 'Track Order' the first time it appears in an answer) rather than relying solely on nav/footer links.
Location: FAQ answer body (currently unrendered, faq_visible:false)
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: "Visible internal links are all nav/mega-menu or footer items (e.g. "Men's T-Shirts", "Women's Dresses", "About Us", "Terms & Conditions")"
Expected: Anchor text is varied and descriptive; no generic "click here" or exact-match stuffing.
Recommendation: Re-evaluate once genuine FAQ answer copy with contextual links exists.
Location: site nav / footer
- N/A Outbound links working, authoritative, to primary sources
Observed: "external_hrefs: facebook.com, instagram.com, twitter.com, pinterest.com, itunes.apple.com, play.google.com"
Expected: Outbound links resolve and point to authoritative, primary sources.
Recommendation: No action needed unless FAQ answers are expanded to cite external authorities (e.g. courier-partner or payment-provider policy pages), in which case link to them directly.
Location: footer social/app icons
Trust and expertise
- Fail Visible author byline + credential above the fold
Observed: "no author byline found"
Expected: An author byline is present and links to an author bio page.
How to verify: Re-run the audit: SR-EAT-01 reads pass
- Fail E-E-A-T verdict roll-up (Trust/Expertise/Authority/Experience)
Observed: "canonical:null; jsonld:[]; author:null; dates all null; faq_visible:false; 6,176 referring domains sitewide (dataforseo)"
Expected: A banded Trust 30 / Expertise 25 / Authority 25 / Experience 20 roll-up, honestly labeled a quality concept.
Recommendation: Render the actual FAQ answers server-side (not just category labels), add FAQPage schema, show a last-updated date, and attribute the page to the support/editorial team to lift the Expertise and Experience bands.
Location: whole-page roll-up
How to verify: Re-run the audit: SR-EAT-06 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.
Not measured this run (2)
- N/A Affiliate/commercial disclosure above the fold
Observed: "internal_hrefs include "/about-us/our-story", "/terms-and-conditions", "/privacy-policy-and-disclaimer"; no affiliate/sponsorship language present"
Expected: Affiliate or commercial relationships are disclosed above the fold.
Recommendation: No action needed.
Location: n/a
- N/A No regulatory superlatives on regulated topics
Observed: "Page covers order/delivery/payment FAQs for a fashion retailer; run flagged YMYL: no."
Expected: No "best/guaranteed" language on regulated finance/health topics; required disclosures present.
Recommendation: No action needed.
Location: n/a
Freshness
- Fail Freshness-sensitive (QDF) topics are genuinely recent
Observed: "No publish date, 'last updated' stamp, or any temporal marker appears anywhere in main_text."
Expected: Evergreen topic still needs an honest, visible date of publication/update.
Recommendation: Add a visible 'Last updated' date to the article content.
Location: main_text overall
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
- Warn No outdated statistics on a dynamic topic
Observed: "'4.7M People like this 1M People like this' and '15 Days Return Policy* Cash On Delivery*' are stated as current facts with no as-of date."
Expected: Statistics/policy claims on a page should be dated so they can be fact-checked as current.
Recommendation: Timestamp the return-policy and social-proof figures, and set a review cadence to refresh them.
Location: policy/social block of main_text
How to verify: Re-run the audit: SR-FR-03 reads pass
Performance
Not measured this run (8)
- Needs data LCP < 2.5s, CLS < 0.1, INP < 200ms at p75
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: LCP, CLS and INP each meet the Core Web Vitals "good" threshold at p75.
- Needs data All-three-Poor veto: LCP, CLS, INP all Poor
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: Not all three Core Web Vitals rate Poor at once.
- Needs data TTFB <= 800ms, FCP <= 1.8s
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: TTFB is 800ms or under (warn to 1,800ms); FCP is 1.8s or under.
- Needs data First 3 images not lazy-loaded, LCP image preloaded
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: The hero/LCP image is not lazy-loaded and is preloaded with high fetch priority.
- Needs data Render-blocking budget: no sync head scripts, controlled weight
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: No synchronous head scripts; page weight and request count stay within budget.
- Needs data Font strategy and deferred third-party scripts
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: font-display:swap, primary font preloaded, at most 6 font files; third-party scripts deferred.
- Needs data Mobile: viewport meta, tap targets, font size, parity
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: A viewport meta tag is present and mobile usability audits pass.
- Needs data Delivery hygiene: compression, HTTP/2+, cache-control, preconnect
Observed: "no performance service connected; run PageSpeed Insights by hand"
Expected: Responses are compressed, served over HTTP/2+, with cache-control and preconnect hints.
AI answers
- Fail Answer-first sections, question-shaped H2s, key-takeaway box
Observed: "no H2 headings found"
Expected: At least half of H2 headings are question-shaped.
How to verify: Re-run the audit: AI-EXT-04 reads pass
- Fail Each passage stands alone
Observed: "main_text is one long run-on of nav labels, FAQ question stubs (no answers shown), and category link names ('Men's T-Shirts Men's Hoodies & Sweatshirts ...'). There are no self-contained passages that answer an implied question on their own."
Expected: Each passage answers its implied question without needing the paragraphs before it.
Recommendation: Write self-contained answer paragraphs (e.g. 'What is online fashion shopping for men and women? ... [complete answer]') that don't depend on surrounding nav.
Location: main content body
How to verify: Re-run the audit: AI-EXT-01 reads pass
- Fail Entity context retained in each passage
Observed: "The extracted content never uses the entity name in a descriptive sentence; 'Bewakoof' appears once only inside the phrase 'My Bewakoof® Wallet' (an account-menu label), not as a grounded subject."
Expected: The named subject appears in the passage itself, not just 'it'/'this'.
Recommendation: Ensure any new answer passages explicitly name 'Bewakoof' as the subject each time, not pronouns.
Location: main content body
How to verify: Re-run the audit: AI-EXT-02 reads pass
Not measured this run (1)
- N/A Attribution survives inside the passage
Observed: "No sourced/attributed claims exist anywhere in the crawled content (see AI-GATE-02), so there is nothing for attribution to survive inside a passage."
Expected: A sourced claim carries its source inside the same passage.
Recommendation: Re-check this gate once attributed claims are added under AI-GATE-02, ensuring the source stays in the same passage as the claim.
Location: main content body
AI citations
- Fail Claims attributable: inline sources on load-bearing facts
Observed: "The crawled main_text is entirely site chrome — nav menu, FAQ headings without answers, footer links, and category link lists. There are zero attributed factual claims and no outbound citation links anywhere in the extracted content."
Expected: At least one attributed claim per 500 words, with real outbound links, on load-bearing facts.
Recommendation: Add a genuine descriptive/editorial section (e.g. 'About Bewakoof' or a buying-guide block) with concrete, attributed facts and real outbound links, not just category navigation.
Location: main content body
Before: MEN WOMEN ACCESSORIES | LOGIN ... Frequently Asked Questions! Orders, Delivery & Payments ...
After: Bewakoof is an Indian D2C fashion brand founded in 2012, serving 4.7M+ social followers (source: Bewakoof company page, linked) with graphic tees, hoodies, and dresses for men and women.How to verify: Re-run the audit: AI-GATE-02 reads pass
- Fail Entity-dense: claims pinned to named things
Observed: "h1 array is empty (no H1 element detected), and first_100_words is navigation/FAQ chrome ('MEN WOMEN ACCESSORIES | LOGIN ... Frequently Asked Questions!') that never states the primary entity descriptively. The title tag does name the entity ('Bewakoof.com') and topic."
Expected: The primary entity is salient in the title, H1 and first paragraph.
Recommendation: Add a visible H1 that names the entity and topic, and open the visible content with a sentence stating what Bewakoof is and does, before the nav/FAQ content.
Location: page head/H1
Before: h1: []
After: <h1>Online Fashion Shopping for Men & Women | Bewakoof.com</h1><p>Bewakoof.com is an online fashion store selling men's and women's clothing, footwear, and accessories across India.</p>How to verify: Re-run the audit: AI-GATE-03 reads pass
- Fail Corroborated on an independent trusted domain
Observed: "The page has no load-bearing claims to corroborate, and in the citability sample bewakoof.com does not appear among the domains either engine drew on (query 1 domains: shopclues.com, gatamagazine.com, demonssouls.wikidot.com; query 2 domains: easily61.blogspot.com, steelworld.com.ph, sprayonyx.com, besttool85.blogspot.com, demonssouls.wikidot.com, keywords84.blogspot.com)."
Expected: Load-bearing claims are corroborated on at least one independent trusted domain.
Recommendation: Once AI-GATE-02 content exists, seek independent coverage (press, review sites, marketplaces) that restates the same facts so engines see corroboration beyond bewakoof.com itself.
Location: off-page / citability sample
How to verify: Re-run the audit: AI-GATE-06 reads pass
- Fail Key facts as semantic triples, consistent naming
Observed: "Content is category-label fragments ('Men's T-Shirts Men's Hoodies & Sweatshirts Oversized T-Shirts for Men ...') with no verb-bearing sentences, so no facts read as [subject][verb][object]."
Expected: Key facts read as [subject] [verb] [object]; each entity is named consistently.
Recommendation: Convert category lists into fact sentences, e.g. 'Bewakoof sells men's hoodies, joggers, and oversized T-shirts starting at ₹499.'
Location: main content body
Before: Men's T-Shirts Men's Hoodies & Sweatshirts Oversized T-Shirts for Men Men's Long Sleeve T-shirts
After: Bewakoof sells men's T-shirts, hoodies, sweatshirts, and oversized T-shirts, and ships them across India within 5-7 days.How to verify: Re-run the audit: AI-ENT-02 reads pass
- Fail Information gain: a sourced specific the consensus lacks
Observed: "Entire page is nav labels, FAQ question titles without answers, a corporate address, and footer links — no data point, no named example, no expert quote, no original figure anywhere."
Expected: Commercial/high-competition query should reach information-gain L3+ (aggregated original data with sample size and date range).
Recommendation: Build real article content and add an original data point: e.g., aggregate the site's own order data ('of N orders placed Aug–Sep 2026, X% were men's vs Y% women's categories, top 3 return reasons were...') with sample size and date range, plus one attributed expert (stylist/merchandiser) quote (L2.5) woven into buying-guide sections.
Location: main_text overall
Before: Men's T-Shirts Men's Hoodies & Sweatshirts Oversized T-Shirts for Men...
After: Of 4,200 men's orders placed on the site between June and August 2026, oversized tees accounted for 38% of units sold — up from 24% a year earlier, per internal sales data.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: "The page names roughly 20 distinct entities (Bewakoof, Marvel, Disney, Avengers, Star Wars, Batman, Superman, Joker, Apple, Realme, Samsung, Xiaomi, OnePlus, Vivo, Oppo, Poco, Maharashtra, India, Thane, Bhiwandi) across ~500 words of scraped text, but almost all appear as bare category/franchise tags, not in sentences, and the primary entity 'Bewakoof' is not salient in the opening content."
Expected: Enough distinct named entities per 100 words to ground the page; primary entity salient early.
Recommendation: Move key entities (Bewakoof, India, product categories) into descriptive sentences near the top of the page, not just link labels.
Location: main content body
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: "The crawled content contains no fabricated statistics, no unverifiable superlatives, and no YMYL claims; the title itself is neutrally descriptive rather than using banned superlatives like 'best' or '#1'."
Expected: Verifiable, credentialed, compliant; no wrong YMYL figures, no fabrication, no banned superlatives.
Recommendation: Keep any new claims added under AI-GATE-02 verifiable and free of unsupported superlatives.
Location: main content body
Not measured this run (9)
- Needs data Knowledge-graph presence
Observed: "No knowledge-base entry, encyclopedia article, or knowledge-panel data was provided in the crawl or sample for the Bewakoof entity."
Expected: The entity has a knowledge-base entry, an encyclopedia article, or a confirmed knowledge panel.
Recommendation: Manually verify presence of a Wikipedia/Wikidata entry or Google knowledge panel for the Bewakoof brand.
Location: manual check — not in provided data
- N/A Every statistic/quotation attributes to a named source
Observed: "No statistics or quotations appear anywhere in the crawled title, headings, or main_text — the content is navigation, FAQ labels, and category links only."
Expected: Every statistic or quotation names a source, credential and org on one line.
Recommendation: If adding social-proof numbers (e.g. follower counts), attribute them to a dated, named source line.
Location: main content body
- N/A No fabricated or unverifiable statistic or quote
Observed: "No statistics or quotes are present in the crawled content, so none can be assessed as fabricated or unverifiable."
Expected: No statistic or quote is fabricated or unverifiable on a claim-making page.
Recommendation: Ensure any future added statistics are independently verifiable.
Location: main content body
- N/A Authoritative declarative tone, with the YMYL hedging exception
Observed: "The extracted content has no declarative prose to assess tone against — it is link/label fragments ('CUSTOMER SERVICE Contact Us Track Order Return Order Cancel Order')."
Expected: Tone is declarative; a YMYL page hedges with 'as of [date]' rather than vague hedging (not applicable — YMYL: no).
Recommendation: Write new sections in a direct, declarative style once added.
Location: main content body
- Needs data Per-engine backend presence and crawler access
Observed: "The citability sample covers only the two target questions against one retrieval context each (domains cited suggest a single search-grounded engine); bewakoof.com did not appear in either answer's domain list. Of the seven target engines (chatgpt, copilot, perplexity, ai_overviews, ai_mode, gemini, claude), only one appears represented in the sample and it is not explicitly labeled."
Expected: The page is present in each target engine's retrieval backend, reported per engine.
Recommendation: Run the same two target questions through chatgpt, copilot, ai_overviews, ai_mode, gemini, and claude individually and log domain citations per engine.
Location: manual check — not in provided data
- N/A Training-only blocks presented as a documented trade-off
Observed: "Auto findings show no blocked crawlers at all (AI-BOT-01 pass, AI-BOT-03 pass, retired anthropic-ai token removed) — no training-only block exists to document."
Expected: Any training-only crawler block is a stated trade-off, never described as hurting rankings.
Recommendation: If a training-only block (e.g. GPTBot for training) is ever added, document it internally as a deliberate trade-off, separate from retrieval/citation bots.
Location: robots.txt
- Needs data llms.txt and IndexNow carry low/zero weight, never a gate
Observed: "No llms.txt or IndexNow signal was reported in the data provided."
Expected: llms.txt/IndexNow presence is noted informationally, never scored as a gate.
Recommendation: Optionally check for llms.txt/IndexNow presence for completeness; do not treat as a gate.
Location: manual check — not in provided data
- Needs data Knowledge-graph footprint (web search sample)
Observed: "No web-search sample for the Bewakoof brand entity (Wikipedia/Wikidata/knowledge panel) was provided."
Expected: A knowledge-base entry, encyclopedia path, or consistent cross-platform presence exists.
Recommendation: Run a manual web-search sample for 'Bewakoof' to check for a knowledge panel or Wikipedia/Wikidata entry.
Location: manual check — not in provided data
- Needs data Brand-mention sample on AI-visibility-correlated platforms
Observed: "No data on forum, video, news, or professional-network mentions of Bewakoof was provided."
Expected: Earned brand mentions appear on forums, video, news or professional networks.
Recommendation: Manually sample Reddit, YouTube, news, and LinkedIn for organic Bewakoof mentions.
Location: manual check — not in provided data
Programmatic pages
Not measured this run (3)
- N/A Every page carries genuinely unique data
Observed: "PAGE TYPE: article (inferred); no evidence in the data that this page is one of a templated programmatic set."
Expected: The data on the page is the value; it's not an interchangeable template shell.
Recommendation: No action needed unless this page is confirmed to be one of a templated set.
Location: n/a
- N/A No two pages share >80% of their field content
Observed: "PAGE TYPE: article (inferred); no cross-page template data provided."
Expected: Cross-page field-content similarity stays under 80%.
Recommendation: No action needed unless this page is confirmed to be one of a templated set.
Location: n/a
- N/A Scale governance: review at 100+, justification at 500+
Observed: "PAGE TYPE: article (inferred); no evidence of a templated rollout scale to govern."
Expected: Templated rollouts past 100 pages have had human review; past 500 have documented justification.
Recommendation: No action needed unless this page is confirmed to be one of a templated set.
Location: n/a
Data validation
What this is: Every factual claim on the page that was checked against a source.
How to read it: Verdict is the check's status; a needs-human-verification chip means the model could not settle it alone.
Your action: No claims need manual verification.
| Claim | Verdict | Recommendation |
|---|---|---|
| 15 Days Return Policy | Warn | Add a source or remove the claim |
| 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 |
Content gaps
What this is: Topics this page should add, expand or cut, plus where it sits on the information-gain ladder.
How to read it: Each line is one gap and the rule that flagged it.
Your action: Close the 7 gaps listed below
- Cut: Raw nav/footer/category link dump currently standing in for article body (menu labels, corporate address, download-app prompts)
- Add: A direct-answer opening paragraph addressing 'online fashion shopping for men and women' before any other content
- Add: Editorial sections explaining shopping categories, sizing/fit guidance, and how to compare platforms (comparison + discovery journey stages), matching the buying-guide/listicle format competitors use
- Add: Actual answer text for the listed FAQ questions (e.g., 'How do I check the status of my order?') instead of bare question titles (troubleshooting stage)
- Add: Validation content: real customer reviews/ratings or an attributed expert (stylist) quote, and dated trust signals (return policy, security) instead of bare undated badges
- Add: One aggregated, dated original data point (internal order/survey data, sample size + date range) to clear the L3 information-gain gate
- Add: Visible 'last updated' date on the article
Information gain: Below L0 — the audited page has no editorial content at all: no H1/H2/H3, no prose paragraphs. It is scraped site chrome (nav menu, FAQ question titles with no answers, footer address, undated follower counts) for a fashion retailer. There is no consensus-level explanation, no example, no data, and no answer to 'online fashion shopping men women' present anywhere. to Commercial, high-competition query — target L3: add at least one aggregated, dated original data point (e.g., internal order/checkout data: 'of Sept 2026 orders (n≥X), Y% men's vs Z% women's category split, top return reasons...' or a shopper survey with n≥100 on sizing/fit pain points), plus one attributed L2.5 expert quote (stylist/merchandiser), inside real prose covering category guidance, sizing/fit, comparison of shopping options, and validation/trust content — replacing the current nav/link dump entirely. Note: one comparison-set competitor (a Demon's Souls wiki armor page) is topically unrelated and should be treated as SERP noise, not a content target.
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 39 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 | Start of main text (no H1 present) | 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 | Page <head> / JSON LD | See finding | Re-run the audit: SR-SCH-02 reads pass |
| High | Add internal link | FAQ answer body (currently unrendered, faq visible:false) | 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 category list, main content area | See finding | Re-run the audit: SR-ONP-04 reads pass |
| High | Fix | Whole page roll up | See finding | Re-run the audit: SR-EAT-06 reads pass |
| High | Fix | Main content body | See finding | Re-run the audit: AI-GATE-02 reads pass |
| High | Fix | Page head/H1 | See finding | Re-run the audit: AI-GATE-03 reads pass |
| High | Fix | Main content body | See finding | Re-run the audit: AI-EXT-01 reads pass |
| High | Fix | Main content body | See finding | Re-run the audit: AI-EXT-02 reads pass |
| High | Rewrite section | Footer block of main text | 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 |
| Medium | Fix | Final URL query parameter + missing canonical tag | See finding | Re-run the audit: SR-CR-06 reads pass |
| High | Rewrite section | Category list section of main text | See finding | Re-run the audit: SR-CNT-06 reads pass |
| High | Fix | Main text overall | 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 content body | See finding | Re-run the audit: AI-ENT-02 reads pass |
| Medium | Fix | Main text overall | See finding | Re-run the audit: SR-FR-02 reads pass |
| Medium | Fix | Off page / citability sample | See finding | Re-run the audit: AI-GATE-06 reads pass |
| Medium | Rewrite section | Main text overall | See finding | Re-run the audit: SR-CNT-04 reads pass |
| Medium | Rewrite section | Social block of main text | 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 | 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 | Main content body | See finding | Re-run the audit: AI-ENT-01 reads pass |
| Medium | Fix stat | Footer, left column before DOWNLOAD THE APP | See finding | Re-run the audit: data-fc-1 reads pass |
| Medium | Fix | Policy/social block of main text | See finding | Re-run the audit: SR-FR-03 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 | Footer, CONNECT WITH US section | See finding | Re-run the audit: data-fc-2 reads pass |
| Medium | Fix stat | Footer, CONNECT WITH US section | See finding | Re-run the audit: data-fc-3 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
- Entity floor + salience
- Key facts as semantic triples, consistent naming
- Direct answer up top (BLUF)
- Not thin/padded, density over length
- Readability in the audience band
- Varied sentence rhythm (burstiness)
- Fact-density adequate on claim-making pages
- Freshness-sensitive (QDF) topics are genuinely recent
- No outdated statistics on a dynamic topic
- 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
- No crawl traps: session-ID or internal-search links, unmanaged parameters
- 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
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.